Omu Staff Policy

OmuStation Staffing Policy

Admins:

1. General Administration

General admin-guidelines. These apply to all ranks of admins: Headmins, Game Admins, and Trial Game Admins.

1.1 Administrators will be held responsible for their actions.

Administrators are not unaccountable, and should be held to higher standards than the playerbase, an administrator should be banned or noted as a normal player, and there should be no bias in defense of the admin. If you have a problem with an admin’s behavior, discuss it with the head admin. All administrators are expected to have a solid reason behind their actions. Failure to follow the Admin Policy will result in a strike or removal from the Admin team, all Administrators are expected to know and have the Admin Policy

1.2 Be respectful, polite and welcoming.

Being respectful back to respectful players is important, and in general will help reduce the number of issues you run into as staff. You are expected to try your best to deescalate, rather than escalate situations. As staff, you’re often the first person that a player with an issue will talk to. No matter your opinion on the player, try your best to be respectful towards them.

1.3 Do not leak or share sensitive information without permission.

This does pertain to any information posted in the game admin Discord chats, information discussed in admin chat in-game, as well as PII (IP, HWID) accessible through the central ban DB. This does not pertain to basic ban info (time, reason, count), admin notes, or admin log information. Ignoring of failure to follow this policy may result in your immediate removal.

1.4 Ban Appeals

Ban appeals are covered by the Banning Policy. (Link to banning policy)

1.5 Administrators must use their powers in moderation

The Admin team must use their powers in moderation ensuring that they do not attempt to abuse obstacles set in place by higher ranks, you will need permission before doing so, in cases of utmost emergency while no game admins are online. This also covers commands such as Customvote, and so forth. This includes not giving items to yourself or putting yourself at an unfair advantage while in character.

Example; A trial admin editing variables in a taser, allowing it to shoot debug uplinks, or items of their choice, overcoming the anti-spawn enacted on trialmins by the Head of Staff.

Example; Spamming custom votes to the detriment of the game or roleplay. Event votes, event feedback votes, and admin intervention votes, such as manually restarting the round if the restart breaks, are all reasonable causes.

1.6 Administrators must listen to a reasonable request by a head admin or higher.

Administrators must listen to what they deem a reasonable request by a head admin or higher, if you personally do not deem the request reasonable, refer it to the Head of Staff and do not act upon it until you get confirmation if the task is reasonable or not.

Example of reasonable requests:

• Being told to stop speaking in LOOC to one player while you’re the only administrator on, while there are adminhelps that need attention.
• Unreasonable request
• Being told to stop orbiting what you believe is a potential Raider is not reasonable.

1.7 Administrators must follow Discord and Server Rules.

Goobstation Administrators must follow the Goobstation Discord server rules at all time, if you see someone violate a rule, you should either warn them or time them out for a select amount of time. Administrators are expected to not break any server rules while deadminned or adminned.

2. Game administration

Rules specific to admin in a round of SS14.

2.1 Do not ever process a case you are/were a part of.

Even if you’ve started to admin after dying, do not process a case you were involved in. You may ask headmins for permission to do this if there are no other staff online. Otherwise, ahelp yourself and get the other staff to handle it. Disregarding this rule allows a headmin or the Head of Staff to strike you immediately if the case is found to be especially unsavoury.

2.2 Superseded by banning policy

Bans and ban appeals are covered by the Banning Policy.

2.3 Deadmin when you play the game.

Don’t misuse your game admin tools to metagame, this is pretty self-explanatory. Do not use your admin powers to message players whilst IC. If something happens that breaks the rules, you should engage with admins as a normal player via the regular ahelp command. Exceptions to this are:

• You may start to admin a round after you have died. Do note that policy 2.1 still applies!
• You may use admin tools when running admin events if necessary, even if you are playing a character for it.
• You are the only admin online and you choose to play a round, you can re-admin yourself but you should not enable overlay, or do any administrative actions unless Ahelped or if admin logs show something concerning, such as a non-antagonist blowing up a welding tank, policy 2.1 still applies.

2.4 Admin events should be done in moderation without heavily altering the flow of the round.

An “event” here is generally meant to be any admin intervention in the round that affects more than a handful of people: spawning a cookie for a prayer no, spawning a sentient monkey that runs around and messes with people yes.

Heavily round-altering admin events (e.g. powerful wizard invasion, nations) should be voted for by the playerbase with customvote and only done on Extended (that means forcing the preset before the round starts!).

Events overall should not be something that occur every round. Log what events you’ve done in Discord (just when & what, and no need to log very minor stuff), and try not to overwhelm players. That said, a lot of lenience is given towards what kinds of events can be run.

2.5 Do not interfere unless you are needed.

If it looks like the situation will be able to resolve itself, or escalated naturally; and nothing actually actionable has happened, then there is no reason to interfere.

2.6 Check with other admins before enacting bans outside of guidelines.

Bans and ban appeals are covered by the Banning Policy. Administrators who place bans outside of the guidelines are required to be able to justify the decision to head admins and head of staffs in the event of a staff complaint. In the event of a ban appeal, the banning admin should be prepared to justify themselves to the entire team. You are not required to justify anything unless asked by another admin until there is an appeal or complaint filed.

2.7 Use notes as consideration for punishment, and give notes frequently

If a player is AHelped for some behavior, but this behavior skirts the rules and is not explicitly bannable, you should always give them a note for it. When handling AHelps, you should always check their notes before interrogation or applying punishment. If a user is noted to have been skirting the rules multiple times previously in their notes, you may apply a ban for this behavior. Lastly, if a user has more than 4 days on the server, you should also take this into consideration while applying a ban or note.

2.8 Monitor admin helps when online, leave if you have to go AFK for extended periods of time.

An administrator should always make an attempt to monitor active admin helps, if you are aware you will go AFK for an extended amount of time of 15-20+ minutes, disconnect so the panic bunker is enabled.