Administrative Guidelines
Jump to navigation
Jump to search
Staff Conduct Policy
Conduct we expect from Staff acting in an official capacity both in and out of the server.
If you have concerns with an admin violating any of these, make a complaint via a staff-ticket or PM a Staff Manager or a Head Administrator if you’re having an issue with high-ranked Staff.
Staff Preamble
As staff our goal here on the server is to create a fun healthy environment for all to enjoy, this means moderating the community and most importantly ourselves. If we do not act in a way that facilitates what we desire out of the server, then we cannot gear or push the community to how we desire it.
Staff Rules :
- Do not exploit any of your staff powers for in-game advantages. You may not use it to create an unfair disadvantage for others, nor may you use it for any abusive purposes.
- You must be on Discord to staff the server.
- Respect the chain of authority, the people higher on the chain then you have the final say on a matter ____________________________________________________________________
- Head Admins > Staff Managers > Administrators > Game Assistants > Moderators > Trial Moderators > Chat Moderators
- Maintainers have their own separate branch. Contact a Head Maintainer if a Maintainer's handling of technical tickets or use of ingame-tools are unacceptable.
- Do not involve yourself in any tickets that involve you, or someone you have personal connection to. This is for the sake of fairness towards the players.
- Do not interfere with a Staff’s admin-help or ruling if they are the same rank as you or higher. Feel free to point out important missed details in ASAY on a as requested basis.
- There is a minimal tolerance for drama between staff members. Keep it out of the staff ecosystem as much as possible. If needed, contact a Staff Manager.
- Privacy is paramount. Do not publicize IP(s), Computer IDs (cids), notes and bans anywhere outside of the staff channels, no matter where.
- You can talk about it with the person it belongs to, but don’t post images if you can, and blank any names/ckeys in those pictures. High-ranking staff members, such as Staff Managers and above, can share notes, bans, CKEYs, and Discord ID with the staff of other servers if requested and if deemed crucial.
General Staff Conduct Guidelines :
- Remember to be neutral. This means you shouldn’t be accusatory, derogative or condescending when addressing players.
- Do not take sides if a report comes in, until we have enough information to get a good idea of the situation. Ensure that both sides are heard out before judgment is rendered if possible.
- Maintain professional conduct both in game and outside of the game. It is expected that you take the position seriously. This doesn't mean you can't talk casually to the playerbase, but remain professional on the Discord, as well as on other Space Station 13 communities
- Do not interfere or try to “Add your own spice” to events being run by other Staff without asking first.
- Be careful using VV or testing our admin tools, you will be held liable if shit goes wrong.
- If you make an ahelp about an issue, do not talk about it in ASAY, until it has been resolved.
- ASAY is not a place for you to voice your discontent.
- You are expected to de-admin while playing sensitive roles. These roles include : Captain, Security, AI, Antags, Blueshield, Heads of staff. If you are the highest-ranked Staff online, you can stay admined, or if there are low staff count
- If you are not planning to take tickets, you should not remain admined up on the server for the sake of it.
- Ensure your discord name contains your CKEY, on the left side, or you are easily recognizable and reachable by players.
- If you wish to do events, ensure you have been active and sufficient in your recent staff work.
Ticket Conduct Guidelines :
- If someone is asking whether something was valid to do, IT IS A TRAP, give vague non answers, until you have EXACT context.
- Staff has the final say and ruling in the ticket, not the player.
- We do not take suggestions for punishments from players.
- Do not give rulings to situations that are expected to be held through multiple rounds.
- Check a player's notes and the like before handling issues surrounding them, it may provide context before going into the situation.
- If a situation is about a friend of yours, or involves one of them you are to separate yourself from that ticket, and not comment on it.
- if you have to handle it despite bias, just send it to someone to be looked over (staff manager) elsewise, try to find someone whom isn't
Rule Enforcement Guidelines :
- A player who makes a genuine mistake does not need to be punished but at the very minimum all instances need to be noted down for record keeping purposes, but genuine accidents can happen and are up to your discretion in those cases.
- Intent matters when dealing with a rulebreak. You should carefully assess the player’s intent behind their actions and adjust your ruling accordingly. Accidentally messing up shouldn’t be handled in the same way as acting with a complete disregard for the consequences of your actions on other players’ rounds, for example.
- Do not let salty deachat, players or Staff members in ASAY affect your decision. If need be, ask for second opinions to avoid bias.
Notes, Watchlists and Bans Guidelines :
Notes:
- [Round id, What role they were, what did they do, what rule was broken, how did they act in the ticket.]
- Example: Round 69420, as an Assistant, they went around attacking random members of Security without using CI, which is breaking CI policy. They were apologetic in ticket and understanding of where they went wrong.
- In terms of details, specifics as much as possible to help give people an idea of the situation without having to be there.
Watchlists
No.
Secret Notes:
- What watchlists should have been, information or noting down on a incident that we do not have concrete proof of, that we do not want players to see
Bans
- Same format as notes, but it is important to put down why it is a ban of that type i.e. server ban vs role ban. And the duration in the ticket, and its appeal date if permabanned (minimum 1 month, up to 6 months if they had a bad attitude)
Formatting for bans
- For in Game bans
- they should follow proper escalation as followed unless the incident is severe 1 day -> 3 days -> 1 week -> 2 weeks -> 1 month -> Permanent
- For Dead Chat bans
- *Do not note for this, toxicity in deadchat STARTS with bans not notes*
- The timings are: 1 week -> 1 month -> Permanent
- For Role/ghost/antag bans,
- they should be longer than the average game ban as they are less restrictive: 1 week -> 2 weeks -> 1 month -> 3 month -> Permanent
Event Running Guidelines :
TBD
- OPFORs that require Special Announcements, permissions, or the spawning of items beyond 1 or 2, and elsewise, require heavy oversight, should be classified as an event and will be required to be treated as such and need approval from Admin+ Staff or Event Staff as well as the proper logging.
To Do Opfor’s you must be atleast GA+, if you are below the rank of ga, and no other staff is available, then you may but note you must be strict as you will be held liable. Also You are not required to approve opfors.
Do’s and Don'ts
- Do not abuse your powers to spawn in items while you're in game for yourself or to benefit someone else who has not explicitly requested beforehand without approval from a Staff Manager +.
- Do not force a roll of an antagonist or spawn then roll for it yourself, optically it's incredibly bad faith on our part.
- Reminder if you're running an event or doing spawns for said event, DO NOT play as one of the spawns yourself and elsewise try to allow players themselves to take part of the spawns of said event.
- Do not approve OPFORs for the following:
- Standard Antags: Cult (Nar’sie), Gangs (the antag), Revolutionaries, Nukies, or Assault Operatives, as most of these (if not all) immediately fall into the event tier.
- Do not allow OPFORs that involve any form of exfiltration (i.e. do their objectives and fuck off) Midrounds: Morph, Blob, Space Dragon, Xenos, Borers, Spiders, or elsewise, Abductors.,
- You cannot approve your own events(Not Mandatory as of now, just talk to other online staff members first).