Policy/Administration

Administration

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

---

Administrative Precedents

---

PAGE UNDER CONSTRUCTION

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.
• Anyone with game server permissions is allowed to apply temporary / inconsequential punishments if a player is overly disruptive on an OOC level. This includes muting OOC, muting specific players from OOC for the round, etc.

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 cordial and impartial in admin tickets.
  • Intentionally being belligerent towards 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.
  • This can kick in if an admin becomes personally invested when otherwise attempting to handle a ticket impartially. Call another admin if you're getting heated.
• 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.
• Staff should keep each other accountable. Please bring concerns up with each other in staff-chat.
  • We are all here to collaboratively build a community; there is no ego, only right and wrong.
• Try to give players proportionate warning before serious consequences unless it is an egregious infraction.
  • Outside of cases of obvious grief and/or established hostility, avoid giving excessively long bans.
  • Players should generally be warned if they are spotted doing / planning a TK/PK (temporary/until-appeal removal of character) worthy action.
• Try to give IC punishments for IC infractions.
  • OOC punishments (full-job-bans, server bans) should be for OOC / rules infractions, or when a player is abusing their allotment of allowable IC trouble-making.
• Investigation is expected when handling a non-trivial ticket.
  • Logs do not provide full context. Always talk to everyone involved.
  • Logs may leave out context, but logs are factual. Validate the story of those involved before applying a punishment.

'Central Command' / 'Higher Authorities'

This section applies to all 'higher authority' roles. Central Command (potentially to be refluffed) is simply the authority for Nanotrasen. There are others, like faction leaders, other megacorporation executives / leadership, etc.

The word CCO refers to these characters / authorities. Use common sense, do not rules lawyer this section to the letter.

• Be professional (or act in character if your character is not meant to be professional). It hurts player confidence if staff are shit-posting as an IC that can literally fire them.
• CCOs may visit for the sake of visiting, even without a grievance.
  • As a CC visitor, they have no overrule authority.
  • As a CC officer, they do; they are expected to not show up as an on-duty officer trivially.
  • These are some of the only characters that have an exception to 'do not job swap by leaving and rejoining'. Staff are obviously expected to use common sense (ergo; extreme example: getting in a barfight as a visitor and then rejoining as an officer to flex is not acceptable).
  • A CCO visiting is still a CCO. Don't do stupid things like provoke fights or otherwise make players miserable.
• Do not dogpile players. There is absolutely no reason for more than 2-3 staff to join as CCOs outside of extreme scenarios.
  • It is an absolutely awful feeling to have all the administrators dogpiling you IC as in many non-Citadel servers this is what happens before you are banned. Do not propagate this. Wanting to watch is not a valid reason to join as a CCO.
• Using 'radio monitors' to speak for / as CCOs or just as the corporation is allowed.
  • Use common sense. If there's an event that all subspace communications to command are suppressed, don't start shitposting over the traffic monitor if the traffic monitor is lightyears away.

Ascension Clause

'Ascending' existing player characters to a CCO-equivalent is not allowed without prior authorization from a head administrator and discussion with the staff team.

• Existing CCOs at time of writing (4/15/2024) are grandfathered in and are allowed to continue being used.

Fraternization Clause

After a colossal clusterfuck in the ancient eras of the server's history, under no circumstances are CCO-equivalent characters allowed to engage in ERP while in game.

• ICly, if you were too attached to a significant other / associate to the point of losing your impartiality, you would not be allowed to continue making decisions regarding them / their posting by any reasonable corporation.