Flight Consoles Control Tweak

[Sarah_U.]

Summary (a quick, 2-3 sentence summary):
Simply put, add the name of the last person that executed any 'flight-action' on the consoles of the dropship and Vindicator.
Furthermore, possibly let all people with command access lock the shutter controls.

Benefits (How this will benefit the server and game as a whole):
This'll allow more control and possibly more sanctions toward the usage of the dropship and pod. Often I see it being sent without any authorizations which leads to various issues later-on.
Furthermore, on a military ship you SHOULD have prevention-measures like this to make sure everything goes well.

Details (Description of how you think this would work, the benefits, etc):
The first sentence (log) is self-explanatory. If someone press the button their ID is recorded in the system and shows up on the interface everywhere linked to the ship they manipulated.

For the second sentence (restriction) any player with a proper ID can step forth and lock the shutters from any non-command role somehow. I'm not entirely sure if it's possible since I didn't program in Byond / Map in byond yet, but if it's not possible then discard it from the main suggestion and only concider the first.
This method could let engineers and aliens break the shutters so it'd be great early-round when the pod or shuttle isn't entirely broken up, but later it'll be entirely up to the efficiency of the command staff if marines board illegally or not.

Implementation (Optional, if you have an idea how to implement it):
Your name is updated on the interface when you press the button to move the shuttle/pod.

[RadiantFlash]

I like the idea of this, except for one thing. retricting it to XO and CO, is a bit of a problem. There are rounds where our XO and CO are, either wounded, dead, or SSD, and BO's can't upgrade their access per server rules. So, Theres a chance of it just getting locked up for a quite a while until someone can get the XO or CO's ID. This also tends to happen with evac calls and distress signals.
Maybe if you gave it access to the BO's, as well it wouldn't be an issue.

[Sarah_U.]

Ah, thanks for reminding me of that, updating with the following:
If a CO / XO trigger the SSD / Cryo-sleep trigger the value is set to ZERO.

[KingKire]

+1/-1:
+1 for adding a small "last used person" text to the console so everyone can know who launched the ship that killed 15 marines planetside.
-1 for locking the console: The only people who have access to the console are already in trusted leadership positions. If you cant trust them to launch the dropships, why even give them bridge access. Also, the SSD effect takes usually 5-10 minutes to kick in. Put in overworked/dead command staff and you soon find yourself trying to find anyone whos still around that can launch those ships to or from the SULACO before everyone on the planet is killed.

[Sarah_U.]

Hm... I see what you people get to.
I'll change the following then:

---

Previous:

► Show Spoiler

#1: Furthermore, possibly let the XO & CO restrict access to the consoles.

#2: For the second sentence (restriction) any player with XO / CO ID could step forth and lock the console in a way or another.
Personally I believe that making it lock the console via the interface is the best way- EITHER WAY. The CO/XO could lock the console, and on doing so disable anyone from using it untill they unlock it.
If the queen access the console, it unlocks itself and can be accessed by anyone as if she unlocked it with the ID.

NOTE: If both the XO and CO goes SSD or in cryo-sleep the console is unlocked.

#3: Use the queen touching the console trigger to force the value of the lock to ZERO (Considering you'd use a BOOL), using the ID trigger an action that toggle the value from ZERO and ONE and finally touching the button to send / recall it store your name in the interface for anyone to see it.
EDIT: If a CO / XO trigger the SSD / Cryo-sleep trigger the value is set to ZERO after a check to see if the other role is actually active or not.

---

New:
#1: Furthermore, possibly let all people with command access lock the shutter controls.

#2: For the second sentence (restriction) any player with a proper ID can step forth and lock the shutters from any non-command role somehow. I'm not entirely sure if it's possible since I didn't program in Byond / Map in byond yet, but if it's not possible then discard it from the main suggestion and only concider the first.
This method could let engineers and aliens break the shutters so it'd be great early-round when the pod or shuttle isn't entirely broken up, but later it'll be entirely up to the efficiency of the command staff if marines board illegally or not.

#3: Your name is updated on the interface when you press the button to move the shuttle/pod.

[KingKire]

i want to rebump this. having people see the last person who had launched the shuttle would really help clear up command mishaps and confusion. If you want in-lore reasons, the marine in question needs to have his ID scanned to show that he is authorized to use the console, which allows the computer to log that name into the system.

as for coding wise, i would just have it place the name of the last person who successfully launched the ship be displayed under or over the launch ship button.

If its the queen, just have it display garbled code or error code. would be a nice touch.

[Fritigern]

+1 Another quality of life change for the shuttle, one of many piling up (like the clock suggestion for landings and such).

While you're in there tinkering with the code for this one, please also make the shuttle console act as a wall radio tuned to the command channel. Having marines trapped on a shuttle, unable to move it and desperately trying to get a retarded commanders attention would be a lot less frustrating if a marine could walk to the front of the ship and scream into the mic about how everyone is slowly being eaten alive.

[Snypehunter007]

Old. No support.

Locking.