I thought about it a bit more and have come to conclusion that the shuttle call mechanics would be much more fun if instead of pressing the button "time for the round to end" the crew had to prove that they actually have a serious problem. For example, comms console can have a shuttle call tab with a subcategories of disaster events like: "Blood cult activity", "Nuclear ops', "Xenomorph infestation", "Critical station integrity", "half of the crew dead or incapacitated" "We have already completed our station goals - time for a crew rotation", "hazardous environment (plasma flood, high temperature, low pressure in a large chunk of the station..)" etc. When one of the options selected, lets say - ""Blood cult activity" then CentCom will require a proof sent in via Cargonia shuttle. It can be something like a ritual dagger or other cult item. In a case of xenomorph infestation it can be a benos corpse or organs. Alternatively condom can ask CentCom for a shuttle and admemes will dispatch it manually.OFQ wrote:The problem of premature shuttle calls can be addressed at the broth ends. Making situations that have 99% chance to end in a shuttle call more manageable (unless it's a total disaster like a tesloose or singuloth) but also punishing/preventing questionable shuttle calls by:
1. Removing AI shuttle call and borg ability to red alart. Both because AIs getting really bored at slow/green shift and bait shuttle calls but also because being ASSMOVE kinda makes it so that almost any shitty situation is a good enough reason to call it.
2. If you call shuttle under 30 minutes into the round when the half of the crew still alive + there is no catastrophic event like "IT'S LOOSE!!!" you have to get 2-3 shuttle call conformations from the heads (if there is more than a single head)
3. If should gets called without particular reason admemes (Centcom) should deny it or even demote condom for being a pussy.
At the first glance, it may seems that it will be hard to cover all the cases, but I think the "half of the crew is dead" and "station integrity is below 60%" would do. The more specific cases like "AAA BENOS ON THE STATION" designed to get the shuttle before those thresholds are reached. Besides, you can fake a threat by getting items that CentCom requests from the different sources (could be banable if abused) or actually get the station goals done.
To test this system I propose disabling the shuttle call button on Manuel when there is an active admeme so the shuttle calls will be performed via CentCom communication and admeme will come up with a condition(if any) on the spot. Then the server logs can be analyzed to generate a proper set of disaster categories and gates(requirement) to automate this system.