[BAN] [Ridgyax] Dopamiin
Posted: Tue Jan 16, 2024 4:45 am
BYOND account: Dopamiin
Character name: CASS-E
Ban type: Server
Ban length: 12 hours
Ban reason: Fired an OB as AI (The FC had placed down a laze as a joke in the middle of a marine push) that resulted in the deaths of multiple marines. Light punishment due to having said prior in the round that they would instantly firing on any OB and an overall lack of notes.
Time ban was placed: 2024-01-16 15:25:17
Round ID in which ban was placed: 25228
Your side of the story:
One of the generally more compelling reasons to play AI at all, or have one on the marine team, is their knack for "fast firing" OBs. Most squad leaders and field commanders are extremely grateful to have their OB lases fired extremely quickly, as AIs get a loud audio and visual notification whenever an OB is lased for and can keep the overwatch console open at all times, so they can fire OBs while focusing on something completely different. At the beginning of the round during preparation, I announce- twice- in fire support communications that I will be doing this, and that "fake out" lases or similar should be avoided unless I am made aware.
Prior to the incident, multiple OBs have already been fired, to similar extremely fast response. There is a reasonable expectation, at least in my mind, that any OB lased for would be quickly fired upon. As an additional note, unlike with staffing CIC as an SO or Captain, clicking on the lase target as AI does NOT show you the target location.
Due to events in the round I was manning a combat droid when I got the audible OB notification. I became aware after the fact that there was a message in the common channel indicating that this was aimed directly for marines, but as I was actively piloting a combat droid, I missed one green message among the hoard of fifty others as I fired the OB.
After this fact, Ridgyax proceeded to use the admin announce tool to say (off of memory, please correct me if I'm wrong) "That's a banning" to the entire server - that is to say, before the ticket had even been created or any of the context known, the end result was already decided.
Why you think you should be unbanned: What, exactly, is the precedent this ban is meant to service? That command staff have a responsibility to read every message in common before firing an OB? That AIs are always responsible for the outcome of an OB? Is the process of fast firing simply disallowed, and AIs have a responsibility to stop and ask marines if they're CERTAIN they want that OB that was lased for to be fired, for every single OB?
SS13, and TGMC specifically, is a game about making fast paced decisions with partially flawed information. Sometimes the decisions you make will have negative consequences. Almost every round with an AI has functionally identical behavior to what I did that round - an OB is lased, an OB is fired. The difference in my case was that I failed to read a single message, in the same color as every other message, in the middle of a heated round, that would have informed me that an OB would be lased deliberately under marines, a decision I had zero reason to expect otherwise. I ask again: what precedent, exactly, is being set here, that genuine mistakes in a game about acting quickly with flawed information is worthy of a first time offense being a ban?
Frankly speaking, the ban itself isn't a big deal to me. It's 12 hours. But bans should serve, at least in my opinion, as a tool to stop detrimental behavior the offender is likely to repeat. What exactly is the behavior, and why am I considered likely to repeat it?
References of good conduct: I have played SS13 for about 2500 hours (TGMC specifically for 700-800) and before this my only two negative notes have been automutes in TGMC.
Character name: CASS-E
Ban type: Server
Ban length: 12 hours
Ban reason: Fired an OB as AI (The FC had placed down a laze as a joke in the middle of a marine push) that resulted in the deaths of multiple marines. Light punishment due to having said prior in the round that they would instantly firing on any OB and an overall lack of notes.
Time ban was placed: 2024-01-16 15:25:17
Round ID in which ban was placed: 25228
Your side of the story:
One of the generally more compelling reasons to play AI at all, or have one on the marine team, is their knack for "fast firing" OBs. Most squad leaders and field commanders are extremely grateful to have their OB lases fired extremely quickly, as AIs get a loud audio and visual notification whenever an OB is lased for and can keep the overwatch console open at all times, so they can fire OBs while focusing on something completely different. At the beginning of the round during preparation, I announce- twice- in fire support communications that I will be doing this, and that "fake out" lases or similar should be avoided unless I am made aware.
Prior to the incident, multiple OBs have already been fired, to similar extremely fast response. There is a reasonable expectation, at least in my mind, that any OB lased for would be quickly fired upon. As an additional note, unlike with staffing CIC as an SO or Captain, clicking on the lase target as AI does NOT show you the target location.
Due to events in the round I was manning a combat droid when I got the audible OB notification. I became aware after the fact that there was a message in the common channel indicating that this was aimed directly for marines, but as I was actively piloting a combat droid, I missed one green message among the hoard of fifty others as I fired the OB.
After this fact, Ridgyax proceeded to use the admin announce tool to say (off of memory, please correct me if I'm wrong) "That's a banning" to the entire server - that is to say, before the ticket had even been created or any of the context known, the end result was already decided.
Why you think you should be unbanned: What, exactly, is the precedent this ban is meant to service? That command staff have a responsibility to read every message in common before firing an OB? That AIs are always responsible for the outcome of an OB? Is the process of fast firing simply disallowed, and AIs have a responsibility to stop and ask marines if they're CERTAIN they want that OB that was lased for to be fired, for every single OB?
SS13, and TGMC specifically, is a game about making fast paced decisions with partially flawed information. Sometimes the decisions you make will have negative consequences. Almost every round with an AI has functionally identical behavior to what I did that round - an OB is lased, an OB is fired. The difference in my case was that I failed to read a single message, in the same color as every other message, in the middle of a heated round, that would have informed me that an OB would be lased deliberately under marines, a decision I had zero reason to expect otherwise. I ask again: what precedent, exactly, is being set here, that genuine mistakes in a game about acting quickly with flawed information is worthy of a first time offense being a ban?
Frankly speaking, the ban itself isn't a big deal to me. It's 12 hours. But bans should serve, at least in my opinion, as a tool to stop detrimental behavior the offender is likely to repeat. What exactly is the behavior, and why am I considered likely to repeat it?
References of good conduct: I have played SS13 for about 2500 hours (TGMC specifically for 700-800) and before this my only two negative notes have been automutes in TGMC.