Staff Code of Conduct, Procedures, Protocols

Locked
User avatar
apophis775
Host
Host
Posts: 6985
Joined: 22 Aug 2014, 18:05
Location: Ice Colony
Byond: Apophis775
Contact:

Staff Code of Conduct, Procedures, Protocols

Post by apophis775 » 25 Apr 2015, 15:46

This topic, is public, because I want all players to know both the rights we are ensuring them, and our admin procedures so that any complaints or appeals are resolved as fairly as possible.

---THIS DOCUMENT IS IN PROGRESS ---

Section 1 - Ranks and their Jobs:

Host - Apophis775
The job of the Host, is to keep the server and forums running smoothly and manage the entire staff. His job is also to ensure that this document is followed by all staff, and to make sure that they staff is accountable for their actions. Finally, the host must ensure that all appeals, applications, and complaints, are processed fairly and without bias.

Vice Host - Rahlzel
The job of the Vice Host, is the same as the Host. He has the same authority as the Host on the server and forums. He has the additional job, of keeping the Host in check, and ensuring the Host also follows the Code of Conduct.

Head Admin - SASoperative
The job of the Head Admin, is to manage the admin staff. He has final say in all ban appeals, the hiring and firing of staff, and will investigate complaints against any staff (unless he is involved, then the Host will investigate). He must also ensure that all staff are following the procedures in this document, and ensuring fairness with all complaints, applications, and appeals. He can over-rule the Head Moderator in decisions, but MUST provide sufficient reason.

Head Moderator - Lostmixup
The job of the Head Moderator, is to help manage the admin staff. His focus, is training new moderators, and performing the staff reviews at the end of their trials. He will accept/deny applications and staff members, but can be over-ruled by the Head Admin. His job, is also to investigate complaints against players, and review ban appeals. He has the authority to approve or deny ban appeals, though he can be over-ruled by the Head Admin, if there is sufficient reason. He is also charged with making sure staff are following the procedures in this document.

Game Admins
The Game Admins, are more serious levels of admins, their job is to handle ahelps on the server that are escallated to them by moderators, as well as help when the moderators are offline or overwhelmed. In addition, they are the lowest rank able to run events and issue permabans (though, there is a process). They are also responsible for helping guide new moderators and trial admins, into making good decisions.

Trial Admins
Trial admins, hold the same powers as Admins, with the exception of not being allowed to run events without a full game admin present as well. After 1 month of the trial, the performance of the Trial Admin is reviewed and either accepted as a Game Admin, returned to Moderator, or extended an additional month.

Moderator
The moderators, are the police of the server. Their PRIMARY FOCUS is to ensure that rules are not being broken, and that the integrity and fun of the server is maintained. Player enjoyment and enforcement of the rules, are their top two priorities. However, the rules are NOT unbend-able, and if bending a rule allows the server to have fun, then the moderator must use their own judgement to determine the course of action. The most important thing, is that we are making sure players are enjoying themselves as best we can, remember that.

Trial Moderators
These are the potential new moderators. They have VERY limited powers, and should be given the chance to answer any ahelps, before anyone else. Moderators, Admins, and staff should help them through the ahelps, and only take over if the situation is escallating. This is a 2-week trial period, and after the 2 weeks, they will be promoted to full moderator, extended, or demoted back to play.

Mentors
Mentors are the small percent of people who know about the mechanics and lore of our server and SS13 who are willing to share their knowledge with new players. They have little to no power and should only be replying to ahelps regarding questions about the game or how to do a certain thing such as what caste does what etc. They are NOT moderators

Development team
The development team, contains many ranks. All of them, hold the equalivent rank of a moderator on the server, but have custom permissions. Their PRIMARY JOB is development, and will only aid the mod/admin staff when necessary. They are also bound, by the same procedures and code of conduct in this document.



Section 2 - Code of Conduct:

The Admin Code of Conduct is the code by which ALL STAFF will be held accountable. Violations, will result in at least one strike. 3 strikes, and your demoted. Strikes will have a duration, dependent on their severity ranging from 2 months, to permanent.

0. NEVER ABUSE YOUR POWER
This should go without saying, but abusing your power as staff, will result in swift punishment.

1. Remain Professional, no matter what happens.
Even if a player is swearing up and down at you, keep your composure, and remain professional. I understand you may get angry, and if a player is out of hand, you are free to mute them until they are ready to have a calm conversation. At no time, should you be calling them horrible names or swearing profusely. I understand, due to the nation of the internet that there is a degree of Saltiness (I know I'm FAIRLY SALTY) and I understand that. But don't go around calling people horrible names in Ahelps. Save that for Msay/Asay.

2. Preserver the RP and enjoyment of the server
If, a player breaks a minor rule, but it contributes to either the RP or enjoyment on the server, that does not necessarily mean they need to be punished. If noone ahelps a complaint, or seems to be complaining or taking issue with it, it may be best to let it go. We are a game server, not Nazi Germany.

3. Enforcement of the rules
Enforcement of the rules, should be done so that if someone is receiving a punishment, they know what they did. Also, you should ensure you do an adequate investigation into the incident before punishment. Also, any punishment should fit the violation, adjusted for past actions.

4. Follow the orders of the staff above you
If your a moderator, and an admin tells you to cool down and let something go, let it go. If it's a big issue, bring it up on the Admin Skype or the admin forums. But nothing will be gained, by staff fighting among themselves on the server, especially if your directly going against a decision publicly.

5. Clock In and Clock Out
We use the Clock in and Clock Out verbs to track time your on the server, as well as determine that your not inactive. Remember to use these.

6. Only HEAD STAFF may give the nuke codes
If the game has gone for 2-3 hours and is stagnating (aliens and marines avoiding combat), Head Staff may authorize the nuke code ONLY if the marines have not secured the disk or code yet.


Section 3 - Protocols:

These procedures, server as GUIDE to enforcement of the rules and other violations on the server. They should be followed as closely as possible, however, a staff member MAY divert from these, during extenuating circumstances, but will be expected to justify WHY they broke from procedure.


1. Message
Send a violator a message, asking them to explain their actions. Give them an ADEQUATE time to respond. They might not be able to respond that second. If there is a group running and fighting, over OOC tell everyone to STOP so you can deal with the situation. This can get hectic, and you can message anyone involved, to Stop in order to speed things up.

2. Investigate the situation
Contact anyone involved and get their side of the story. Also, check logs (there will be a how-to guide up soon, to explain how to check logs, view variables, etc). It may not be immediately visible WHO caused the situation, and you may need to talk to several people to figure it out. Try to do this as quickly as you can, but also as thorough.

3. Determine how serious the violation was
This is very important, because the seriousness, should match the punishment. For example, changing someones ID, is not ban worthy, but killing several marines is.

4. Determine the players history
Check the players notes. If they frequently break the same rule, then the punishment may need to be more serious. If they haven't had a new note or violation for a few months, it might be best to give them a more minor punishment.

5. Determine the punishment.
Try to determine the most minimum punishment possible. There's no reason to jump DIRECTLY to a ban, especially if the incident didn't cause a major disruption to the game. Try to use warnings, and if you do need to ban, don't go excessive. There are very few reasons to ban more than 12 hours. (Sample ban numbers will be in another section of this document). If you feel someone needs to receive a permanet ban, give them a ban for 14000 minutes (10 days) and make a post in the Permaban Request section of the admin forums, explaining the situation, and why you believe a permaban should be enforced. This should ONLY be done for repeat offenders, or direct griefers.

6. TAKE NOTES.
Explain the situation clearly in a player-note on their c-key. The note, is your method to explain the situation, and the circumstances. Evne if it's a verbal warning, give a note. In the note, make sure, you state the violation, punishment, and resolution. Also, remember that notes will be made PUBLIC on player request, application to staff, or ban appeals, so be professional.


Section 4 - Standard Procedures

This section, contains the standard procedures for some of the incidents that happen, to better guide staff in decisions. This is a guide, and the staff MAY divert during extenuating circumstances, however they will be required to explain why they diverted, if it becomes an issue. And remember, try to go for the LOWEST punishment you can if they are a first-time or only occasional offender (when you check their notes, if they have no offenses, or only offenses from a long time ago).


1. ERP
If a player is simply "hinting" at ERP, give them a stern warning that ERP is not tolerated. However, if a player is acting out an ERP session and players are complaining, they should be immediately told that ERP is permabannable, and then Permabanned. ERP is the *ONLY* time that a permaban can be given by staff without requesting it through the permaban area in the staff forum. No ERP is also a ZERO TOLERANCE. However, simply posting a link to anything that should be 18+ does not mean they are ERPing. If that happens, give them a stern warning that next time they will receive a ban. If they repeat the infraction, give them a 10-day ban.


This is still a work in progress, and more is on the way.

Locked