Staff Overview
Staff are responsible for protecting roleplay, maintaining a fair and enjoyable community, handling situations professionally, and using their permissions only for legitimate staff duties while keeping internal information confidential.
Staff Standards
Staff must remain respectful, calm, professional, and unbiased at all times, base decisions on evidence and context, avoid conflicts of interest or misuse of rank, keep staff information private, and seek guidance from leadership whenever necessary.
Chain of Command
Staff must follow the chain of command, escalate situations beyond their authority, avoid overriding another staff member without discussion or approval, and respect leadership's final decisions on major punishments, staff discipline, and server policy.
Staff Roles
Moderators handle routine reports and support, Administrators oversee escalated cases and staff guidance, and Leadership manages policies, appeals, staffing decisions, and major disciplinary matters while ensuring consistency across the team.
Tickets & Reports
Staff must thoroughly review reports, gather all necessary evidence and context, remain impartial, communicate respectfully, document important actions, avoid punishing without sufficient proof, and escalate unresolved or complex situations when appropriate.
Punishments
Punishments must be fair, evidence-based, proportional to the severity of the violation and player history, never influenced by personal feelings, and escalated to higher staff whenever policy or the situation requires it.
Admin Commands
Administrative commands may only be used for legitimate staff duties, support, testing, or approved events, must never provide a personal or roleplay advantage, and should not be used while actively roleplaying unless handling an official staff scene.
Abuse of Permissions
Staff must never misuse administrative permissions for personal gain, favoritism, revenge, or unfair advantages, leak confidential staff information, and should immediately report any suspected abuse to leadership with supporting evidence.
Activity
Staff are expected to remain consistently active in server moderation, Discord, tickets, and player support, notify leadership of extended absences, and contribute meaningfully rather than simply remaining online.
Internal Conduct
Staff must communicate respectfully, avoid drama, rumors, cliques, or public arguments, handle disagreements privately and professionally, treat everyone with respect, and bring concerns to leadership instead of creating conflict.
Suspension & Removal
Staff who abuse their authority, violate policies, leak confidential information, display favoritism or poor judgment, fail to meet activity expectations, or otherwise damage the integrity of the staff team may be warned, suspended, demoted, or removed depending on the severity of the offense.
Staff Jobs
Server Director
Oversees the entire server, makes final decisions, manages all departments, and sets the server's direction.
Developer
Develops, maintains, and improves server systems, scripts, and technical infrastructure.
Server Manager
Oversees daily server operations, coordinates staff teams, and ensures policies are properly enforced.
Manages the community, handles player relations, oversees announcements and events, and helps maintain a positive environment.
Head Management
Supervises the Management team, oversees staff operations, and assists with major administrative decisions.
Management
Manages staff, handles escalated situations, oversees promotions and discipline, and enforces server standards.
Head Administration
Supervises the Administration team, reviews escalated reports, mentors administrators, and ensures consistent enforcement.
Administration
Handles escalated reports, major punishments, appeals, and provides guidance to the moderation team.
Trial Administration
Assists Administrators, learns administrative procedures, and performs duties under supervision.
Head Moderation
Supervises the Moderation team, mentors moderators, reviews difficult reports, and ensures consistent moderation.
Moderation
Handles player reports, provides player support, enforces server rules, and issues punishments within policy.
Trial Moderation
Assists with player support, learns moderation procedures, handles basic reports under supervision, and escalates situations beyond their authority.
Staff Training Guide
This section explains what each staff level is expected to handle, what activity is required, and what actions staff members should avoid.
Moderator
Moderators handle in-game reports, help keep players following the rules, and assist tickets when support needs an in-game staff member.
- Respond to player reports when available.
- Listen to both sides before making a decision.
- Ask for clips, logs, screenshots, or other proof when needed.
- Stay calm and respectful, even if the player is upset.
- Explain what rule was broken and why action is being taken.
- Ask an Administrator for help when unsure.
- Report cheating, exploiting, or staff abuse right away.
- Help Junior Moderators when they need guidance.
Moderator Activity
- Moderators must have at least 7 hours per week in-game.
- Moderators must stay active in the staff Discord.
- Moderators must attend required staff meetings and training.
- Moderators must submit an inactivity notice before being away.
Moderator Limits
- Do not punish someone without proof.
- Do not handle your own report or a report involving a close friend.
- Do not use staff powers to help yourself or your friends.
- Do not revive, heal, teleport, or spawn anything without a staff reason.
- Do not argue with or disrespect players.
- Do not ignore reports just because you are roleplaying.
- Do not share private staff information.
- Do not interrupt active roleplay unless it is actually necessary.
- Do not permanently ban anyone without Administrator approval.
- Do not reimburse weapons, items, donation items, or vehicles without valid proof and proper approval.
Administrator
Administrators handle serious situations, support Moderators, review evidence, and manage cases that are above Moderator authority.
- Help Moderators with situations they cannot handle alone.
- Deal with serious or repeated rule violations.
- Review clips, logs, and punishment history.
- Handle cheating, exploiting, ban evasion, and staff abuse reports.
- Review ban requests and appeals.
- Make sure punishments are fair and consistent.
- Correct staff members privately when they make a mistake.
- Keep serious staff situations documented.
- Bring major problems to Management.
Vehicle Reimbursements
Administrators may reimburse vehicles only when there is clear proof that the vehicle was lost because of a server or game glitch. The vehicle, owner, and evidence must be verified. If the situation is not clear, send it to Management.
Administrator Activity
- Administrators must have at least 8 hours per week in-game.
- Administrators must stay active in the staff Discord.
- Administrators must check reports and staff logs regularly.
- Administrators must attend required staff meetings and training.
- Administrators must submit an inactivity notice before being away.
Administrator Limits
- Do not punish players based on assumptions.
- Do not protect friends, faction members, or other staff.
- Do not overturn another staff member's decision without checking everything first.
- Do not abuse access to inventories, logs, or player information.
- Do not leak staff discussions or investigations.
- Do not remove punishments without documenting why.
- Do not disrespect lower-ranking staff.
- Do not reimburse weapons, items, donation items, or vehicles without valid proof and proper approval.
- Do not make major staff or server decisions without Management.
Management
Management keeps the staff team organized, reviews serious reports, handles staff issues, and makes sure staff decisions are consistent.
- Watch over the Moderation and Administration teams.
- Handle serious or disputed player reports.
- Deal with staff complaints and staff investigations.
- Review staff activity and performance.
- Handle promotions, demotions, suspensions, and removals.
- Organize staff meetings and training.
- Make sure rules and punishments are handled the same way by everyone.
- Keep private staff matters private.
- Bring major server problems to Ownership.
- Help with tickets when Management is actually needed.
Weapon and Item Reimbursements
Management handles weapon and item reimbursements. Players must provide a clip showing the item was lost because of a server or game glitch, or staff must be able to verify the issue. Items lost from dying, being robbed, roleplay, or player mistakes are not reimbursed.
Donation Items
Only Head Management may give players donation items. Donation items must go through an official donation ticket, and the purchase, player information, and item must be verified before anything is given out.
Management Activity
- Management must have at least 10 hours per week in-game or doing approved Management work.
- Management must stay active in the staff Discord.
- Management must check important reports, tickets, and staff activity.
- Management must attend and help lead staff meetings.
- Management must submit an inactivity notice before being away.
Management Limits
- Do not promote or demote someone because they are your friend.
- Do not ignore staff abuse or misconduct.
- Do not leak private staff discussions.
- Do not make decisions without checking the evidence.
- Do not use rank to shut down disagreements.
- Do not embarrass or disrespect staff in public.
- Do not reimburse weapons, items, or donation items without valid proof and proper authority.
- Do not let personal problems affect staff decisions.
- Do not make promises for Ownership without permission.
Ticket Guide
Tickets should be handled quickly, respectfully, and with clear ownership. Gather the needed information, keep the ticket focused, document the outcome, and close it when finished.
Ticket Standards
- Support Team should be the first staff in a ticket to gather the required information unless a higher-up is already handling it.
- Be respectful in every ticket, even when the player is upset or impatient.
- If you claim or handle a ticket, you are responsible for finishing it, creating the transcript when needed, and closing it.
- Do not have side conversations in tickets. Handle the issue, transcript it if needed, and close it.
- If you create a ticket, wait for another staff member to respond. Do not handle your own ticket.
- Only one staff member should handle a ticket at a time unless a higher-up is requested, pinged, or needed because the original staff member has not responded.
Ticket Commands
| Command |
Use |
| /ticket claim | Claim a ticket. |
| /ticket unclaim | Make the ticket available for another staff member. |
| /ticket add user: | Add a user to the ticket. |
| /ticket remove user: | Remove a user from the ticket. |
| /ticket rename name: | Rename the ticket. |
| /ticket close reason: | Close and lock the ticket. |
| /ticket closeprompt | Send the closing message. |
| /ticket delete | Delete the ticket channel. |
| /ticket transcript | Manually create or upload a transcript. |
| /adduser user: | Alternate command for adding someone. |
| /pre-support | Send the standard support request message. |
| /pre-claim | Send the standard claim message. |
| /pre-close | Send the standard closing message. |
Ticket Rename Guide
Support Tickets
- If someone requests an owner, ping the owner and rename the ticket to waiting for owner.
- If someone requests Management, ping Management and rename the ticket to waiting for management.
- If someone does not state what they need, rename the ticket to waiting for response.
- If someone wants to transfer from another server, rename the ticket to staff transfer.
- If someone asks about making a purchase, rename the ticket to waiting for payment.
Ban Appeals
- If someone sends their ban message, rename the ticket after the staff member who banned them, such as rat ban.
- If the ban message says cheating appeal, rename the ticket to cheating appeal and ping the staff member who issued the ban.
Donation Tickets
- If someone purchased from the Tebex store, ask for their Tebex code and player name.
- Once the information is sent, ping Owner so the payment can be verified.
- Do not give donation items until the payment is verified by Owner or the proper authorized higher-up.
Who To Ping Or Add
| Reason |
Ping / Add |
| Female Verify | Management |
| Gang Alliances / Strikes | Faction Manager |
| Staff Transfers | Management |
| Staff Strikes | Management |
| Higher-Up Strikes | Owner |
| Tx Bans | Management, then Owner if needed. |
Staff Permissions
Staff permissions are for staff work only. Every command, action, and permission use may be logged and reviewed by higher staff or ownership.
When Staff Perms Are Allowed
- Handling reports, tickets, staff sits, appeals, or active staff situations.
- Checking evidence, logs, player information, or inventory information for a real staff reason.
- Teleporting, bringing, freezing, spectating, reviving, healing, or using noclip when it is needed to handle a staff situation.
- Testing server issues, bugs, scripts, or approved development work.
- Helping run approved staff events or management-approved server events.
- Fixing a legitimate server issue that affects players or roleplay.
When Staff Perms Are Not Allowed
- Do not use staff permissions for personal convenience, curiosity, or entertainment.
- Do not use staff permissions to help yourself, your friends, your gang, your department, or your roleplay scene.
- Do not use revive, heal, teleport, bring, freeze, noclip, spectate, spawn, or inventory tools during normal roleplay.
- Do not check logs, inventories, locations, identifiers, or player information without a valid staff reason.
- Do not use staff tools to gain information for roleplay or to give another player an advantage.
- Do not spawn vehicles, weapons, items, money, or donation items unless you have proper approval and a documented staff reason.
- Do not use staff permissions to win arguments, scare players, punish people emotionally, or prove a point.
Permission Abuse
- Abuse of staff permissions counts as staff misconduct and may result in a staff strike.
- Severe permission abuse may skip normal strike progression and result in suspension, demotion, or removal.
- Everything is logged. Staff should assume every command and staff action can be reviewed.
- If you are unsure whether a permission use is allowed, ask higher staff before using it.
Important Note: Staff permissions are not rewards, shortcuts, or roleplay advantages. Use them only when there is a real staff reason.
What To Do
- Stay calm, respectful, and professional in every staff situation.
- Review all available evidence before making a decision.
- Ask for clips, logs, screenshots, IDs, and context when needed.
- Remain unbiased, even if the situation involves friends, gangs, departments, or people you dislike.
- Escalate anything serious, unclear, sensitive, or outside your authority.
- Document important actions so other staff can understand what happened.
- Use staff permissions only when handling legitimate staff duties.
- Protect internal information and keep staff matters inside staff spaces.
- Ask leadership before acting if you are unsure.
What Not To Do
- Do not use staff rank to win arguments, intimidate players, or protect friends.
- Do not punish players without enough evidence or context.
- Do not handle reports involving your own character, friends, enemies, gang, or department conflict.
- Do not leak staff chats, logs, reports, private information, or internal decisions.
- Do not use admin commands for personal gain, roleplay advantage, revenge, or convenience.
- Do not argue with players in tickets, sits, Discord, or public chats.
- Do not override another staff member without discussion or approval.
- Do not ignore chain of command on major punishments or staff issues.
- Do not create drama, spread rumors, form cliques, or bring internal conflict into public spaces.
- Do not allow your personal opinions of a player to influence your decisions.
Professionalism Standards
Staff are expected to speak and act like representatives of Brick City RP when handling staff duties. Your tone should stay calm, clear, mature, and respectful even when a player is upset, disrespectful, or wrong.
- Use clear staff language when handling tickets, reports, sits, punishments, and Discord issues.
- Do not insult players, mock them, talk down to them, or match their energy when they are angry.
- Do not use street talk, trolling, threats, or disrespectful language while acting as staff.
- Explain decisions briefly and professionally. Do not lecture, argue, or try to embarrass players.
- Keep staff conversations focused on facts, evidence, rules, and the action being taken.
- If you are too irritated to handle a situation fairly, step away and ask another staff member to take over.
Conflict Resolution
Staff should reduce conflict, not make it worse. The goal is to understand what happened, apply the rules correctly, and move the situation forward without creating extra drama.
- Let each side explain the situation without being interrupted.
- Ask direct questions and keep the conversation on the rule issue.
- Separate players if the conversation turns into arguing, baiting, or insults.
- Use clips, logs, and facts instead of opinions or assumptions.
- Do not take sides because of friendships, reputation, gang affiliation, or past issues.
- If the situation becomes too heated, pause it and escalate to higher staff.
- End the situation with a clear decision, warning, punishment, or escalation path.
Escalation Procedures
If a situation is serious, unclear, personally connected to you, or outside your authority, do not force a decision. Pass it to a higher rank or neutral staff member.
- Escalate major punishments, staff complaints, unclear evidence, exploits, and server-wide issues.
- Do not handle reports involving your friends, enemies, gang, department, or personal conflict.
- Send the clip, logs, player information, rule involved, and a short summary of what happened.
- Do not add personal opinion. Let higher staff review the facts.
Strikes & Inactivity
Staff Strikes
Staff members who break staff rules, server rules, abuse permissions, act unprofessionally, or ignore expectations may receive a staff strike.
- Staff strikes may stack up to three active strikes.
- A third strike may result in demotion to a previous rank, full demotion, suspension, or removal depending on severity.
- Strike outcomes may depend on the time between strikes, the type of violations, staff history, and the level of abuse involved.
- Severe misconduct may skip normal strike progression and result in immediate action.
- If you believe a strike is unfair, speak with leadership calmly and professionally.
- Acting immature, hostile, or disrespectful about receiving a strike may lead to additional discipline.
Inactivity
Staff are expected to manage their own activity. If you need time away, submit an inactivity notice before disappearing.
- Being inactive for four or more days without an inactivity report may result in full demotion.
- Inactivity reports may be submitted through the forums or the proper Discord channel.
- Leadership is not required to remind staff about their activity.
- Staff are responsible for knowing the rules, communicating absences, and staying accountable for their rank.
Punishment Times
These times are staff guidelines. Punishments should always be based on evidence, severity, intent, player history, and whether the player has already been warned for similar behavior.
Kick Guidelines
| Action |
When Appropriate |
| Verbal Warning |
Minor first-time issues, confusion, accidental rule breaks, or teachable moments. |
| Kick |
Player refuses to listen, continues minor disruption, needs to reset behavior, or ignores staff direction. |
| Kick + Warning |
Clear rule break that is not severe enough for a ban but needs to be documented. |
Racial Slurs
Racial slurs, hate speech, or targeted discriminatory language should be handled as a serious offense. Staff must collect evidence, confirm context, document the action taken, and issue the listed Racism / Hate Speech punishment unless management approves a different outcome.
Punishment Matrix
Use this matrix as the standard starting point. Staff may escalate, reduce, or bypass steps depending on severity, evidence, intent, player history, and management discretion.
| Offense |
1st Offense |
2nd Offense |
3rd Offense |
4th+ Offense |
| RDM | 1 Day | 3 Days | 7 Days | Permanent |
| VDM | 1 Day | 3 Days | 7 Days | Permanent |
| FailRP | Warning | 12 Hours | 1 Day | 3 Days |
| FearRP / Value of Life | Warning | 12 Hours | 1 Day | 3 Days |
| Powergaming | Warning | 12 Hours | 1 Day | 3 Days |
| Metagaming | Warning | 12 Hours | 1 Day | 3 Days |
| Character Blurring | Warning | 12 Hours | 1 Day | 3 Days |
| Force RP | Warning | 12 Hours | 1 Day | 3 Days |
| Low Quality RP | Warning | 6 Hours | 12 Hours | 1 Day |
| Combat Logging | 1 Day | 3 Days | 7 Days | Permanent |
| Combat Storing | 12 Hours | 1 Day | 3 Days | 7 Days |
| NLR | 12 Hours | 1 Day | 3 Days | 7 Days |
| Safe Zone Violation | 12 Hours | 1 Day | 3 Days | 7 Days |
| Gang Limit (5-Man Rule) | 1 Day | 3 Days | 7 Days | Permanent |
| Cop Baiting | Warning | 12 Hours | 1 Day | 3 Days |
| EMS Baiting | Warning | 12 Hours | 1 Day | 3 Days |
| Revenge RP / RK | 12 Hours | 1 Day | 3 Days | 7 Days |
| Random Knockout (RKO) | Warning | 12 Hours | 1 Day | 3 Days |
| Unrealistic Driving | Warning | 6 Hours | 12 Hours | 1 Day |
| Third-Party Communication | 1 Day | 3 Days | 7 Days | Permanent |
| Stream Sniping | 3 Days | 7 Days | Permanent | Permanent |
| Invalid Robbery | Warning | 12 Hours | 1 Day | 3 Days |
| Invalid Hostage RP | Warning | 12 Hours | 1 Day | 3 Days |
| Invalid Kidnapping | Warning | 12 Hours | 1 Day | 3 Days |
| Invalid Gang War | 1 Day | 3 Days | 7 Days | Permanent |
| Invalid Police Raid | Warning | 12 Hours | 1 Day | 3 Days |
| Invalid Search / Arrest | Warning | 12 Hours | 1 Day | 3 Days |
| Fail Cop RP | Warning | 12 Hours | 1 Day | 3 Days |
| Fail EMS RP | Warning | 12 Hours | 1 Day | 3 Days |
| Toxicity (IC) | 12 Hours | 1 Day | 3 Days | 7 Days |
| OOC Toxicity | 1 Day | 3 Days | 7 Days | Permanent |
| Harassment | 3 Days | 7 Days | Permanent | Permanent |
| Racism / Hate Speech | Permanent | Permanent | Permanent | Permanent |
| Sexual Harassment | 7 Days | Permanent | Permanent | Permanent |
| Threats (Real-Life) | Permanent | Permanent | Permanent | Permanent |
| Advertising | Permanent | Permanent | Permanent | Permanent |
| Trolling | 1 Day | 3 Days | 7 Days | Permanent |
| Lying to Staff | Warning | 1 Day | 3 Days | 7 Days |
| False Reports | Warning | 12 Hours | 1 Day | 3 Days |
| Staff Sit Evasion | 1 Day | 3 Days | 7 Days | Permanent |
| Failure to Comply with Staff | Warning | 12 Hours | 1 Day | 3 Days |
| Exploiting | 7 Days | Permanent | Permanent | Permanent |
| Bug Abuse | 3 Days | 7 Days | Permanent | Permanent |
| Economy Abuse | 7 Days | Permanent | Permanent | Permanent |
| Duping | Permanent | Permanent | Permanent | Permanent |
| Cheating / Mod Menu | Permanent | Permanent | Permanent | Permanent |
| Lua Executor / Script Injection | Permanent | Permanent | Permanent | Permanent |
| Ban Evasion | Permanent | Permanent | Permanent | Permanent |
| Alternate Account to Evade Punishment | Permanent | Permanent | Permanent | Permanent |
Major punishments must include evidence, reasoning, and escalation when required.