Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document monster movement and visibility functions #652

Merged
merged 2 commits into from
Feb 19, 2024

Conversation

zenzombie
Copy link
Collaborator

No code changes, just some documentation.

Copy link
Owner

@tmewett tmewett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, v useful!

Comment on lines 225 to 226
/// clairvoyance, telepathy, or entrancement. However, the kind may be unknown (e.g. player is
// hallucinating or monster is submerged).
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The kind may be unknown

Hmm, this disagrees with my understanding. Probably applies when hallucinating but in other cases?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The other case is when the monster is submerged and the player is telepathic but not submerged (doesn't matter if hallucinating or not). The player knows a monster is underwater and where it is, but doesn't know what kind it is. Hovering the monster gives the "small/large" psychic emanation message.

Maybe I should update the comment?

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the monster is submerged but player isn't, isn't monsterIsHidden(monst, &player) true, meaning canSeeMonster returns false?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You sir are absolutely correct. I pushed an update. Hope I didn't go overboard.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems you've added more (correct) detail but canSeeMonster is still described as just knowing location and it still says kind may be unknown - which is what I thought we invalidated above ^

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It think we determined that hallucination is the only reason for not knowing the kind. How about this instead? "A monster can be "seen" but its kind unknown due to hallucination."

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pushed an update. Feel free to reword as you see fit.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pushed a change, what do you think?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@tmewett tmewett changed the base branch from master to release February 19, 2024 16:52
@tmewett tmewett merged commit ae8d652 into tmewett:release Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants