SierraKomodo Posted March 10, 2017 Posted March 10, 2017 After we had a round where mercs cancelled a CT vote and the mods determined it valid because mechanics allow it, and considering previous rounds where malf AIs have gotten in trouble for cancelling a CT vote, I think there needs to be something actually set in stone regarding cancelling a voted crew transfer and when or if it's acceptable.
Scheveningen Posted March 10, 2017 Posted March 10, 2017 For the record it wasn't considered valid. There was a brief discussion in msay where everyone but myself thought it wasn't fair. The merc who again recalled the shuttle was spoken to. and considering previous rounds where malf AIs have gotten in trouble for cancelling a CT vote I've played rampant AI several times where I cancelled both shuttle types without requiring permission from an administrator or moderator, or even having to be spoken to about it. If this is recent policy because people whined enough and can't get over the differing game mechanics each antagonist type has, in combination with the fact that it makes more sense for a malf AI to interrupt crew transfer procedures than it does for anyone else... then it's pretty dumb in my opinion. There is no need for staff to be shoehorned into the role of babysitting the round any more than it already does. Longer rounds are a good thing, it permits people who are still invested to continue the round to keep playing. If nobody else likes it they can cryo and observe instead of being a poor sport and wanting to transfer at the 2hr mark because they didn't get a chance to be an antagonist or they don't want to keep playing and must absolutely restart the round. These kinds of attitudes suck the fun out of SS13. To my understanding, though, this is going to be fixed code-wise rather than ratified as a singular arbitrary guideline.
SierraKomodo Posted March 10, 2017 Author Posted March 10, 2017 For the record it wasn't considered valid. There was a brief discussion in msay where everyone but myself thought it wasn't fair. The merc who again recalled the shuttle was spoken to. and considering previous rounds where malf AIs have gotten in trouble for cancelling a CT vote I've played rampant AI several times where I cancelled both shuttle types without requiring permission from an administrator or moderator, or even having to be spoken to about it. If this is recent policy because people whined enough and can't get over the differing game mechanics each antagonist type has, in combination with the fact that it makes more sense for a malf AI to interrupt crew transfer procedures than it does for anyone else... then it's pretty dumb in my opinion. There is no need for staff to be shoehorned into the role of babysitting the round any more than it already does. Longer rounds are a good thing, it permits people who are still invested to continue the round to keep playing. If nobody else likes it they can cryo and observe instead of being a poor sport and wanting to transfer at the 2hr mark because they didn't get a chance to be an antagonist or they don't want to keep playing and must absolutely restart the round. These kinds of attitudes suck the fun out of SS13. To my understanding, though, this is going to be fixed code-wise rather than ratified as a singular arbitrary guideline. On a counter point. Between 2 and 3 hours, in order for a CT vote to pass, you need a 2/3 majority voting to end the round. That would mean that, if a CT passes, only a 1/3 minority actually wants to continue with that round and the remaining players want it to end for whatever reason. A minority (Or in this case, a single person who has the power to hit that button) extending a round that a majority voted to end simply because they're having fun, without considering if everyone else is enjoying the round can also be considered being a poor sport.
Scheveningen Posted March 10, 2017 Posted March 10, 2017 That'd be a good point, but: It's already been part of the existing game mechanics to be able to do for a long time now. How's it suddenly poor sportsmanship out of the blue, and what mandated this invisible policy change that hasn't been mentioned once on the forums prior to this thread? In addition, the CT vote that went last round was an exact 2:1 draw ruling where RNG decided to transfer. Not quite over 2/3rd majority. But there was a significant amount of people who still wanted to stay. Let's take into account observers and people who died. CT shouldn't be treated as a "I ded restart" button, yet for most it is. I've a general idea on how to amend the latter detail but it's for another time. Code will likely be written in the near future completely disabling recalling CTs sans an admin/malf AI being able to do it. I will not support a rule being written in banning malf AIs from recalling the shuttle as is their right to do so in their mechanical abilities, because otherwise, why is it even coded in? Pun not intended. It's also unproductive and even more of a hassle to have to require staff to further add unnecessary crutches to organic antagonist play. Calling the shuttle super early for no good reason is one thing. Recalling it as an antagonist AI, specifically, returns the crew's attention at recognizing something going on with station systems and they need to resolve it before they can even consider leaving.
SierraKomodo Posted March 10, 2017 Author Posted March 10, 2017 This has actually come up many times in the past as in issue that's been ahelped and handled situationally in the past, ever since it first became something you could actually do mechanically. The mechanics for this being something a player could do manually didn't exist until the first baymerge several months ago - Before that, it only happened automatically during malf rounds. I presume it never came to the forums because most people seem to only want to bring it up in ahelps, deadsay, and OOC - I made this thread because it was being dragged out with no progress and no input from admins in OOC. My main intent here is to just get a final ruling from admins on whether or not this is allowed, when it's allowed, etc, so that the community has a basis/precedence to go off outside of 'Well admin A said its fine a week ago, but admin B said it's bad two weeks ago'.
Shadow Posted March 10, 2017 Posted March 10, 2017 We will give a definite answer within the next 24 hours.
Shadow Posted March 11, 2017 Posted March 11, 2017 A new rule will be added today: Recalling a CT shuttle is not allowed as antag unless you get permission from staff first.
sonicgotnuked Posted March 11, 2017 Posted March 11, 2017 I think canceling CT can be fine IF you are not being a stealth shit and actually causing fear within the station. You should be BWOINKED if you just recall it to continue being a stealth AI.
SierraKomodo Posted March 11, 2017 Author Posted March 11, 2017 I think canceling CT can be fine IF you are not being a stealth shit and actually causing fear within the station. You should be BWOINKED if you just recall it to continue being a stealth AI. Recalling a CT shuttle is not allowed as antag unless you get permission from staff first. I think this ruling pretty much covers that.
UnknownMurder Posted March 11, 2017 Posted March 11, 2017 I usually always ask moderators/admins for permission to turn down the crew transfer votes to continue the round and attempt to make the round turn for the better. I guess I was doing the right thing before the ruling was declared.
Arrow768 Posted March 11, 2017 Posted March 11, 2017 The ruling has been provided. Archiving the Suggestion.
Recommended Posts