Policy/Administration

Administration

Global Policy | Server Rules | Silicon Policy | Administrative Precedents
Standard Operating Procedures | Corporate Regulations

---

Administrative Precedents

---

Administrative Protocols

This page contains procedures and precedents for administrators.

• An administrator is anyone with game server permissions. This includes event managers and maintainers.
• This page is intentionally (relatively) informal. This is a roleplaying game, not a corporate service. We expect staff to represent the server's community and ideals, not act like machines.

Roles

In-game staff roles currently consist of:

• Administrator: Responsible for handling player disputes, policy questions, etc.
  • Trial Admins are not lower ranked than Game Admins; it simply symbolizes a learning period for new staff.
• Maintainer: Given server permissions as codebase maintainers.
• Event Manager: Given server permissions to run events / storylines.

What staff can / can not do:

• Non-administrators should not handle player / policy disputes in most cases.
• Administrators / Maintainers can run events if they choose to, as long as they abide by the standards set for events.
• Anyone with game server permissions is allowed to interfere with the round if said interference abides by the standards set for events.

General Protocol

These are things staff are generally expected to follow.

Slip-ups happen. We will not side with you if you are obnoxiously hostile to staff over a mistake that is insignificant in the long run. Don't be a dick.

• Staff are expected to remain professional and impartial in admin tickets.
  • Being obnoxiously hostile to staff may net you snarky responses in return. Staff are still human.
• Staff are expected to not handle tickets that they are involved / personally invested in / otherwise unable to make an impartial call.
  • This applies to everyone, including head admins. We have a staff team for a reason.
• Staff are generally expected to not share data / knowledge only they know that players are trying to conceal.
  • Example: character names - while normally not an issue, some players prefer having their identity be on the down-low.
  • Anti-example: Whether or not something was sabotaged. After the round, staff are free to share anything they know about general round flow for transparency reasons.
  • Pseudo-example: Specifically who did an otherwise stealthy sabotage. Remember, players might have characters trying to be stealthy. Don't ruin it for them.