Administration Guidelines

Moderator Powers

As a Moderator, you are given several powers, typically used in the event that an administrator is not present. These are powers that you typically should use extremely carefully, as you are not protected by the ability to host an event. It is very easy to contribute to a gimmick and spawn an extremely powerful item by trusting the player on the other side of the admin ticket, and then have the round end up in a total catastrophe for everyone involved. Be thorough, investigate, and be reasonable before using any of these verbs.

• Moderators may not use their powers to alter a round, or in other words, to create a situation that may be considered an event. Hosting events is exclusively the purview of administrators.
• Do not spawn items for players just because they asked. Double and triple check when spawning items for a gimmick, as it is easy to spawn something that is far too powerful for the antagonist that is asking.
• When using the Spawn verb, make sure to not click the verb itself and to use it in the command bar with an argument, otherwise you will lag the server quite a lot.
• You are under no circumstances allowed to spawn an item for yourself, unless it is cleared by a staff member that has those powers. Spawning items should be reserved for fixing bugs and helping antagonist gimmicks in the absence of an administrator, or if an administrator has allowed you to, as gimmicks could easily fall under the purview of a mini-event and administrators have better tools in general for fixing bugs.
• Teleportation and rejuvenation should generally only be used if there is no other solution. The game must still punish players; we do not want to remove every single element of risk from the game. Try to reserve these powers for fixing bugs.
• You should only use the delete button to fix bugs or if you absolutely must (e.g. if you spawned the wrong item).
• Be reasonable when giving out languages, and keep in mind a species' maximum limit of languages.

Adminhelps and Complaints

• If a staff member is ahelped, preferably someone of a higher ranking should deal with the situation, otherwise another moderator or an admin of a lower or equal rank should handle the situation. For example, if a secondary admin is involved in an ahelp, a primary or headmin should take it. If no primary is around, a moderator can take the ahelp and solve it.
• If staff is directly involved in the situation, they should not take ahelps related to it. They should take the ahelp if there is no other option.
• Staff are considered involved in a situation when their actions are directly related to what is being ahelped in a way that they were subject to the effects of the action or they caused said actions. Being in round is not enough of a reason.
• If a moderator is the subject of a complaint, any admin, with the help of a moderator or another admin if they wish, should handle it.
• If a secondary admin is the subject of a complaint, a primary admin or headmin, with the help of a moderator or another admin if they wish, should handle it.
• If a primary admin is the subject of a complaint, a headmin, with the help of a moderator or another admin if they wish, should handle it. If a headmin or head dev is the subject of a complaint, another headmin or head dev, with the help of a moderator or another admin if they wish, should handle it.

Ban Appeals

• Staff is not obligated to unban anyone and can deny an unban.
• Two permabans are the limit. There are no third chances.

Non-canon Events

• Always make a vote in the round before, asking if people want a non-canon event. The vote should preferably be done after the transfer/emergency shuttle leaves the station. Do not run a vote during the lobby before the game starts, this will break the gamemode vote.

• Explain what the event is about, if it is going to be violent, and other details. It is not necessary to explain everything that is going to happen.

• Always set the custom event text with the basic information about your event. This can be done by using the Change Custom Event verb.

• Take into consideration the rules and atmosphere of the server. While some lighthearted shenanigans are fine, don't just run events that are just jokes or memes.

• Take into consideration who you are picking to be in a volunteer/event role. You should always check someone's notes before selecting them. While an admin might not be held accountable for something that an event character did, they can be responsible for ignoring someone's note and overall behavior.

• It is recommended that admins mute ooc. However, this is not mandatory.

• Don't run non-canon events consecutively. If someone ran an event today, wait some days to try to run another. No more than two events a weekend.

• These guidelines do not apply to minor adminbus stuff in the round, like helping antags with gimmicks or doing a vote to add something else to the round. This kind of thing is mostly based on common sense and if they will improve the round somehow.

• Always include a way for the crew to be able to deal with the opposing force, if such a force exists. It does not have to be brute force, but an intelligent way that you have hinted about throughout the round.

Midis

• Unless it is something related to what is going on in character, only play midis before or after the round.
• Do not spam midis, try to restrict yourself to one or two at most.
• Ensure to respect applicable copyright laws when playing midis.
• If staff is dealing with ahelps, do not play midis.