Staff Regulations for ER:LC

The Regulations are an instructional document that describes in detail the procedures, rights, duties, and action algorithms in various situations. It has a strictly normative and applied character. If the code of ethics answers the question “Why do we act this way?” and “What principles do we follow?”, then the regulations provide a clear answer to the questions “What exactly to do?” and “How to do it?”. It standardizes processes, minimizes ambiguities, and serves as a direct guide to action with clear criteria for compliance or violation.

---

• A-1 — Prohibitions:
  • A-1.1 — Violation of subordination — public disputes with management, ignoring orders without reason.
  • A-1.2 — Abuse of authority — punishments without grounds, misuse of commands.
  • A-1.3 — Inappropriate behavior — insults, provocations, aggression, violation of the RP process.
  • A-1.4 — Violation of work format — punishments without reason, without speaking to the player when necessary.
  • A-1.5 — Arbitrary actions — unauthorized changes to rules, server structure, assigning/removing roles without management approval.
  • A-1.6 — Insulting players or staff.
  • A-1.7 — Disputes with the owner/management.
  • A-1.8 — Disrespect towards superiors.
  • A-1.9 — Using authority for personal purposes.
  • A-1.10 — Deleting messages without reason.
  • A-1.11 — Abuse of mutes, kicks, and bans.
  • A-1.12 — Ignoring complaints from players.
  • A-1.13 — Training players in a fraction without the leader’s or senior staff’s permission.
  • A-1.14 — Making personnel decisions without coordination (except for the owner/co-owner).
  • A-1.15 — Violation of subordination even outside the server.
  • A-1.16 — Violation of behavior in voice channels — conflicts, aggression, moving participants without permission.
• A-2 — Permissions:
  • A-2.1 — Apply punishments (mute, kick, ban) strictly according to rules and format.
  • A-2.2 — Report violations by players/other administrators to higher-ranking administrators.
  • A-2.3 — Maintain order in chats and on the server.
  • A-2.4 — Communicate with players while respecting boundaries.
  • A-2.5 — Request clarifications from higher-ranking staff in private.

---

• B-1 — Processing Punishments:
  • B-1.1 — All punishments (warns, kicks, bans) must be processed through the special ClueControl M bot using the /punish command.
  • B-1.2 — Punishments issued without processing through ClueControl M are considered invalid.
  • B-1.3 — When issuing a punishment through the bot, specify in the “reason” field:
    • The exact rule item.
    • A detailed description of the violation.
  • B-1.4 — Ban/BOLO processing must be formatted as follows:
    Ban/BOLO reason ban/BOLO duration
    Example: Ban I MSRDM I duration 7 days
  • B-1.5 — All commands not related to gameplay must be used only in the ”🤖┃bot-commands” channel in the “ER:LC Staff” section.
• B-2 — Issuing Punishments:
  • B-2.1 — Before processing a punishment through the bot, the administrator is required to notify the player of what exactly they violated.
  • B-2.2 — Standard punishment format:
    W(number)/Kick/Ban | Rule Code — Specific reason
    • Example:
      • W1 | A-3 — Conducting an auto rally without administration permission.
      • Kick | D-1 — Driving a sports car off-road, ignoring traffic rules.
      • Ban | Mass RDM — killed many people at spawn.
  • B-2.3 — The reason must contain not only the rule number but also a specific description of the violation.
  • B-2.4 — Issuing a punishment without first checking the punishment history via the /search command is considered a violation.
  • B-2.5 — Punishments not processed through ClueControl M are considered invalid.
  • B-2.6 — When processing a punishment, specify:
    • The exact rule item
    • A detailed description of the violation
  • B-2.7 — After that, the administrator must issue a notification to the player using the template:
    • For a warn:
      
      You need to wait until the punishment is processed through the special ClueControl M bot.
      You can appeal the punishment ONLY through a ticket.
      
    • For a kick:
      You cannot join for one hour, otherwise a BAN will follow.
      Note that this rule applies if the player received three warns in one gaming session.
      In other cases, such as systematic interference, you must give the player several verbal warnings and only then apply a kick.
      
    • For a ban:
      
      You will be banned. You can appeal on our community Discord server - MoscowRus.
      
  • B-2.8 — Punishment without proper processing is grounds for disciplinary action against staff.
• B-2 — Reports on Administrative Commands Outside of Shift:
  • B-2.1 — Any use of administrative commands outside of a shift requires a report via the /report command command.
  • B-2.2 — The report must include:
    • Which commands were used.
    • Reason for use.
    • Time of command application.
    • Link to the command log (from the ”📑┃command-history” channel).
  • B-2.3 — It is allowed to combine several commands into one report if they were applied within the same situation and close in time.
  • B-2.4 — For different situations — separate reports.
  • B-2.5 — Absence of a report — warning for 1 week.
  • B-2.6 — These rules apply even in emergency situations (raids, mass violations): after eliminating the threat, process all punishments according to regulations.
  • B-2.7 — Appropriateness and justification of command usage:
    • Having a report does not justify unjustified use of powers. Any actions outside of a shift are subject to strict review by senior staff.
    • Using commands with formal or non-constructive reasons (e.g., :tp with reason “needed to”, “just because”, etc.) is considered a violation.
    • It is prohibited to use the :load or :respawn command if the player had the technical ability to use the standard respawn button. Using commands to shorten the path or bypass game death mechanics is equated to admin abuse.
• B-3 — Recording and Documentation:
  • B-3.1 — Each employee is required to record their screen with audio while performing their duties.
  • B-3.2 — Recording is necessary to confirm the correctness of punishment issuance and to resolve disputed situations.

---

• C-1 — Disciplinary Measures:
  • C-1.1 — System of violations and punishments:
    • C-1.1.1 — For a minor or insignificant rule violation, a verbal warning is issued for a specified period.
    • C-1.1.2 — More serious violation:
      • Official warning.
      • After 2 warnings, a reprimand is issued on the 3rd warning.
    • C-1.1.3 — Reprimand system:
      • 2 reprimands — internal investigation and temporary suspension, possible demotion.
      • 3 reprimands — dismissal from staff.
  • C-1.2 — Example scale:
    • Verbal warning.
    • Official warning.
    • Official warning.
    • Official warning ⟶ first reprimand.
    • Official warning.
    • Official warning.
    • First reprimand + second reprimand ⟶ internal investigation, suspension.
    • Third reprimand ⟶ dismissal.
  • C-1.3 — Notes:
    • C-1.3.1 — A reprimand may be issued immediately, without three warnings, if the violation is very serious.
    • C-1.3.2 — Serious violations (disrespect to the owner, abuse of power, sabotage) — immediate removal of authority and dismissal without discussion.
    • C-1.3.3 — All warnings and reprimands are recorded in a separate channel.
    • C-1.3.4 — Internal investigation is conducted by the Roblox Internal Affairs Team.
    • C-1.3.5 — In case of serious damage to the server or team, immediate removal of authority is applied.
• C-2 — Disciplinary Procedure
  • C-2.1 — Recording the violation — staff or the log system records the fact of the violation.
  • C-2.2 — Written explanation — the employee is required to provide written explanations within 48 hours (or 4 hours if actively in-game) in a service ticket and can thus contest the decision.
  • C-2.3 — Review — the personnel manager/Roblox Internal Affairs Team makes a decision.
  • C-2.4 — Punishment order — official notification indicating the reason and term/type of punishment.
  • C-2.5 — Disciplinary rules are mandatory for everyone, including management (except in exceptional cases).
  • C-2.6 — Punishments are intensified in case of recidivism.
  • C-2.7 — The employee has the right to demand evidence of their violation (logs, screenshots, recordings).

---

• D-1 — Staff Balance:
  • D-2.1 — Online 2-10 players
    • With 2-10 players online, at least one moderator/administrator should be online.
    • One moderator/administrator stands at spawn with their service vehicle.
    • The maximum number of staff depends on the number of players; if there are 5 on the server, it is better not to have 2 moderators/administrators on shift. Maximum staff at this online level — 1-2.
  • D-2.2 — Online 10–15 players
    • With 10–15 players online, at least one moderator/administrator should be online.
    • One moderator/administrator stands at spawn with their service vehicle.
    • Maximum number of moderators/administrators at this online level — 2-3.
  • D-2.3 — Online 15–20 players
    • With 15–20 players online, two to three moderators/administrators should be online.
    • Two moderators/administrators stand at spawn.
    • The third moderator/administrator is located in a place with increased activity (e.g., MVD building).
    • Maximum number of moderators/administrators at this online level — 3-5.
  • D-2.4 — Online 20–30 players
    • With 20–30 players online, three to five moderators/administrators should be online.
    • Two moderators/administrators stand at spawn.
    • The remaining moderators/administrators are distributed across points with increased activity (MVD, hospital, EMERCOM, popular parking lots, etc.).
    • Maximum number of moderators/administrators at this online level — 5-6.
  • D-2.5 — Online 30–39 players
    • With 30–39 players online and five or more moderators/administrators, two remain at spawn.
    • The remaining moderators/administrators are located near spawn and in places with increased activity.
    • Maximum number of moderators/administrators at this online level — 7.
  • D-2.9 — Violation of Staff Balance
    • Ignoring patrols, constant gathering of three or more staff at one point without reason, or refusing to distribute across the map is considered a staff balance violation.
    • Systematic violation of this clause may result in internal disciplinary measures in accordance with project regulations.
• D-2 — Staff Placement Points
  • Fixed points are established for staff where it is allowed to stand in standby mode (spawn, MVD, hospital, EMERCOM, large public places, and other approved points).
  • It is prohibited for more than three staff to stand nearby: no more than two staff representatives can be at one point simultaneously.
  • Staff must be distributed across the map and not gather in one place without necessity.
• D-3 — City Patrols
  • Each active moderator/administrator is required to go on city patrol every 5–10 minutes in the absence of urgent requests.
  • Patrols are conducted on service vehicles around the city and problem points, after which the employee can return to their standby point.
  • Staff are prohibited from constantly being AFK in place and limiting themselves to only responding to mod calls.
• D-4 — Response to Mod Calls During Patrol
  • During patrol, the moderator/administrator is required to promptly respond to mod calls if they are closest or can arrive at the scene fastest.
  • After handling a mod call, the employee either continues patrol or returns to their point in accordance with the current distribution.

---

• E-1 — Weekly Norm, LOA, and Probation:
  • E-1.1 — Each employee is required to show activity of at least 5 hours per week.
  • E-1.2 — You must be on shift for at least 40 minutes daily to maintain stable operation and engagement.
  • E-1.3 — LOA (leave of absence) — maximum 1 month, no more than once every 3 months. Processed via the /loa request command.
  • E-1.4 — Probation period (Trial Moderator or separate Probation role) — 1 week from the date of training completion. If the employee does not pass training within this time — they are removed from the team, reapplication only from scratch.
  • E-1.5 — All training and trials are conducted under the supervision of senior moderators or administrators.
• E-2 — OPiG (Spelling, Punctuation, and Grammar):
  • E-2.1 — You must comply with Russian language rules when writing any messages in any chats.
    No abbreviations, slang, or errors.
  • E-2.2 — Examples:
    • Incorrect:
      draсте sсhа ya tutаь sdlaю varn
      privet vse tut?
      vydal nakаzаnie
    • Correct:
      Hello, I will issue a punishment now.
      Hi, is everyone here?
      I issued a punishment.
• E-3 — Message Literacy (:h and :m):
  • E-3.1 — Every announcement (:h) and message (:m) must be written in compliance with Russian language rules: spelling, punctuation, and grammar.
  • E-3.2 — Start all sentences with a capital letter, use correct phrasing, and avoid errors.
• E-4 — Conducting Events and RP
  • E-4.1 — It is prohibited to start events or large-scale role-play events without Manager permission.
  • E-4.2 — All events and RP sessions must be pre-coordinated with Community Managers.
• E-5 — Session and Event Pings
  • E-5.1 — Only 2 pings are allowed at the beginning of an event (voting and start).
  • E-5.2 — Afterwards, 2–3 pings are allowed: one can be “Citizen of Russia,” and “Session Ping” no more than 1-2.
  • E-5.3 — Interval between pings — minimum 2–4 hours.
• E-6 — Welcome Message
  • E-6.1 — Each employee must have a pre-prepared welcome message for addressing a player or ticket participant.
  • E-6.2 — Example for taking a mod call:
    Hello, I am (position) of the Moscow RolePlay server.
Hello, I am (position) of the Moscow RolePlay server, how can I help you?
  • E-6.3 — Example for a ticket:
    Hello 👋! I am [Your_nickname] [position] Moscow RolePlay. Thank you for contacting the ticket. I am currently handling your ticket. If necessary, I will transfer the ticket to a higher-ranking employee or inform you of my temporary absence.
@Participant Ping
• E-7 — Fraction Staff Balance (from 5 to 40 players) ← Disputed points, rule under revision.

Why this balance is needed:
The table was created for fair and interesting distribution of players among all gaming fractions on the server.
Everyone will be able to choose their role and be confident that every fraction will have enough participants for role-play interaction, and no team will be overcrowded.
Such a balance helps maintain realistic service operations, prevents “overpopulation” of law enforcement structures, and preserves the importance of civilian professions.

Special rule:
In the FSB, playing as special forces is allowed only if there are 3 or more people in the fraction.
This is done so that roles are distributed fairly and there is no bias towards special units with a small staff.

Balance Table

Players	Civilians	FSB	MVD	EMERCOM & SMP	CODD & MP
5	2	1	1	0	1
6	2	1	1	1	1
7	3	1	1	1	1
8	3	1	2	1	1
9	3	2	2	1	1
10	4	2	2	1	1
11	4	2	2	2	1
12	5	2	2	2	1
13	5	2	3	2	1
14	5	2	3	2	2
15	6	3	3	2	1
16	6	3	3	2	2
17	7	3	3	2	2
18	7	3	4	2	2
19	7	3	4	3	2
20	8	4	4	3	2
21	8	4	4	3	2
22	9	4	5	3	2
23	9	4	5	3	2
24	9	4	5	4	2
25	10	5	5	4	2
26	10	5	5	4	2
27	11	5	6	4	2
28	11	5	6	5	2
29	11	5	6	5	2
30	12	6	6	5	2
31	12	6	7	5	2
32	13	6	7	5	2
33	13	6	7	6	2
34	13	7	7	6	2
35	14	7	8	6	2
36	14	7	8	6	2
37	15	7	8	6	2
38	15	7	8	6	2
39	15	7	8	6	2
40	16	8	8	6	2

• E-8 — Reviewing Tickets Against Players:
  • It is prohibited to review complaints against players without the participation of the person against whom the complaint was filed.
  • A staff member is obligated to necessarily add the accused player to the ticket and listen to the details of the situation from their side in order to make an objective assessment of what happened.

---

​

Project Leadership

---

​

Project Management

---

​

Staff Team Leads

---

​

ER:LC Administration

---

​

ER:LC Moderation

---

​

Promotion Team

---

The Promotion Team Regulations define the authority, responsibilities, ethics rules, reporting system, and disciplinary measures for PR Leadership, promotion staff, and media partners of the Moscow RolePlay project.

• G-1 — Promotion Team Balance
  • G-1.1 — Authority and Status of Media Partners:
    • The PR-Leader is required to grant helper status (:helper (nickname)) in-game to a media partner. Moderator status is granted exclusively with permission from the Community Manager.
    • Management may restrict a Media Partner’s access to helper status (:helper / Free Camera) if the person abuses it. For example: Grant only during filming, then remove it.
    • Permission from management is required only for large-scale shoots. In other cases, a media partner can join any faction without coordination, simply by using the MEDIA prefix.
  • G-1.2 — Regulations for PR Leadership:
    • PR-Leader / PR-Assistant do not have the right to use moderator rights for their own purposes.
    • PR-Leader / PR-Assistant do not have the right to intervene in an RP scene to give a verbal warning or issue a warn to a media partner.
    • The PR-Assistant is granted moderation rights (:mod nickname) in-game; they also do not have the right to use their powers for personal purposes.
    • The PR-Teamlead has the right to obtain permission from the Community Manager to hold unscheduled events (for example, if activity drops).
  • G-1.3 — Duties and Ethics of Employees:
    • Every team member is the face of the Moscow RolePlay project. Everything you create or promote reflects the server’s image.
    • The promotion team is required to observe grammar and be polite everywhere.
    • Publicly criticizing the decisions of management or other team members is prohibited.
    • The promotion team can speak directly to the PR-Teamlead in private messages.
  • G-1.4 — Internal Discipline and Resources:
    • Activity on schedule: be in touch, complete tasks on time, participate in server life.
    • Maintain confidentiality: do not disclose internal documents, strategic plans, and other server information.
    • It is prohibited to use server resources for personal purposes (materials, budgets, audiences).
    • It is prohibited to publish content that violates server rules. Media partners must ensure that their materials do not contain signs of rule violations.
      • EXCEPTION: Minor violations OR Permission from the Community Manager / PR-Leader.
  • G-1.5 — Violation of the Promotion Team Regulations:
    • Violation of any item of these regulations entails disciplinary action, up to and including dismissal and revocation of media partner status.
• G-2 — Duties of the Promotion Team
  • G-2.1 — Legal Norms and Timeliness:
    • Compliance with legal norms: compliance with copyright, use of licenses, use of others’ materials only with permission or with mandatory source attribution.
    • Providing work in advance with mandatory proofreading and edits.
    • Coordination of advertising creatives and texts with the promotion team and management before launch.
  • G-2.2 — Creating Materials and Strategy:
    • Preparation of texts, visuals, videos, and other materials that match the server’s style and general quality standards (spelling, grammar, factual accuracy).
    • Creating and implementing strategies for promoting content and the Moscow RolePlay server, including advertising.
    • Do not use unreliable information, prohibited promotion methods, hidden advertising without labeling, rating manipulation, etc.
• G-3 — Reporting and Documentation
  • G-3.1 — Reporting Format (Media and Events):
    • A simplified format for recording results is used to evaluate work effectiveness. This is necessary so that management understands which content “resonated” best with the audience.
    • For media: Link to stream/video + key metrics (views/reach).
    • For events: Brief summary (how many people attended, whether the event went as planned).
• G-4 — Filming Violations Regulations
  • G-4.1 — Rules for Documentation and Working with Bans:
    • Suspend a ban for the duration of a scheduled shoot (the shoot must be on the schedule). Restore the ban to the media partner after filming ends (the ban is lifted only if the violation was not of a very serious nature).
    • Establish that complaints against media partners in tickets are reviewed exclusively by the team lead/media assistant or manager.
    • The PR-Leader is required to record all filming violations or event violations (screenshots/video).
• G-5 — Issuing Punishments to Promotion Team Employees
  • G-5.1 — Leadership Authority:
    • In case of a gross violation, the PR-Leader / PR-Assistant / Community Manager has the right to issue a reprimand.
  • G-5.2 — Disciplinary Measures:
    • Upon receiving 3 reprimands — the employee will be dismissed.

• G-5.3 — Additional Conditions for Issuing Measures:
  • PR-Leader / PR-Assistant have the right to:
    • Skip a level (immediately Reprimand 1, if there are no 2 warnings)
    • Escalate the punishment (immediate Reprimand for a gross violation)
    • Mitigate the measure (Verbal Warning instead of a reprimand)
  • The PR-Leader / PR-Assistant reserves the exclusive right to determine the type, order, and severity of disciplinary measures depending on the nature of the offense, circumstances of the case, and the interests of maintaining order on the server.