Advertisement
Guest User

Capesh Moderator Interview

a guest
Mar 29th, 2019
52
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 17.27 KB | None | 0 0
  1.  
  2. FlamingoToday at 3:48 PM
  3. Excellent. For the record, can you state your ckey for me?
  4.  
  5. ErrantToday at 3:48 PM
  6. Capesh.
  7.  
  8. FlamingoToday at 3:50 PM
  9. Perfect. This interview is going to consist of two parts. The first will be a number of “scenario” questions, essentially different common ahelps you might run into on server. The second half will be a number of personal questions more aimed at you. If you have any questions feel free to ask me at any time.
  10. Lemme give you a quick overview of the powers you’ll have.
  11.  
  12. ErrantToday at 3:50 PM
  13. Understood.
  14.  
  15. FlamingoToday at 3:54 PM
  16. This is not an exhaustive list, but covers most of the commonly used powers and such that you’ll use, and need for this interview.
  17.  
  18. 1. The ability to use adminghost (aghost), which works exactly like the ghost command, but let’s you re-enter your body afterwards. This is mainly used to investigate issues in the round.
  19.  
  20. 2. Access to ingame logs (attack logs, ALL LOOC, ALL deadchat logs, ALL warning and admin logs such as people opening valves or welderbombing).
  21.  
  22. 3. The ability to adminpm (bwoink) people for a chat.
  23.  
  24. 4. The ability to place varying degrees of punishment. Notes are staff only messages on a player’s’ account. Warnings are similar but require the recipient to acknowledge it, and they can see what it was for. Bans are time based (or permanent), and can be from the server or specific jobs. People can see why they were banned. You can also view a record of all players past notes, bans, and warnings.
  25.  
  26. 5. Access to moderator only chat (msay) for communication, as well as access to other chats like AntagOOC and DeadChat (as stated earlier).
  27.  
  28. 6. The ability to WIND players, freezing them from all actions.
  29. Any questions about the powers listed here?
  30.  
  31. ErrantToday at 3:55 PM
  32. I have knowledge of or encountered the items on this list. No questions.
  33.  
  34. FlamingoToday at 3:57 PM
  35. Cool. Let’s start with a scenario that’s become increasingly common as of late.
  36.  
  37. You’re playing a round when you see a crew arrival announcement:
  38.  
  39. Yung Killa, Atmospherics Technician, is inbound from NTCC Odin!
  40.  
  41. What do you do?
  42.  
  43. ErrantToday at 4:04 PM
  44. First, check if the player has received any past notes. If (or if not), politely contact them to notify of the server's rules, and class of RP - which, in this instance, would gravitate towards a believable character (naming), and ask if they could cryo, reformat their naming into something less relatable to 'young killer', and respawn again (if I am able to expedite the player's normal 20 minute timer or, alternatively, ask a higher-ranked staff to do it, that would be great - as I'd rather not have a player sit for twenty minutes because they jumped into Aurora believing it was Paradise.)
  45.  
  46. FlamingoToday at 4:06 PM
  47. Cool. You take a quick look at their notes and see they have none. You shoot them a message, but they don’t seem to reply, instead just wandering around and bumping into a few other people there.
  48.  
  49. ErrantToday at 4:09 PM
  50. It's always possible of bad connection, missed message, or simply not having any audio on for the bwoink to be heard. I'll wait a few minutes until shooting them another message, simply inquiring if they received the earlier and/or didn't, and perhaps have questions.
  51.  
  52. FlamingoToday at 4:10 PM
  53. They don’t seem to reply again. They pull out a crowbar and start tearing up floor tiles and hitting windows, before starting to hit themselves.
  54.  
  55. ErrantToday at 4:15 PM
  56. Wind them, as to not cause further self-harm and send a message noting that, while yes you appear new to the server, and I would be more than happy to answer any questions you have, you are presently A, not responding and B, continuing server rule infractions by your name and present actions. I will unwind you, but if you continue to remain unresponsive to these messages, in addition to continuing breaking floor tiles and causing self-harm, I will give you a timed ban (while also linking Server rules again).
  57.  
  58. FlamingoToday at 4:16 PM
  59. He finally responds “fuck you” and disconnects.
  60.  
  61. ErrantToday at 4:16 PM
  62. Am I able to post-disconnect add notes to players?
  63.  
  64. FlamingoToday at 4:18 PM
  65. Yup.
  66.  
  67. ErrantToday at 4:20 PM
  68. Great. Add the timed ban, and a further note on the reasoning and replies of the ban itself - if the player returns after the ban a changed person, then I'm certainly not the one to stop their enjoyment of the server. But if they return the same, attempt conversation once more - and if given the same treatment - a permanent server ban.
  69.  
  70. FlamingoToday at 4:21 PM
  71. Cool, and how long did you want to apply the ban for?
  72.  
  73. ErrantToday at 4:21 PM
  74. What's the minimum time?
  75.  
  76. FlamingoToday at 4:21 PM
  77. 1 minute (it’s done in number of minutes)
  78. the default when you open the window is 1440 minutes, which is 1 day.
  79.  
  80. ErrantToday at 4:22 PM
  81. I was about to say 1 day - quite doubtful they'll read the server rules and return after a minute following their violent departure.
  82.  
  83. FlamingoToday at 4:23 PM
  84. Sounds good. Anything else you’d like to say for this question or are you ready for the next?
  85.  
  86. ErrantToday at 4:23 PM
  87. Ready for the next.
  88.  
  89. FlamingoToday at 4:24 PM
  90. Perfect. You’re sitting in the lobby when you suddenly see a flood of attack logs. Two people are killing eachother. It’s extended.
  91.  
  92. ErrantToday at 4:27 PM
  93. Aghost to check their surroundings, see if visuals can give something on proper escalation or not. Secondly, see who threw the first punch, wind them both, inquire separately as to what just happened.
  94. If winding will just make them both bleed to death, note if security/medical is responsive. If they are, don't wind, allow the fight to A, be stopped by security or B, one die (possible rejuv/void/ban depending on inquiry results) and inquiry them both once they don't have to mash harm intent upon one another at the same time.
  95.  
  96. FlamingoToday at 4:33 PM
  97. One of them has a butterfly knife and the other is bleeding bad. Security arrives to stop the fight as you pm both of them. The first is a cargo tech, he threw the first actual punch according to the logs. He says this engineer pushed him over and was talking shit so he hit him with a wrench and things escalated. The other guy is an engineer. He said the cargo tech was getting all up in his face so he pushed him over and the guy hopped back up and hit him with a wrench, so he fought back.
  98.  
  99. ErrantToday at 4:33 PM
  100. Which one has the knife?
  101.  
  102. FlamingoToday at 4:34 PM
  103. The engineer.
  104.  
  105. ErrantToday at 4:34 PM
  106. Does pushing (aka disarming) throw attack logs?
  107.  
  108. FlamingoToday at 4:35 PM
  109. Yeah but it just says “attempted to disarm”. The engineer definitely did that first, but the cargo tech hit him with a wrench right after that.
  110.  
  111. ErrantToday at 4:35 PM
  112. Alright.
  113. Based on their initials replies (along with logs), both view the event as it appears to have happened, with the engineer acknowledging pushing first, and the cargo tech acknowledging doing the actual first attack log - always a blessing with corroborating statements. For me, the actual first red flag is the knife/wrench - and the usage of it. Not, of course, to mention the fact that 'talking shit' equals 'let me smash/shank you to actual death.' I check both of their notes.
  114.  
  115. FlamingoToday at 4:44 PM
  116. Their notes are both relatively clear. The cargo tech has some notes about being aggressive in LOOC, and the engineer has a warning about powergaming from a few weeks before.
  117.  
  118. ErrantToday at 4:45 PM
  119. What did the engineer's powergaming warning entail?
  120.  
  121. FlamingoToday at 4:46 PM
  122. It reads that he was ordering weapons as a quartermaster.
  123. Without a valid reason.
  124.  
  125. ErrantToday at 4:53 PM
  126. Gotcha. I inquire the engineer about his butterfly knife possession, while gently reminding him of his previous warning - as this is extended, there are no free-pass-possession/escalation-within-reason antag roles around. I will verbally (textually?) warn them both concerning the round-type and their deeds, judge who kept up the fight the most, and tack notes of impromptu escalation/unnecessary attack log prolonging if required. I will not, however, issue an actual warning to either (but be firmly clear with the engineer, concerning their previous warning). As both weren't antags, it doesn't matter if it was secret-extended or voted extended.
  127.  
  128. FlamingoToday at 4:55 PM
  129. Cool. Anything else you’d like to do for this one?
  130.  
  131. ErrantToday at 4:55 PM
  132. If both players are amicable enough in their responses, then no.
  133. Neither died, no one tried to lampshade/throw a bus.
  134.  
  135. FlamingoToday at 4:57 PM
  136. Cool. Yeah they’re both alright with it. The engineer seems a little irritated but otherwise is fine. Ready for the next one?
  137.  
  138. ErrantToday at 4:57 PM
  139. Mhm.
  140.  
  141. FlamingoToday at 4:59 PM
  142. Excellent. Let’s do just one more of these scenarios, then.
  143.  
  144. ErrantToday at 5:00 PM
  145. o/
  146.  
  147. FlamingoToday at 5:00 PM
  148. You’re playing a round of mercenary when you suddenly see some attack logs and an ahelp pops up:
  149.  
  150. “UHM GANK???”
  151.  
  152. ErrantToday at 5:02 PM
  153. Depending on the role I am playing (AI/Merc/Crewmember) I will first see if I am in the position to viably take the ahelp (AI + merc + ahelp isn't the best of mixes). If I am not, I will see if any other staff members are online. If they are, ask if they can take it. If not, take it and, if the issue is a prolonged one, OOCly note that my character is momentarily unavailable.
  154. As merc requires quite a lot of active players, the chance of me being the only viable staff member is relatively low. But still.
  155.  
  156. FlamingoToday at 5:05 PM
  157. For the purposes of the question we’ll say you’re able to handle it, though I like your thinking there.
  158.  
  159. You hop over there and see that the mercenaries have just killed an engineer on the solars. You know from being ingame that the mercenaries haven’t been discovered yet. Its 0:18 into the round.
  160.  
  161. ErrantToday at 5:05 PM
  162. Do I have access to AOOC?
  163. Easier to confront the merc team there than ping every single one present at the scene for the same issue.
  164.  
  165. FlamingoToday at 5:06 PM
  166. You do, yes.
  167.  
  168. ErrantToday at 5:07 PM
  169. I'll pop in, say hi, and gently ask why the team gunned down an engineer 18 minutes into the round, and take note of their responses. I'll also answer the engineer's ahelp and ask their side of the story.
  170.  
  171. FlamingoToday at 5:09 PM
  172. The engineer says he was wiring the solars when the mercs walked into view and shot him
  173. The mercs say that they landed near the solars to sneak onto the station. They space walked and ran into an engineer. They tried to tell him to stop but he started running towards the airlock, so they shot him before he could escape and reveal them so soon.
  174.  
  175. ErrantToday at 5:13 PM
  176. Well, firstly, talking in spess is limited to one-tile - or reading the exclamation points from a head. Running from guns to safety is also realistic, if you didn't hear anything at all.
  177.  
  178. Of course, we have discrepancies. If all the mercs really swear the engineer ran towards the airlock, I'll ask the engineer if he did anything provocative - like attempting to run away. Odd thing overall is that the engineer did not say anything over communications.
  179.  
  180. Do logs reveal if a gun is aimed at someone else/and/if it's a reflexive fire?
  181.  
  182. FlamingoToday at 5:17 PM
  183. They do make a log, yes.
  184.  
  185. The mercs all seem to corroborate the same story when prompted. The engineer admits he took a few steps away from the mercs but didn’t expect to just be killed outright. None of the mercs aimed they just shot.
  186. ErrantToday at 5:26 PM
  187. Murder for the sake of murder is frowned upon (and rule-breaking), unless the reason is good and the roleplay is forwarded. As there was zero escalation (or the fact the mercs hadn't even been discovered yet), such a reason can only be attributed to 'we want to keep being hidden,' which, normally, is a weak one for me - however as the merc team had assembled unusually quickly this round (18 minutes), it carries a bit more weight.
  188.  
  189. However, the second issue is that the mercs did not give the engineer any time nor inclination to stay put (by aiming), and while I note AOOCly that I understand the 'want to keep being hidden' part, I also press that had they not killed the engineer, or at least given him escalation/incentive (once again, aiming), the issue would have been less stark, and the roleplay ultimately forwarded.
  190.  
  191. As the mercs did not aim, I cannot fault the engineer for reflexively taking a step back and being riddled with bullets. I am actually on the fence about rejuving the engineer for a re-do, now with actual aiming and capture.
  192. While the engineer is right in the fact his death was quick and unjust, I can't really, well, remove the mercs.
  193. Nor would I want to.
  194. Third option would be to rejuv the engineer, tell the merc team to go somewhere else, and void the entire thing.
  195. I'll most likely confer with staff - if none are still available, ask both parties which option they'd want, but lean towards the engineer's decision as they are the victim of the incident (and the one who's dead.)
  196.  
  197. FlamingoToday at 5:31 PM
  198. Instead of making up some different examples of staff conference, I’ll instead say that generally speaking we don’t really interfere with the flow of the round (rejuvenating dead people, etc) except because of grief, or when bugs cause issues.
  199.  
  200. ErrantToday at 5:32 PM
  201. Alright.
  202.  
  203. FlamingoToday at 5:33 PM
  204. Generally is just ends up causing more issues than it’s worth.
  205.  
  206. ErrantToday at 5:35 PM
  207. In such a case I'll warn the merc team that further deaths without a window for appropriate response will lead to harsher punishment, while apologizing to the engineer that, although I understand his frustration, I am unable to void or rejuv the incident - but note that, if biosensors were active, and medical are active, their body will be retrieved soon for a second try.
  208.  
  209. FlamingoToday at 5:36 PM
  210. Sounds good. The merc team seems to understand. The engineer is a bit disappointed but accepts it. Anything else you’d like to do?
  211.  
  212. ErrantToday at 5:37 PM
  213. Check the merc team's notes, and add appropriate ones for those who conducted attack logs.
  214. The engineer did nothing wrong, so he gets an internet hug.
  215.  
  216. FlamingoToday at 5:38 PM
  217. Alright sounds good. Ready for the next section?
  218.  
  219. ErrantToday at 5:38 PM
  220. Growing late, but yes.
  221.  
  222. FlamingoToday at 5:40 PM
  223. This should hopefully be faster.
  224.  
  225. ErrantToday at 5:40 PM
  226. Sorry, I did agree to the timing after all.
  227.  
  228. FlamingoToday at 5:42 PM
  229. We’d better start then! First question: You’ve been around the server for some time now. What prompted you to apply for a moderator position?
  230.  
  231. ErrantToday at 5:44 PM
  232. Honestly been toying around with the idea for quite some time. At this point I feel I have good enough a grasp on mechanics and knowledge that, well, applying would be a possibility - I do strive to offer aid as Arlo/O.R.B., and experiencing the ups and downs of moderation on a server as Aurora would be a welcoming experience.
  233.  
  234. FlamingoToday at 5:45 PM
  235. Good to hear. A follow up question: moderating can be severely draining at times. You sometimes have to do unpleasant things (doling our punishment to friends, banning someone who isn’t hostile for repeat offenses, etc). Is this something you’re comfortable doing? It can sometimes ruin the game for people.
  236.  
  237. ErrantToday at 5:48 PM
  238. Well, as mentioned in my application, my actual work is retail; being drained is part of daily life, not to mention my timezone and the late-hours I have to regularly pull, on my own volition.
  239.  
  240. As for additional mental drainage in moderation: I never enjoy acting as an opposing force to other people's enjoyment; and while I hope such instances will be low, I will not shy away from the moderation duty.
  241. Of course, we'll have to see following the trial status.
  242. As is its purpose.
  243.  
  244. FlamingoToday at 5:49 PM
  245. Excellent. Just want to make sure you are aware of the possibilities beforehand.
  246. Just a couple more questions.
  247.  
  248. ErrantToday at 5:49 PM
  249. Shoot.
  250.  
  251. FlamingoToday at 5:50 PM
  252. You’ve been well known to play lawed stationbound synthetics (ORB). How do you think this might offer you a unique perspective while moderating?
  253.  
  254. ErrantToday at 5:54 PM
  255. State laws Moderator malf
  256.  
  257. As a non-squishy organic, I have learnt to be quick, polite, concise, and friendly. Shrug insults off, stick to your laws with a metal claw, and enjoy the fact you can always blame your AI.
  258.  
  259. Heh. But in all seriousness, I imagine moderating to be doing ORB/Arlo - same underlying people, just with the acute difference that your actions actually matter in moderating.
  260. Trust in your laws, be clear on judgment.
  261.  
  262. FlamingoToday at 5:56 PM
  263. Cool. Just one more question for now. If you could change one thing with how the server operates now, what would it be?
  264.  
  265. ErrantToday at 5:57 PM
  266. As far as I've come to know it, the server and its people chug along as well as can be, considering we are all human.
  267. With the recent merge-process change, PRs flow in at a rapid pace. The Ssethening keep our numbers moderately high on even lowpop. Staff have handled the influx great.
  268. There are always, and will always be, rotten eggs around. But I'm glad the positive people far outshines them.
  269.  
  270. FlamingoToday at 6:01 PM
  271. No changes?
  272.  
  273. ErrantToday at 6:01 PM
  274. Nothing is burning.
  275.  
  276. FlamingoToday at 6:01 PM
  277. This is true. Good enough for me.
  278. I lied, one more question.
  279.  
  280. ErrantToday at 6:02 PM
  281. :^ )
  282.  
  283. FlamingoToday at 6:02 PM
  284. Is it alright if I post this to the forums? Or would you prefer to keep it private?
  285.  
  286. ErrantToday at 6:02 PM
  287. Post on.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement