Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kerberos medbay missing a fire alarm #28060

Open
1 task done
Kholdstare2 opened this issue Jan 22, 2025 · 0 comments · May be fixed by #28061
Open
1 task done

Kerberos medbay missing a fire alarm #28060

Kholdstare2 opened this issue Jan 22, 2025 · 0 comments · May be fixed by #28061

Comments

@Kholdstare2
Copy link

Exploit Reports

  • 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.

Image

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.

  1. Trigger an atmos alert or fire alert that affects the main medbay hall.
  2. Woe, the firelocks are engaged forever.
  3. (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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

Successfully merging a pull request may close this issue.

1 participant