Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fixes Warrior Pulls continuously breaking after lunging a M56D/M2C us…
…er from front (#5151) # About the pull request <!-- Remove this text and explain what the purpose of your PR is. Mention if you have tested your changes. If you changed a map, make sure you used the mapmerge tool. If this is an Issue Correction, you can type "Fixes Issue #169420" to link the PR to the corresponding Issue number #169420. Remember: something that is self-evident to you might not be to others. Explain your rationale fully, even if you feel it goes without saying. --> So that one took a lot of debugging... To keep it as short as possible, when you lunge a M56D/M2C user from front as Warrior, they get stunned. The stun cancels their HMG interaction, causing them to step away. This means they leave the grab range, breaking it. Warrior code incorrectly re-sets pulledby, resulting in a mob "pulledby" one that doesn't pull it. In practice once this happens, this means that the "incorrectly" pulled mob will reset any active grabs from the Warrior when it moves. Negating the use of lunges completely. # Changelog :cl: Firartix, Birdtalon fix: Fixed a logic error in Warrior code causing lunging some M2C/M56D users to semi-permanently brick lunge. /:cl: --------- Co-authored-by: BeagleGaming1 <[email protected]>
- Loading branch information