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
I confirm this issue is not an exploit. (Required)
BYOND Version
n/a
Issue Description
There is a missing fire alarm in the Kerberos medbay main hall. Whenever an atmos or fire alarm is triggered, the firelocks pictured below will be permanently engaged unless a fire alarm is constructed to deactivate them.
What did you expect to happen?
To be able to turn the alarms off.
What happened instead?
The firelocks are permanently engaged, making movement through medbay difficult, especially during emergencies.
Why is this bad/What are the consequences?
It inhibits movement in medbay, requiring you to carry a crowbar or manually pass through each firelock. This is bad and hinders medbay considerably.
Steps to reproduce the issue.
Trigger an atmos alert or fire alert that affects the main medbay hall.
Woe, the firelocks are engaged forever.
(Optional) build a fire alarm to turn the fucking thing off.
When did the problem start happening?
Since Kerberos medbay was remapped.
Extra information
No response
Relevant log output/runtime error
The text was updated successfully, but these errors were encountered:
Exploit Reports
BYOND Version
n/a
Issue Description
There is a missing fire alarm in the Kerberos medbay main hall. Whenever an atmos or fire alarm is triggered, the firelocks pictured below will be permanently engaged unless a fire alarm is constructed to deactivate them.
What did you expect to happen?
To be able to turn the alarms off.
What happened instead?
The firelocks are permanently engaged, making movement through medbay difficult, especially during emergencies.
Why is this bad/What are the consequences?
It inhibits movement in medbay, requiring you to carry a crowbar or manually pass through each firelock. This is bad and hinders medbay considerably.
Steps to reproduce the issue.
When did the problem start happening?
Since Kerberos medbay was remapped.
Extra information
No response
Relevant log output/runtime error
The text was updated successfully, but these errors were encountered: