Garnascus — Today at 7:45 PM
So, basically i am going to throw a bunch of random situations at you that you might encounter while being a staff member.
[7:46 PM]
You're not expected to answer these 100% correctly. What we are trying to figure out is your thought process. You can ask me any questions you want during this interview.
[7:46 PM]
So, question number 1.
[7:47 PM]
You are alone on the server and you see someone join with the name "Big long schlong". They are a 0 day account and they are just wandering around the station.
[7:48 PM]
What do you do?

kermit — Today at 7:50 PM
Despite it being a zero day account, I'd have a cursory glance at their note history just to see if this is repeated behaviour. Whether it's a repeat or not, I'd shoot them a message with the usual 'Hey, nice name, sadly that's not gonna be allowed here' and direct them to the rules.

Garnascus — Today at 7:51 PM
Alrighty. He appears to be ignoring your PMs. Instead he has hopped the counter in the kitchen.

kermit — Today at 7:54 PM
So, judging by the name, it's clear they're not gonna be taking things seriously. I'd message them again as they jump the counter, give them another chance to respond, though should they do anything silly or should they bump into a chef, I'd wind them.

Garnascus — Today at 7:54 PM
Alright. They finally respond but the entire sentence is in russian.

kermit — Today at 7:59 PM
I'd ask them to speak english, server's an english-speaking place and all. Assuming they continue speaking Russian and make no attempts to communicate with me, I'd leave a note about the interaction - so and so joined with a wacky name, jumped the kitchen counter, then only spoke Russian in the ticket interaction - and give them a hefty ban encouraging them to appeal on the forum in English. Not too sure what else to do in a situation where a pretty large language barrier is between you and the person in the ticket. Of course, if they suddenly started speaking English, things'd go differently

Garnascus — Today at 7:59 PM
Alrighty next question.
[8:01 PM]
You are ghosting around when suddenly you see a large amount of attack logs between two people. One of them is a regular player, the other is a 0 day account. The 0 day account clearly started it accoring to the logs. The two of them are currently fighting and their is a good amount of blood everywhere. What do you do?

kermit — Today at 8:05 PM
0 day account may suggest the fight has no reasonable IC grounds, though it'd be wrong to entirely go based on that. I would probably let the fight run it's course, then afterwards enquire with the regular player about what happened, whether there was justification behind the altercation or not.
[8:06 PM]
Interrupting it just 'cause a 0 day account is involved could ruin the interaction between them, it may have been a justified fight between the two. Alongside messaging the regular player first, I'd also sneakily peek at if either of them are antags, that'd also explain a lot.

Garnascus — Today at 8:08 PM
Neither of them are antags. You message the regular player and they apologize to you immediately. They explain they have invited one of their friends to play with them and are helping them learn the mechanics of the game. While attempting to explain the various "Intents" their friend punched them in the head twice. The regular player punched back as a joke and before both of them knew it they where bothing beating each other up.

kermit — Today at 8:13 PM
After chuckling a bit, I'd say that's fine. Keep the ticket open with the regular player while I open a new one with the 0 day old player where I'd ask if they need a hand, direct them to the wiki so they know where it is, though also remind them that they ought to remain sensible - even if they are new. Given the altercation ended pretty bloody, it'd likely affected the round to some degree - Medical or Security called, what have you - so I'd have to leave a note for the new guy regarding the altercation, including that they're just getting the hang of things. Assuming the new guy's happy with any resources I provided them, I'd close their ticket and then perhaps suggest to the more regular player that, if they're gonna test intents or whatnot, they try do it in a more sensible manner from an IC standpoint - use the holodeck or whatever.

Garnascus — Today at 8:14 PM
Alrighty on to the next question.
[8:16 PM]
Alrighty, so you have taken an ahelp from a security officer who is quite upset. His ahelp reads something along the lines of "Ok this is fucking ***** is he really allowed to just kill me like that? i didnt even have a weapon out".

kermit — Today at 8:18 PM
I'd ask him to explain what happened, first and foremost. While they take however long they need to write up their response, I'd check the logs to who they are referring to, then aghost to that player and observe - if there's a chance an antag's just ganked someone, I'd wanna make sure they're not in a position where they may start killing other players for little reason. (edited)

Garnascus — Today at 8:21 PM
He explains that he received a tip from the janitor along the lines of "Hey someone is kinda loitering around the vault and he has a full belt of tools on him. can you check it out?". The security officer then went to the vault and sees an assistant in the process of deconstructing the vault door. It also appears he has stolen access to be able to disable the turrets. He then explains that upon seeing the security officer the assistant pulled a gun from his back and unloaded the clip into him. The officer was caught by surprise and wasnt able to unholster his weapon in time to fire back or call for backup.
[8:21 PM]
You ghost over to the vault and see the antagonist looting all of the vault's contents.

kermit — Today at 8:26 PM
As the antag is in the vault busy looting, winding shouldn't be too necessary. Even if other security officers appeared during the course of the ticket, they've escalated to the point where a shoot out is inevitable - an officer's just been killed and they're arms deep in the vault cases. Winding them would only give the rest of security time to set up outside.

I'd tell the officer who opened the ticket that I'd look into his case and would then open a ticket with the antag, telling them that the officer is unhappy that they were removed from the round without so much as a word, and that proper escalation is required before an antagonist may start killing. (edited)

Garnascus — Today at 8:27 PM
Alright, after you PM the antag he argues with you that he was in the process of breaking into the vault. He had been caught red handed by a security officeer who with a single radio call can summon backup and throw him into jail for the rest of the round. He argues he was justified in immediately killing the officer due to the extreme risk involved.

kermit — Today at 8:31 PM
I'd remind them again that proper escalation is required. While being caught red-handed breaking into the vault sucks, a more proper way of handling things would have been to engage in brief dialogue with the officer, or perhaps drawing a weapon but with no intent to fire immediately, such that the situation may more smoothly progress from being caught to having to kill the officer. I'd then direct them to the rule regarding this. While waiting for a response, I'd apply a warning and a complimentary note for ganking behaviour which I would then inform them of.

Garnascus — Today at 8:33 PM
Alrighty, last question.
[8:35 PM]
You are observing during a merc round when you take an ahelp accusing the scientist of powergaming. He has built a combat mech for a security officer with mech training so that he can ambush the mercs and kill them. The mercs at this time have captured a number of crew from the station and are holding them for ransom. The captain and the HoS are holding negotiations and have forbidden any aggressive action towards the mercs for the time being. What do you do? (edited)

kermit — Today at 8:38 PM
Given multiple members of crew have been captured and are being held for ransom, enough escalation has occurred for robotics to produce a combat mech. That said, the security officer being given this combat mech has the potential to cause a lot of issues down the line, so I'd begin observing the security officer after they've acquired the combat mech to see where things go from there.

Garnascus — Today at 8:39 PM
Alright. Once he acquires the mech he uses it to break aboard the merc's ship. A firefight ensues with multiple security personnel and mercs dieing. One or two of the hostages also die in the crossfire.

kermit — Today at 8:42 PM
Yeah, at that point I'd open a ticket with the mech pilot and ask if they have a moment. I'd ask if they were aware that the captain/HoS forbade any aggressive action towards the mercenaries.

Garnascus — Today at 8:42 PM
He explains that yes he does understand that but he explains to you that his wife was one of the hostages. He felt obligated to try to rescue her at any cost.

kermit — Today at 8:47 PM
I'd say that the means in which they attempted to incorporate that snippet of information into the round was pretty devastating towards the story the antagonists and command were trying to drive, and that they could have perhaps attempted to try other avenues to fuse this husband-wife dilemma into the greater story the antagonists and command are telling. I'd inform them that I would be warning them for powergaming and bulldozing the story with a combat mech, alongside a complimentary note explaining the situation.