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

Engineering Reworks: Airlock Reprogramming #1757

Open
3 tasks
VMSolidus opened this issue Feb 10, 2025 · 1 comment
Open
3 tasks

Engineering Reworks: Airlock Reprogramming #1757

VMSolidus opened this issue Feb 10, 2025 · 1 comment
Labels
Type: Feature Creation of or significant changes to a feature

Comments

@VMSolidus
Copy link
Member

Description

Engineers currently don't have any real method of fixing Security airlocks if for instance, a Greytide Virus sweeps through and emags all the doors. In SS13, you could program airlocks to have accesses that you yourself don't have, but you could only remove accesses that you have. Also, any engineer could reprogram airlocks, rather than just the Chief Engineer. Engineers need to not be dependent on the CE + Captain giving them all access in order to be able to fix the Armory doors after a traitor emagged them.

To that end, I need the following changes:

  • The Access Configurator tool needs to be available to all engineers. Put it in the engineering lockers. Put it in loadouts. Put it in the engineering vendor. Whatever the case.
  • The access configurator needs to be removed from the HoP locker(Seriously).
  • The access configurator needs to not check your access requirements for ADDING access to an airlock. It only needs to check your access requirements for REMOVING accesses from an airlock.
@VMSolidus VMSolidus added the Type: Feature Creation of or significant changes to a feature label Feb 10, 2025
@VMSolidus
Copy link
Member Author

Image

A brief reading of the code determines that this PR largely lives in the Access Overider System, and that this system is mega fucking hardcoded for "The entire access list must pass", rather than based on individual accesses. So it would require a substantial rewrite. That part of this demand is much harder to do.

On the other hand, a safe and "Small" PR that would still work is moving the access configurators anyway to engineering lockers, since if an engineer is handed a security ID while being watched by the warden, they can still fulfill the requirement of being able to fix the armory doors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Feature Creation of or significant changes to a feature
Projects
None yet
Development

No branches or pull requests

1 participant