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
Burrower can stun the PO from inside the cockpit by burrowing outside the cockpit and therefore denying alamo unlock, preventing the Alamo from taking off during a full alamo-surrounded siege..
What's the difference with what should have happened?
Should allow the unlock.
How do we reproduce this bug?
Burrower burrows up from near cockpit.
Burrower slams his big feet into the ground.
Alamo pilot goes aaaa
Can't fix Alamo.
Attached logs
N/A
Additional details
Author: AnonHault
Admin: SmellyHippie
Note: None
The text was updated successfully, but these errors were encountered:
Not a bug? The way unlocking works is bit by bit, every successful completion of 20 seconds windup removes 20 additional seconds from the lockout (which is temporary in the first place). Tremor CD is 45 seconds. You can interrupt every third windup (if you face no opposition from the marines), but you cannot prevent it completely.
Testmerges
#8442: 'Removes devour, replaces it with haul. #2737 Revival' by casperr04 at commit 385b1c4730
#7645: 'adds poll subsystem, entities and ui' by hry-gh at commit ddd2f66fd9
#8378: 'Yautja Ship - Complete Remake & more...' by Zenith00000 at commit 0cdba4c8ed
#8492: 'chunk tgui topic payloads on 516' by hry-gh at commit f003f713b4
#8181: 'Nerfs playable huggers' by Git-Nivrak at commit 9d320b716f
#8606: 'refactors audio player (by adding a 516 version with nicer code)' by hry-gh at commit c08ed16336
#8632: 'Adds missing OOC icon' by realforest2001 at commit b0966fb613
#7816: 'Hostile Survivor Rework Revival' by BOBAMAx at commit 3cbca27874
Round ID
26653
Description of the bug
Burrower can stun the PO from inside the cockpit by burrowing outside the cockpit and therefore denying alamo unlock, preventing the Alamo from taking off during a full alamo-surrounded siege..
What's the difference with what should have happened?
How do we reproduce this bug?
Attached logs
Additional details
The text was updated successfully, but these errors were encountered: