You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Warrior lunged me, pulled me back, hugger hugged me, warrior continued dragging me, and then decapitated me.
What's the difference with what should have happened?
Xenos are supposed to not be able to do this sort of stuff to caps, queen is mechanically locked from gibbing infecteds for this reason. It doesn't make sense that warrior should be able to bypass it.
How do we reproduce this bug?
Warrior Lunge.
Still maintaining the lunge, have hugger grab onto victim.
Proceed to tear their head off after the hugger pops off.
Issue Bingo
Issue could be reproduced at least once
Issue happened in a recent (less than 7 days ago) round
…HOST
# About the pull request
Fixes#4977
Refactors Warrior ripping procs to warrior class and adds a further
check for XENO_HOST after do_after to account for delay between hugger
jumping on and emplanting embryo.
# Explain why it's good for the game
Consistency with other anti host killing mechanics.
# Testing Photographs and Procedure
<details>
<summary>Screenshots & Videos</summary>
Put screenshots and videos here with an empty line between the
screenshots and the `<details>` tags.
</details>
# Changelog
:cl:
fix: Warriors can no longer behead caps if they start limb ripping
before embryo is inserted.
code: Refactors warrior limb proc to the warrior class.
/:cl:
Testmerges
#4793, #4866, #4915, #4934, #4960
Round ID
19600
Description of the bug
Warrior lunged me, pulled me back, hugger hugged me, warrior continued dragging me, and then decapitated me.
What's the difference with what should have happened?
Xenos are supposed to not be able to do this sort of stuff to caps, queen is mechanically locked from gibbing infecteds for this reason. It doesn't make sense that warrior should be able to bypass it.
How do we reproduce this bug?
Issue Bingo
The text was updated successfully, but these errors were encountered: