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.
The initial frame for the Viper's Rhino/Lunge attack is hardcoded to start the animation at frame 7, giving context that the attack is intended to start at frame 7 and not exceed past the end of the animation. The lunge only occurs when the viper is exactly 2 tiles away from the player. The lunge also does not deal any damage, or cause knockback. This fix consistently stops the viper at the end of the animation length, which by testing has resulted in the desired behavior, where the viper will not stop short of reaching their target, but also will not continuously run into the distance if the target is missed.
Fixes: #7034