​

A-1.1 — Server Leak / Sabotage

Deliberately causing harm to the server through massive, conscious, or intentional violations of the staff regulations, as well as by any other means.

​

A-1.2 — Sabotaging Players and Staff

Deliberately targeting/harassing players or staff members, focused targeting, as well as abuse of the report/ticket system for biased persecution. The punishment is issued for documenting a deliberate “hunt” on a player or another staff member, even if the submitted complaints have actual grounds.

​

A-1.3 — Interference in the RP Process

Staff members are strictly prohibited from interfering in the players’ RP process.

​

A-1.4 — Interference in Other’s Reports/Complaints

It is prohibited to interfere in complaints/reports of other staff members without their permission, both in-game and in Discord tickets. Any word written off-topic regarding complaints of other staff members will be considered a violation of this rule.

​

A-1.5 — Using Staff Capabilities Off-Duty

It is prohibited to use staff capabilities while off-duty. The use of any mod commands off-duty is governed by rule B-1.2.

​

A-1.6 — Unauthorized Events

It is prohibited to host events unless you are an Event Maker.

​

A-1.7 — Negligence and Inappropriate Behavior

Negligent or inappropriate behavior while on duty is prohibited.

​

A-1.8 — Threats of Punishment

It is prohibited to use punishments or threats of issuing them for personal purposes, to intimidate players, or during personal conflicts.

​

A-1.9 — Ignoring Orders of Management

It is prohibited to intentionally ignore directives from a higher-ranking staff member, senior, or executive staff.

​

A-1.10 — Reviewing Staff Complaints

Regular staff members are prohibited from reviewing complaints about violations by staff.

​

A-1.11 — Conflict of Interest

It is prohibited to review complaints involving yourself if you participated with the player in the same RP scene.

​

A-1.12 — Insulting Players

ER:LC staff, team leads, management, and executive/senior leadership are strictly prohibited from showing disrespect, using profane language, provoking, or in any way insulting players. This rule applies to all staff and administration representatives without exception, regardless of whether the staff member is on duty, personal relationships, or the platform of communication (in-game, Discord, or direct messages).

​

A-1.13 — Using Mod Privileges for Personal In-Game Benefits

It is prohibited to use moderator rights to obtain in-game privileges that are unavailable to regular players through the server settings. Such privileges include: spawning restricted vehicles, obtaining weapons that are locked by server restrictions, and any other in-game features unavailable to players due to the rules or server configuration.

​

A-2.1 — Mandatory Recording

Every staff member is required to record their screen with audio while performing their duties. The recording is necessary to confirm the validity of punishments and resolve disputes. The recording must be stored for at least 3 days.

​

A-2.2 — Favoritism and Abuse of Privileges

It is prohibited to exceed the authority of your granted privileges, cover for friends, or interfere in punishments and complaints related to your friends.

​

A-2.3 — Proportionality of Punishment

The punishment must be proportional to the committed violation.

​

A-2.4 — Unjustified Removal of Punishments

It is prohibited to lift restrictions from a player unless there is a justified reason, a ticket decision, or a directive from senior staff.

​

A-2.5 — Disclosure of Internal Information

It is strictly prohibited to disclose internal information, correspondence, decisions of the staff, as well as to broadcast any internal chats (inaccessible to ordinary players) on screen shares, streams, publish their photos, screenshots, or distribute them in any other way.

​

A-2.6 — Disclosure of Confidential Information

If the project leadership or management has instructed not to disclose certain information (whether it is plans for future updates, upcoming personnel changes, internal investigations, technical details, or any other information), staff members are strictly prohibited from sharing or distributing it in any form.

---

​

B-1.1 — Violation of the Punishment Issuance Form

Expand rules for formatting and working with bots

All punishments (warnings, kicks, bans) must be processed through the special ER:LC Россия Roblox bot using the /наказание выдать command.

Punishments issued without being registered through this bot are considered invalid.

Important: Absolutely any Kick or Ban issued by you (whether on-duty or off-duty in an emergency situation) MUST be registered through the bot. Issuing punishments without recording them in the bot is considered a violation of regulations.

​

Rules for filling out the reason

When issuing a punishment through the bot, in the “reason” line you must specify: W1, W2, W3 (which session warning this is for the player), the RULE POINT, and a Detailed description of the violation.

• Example of correct filling:

​

Formatting Ban/Ban Bolo

The Ban/Ban Bolo formatting must be detailed in exactly the same way.

Important to understand: BAN ≠ Ban Bolo. Ban is a command that can only be used from the Administrator rank. Ban Bolo is a ban request that is verified by Administrators and higher.

• Example of Ban/Ban Bolo formatting:

​

Using bot commands

All non-in-game commands must be used by the staff member only in the special “🤖┃бот-команды” channel under the “Персонал ER:LC” section.

• Example of the channel:

​

B-1.2 — Reporting on Commands Off-Duty

Any use of staff commands off-duty requires a mandatory report via the /отчёт команды command. The report must specify:

• Which commands were used.
• Reason for use.
• Time of command application.
• Link to the command log (from the ”📑┃история-команд” channel).

---

​

C-1.1 — Disciplinary System and Limits

The server implements a strict division of punishments based on the severity of the misconduct:

• Verbal warning — issued for a fixed term for minor violations.
• Official warning (Warn) — issued for significant misconduct. Every 3 warns automatically convert into 1 strike.
• Strike — a critical measure. Strict limits apply:
  • 2 strikes — temporary suspension from duty, initiation of an investigation, and possible demotion.
  • 3 strikes — automatic termination from the staff.

​

C-1.2 — Order of Issuing Punishments

1. [Verbal Warning] ⟶ Initial stage for minor misconduct.
2. [Warn #1] ⟶ [Warn #2] ⟶ [Warn #3]
   • Automatic conversion: (STRIKE #1)
3. [Warn #1] ⟶ [Warn #2] ⟶ [Warn #3]
   • Automatic conversion: (STRIKE #2) ⟶ [Temporary suspension + internal investigation]
4. (STRIKE #3) ⟶ ⚠️ [AUTOMATIC TERMINATION FROM STAFF]

​

C-1.3 — Emergency Situation Rules

• Instant strike: Management has the right to issue a strike immediately, bypassing the warning stage, if the staff member’s misconduct is deemed gross.
• Instant termination: A staff member is terminated without discussion for: disrespect to the owner, abuse of power, sabotage, or causing critical damage to the project.
• Registration: All warns and strikes must be recorded in a special log channel.
• Investigation: Investigations and audits within the staff are conducted exclusively by the Internal Affairs Team and the Staff Manager.

​

C-1.4 — Step-by-Step Algorithm for Resolving Misconduct

The disciplinary regulations are mandatory for everyone, including management. Any incident goes strictly through four stages:

1. Recording: The fact of misconduct is recorded by the log system or other staff.
2. Explanatory statement: The staff member is required to provide written explanations in a duty ticket to defend their position. Deadline: 48 hours (if the staff member is in-game — 4 hours). Refusal equals admission of guilt.
3. Review: The staff manager or Internal Affairs Team reviews the arguments and renders a verdict.
4. Penalty: Official notification (penalty order) specifying the reason, term, and type of disciplinary action.

---

​

D-1.1 — Distribution Standards for Various Player Counts

The number of staff on shift and their positioning strictly depend on the current number of players on the server.

​

D-1.2 — Staff Placement Points

Fixed points are set for staff to stay in standby mode (spawn, MVD, hospital, EMERCOM, large public places).

• Point limit: No more than two staff representatives may be at one point simultaneously.
• Grouping prohibition: It is prohibited for more than three staff members to stand together. Staff must be evenly distributed across the map and not gather in one place without duty necessity.

​

D-1.3 — City Patrols and Response

Every active staff member is required to maintain dynamic control over the situation on the server.

• Frequency: In the absence of urgent requests (tickets/mod calls), the staff member must go on a city patrol every 5–10 minutes.
• Patrol procedure: Patrol is carried out in duty transport through the city and problem areas, after which the staff member returns to their position.

Response to mod-calls: During patrol, the staff member must promptly accept mod calls if they are closest to the incident site. After resolving the call, they must continue the patrol or return to the point.

​

D-1.4 — Violation of Staff Balance

Ignoring patrols, constant groundless grouping of three or more staff members in one point, or refusing to distribute across the map is considered a violation of discipline.