Skip to content

Staff Handbook & Moderation Guide

Core rule: NO STAFF ABUSE. Staff permissions are a responsibility, not a reward. Every staff member is expected to act fairly, protect the community, and follow this handbook regardless of rank, friendships, or personal disagreements.

1. General Staff Expectations & Code of Conduct

Lead by example

Your behavior sets the standard for the community. Avoid toxicity, public arguments, harassment, and trash talk in public chat or Discord. Staff must remain calm even when players are rude, frustrating, or trying to provoke a reaction.

Zero privilege abuse

Staff permissions such as /vanish, /tp, /gamemode, /fly, /co i, /god, and /invsee exist for legitimate moderation and server safety only.

  • Never use vanish or teleportation to spy on enemy bases during active gameplay or wars, or share intel with friends.
  • Never spawn items, spawn eggs, currency, ranks, or gear for yourself or players.
  • Never use staff commands to win fights, gain resources, avoid consequences, harass players, or settle personal disputes.
  • Never use inventory inspection, logs, or private staff information out of curiosity or to benefit yourself or friends.
  • Never threaten players with your rank, commands, or connections.
  • Never leak staff channels, ticket discussions, evidence, or internal decisions to regular players.
  • Never use an alternate account to bypass staff restrictions or hide misconduct.
  • Use only the permissions needed for the task and follow role restrictions.
  • If you accidentally use a command incorrectly, stop, preserve the relevant information, and report it to a Manager or Owner immediately. Do not conceal or delete evidence.

Policy supplied by server leadership: privilege abuse can result in immediate demotion to Default, a permanent ban, and ineligibility for future staff applications. Owner/Manager leadership should review context and apply current official policy. Rank does not excuse misconduct; allegations against senior staff must be reviewed by a higher or independent authority where possible.

Evidence standard

Attach evidence to every mute, kick, temporary ban, or permanent ban. Post evidence in the designated private #staff-evidence channel and retain it for at least 90 days for appeals, subject to applicable privacy and retention rules.

Hacked-client reports: collect at least 15 seconds of continuous, unedited footage; 30 seconds or more is preferred. Include relevant target HUD, latency context, and observable behavior where possible. Claims such as “they admitted it in DMs” or “everyone knows they x-ray” are not sufficient evidence on their own.

Chat violations: use full-screen, unedited screenshots with timestamps, or raw log excerpts that preserve context.

  • Preserve original files. If a clip is needed for review, create a clearly labeled copy rather than altering the original.
  • Record who collected the evidence, when it was collected, and which rule it may demonstrate.
  • Do not crop away relevant context, edit clips to make a player look guilty, or present speculation as fact.
  • If evidence is incomplete, keep investigating or ask a senior staff member for guidance instead of guessing.

Professionalism in tickets and public chat

Players may be upset or try to provoke staff after a punishment or denied appeal.

  • Do not roast, bait, or argue with players in public chat or ticket threads.
  • Do not use sarcastic or passive-aggressive reasons such as “cya bozo” or “enjoy the break kid”.
  • Use clear, neutral, standardized reasons so later appeals can be reviewed fairly.
  • Do not promise refunds, unbans, rollbacks, or appeal outcomes without the required authorization.
  • If a conversation becomes heated, pause and ask a Manager to take over.

2. Fair and Consistent Enforcement

  • Check the relevant history and available evidence before choosing a punishment.
  • Use the punishment matrix as a guide, not a substitute for reviewing context.
  • Consider severity, intent where it can be established, prior history, impact, and the written rules.
  • Apply rules consistently. Friends, donors, popular players, and staff members are not exempt.
  • Do not punish a player because they criticized staff, reported a staff member, or declined to do you a favor.
  • Do not increase a punishment to “teach them a lesson.” The action must be proportionate and rule-based.
  • If the correct action is unclear or outside your authority, pause and escalate.
  • Record the reason, duration, evidence link, and action taken in the appropriate staff log.

3. Confidentiality and Account Security

  • Never share staff passwords, authentication codes, private ticket links, or access tokens.
  • Use unique passwords and multifactor authentication on staff accounts where available.
  • Share evidence only with staff who need it for a legitimate review.
  • Do not copy or disclose personal information beyond what is necessary to investigate a report.
  • Do not download, retain, or circulate personal information without a legitimate need and approved process.
  • Report suspicious links, unexpected login prompts, and possible access leaks to the Owner/Manager.
  • Never ask a player for their password, authentication code, or account recovery details.
  • If you suspect your account is compromised, stop using staff permissions and contact leadership immediately.

4. Appeals and Review

Review appeals calmly and impartially. Check the original evidence, punishment history, applicable rule, and staff notes.

  1. Confirm which punishment is being appealed and who issued it.
  2. Read the original evidence and the player's explanation.
  3. Compare the action with the rules and punishment matrix.
  4. If possible, have a staff member who was not directly involved review a disputed action.
  5. Record the outcome and the reason for it.
  6. If the evidence is missing, contradictory, or insufficient, escalate rather than automatically defending the original decision.

Never retaliate against a player for appealing or reporting a staff member. An appeal is a review process, not a personal challenge.

5. Escalation

Escalate immediately for real-life threats, doxxing, IP leaks, staff privilege abuse, possible data exposure, large-scale exploits, and cases where staff safety or server integrity may be at risk. Do not repost private information in public channels.

Escalate to a Manager or Owner when: - A case may lead to a permanent ban and you are not authorized to issue one. - The evidence is ambiguous or a punishment may be unusually severe. - A staff member is accused of misconduct. - A report involves a friend, rival, teammate, or someone you have a conflict with. - You suspect a serious exploit, account compromise, or a coordinated attack. - You are unsure whether a command or action is permitted.

If the allegation involves the person you would normally report to, contact another appropriate senior leader. Do not let the subject of a complaint control the evidence or decide the outcome alone.