W3bster interview.

Coalf - Today at 9:56 PM
Alright, first do you have any questions before we start? Anything regarding staff powers and stuff?

Denuvo - Today at 9:56 PM
None at all, no.

Coalf - Today at 9:57 PM
Also have to confirm, your in-game ckey is w3bster, correct?

Denuvo - Today at 9:57 PM
Yes.

Coalf - Today at 9:58 PM
Alright, first question.
A new player joins with the character name "Karl Marx", a bearded, white haired 30 year old assistant. Our records show their account is 2 days old. What do you do?

Denuvo - Today at 10:02 PM
- Check for any previous history (warnings, kicks, bans, ETC)
- Send him a friendly message. Remind him that Karl Marx is obviously not a name that is suitable for our server as it is breaking the atmosphere of the game. Depending on his history is what will guide me from there. More than likely offering a name change and a warning.
Warning would be verbal, as in "Please take a bit of time to review our rules and guidelines, found at the top right. Thanks!"

Coalf - Today at 10:05 PM
You find a completely empty record on his history.
And when you message him he simply seems to ignore you, heading straight for the tool storage, stuffing his bag full of everything he can find and screaming into the radio "SEIZE THE MEANS OF PRODUCTION"

Denuvo - Today at 10:09 PM
[If this is a feature] Freeze his character, attempt to further converse with him and get his attention. From my past experience with staffing a server, this will usually go two ways. Either he will begin conversation which can go any kind of ways or disconnect. As the previous warning did not work, i believe it would be justified to either apply a temporary ban if the subject does not appear to be cooperative, or if he disconnected, potentially a permanent ban as to force communication with him on the forums should he wish to join again.

My goal here is not to seek any way to just swing the hammer, more to solve a situation. If his account is two days old and he's got that much understanding of the game, he's obviously been at  it with a purpose.  Although we can  never jump to any conclusion, all factors must be considered.
Coalf - Today at 10:10 PM
Freezing is a feature yes and he immediatly disconnects.

Denuvo - Today at 10:11 PM
Permanent ban would be the most justified option as to force him to communication via forum appeals. Make logs of the situation to keep myself up-to-date should he appear.

Coalf - Today at 10:11 PM
Alright, going to move onto the next question now when you're ready

Denuvo - Today at 10:11 PM
Sure.

Coalf - Today at 10:13 PM
You get an ahelp from a player that claims he was killed due to an AI bolting a door on him and leaving him in a gassed area on purpose.
Denuvo - Today at 10:13 PM
Reply to him i'll be checking it out, as a first means of telling him he's been heard.
- Verify the game mode. and surrounding circumstances. Is it malf? What are the factors involved. Was he an antagonist? Did it escalate up to him being required to be bolted in a gas room?
- Verify if it could just be an error/deemed justifiable. Say it's a phoron leak and he was in an isolated area and it lead to a populated area. AI could of just bolted it to save as much of the station as possible.

There's tons of way this could be ICly justified and be an IC issue, but i would investigate nonetheless. If necessary, bwoink the AI just to inquire what had happened if for some reason i really can't figure it out.
If it ends up being an IC issue, politely advise the player of such and the justification as to why. Sometimes, people get involved in their characters and gameplay and might not be too happy as  to the justification and really, really insist that we get involved.  I'd remind him that we are all here for fun and not to argue/fight. Things that happen IC do happen and everybody that's played the game long enough knows that. There's always a next round and it'll never go anywhere.

Coalf - Today at 10:21 PM
You discover the AI didn't bolt the doors but only closed them to seal the leak, you yourself can see the doors are not bolted nor were they at the time of the ahelp. The player is not a traitor and the AI is not malf/traitor.
You discover the phoron leak was actually caused by the player in that room and you also discover he's not an engineer but a security officer.

Denuvo - Today at 10:30 PM
Then it may turn in an investigation against the player who made the initial report.
Try to find as to why/how the leak was caused. Was it griefing? Was it also an accident?
Contact the player and tell him my findings, and ask him as to why the leak happened in the first place.
Contact any witnesses. Usually if it's grief, we'll get a couple of other notices from surrounding players in the likes of "This dude just walked up to the canister and opened it for no reason".

Depending on the outcome, wether it was grief or not, i would interact with the player.

- If it was grief :  Then i would of established that he opened the cannister for the purpose of harming gameplay and then attempted to get another player in trouble. Usually, seasoned griefers will find all ways to try and cause chaos/confusion. I do not believe in this case a warning would be appropriate. A temporary ban would be necessary. Depending on the server's philosophy as to how long those go for.

- If it was not grief : Establish as to why exactly that happenned. Did the player believe it necessary to do so? Was it an accident? If further investigation returns that it may of been prevented/was complete neglect and overreach by the player, an official warning may be written and if the situation deems it necessary or the server's philosophy for atmospherics of no-tolerance for messing with it, go with the actions the server normally deems appropriate.

To note, i've seen punishments widely differ from server to server.  Although this server's rules do indicate what type of punishments may be use, they do not specify as to what they are used. Although that's completely understandable as every situation is nearly unique in SS13 and everything may need to be judged on it's own basis, at times there is somewhat of a consensus as to what action deems the severity of the punishment

Coalf - Today at 10:33 PM
While questioning he says that his character was sick of his workplace and wanted to gas everyone and says that the AI violated its laws by letting him die.
You also discover the only reason he couldn't get out was because he didn't have access to the doors and admitted he got in by sneaking in behind an engineer that was leaving.

Denuvo - Today at 10:39 PM
Then it would fall under a more servere case of the "don't be a dick" general rule. Assuming he is not an antagonist, i would explain to him as to why that was not appropriate and attempt to prod him further as to why he did it. Although people usually give a first explanation, the more you dig the further they reveal, wether it was because he was truly "bored" of if he really thought there was some in-depth roleplay nobody else knew about or had malicious intent to just go around and mess things up. Atmospherics sabotage, especially phoron is quite severe. Waiting for an engineer to sneak in and aim for the Phoron can be used as a supporting point that he had it really in mind to do what he did. It can truly fuck a round up and put a dent in many people's round. In most cases, i would likely be aiming for a temporary ban while fully explaining to him why i believe so, which centers around the following mentioned :

- Severity of messing with Atmospherics.
- "Sick of your workplace" is not a reason to do so. We do not normally let antagonists mess with power/atmos unless pre-approved as it can be a round-ending move or one that really, really needs a lot of work to fix.

Coalf - Today at 10:40 PM
Okay
That's I think satisfactory
Any questions before the next one?

Denuvo - Today at 10:41 PM
Nope, good to go.

Coalf - Today at 10:42 PM
You receive an ahelp, an antag currently being slapped with cuffs ahelps that he was ganked by a security cyborg while having RP with another officer, the player ahelping also seems to be insulting the borg in LOOC at the time of the ahelp.

Denuvo - Today at 10:45 PM
Immediatly ask him to stop the LOOC talk, as it would only serve to further escalate the issue.
Obviously, emotions are involved. He's upset that this has happened and believes the cyborg unjustified in his actions.
I would follow by investigating with the cyborg and the officer.
- What was the extent of the roleplay?
- What were the surrounding circumstances? Was the officer hostage and the only way to rescue him was to surprise the antagonist? Was there an active roleplay between the two players and the cyborg simply had the aim to "catch the bad guy"?

All in all, i would not issue bans in this circumstance. If it was found that the cyborg had in fact "Ganked" the antagonist without justification as to rushing, i would give him a friendly verbal warning/reminder as to the philosophy of the place and to think for the next time. I'd let the player know if necessary that the issue has been dealt with and should not happen again.

If the cyborg was deemed justified in his actions, i would message the player as to my findings and why it is so. I would explain to him that at times, in exigent circumsstances, things can happen that don't immediatly follow emotes and discussion and that we have to understand that.

Coalf - Today at 10:53 PM
You discover the antag and officer were standing at opposites sides of the hallway being essentially cought in a mexican standoff of who's going to fire first although the officer only had rubber bullets while the antagonist had a mateba (which the antag himself tells you is just a chameleon projector but players couldn't know that).
Both the officer and the antag tell you that the borg walked in on this, started immediatly advancing towards the antagonist and shooting him with a tazer, stunning him and cuffing immediatly.

The borg tells you he can't be at fault because he was following his second and first law, I.E Protect and Serve the crew as he was ordered to arrest the person and the antag was a clear threat.

Denuvo - Today at 10:58 PM
As such, this has turned into an IC issue, and is not ours to deal with.
The cyborg, if his laws are such, can put himself between the officer and the antagonist and attempt immediate containment of the threat.

Only escalate conflict in a realistic manner - some characters might overreact, but you would not realistically go berserk or attempt to kill someone if they stole your prized pen, for instance. Again, your character must be motivated enough to commit to more drastic action, as they undertake it.

The cyborg is justified in thinking the subject is aiming to kill or seriously injure the officer and acted as such. I would then explain to the complainant as to why that is considering all factors involved.

Coalf - Today at 10:58 PM
Alright
Any other comments?
Questions before the next one?

Denuvo - Today at 10:59 PM
Nope, should be good.

Coalf - Today at 11:02 PM
A player adminhelps that another player, one you know well but have never had to deal with as a moderator, is powergaming. A quick check on them reveals that they, as a quartermaster, have managed to arm themselves heavy using the most powerful weapons they could have legitamately aquired in that job (Mining rig, plasma cutter, drills etc.), and is currently in a firefight with the nuke team. The player is winning having killed two of the mercs, wounded the third one into crit and the fourth one is barely holding off.

Denuvo - Today at 11:07 PM
Obviously, there is an active fight upon which if i contact the player it might take them a minute or two to reply.

I would verify his history, as usual, and see if there's any previous cases of this recorded.  with this player. I'd ask them why they believe their actions would be justified. I would then explain why this is considered powergaming as a Quartermaster, who might be able to order all that gear, should not inherently know how to use it, even less be able to take down an entire team of well-equipped antagonists. As per the rules, folks should usually not seek their own demises in which this could be the case. Depending on the history and his answers, i might either give a serious warning or a temporary ban.

Obviously, conflicts do happen. Someone i've roleplayed with and might enjoy the company in-game might end up being hostile/not so fun when dealing with in an official position. This is something that's part of the responsibilities and we have to deal with. Obviously generally our goal is players first, staff second. Although when needed, we act as necessary.

Coalf - Today at 11:12 PM
You discover the QM HAS been previously banned for powergaming for a week but he swears it couldn't be the case this time as the mercs actually happened to find him sitting in the maintenance and he simply decided to fight back as he says his character was afraid these guys would kill him since the only way outside of that room was through the mercenaries.
The mercenaries confirm that they suprised him but were simply not skilled mechanically as the QM was, they demand a rejuv because "If we die here this isn't going to be fun for anyone on the station"
Denuvo - Today at 11:16 PM
I'd seek with higher-up staff how Rejuv works and if they believe it justified, as i'm too rookie on the server to make that judgement myself.

As for the player, obviously he has previous history of Powergaming and does not seem to understand or learn from previous occurences, and has already had a full week ban, i would probably lead to a permanent ban. The reason being previous attempt(s) have been made to have the player understand the situation and it has failed. An appeal on the forums may lead to more constructive discussion and a learning experience for the player.

Coalf - Today at 11:17 PM
The player doesn't seem to understand why he's being banned, calling you a "Rule lawyering cock rider" and "A virgin just abusing his position"
He seems to have decided to start head-gibbing the already dead mercs too.

Denuvo - Today at 11:18 PM
Apply the ban and include that interaction in the ban.

Coalf - Today at 11:18 PM
Alright aaand that's it
Actually one last questions, are you okay with me sharing this on your application on the forum?

Denuvo - Today at 11:19 PM
No problem at all.

Coalf - Today at 11:19 PM
That concludes this interview.