Fix possible bug with talkmonster facing during the script #213
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In Half-Life talkmonsters (barneys and scientists) react to player's touch. One of the consequences is the ideal yaw change. It can mess up with scripts since it happens in any monster state.
Example: load c0a0d, wait for transition to c0a0e (if you load c0a0e straight from the console, the barney will be missing). When barney walks to the button try to mess around him during the scripted
intropushanimation. The barney will face at you instead of the button while playing the animation.I'm not actually sure why monster needs to turn to the player in the first place. It's probably left so if the monster failed to walk away from the player's path, it at least would face the player displaying the powerless gaze.
Probably it also shouldn't happen during the combat since monster is busy anyway. So the more correct way to fix it is to check if the interrupt mask of the current schedule includes the bits_COND_CLIENT_PUSH, but I did not want to complicate it.