Administrator Code

An administrator must not abuse or misuse their powers - to harm a player, for personal benefit, for entertainment (blinding, killing, gravity, beacons, ignition, etc.), or for the benefit of friends or third parties.

An administrator must be competent, polite, and respectful toward all users. Insulting or humiliating users is forbidden.

The administrator is required to keep evidence of each punishment (screenshots or demo recordings) for 3 days and provide them at the request of the curator, deputy creator or creator. Penalties for which no evidence has been provided are abolished.

An administrator must be able to state the reason for any sanction and produce the supporting evidence on request from the user, a curator, or a higher rank. Disputes about sanctions are handled in the Complaints section, not in chat.

The administrator is obliged to control the gameplay, timely prevent various incidents that may entail violation of server rules and loss of online.

When a complaint is filed against an administrator, the administrator must clearly state the reason for the sanction and attach evidence (screenshot or video) provided the complaint is properly filed.

If an administrator issues a sanction in error, they must report it in the errors thread for correction.

An administrator may not cancel, change, or publicly debate another administrator's actions during play. Concerns are raised privately in the admin team chat or escalated to the server head; a higher-ranked administrator may pause an active sanction and review it.

An administrator may not lift another administrator's sanction or chat block without that administrator's consent or the consent of the deputy creator.

An administrator must not disclose the contents of administrator conferences or private team communications to third parties.

An administrator must not slap, freeze, ignite, intoxicate, or blind players during a round. Admin-panel functions may be used for entertainment between rounds only when (a) every player on the server consents and (b) the function is not used as punishment for a rule violation.

An administrator may use admin powers under any nickname to identify violations. All actions taken under any nickname are logged against the administrator's real account; curators audit such actions periodically.

Administrators must not invent rules of their own.

For situations not described in the rules, an administrator may use only soft measures (warning, single-round slay, kick) and must escalate to the server head before issuing any chat block or ban. Inventing new offenses is forbidden under 1.13.

An administrator must not argue with the red administration (deputy creator, curator, creator) in public channels. Disagreement is raised respectfully in the admin team chat or via direct message; appeals against red-administration decisions are filed on the forum.

Project administration must issue sanctions only on the basis of objective rule violations, not on personal hostility or coordinated targeting of a specific user or group ("phantom violators"). This does not refer to ordinary complaints - it refers to a sustained wave of complaints across many alleged violations against the same target. Suspected coordinated targeting is reviewed by a curator panel.

It is categorically forbidden to conduct or request any inspection or search of a user's social media accounts, regardless of suspicion or complaint. This applies to personal messages, direct messages, and group chats (public or private) on Telegram, VK, Facebook, Discord, WhatsApp, Instagram, and any other third-party platform. Off-platform conduct is handled exclusively per Main Rule 2.26 - the complainant supplies verifiable evidence; administrators do not access user accounts or browse their content. Any attempt to do so is itself a violation.

In case of departure or upcoming long-term absence, the administrator is obliged to inform the server manager about this.

During inspections, administrators of any rank must not require disclosure of personal data, in accordance with Federal Law No. 152-FZ on Personal Data and applicable local data protection law.

Project administrators may not hold administrative rights on third-party gaming projects or servers.

Conflict of interest. An administrator must not moderate clan members, close personal contacts, or anyone with whom they have an active personal dispute. Recuse and pass the matter to another administrator.

Proportionality. An administrator must apply the lowest sufficient measure first (warning → chat block → temporary ban → permanent ban). Permanent bans require a rule that explicitly authorizes them or sign-off from a curator or higher rank.

An administrator must not retaliate against a user for filing a complaint. Complaints against an administrator are handled by an uninvolved curator or a higher rank.

Audit logging. Every ban, mute, kick, or other administrative action is logged with administrator ID, rule cited, evidence reference, and timestamp. Failure to log an action is treated as failure to retain evidence under 1.3.

Server-wide actions such as map changes are made only on the basis of a positive vote.

First violation of the general or specific rules: warning.

Repeat violation, or failure to perform admin duties: removal of admin rights on the server and the corresponding site status.

Transferring the account to a third party: rights revoked without right of recovery.

Voluntary resignation: removal of rights.

Inadequate behavior on the game server. "Inadequate behavior" means: harassing users, abusive language directed at users, or a sustained pattern of complaints upheld by curators. Single, contested incidents are handled under section 3.

Receipt of a VAC or game ban: rights revoked without right of recovery.

Using one's privileges for personal gain or fraud (selling VIP, experience, or other in-game benefits outside the official store): removal of rights.

In case of violation or non-compliance with the rules.

If a recruited administrator does not appear on the server for more than 15 days: removal of rights.

Three errors (unfounded sanctions, use of admin panel for entertainment, etc.) within 90 days: removal of rights. Each error must be logged in the curator-visible errors thread, the administrator notified within 7 days, and given an opportunity to dispute before the count increments.

03.05.2026