Jump to content

The issues with command and comms consoles


Recommended Posts

Note this suggestion does not bring up issues about CT shuttles as that is covered by a rule we're supposed to enforce. Emergency shuttles are not covered by that rule.


1.) As of now, anyone with access to an emag and a command and comms board can spam recall emergency shuttles with impunity. It's extremely hard to hunt down said consoles without any initial indication where.

2.) This also (probably, not sure if this was fixed in the modular laptop update) applies to laptops with command and comms modules.


Solutions:


1.) Print out general area locations whenever a shuttle is called/recalled to provide consequence for these sorts of behaviors. Game-design and IC-sense wise, it is probably for the best. This permits the crew to investigate and doesn't make an antagonist with a recall shuttle function completely invisible and untrackable to any degree of counterplay.

2.) Remove the ability for command laptops to call/recall a shuttle, if this does not already exist. Whether it's a matter of theft or a head of staff accidentally abandoning their laptop in an open place, it's not good practice to allow laptops to have the penultimate Key-To-The-Castle functions such as being able to call a shuttle or recall it.

Link to comment

The issue here I don't think is so much that the consoles need to be fixed so much as that shuttle calls and recalls are something that has entirely been relegated to staff moderation at this time. You can recall and call shuttles endlessly with no problem simply because no one has yet coded in a 'stopping point' or even a cooldown period. This should be addressed before we start removing access to the command or telling where someone is recalling the shuttle from.

Link to comment

The issue here I don't think is so much that the consoles need to be fixed so much as that shuttle calls and recalls are something that has entirely been relegated to staff moderation at this time. You can recall and call shuttles endlessly with no problem simply because no one has yet coded in a 'stopping point' or even a cooldown period. This should be addressed before we start removing access to the command or telling where someone is recalling the shuttle from.

 

Something like a five minute cooldown between calling the emergency shuttle could work.

Link to comment
  • 5 months later...
×
×
  • Create New...