White House Roleplay
Read this. All of it.
This is the single source of truth for White House Roleplay Community — for every member, every roleplayer, and every staff member. "I didn't know the rule" is never a valid excuse, because every rule lives right here.
How this handbook works
Use the menu on the left to jump between sections. The Community sections are open to everyone. The Restricted sections are locked — you'll need the passcode for your role to open them.
- Staff Section — for all accepted staff. Policy, commands, on-duty rules, Melonly logging, the punishment ladder, and worked scenarios.
- Trainee Section — for anyone awaiting or in training.
- Trainer Section — for staff who hold the Staff Trainer role.
- SHR Section — for Senior High Rank and above.
Server Rules
These apply everywhere — Discord, in-game, and any WHRP space. They sit above every other rule in this handbook.
- Respect everyone. No harassment, bullying, threats, or targeting. Treat people the way you'd want to be treated.
- Hate speech is an instant ban. Racism, homophobia, transphobia, sexism, ableism, religious hate, or slurs of any kind — zero tolerance, IC or OOC.
- No NSFW, gore, or shock content anywhere, including profile pictures, names, statuses, and roleplay.
- No ERP (Erotic Roleplay) in any form. Instant ban.
- No doxxing or real-life threats. Sharing personal info or threatening someone's safety is an instant permanent ban.
- Keep disputes private. Take conflicts to a ticket — don't start drama or rally people against others.
- No advertising or self-promo without permission from High Rank or above. This includes DM advertising.
- No scams, malicious links, IP grabbers, or phishing. Instant permanent ban.
- No exploiting, hacking, cheating, or game modification of any kind.
- No ban evasion. Using alternate accounts to dodge a punishment extends the ban and bans the alt.
- No impersonation of staff, members, or the community.
- No bypassing moderation. Filter-dodging or evading a mute/ban is treated as the original offence, made worse.
- Follow the Roblox Terms of Service and Discord Community Guidelines at all times.
- Staff have final say. Follow staff instructions; raise disagreements calmly in a ticket, not in the moment.
- Use common sense. No list covers everything — if it clearly breaks the spirit of these rules, staff may act on it.
Discord Rules
Conduct inside the White House Roleplay Community Discord server.
General conduct
- Use the correct channels and keep content on-topic.
- No spam — message spam, emoji spam, copypastas, or chain messages.
- No mass mentions or ghost pings. Don't ping @everyone/@here, roles, or staff unless authorised. Ping-then-delete still counts.
- Open a ticket for support instead of pinging staff. Pinging High Rank or above for general issues isn't allowed.
- No backseat moderating. Report rule-breakers through a ticket.
- No begging for ranks, perms, roles, or giveaways.
- Keep usernames, nicknames, and avatars appropriate — nothing offensive, NSFW, or hoisted.
Content & safety
- No NSFW, gore, or shock content.
- No heated politics or religious debate in public chat.
- No malicious or suspicious links — no scam links, fake Nitro, or grabbers.
- No leaking DMs or ticket contents to start drama.
Voice channels
- No mic spam, ear-rape, or disruptive soundboards.
- No recording members in voice without consent.
- Don't channel-hop to disrupt others. All server rules apply in voice too.
In-Game Rules
You have creative freedom. Build your own characters, stories, jobs, and scenarios — civilian, criminal, or emergency services. These rules exist only to stop people ruining the experience for everyone else. They are not a script for how you must roleplay.
The core rules
- No RDM (Random Deathmatch) — don't kill or attack without a valid roleplay reason.
- No VDM (Vehicle Deathmatch) — don't use a vehicle as a weapon or ram players without a reason.
- No FailRP (FRP) — keep actions believable; no doing things a real person physically couldn't.
- Value your life (Fear RP) — react realistically when in danger. Held at gunpoint? You can't out-draw the gun already on you.
- Follow the New Life Rule (NLR) — when your character dies, you forget the events leading to it. Don't return to the scene or seek revenge until it clears.
- No powergaming — don't force outcomes onto others or roleplay impossible abilities.
- No metagaming — don't use out-of-character info (Discord, streams, OOC) for an in-character advantage.
- No cop-baiting — don't provoke law enforcement purely to trigger a chase with no real roleplay.
- No combat/RP logging — don't leave the server to escape a situation, an arrest, or its consequences.
- Stay in character. Use
(( ))or//for OOC, and keep OOC chatter minimal.
Presidential Roleplay Session Rules
These additional rules apply specifically to official Presidential Roleplay sessions hosted by WHRP. They supplement the general in-game rules above.
A. Player Roles
| Role | Responsibilities & Gameplay Mechanics |
|---|---|
| The President | The focal point of the RP, elected by vote. Has 3 lives per session. Sets their own agenda, destinations, and activities, but has no authority over server rules. If disconnected or out of lives, the Vice-President takes over. |
| The Vice-President | Runner-up in the election. Holds no independent authority. Can remain with the President's detail or play as a normal civilian until called to step up. |
| Guards | A self-formed group of players voluntarily assigned to protect the President. The group is agreed upon between players and the President and is not staff-assigned. |
| LEOs (Police/Sheriff) | Set up checkpoints, secure surrounding zones, and maintain public order. Protect the general area rather than providing close personal protection to the President. |
| EMS / Fire | Free to join and provide emergency response. May treat anyone in the scene except the President. Downed Presidents can only be revived via staff command. |
| DOT | Assists with physical convoy barriers, refueling, and repairing Presidential motorcade vehicles. |
| Whitelisted Departments | Private security details and organized syndicates or mafias aiming to target the President, unless forbidden by HR+ for a specific session. |
| Civilians | Spectators, media, or hostile agents. May observe, interact, or attempt a strike on the President while following all applicable rules. Players may change roles during a session except the elected President and Vice-President. |
B. Election Protocols
- Location: Every official session starts with elections hosted at the Liberty Fountain.
- Timeframe: Target duration is approximately 12 minutes, with a 25-minute hard cap.
- Venue Setup: The Fountain area must be fenced off, equipped with 3 candidate podiums, and arranged cleanly without blocking exits.
- Q&A Phase: Staff or organizers will take one open question from the crowd for candidates to address before voting.
C. Presidential Convoy Rules
- Vehicle Cap: Maximum of 10 non-staff vehicles, unless the Session Lead grants additional vehicles for a major event. Maximum of 2 limousines (1 Primary + 1 Decoy).
- Staff Escort: Exactly 1 staff vehicle leads the front and 1 staff vehicle brings up the rear. No civilian vehicles may enter the core staff escort formation.
- Vehicle Aesthetics: Convoy vehicles must use blacked-out, unmarked liveries with no custom text or lettering, excluding Whitelisted Department vehicles.
- Speed: Maintain a strict 20–35 mph speed limit.
- Convoy Conduct: NO sirens, NO horns, and NO ramming.
- Overtaking: No overtaking within the line unless the lead vehicle is stuck, AFK, or staff directs it.
- Road Control: Roadways should be physically blocked wherever realistically feasible.
- Protection Status: The President is invulnerable under the Peace Timer while inside a moving convoy. If the President's vehicle breaks away without staff approval, protection is immediately lost.
- Enforcement: Drivers who overtake inside the line, drive aggressively alongside or into the convoy, or force their way into the formation may receive an immediate jail penalty.
D. Running Locations & Map Venues
- First Mandatory Stop: The session must open at the WHRC Grand Hotel, providing press and civilians an immediate gathering point outside.
- Location Timers: The President must remain at a location for at least 6 minutes before moving and should relocate to a new venue by approximately the 20-minute mark.
E. Lives, Death & the Settle-In Window
- 3-Life Limit: The President has 3 total lives per session.
- 60-Second Settle-In Rule: Activated immediately following arrival at a new venue or after a staff revive. All players receive 60 seconds to reset and establish positions before combat or fire can resume.
- Session End: At 0 lives remaining, the session officially concludes or transfers to an Emergency Escape protocol at the Lead's discretion.
F. Emergency Escape Protocol
If security collapses, the President can request an Emergency Escape through the Session Lead. Once granted:
- The President may evacuate in a single vehicle without a structured convoy or blocked route.
- The President must have a designated driver and cannot drive themselves.
- Standard convoy restrictions, including route constraints and the 20–35 mph speed limit, are temporarily waived until safety is re-established.
Conduct & driving
- Drive realistically when not in an active scene — no GTA driving, sidewalk driving, or mass-crashing.
- No trolling — no mass RDM/VDM, server disruption, or rage-baiting.
- No mic spam or ear-rape in-game.
- Use a realistic username — no offensive or joke names.
- Restricted weapons and vehicles (military weapons, civilian supercars/hypercars) aren't for general use. Switch when asked.
Scenes
- One major scene at a time. Only one active major crime (robbery, hostage, pursuit) should run at once, with enough players online to respond — as a guide, at least two on-duty LEOs.
- Wait ~10 minutes between major scenes so the server isn't a constant warzone.
- Don't interfere with scenes you aren't part of.
- Comply with in-game staff. On-duty staff handling a situation have full authority.
Chain of Command
The role list mixes several different things. Here it's untangled: the actual ranks you get promoted through, the department dividers, the access/permission roles, and the community/bot roles that aren't ranks at all. Always go to the next rank above you when you need help.
The rank ladder
Top = highest authority. Each department is shown highest-to-lowest internally.
Additional roles — not ranks
Department dividers (just labels)
These WHRP • … roles and the 🗽 separator lines only organise the role list. They grant nothing on their own.
Access & permission roles
Status toggles (set by Melonly)
Bots
WHRP • Bots divider. They run security, logging/management, and webhooks — they aren't staff and hold no rank.Community & supporter roles
perms pass, a status, a helper, a trainee marker, a bot, a supporter perk, or a grey divider, it's an additional role.Join the Staff Team
Want to help run White House Roleplay Community? Here's exactly how staffing works — from applying to getting your first rank.
Requirements
- 13 or older (the Roblox/Discord minimum).
- In the community for at least 2 weeks.
- A clean record — no recent serious punishments.
- Able to take screenshots and record clips for evidence.
- Can commit at least 2 hours per week.
The process
- Apply. Submit the staff application through our Melonly application form (linked in the staff-applications channel). Melonly applications replace Google Forms here.
- Review. An HR+ reviews your answers. We look for maturity, honesty, clear writing, and genuine motivation — not "I want perms."
- Awaiting Training. If you're accepted, you'll be marked Awaiting Training, given the Trainee Section passcode, and added to the training pipeline. You are not a moderator yet — you can't take moderation actions until you've trained.
- Training. A Staff Trainer will schedule and run your session, walking you through the rules, commands, on-duty conduct, and Melonly logging.
- Trial Moderator. Pass training and you're ranked Trial Moderator, given the Staff Section passcode, and you're on the team.
Glossary
The terms you'll see across the server and this handbook.
| Term | Meaning |
|---|---|
| RDM | Random Deathmatch — killing without a roleplay reason |
| VDM | Vehicle Deathmatch — using a vehicle as a weapon without a reason |
| FailRP / FRP | Unrealistic roleplay |
| NLR | New Life Rule — forget your past life after death; don't return to the scene |
| Fear RP | Valuing your character's life realistically |
| Powergaming | Forcing actions onto others or using impossible abilities |
| Metagaming | Using out-of-character info for an in-character advantage |
| Cop-baiting | Provoking police purely to start a chase |
| NITRP | No Intention To Roleplay |
| Combat/RP logging | Leaving the server to dodge a roleplay consequence |
| IC / OOC | In Character / Out Of Character |
| LEO | Law Enforcement Officer |
| EMS | Emergency Medical Services |
| CoC | Chain of Command |
| LOA | Leave of Absence (requested in Melonly) |
| SPaG | Spelling, Punctuation and Grammar |
| SSU | Server Start-Up — booting the ER:LC server (see the SSU perms role) |
| VSM | Virtual Server Management — Melonly's in-game control tools |
| On duty / On break | Actively moderating / clocked in but paused (set in Melonly) |
| LR / MR / HR / SHR / LS | Low Rank / Middle Rank / High Rank / Senior High Rank / Leadership |
Staff Section
This area is for accepted staff. Enter your Staff passcode to continue.
Staff Section
Everything you need to moderate White House Roleplay Community properly. All logging runs through Melonly — that section is required reading. Open each panel below; the worked scenarios at the end show the rules in action.
01 Staff Policy +
You are the face of WHRP. Members decide whether they stay based on how you treat them. Everything in this panel is the standard you're held to every time you're on the team — on duty or not.
Core conduct
- Always act professionally. Stay calm and polite, even with rule-breakers. If it's getting to you, go on break.
- Use proper SPaG in all official messages and while on duty. No slang in staff shouts, punishments, or records.
- No silly behaviour on duty — no messing around while moderating.
- Behave even off duty. Being staff doesn't grant rule-bypasses. Staff are held to a stricter standard than members.
- Stay neutral and treat everyone equally — friends included.
- Never moderate a situation you're part of or angry about. Hand it to another staff member.
- Keep staff matters confidential. Leaking staff chat or tickets means removal.
- Don't ask or hint for promotions. Professionalism and good judgement matter more than raw activity.
- Put your Roblox name in your Discord nickname so you're identifiable.
Why it matters
Every punishment you hand out is remembered by the player on the other end. Fair, calm, well-explained moderation keeps members in the community; rude or inconsistent moderation drives them out and lands on your record. When you treat the standard as optional "just this once", you set that lower standard for everyone who sees you.
02 Command Usage +
Misusing commands is one of the fastest ways to get demoted or blacklisted. Follow these exactly.
Username letter requirements
To avoid hitting the wrong player, type a minimum number of letters of their username — or use their Roblox ID.
| 3+ letters | 4+ letters | Half name | Full name / ID |
|---|---|---|---|
:to :view |
:bring :tp :kill :heal :jail :respawn :load :wanted |
:kick |
:ban :mod :admin |
Rule of thumb: commands that don't affect the target need 3+ letters; commands that do need 4+. Kicks need half the username; bans and permission commands need the full name or, ideally, the Roblox ID. Format: :jail Ryan
"All" / "Others" commands are banned
The only exceptions: healing everyone (:heal all) during a confirmed mass-RDM (5+ players), or when an HR+ explicitly authorises a specific command a specific number of times. Running all/others commands otherwise is treated as raiding and results in a blacklist. Melonly flags server-wide commands like :ban all automatically.
Announcements & off-duty
The H hint command is fine for genuine, important, professional messages while on duty. The M announcement command only when an HR+ authorises it or this guide tells you to. Don't run commands off duty (except staff PMs or with SHR+ authorisation) — and off duty, hide that you're staff to keep RP realistic.
03 On-Duty Protocols +
- Go on duty properly — put on your rank's staff livery, use a staff vehicle, and start your shift in Melonly.
- No chatting on duty. Use the on-duty staff channels for active staff matters only. Want to chat normally? Go on break first — and don't abuse break-hopping.
- Park before you respond. When a mod call comes in, pull your car over properly before walking up — don't abandon it in traffic or in someone's scene.
- Always greet players professionally. Keep a clean copy-paste ready.
- Drive by the rules on duty — no GTA driving. Sirens are fine to pull players over or signal an emergency.
- Callsigns — pick any you like, but don't impersonate a real department/PMC/criminal group or use an undercover plate while on duty.
"Hello! I'm [name], a [rank] with the WHRP staff team. How can I help? If I'm late or no longer needed, please say 'void'."
04 Handling Mod Calls & Tickets +
In-game mod call
- Start your shift in Melonly if you haven't, then respond and approach discreetly — observe before acting.
- Confirm the rule break with your own eyes or ask for a clip.
- Greet the players professionally.
- Apply the correct punishment from the ladder below — and log it in Melonly.
Discord ticket
- Claim the ticket so others know it's handled.
- Ask for details and evidence — clips, screenshots, usernames, timestamps.
- Stay neutral and hear all sides; verify the evidence is real and in context.
- Apply the action and log it, or escalate if it's ban-level (see below). Inform the user calmly and close the ticket.
05 Logging in Melonly +
All WHRP logging runs through Melonly — shifts, punishments, infractions, and LOAs. If it isn't in Melonly, it didn't happen.
Getting access
Make sure you're added to the WHRP Melonly dashboard — open a ticket and an HR+/SHR will accept you. Link your Roblox account; it's required for in-game logging.
Going on shift (every time you moderate)
- Open the Melonly Moderator Panel.
- Click Start Shift (top-left). This logs your time and counts toward your quota.
- Use Start Break when you step away — it pauses your time and marks you as not moderating.
- Click End Shift when you're done.
- Check your hours anytime: the 3 dots next to your name → View My Shifts.
Your On duty and On break Discord roles update automatically with your shift.
Logging a punishment
Log every warning, jail, and kick. Three ways:
- Moderator Panel — create a punishment log with the player, type, reason, and evidence.
- In-game — use the
:logcommand to punish and log in one step. (Custom log types are set up on the dashboard first.) - Auto-log — kicks and bans issued in-game are logged automatically; add the reason later by editing the log in the panel.
Need to jump into a scene's voice channel? Use :log vc s1 (where s1 is the scene's configured abbreviation).
Bans, strikes & LOA
- Bans are applied by HR+ in the Melonly panel (in-game bans auto-log; the reason is added in the panel).
- Staff strikes are recorded by HR+ in Melonly's Infractions module.
- Going inactive? Request a Leave of Absence (LOA) through Melonly before you disappear.
:ban all. Only moderate while on shift.Tutorials & docs
06 Presidential RP Hosting Guidelines +
This section contains the official WHRP Presidential Roleplay hosting procedures, staff assignments, hosting rules, and copy-paste commands. This entire panel is protected by the existing Staff Section passcode.
A. Hosting Requirements & Role Assignment
- Minimum staffing: An official Presidential RP requires at least 3 on-duty staff. Four staff members is ideal.
- Minimum population: At least 12 members online should be present before hosting.
- Session authority: The Session Lead may pause or end the RP if the required staffing or player count drops below the threshold.
- Direct assignment: Hosting roles are assigned by an HR+, or by an MR with explicit HR+ permission.
- Session Lead: The highest-ranked on-duty staff member below HR, normally Junior Moderator or above. Trial Moderators cannot lead.
- Deputy Lead: The next on-duty volunteer ranked Trial Moderator or above, ideally an LR staff member so MR/HR staff remain available elsewhere.
- Remaining staff: Support the Lead and Deputy. If more than 3 staff are on duty, divide them into Field Support and Standby Moderation.
B. Staff Hosting Responsibilities
- Session Lead & Deputy Lead: Run elections, announce locations, validate Presidential kills, handle replacements, route convoys, and manage staff traffic control. Small tasks may be delegated. If the Lead takes a break, the Deputy assumes command.
- Field Support: Answer player questions, observe and validate Presidential kills for the Lead, stage convoys, maintain the route, and punish rule-breakers who disrupt session fairness.
- Standby Moderation: Handle normal server upkeep including mod calls, avatar checks, permission items, and parked vehicles. Assist with Presidential RP when free, but general moderation duty comes first.
C. Hosting Flow
- Begin the election phase. Start a
:pt 500Peace Timer and keep it refreshed until the Presidential convoy reaches its first destination. - Host the election. The election is conducted at the Liberty Fountain under the official election procedure below.
- Select three candidates, allow their speeches, conduct the Q&A, and open voting.
- Announce the President and Vice-President using their exact usernames.
- Form the Presidential convoy. Staff should establish the lead and rear staff vehicles before the convoy moves.
- Issue the convoy warning. Overtaking, sirens, ELS, honking, or disrupting the convoy is punishable.
- Line up the convoy. Everyone participating must line up behind the lead staff vehicle.
- Move between locations. Refresh
:pt 500until the convoy reaches the destination. - On arrival: Announce that the President has reached the location. Civilians may begin attacking once the Peace Timer expires.
- Track the session: Keep the current President, Vice-President, location, and remaining lives updated in staff announcements when appropriate.
D. Election Operations — Liberty Fountain
- Start the Peace Timer.
:pt 500 - Announce the election globally. Use
:monce, or twice if turnout is thin.:m Presidential elections are being hosted at the Liberty Fountain! - Make the local announcement after approximately one minute.
:h Presidential elections are being hosted at the Liberty Fountain! - Choose three candidates.
:h Thank you all for being at this election, I will now be choosing three candidates. - Give the candidates one shared minute for speeches.
:h The candidates have been chosen. They will now be given one minute to pronounce their speeches. - Run the Q&A and voting phase.
:h Voting has started! Please stand in the box of the candidate you are voting for. - Announce the results.
:h The player [President] has been elected as President.:h The player [Vice-President] has been elected as Vice-President. - Form the convoy outside the election location.
:h Please form a Presidential convoy outside the Liberty Fountain. Disrupting the convoy setup may result in punishments.
E. Convoy Hosting & Movement
- Maximum of 10 non-staff vehicles, unless the Session Lead authorises additional vehicles for a major event.
- Maximum of 2 limousines: one Primary and one Decoy.
- Exactly 1 staff vehicle at the front and 1 staff vehicle at the rear.
- No civilian vehicle may enter the core staff escort formation.
- Convoy vehicles should use blacked-out, unmarked liveries with no custom text or lettering, excluding Whitelisted Department vehicles.
- Maintain 20–35 mph.
- NO sirens, NO ELS, NO horns, and NO ramming.
- NO overtaking unless the lead vehicle is stuck, AFK, or staff directs it.
- Roadways should be physically blocked wherever realistically feasible.
- After the convoy announcement, staff should remind participants that overtaking, sirens, ELS, honking, or disrupting the convoy is punishable.
- Everyone participating in the convoy should line up behind the lead staff vehicle.
F. Approved Running Locations
For the WHRP Presidential hosting script, use the following location names exactly as written:
- Hospital (White House) — the designated White House location and first Presidential location where applicable.
- HRP Bunker (High Rock Park Bunker) — a primary recurring destination.
- The Theatres (Theatre [number]) — include the theatre number when relevant.
- Three Guys Burgers and Fries.
G. Positional Relocation Command
- Refresh the Peace Timer.
:pt 500 - Announce the next destination.
:h The President is now going to [Location]. Please form a convoy outside [Current Location]. - Convoy warning: Immediately remind everyone that overtaking, sirens, ELS, honking, and convoy disruption are punishable.
- Formation: Everyone lines up behind the lead staff vehicle before departure.
H. Arrival & Status Announcements
Arrival:
:h The President has reached [Location]. Civilians may start attacking once the peace timer is over.
Session status:
:h Current Roleplay: Presidential Roleplay | President: [President] | Vice-President: [Vice/N/A] | Location: [Location] | Lives: [X]/3.
I. Lives, Death & Revives
2/3 lives:
:h The President [Name] has died. He has now 2/3 lives remaining!:heal [Name]:h Civilians should now exit the area and start attacking the President again once the peace timer is over.:pt 60
1/3 lives:
:h The President [Name] has died. He has now 1/3 lives remaining!:heal [Name]:h Civilians should now exit the area and start attacking the President again once the peace timer is over.:pt 60
0/3 lives with a Vice-President:
:h The President [Name] has died. He has lost all of his lives.:h The new President is now [Vice-President].
0/3 lives without a Vice-President:
:h The President [Name] has died. He has lost all of his lives.:h New elections will be hosted at the Hospital (White House).
J. Emergency Escape
- Only activate an Emergency Escape when approved by the Session Lead.
:h The President is making an emergency escape!- The President may evacuate in a single vehicle without a structured convoy or blocked route.
- The President must have a designated driver and cannot drive themselves.
- Once settled, announce:
:h The President has made an emergency escape and is now at [Location].
07 Punishment Ladder +
This is the official punishment guide. Don't invent punishments — find the closest match, use your judgement, or ask an HR+. Punishments escalate with each offence.
Bans (HR+): any ban-level punishment is applied by High Rank or above. Moderators/Admins escalate with evidence.
| Offence | 1st | 2nd | 3rd | Example |
|---|---|---|---|---|
| Unrealistic avatar | Verbal Warning | Warning | Kick 30m | Headless, Korblox |
| Restricted weapon | Verbal Warning | Warning | Kick 30m | M249, sniper |
| Restricted vehicle | Verbal Warning | Warning | Kick 30m | Supercar / hypercar |
| Car abuse | Warning | Kick 30m | Kick 1h | In/out of car to dodge arrest |
| Minor FailRP | Verbal Warning | Warning | Kick 1h | Driving off after a major crash |
| Breaking NLR | Warning | Kick 30m | Kick 1h | Returning to the scene after death |
| Fear RP violation | Warning | Kick 30m | Kick 1h | Drawing while held at gunpoint |
| Tool / emote abuse | Warning | Kick 30m | Kick 1h | Glitching through walls |
| Player disrespect | Warning | Kick 30m | Kick 1h | Mild insults / toxicity |
| Abusing the mod-call | Warning | Kick 30m | Kick 1h | Repeated false mod calls |
| Minor RDM | Warning + Jail | Kick 30m | Kick 1h | Shooting one player, no reason |
| Minor VDM | Warning + Jail | Kick 30m | Kick 1h | Ramming one car, no reason |
| Offence | 1st | 2nd | 3rd | Example |
|---|---|---|---|---|
| Staff evasion | Kick 30m | Kick 1h | 1 Day Ban (HR+) | Running from on-duty staff |
| Respawn/leave to avoid arrest | Kick 30m | Kick 1h | 1 Day Ban (HR+) | Respawning mid-arrest |
| Spawn killing | Kick 30m | Kick 1h | 1 Day Ban (HR+) | Killing players at spawn repeatedly |
| Repeated RDM / VDM | Kick 1h | 1 Day Ban (HR+) | 3 Day Ban (HR+) | Multiple players killed/rammed |
| Impersonating staff | Kick 30m | Kick 1h | 1 Day Ban (HR+) | Pretending to be staff |
| No intention to roleplay | Kick 30m | Kick 1h | 2 Day Ban (HR+) | Refusing/avoiding RP |
| Harassment / targeting | Kick 1h | 2 Day Ban (HR+) | 5 Day Ban (HR+) | Repeatedly targeting a player |
| Disturbing a major scene | Kick 30m | 1 Day Ban (HR+) | 3 Day Ban (HR+) | Blocking/ramming an active scene |
| Cuff-rush / auto-jail | Kick 1h | 1 Day Ban (HR+) | 3 Day Ban (HR+) | Cuffing with no RP and instant jail |
| Excessive toxicity / foul language | Kick 1h | 2 Day Ban (HR+) | 5 Day Ban (HR+) | Constant abuse at others |
| Offence | 1st | 2nd | 3rd | Example |
|---|---|---|---|---|
| Exploiting / hacking | 180 Day Ban | Permanent | Permanent | Aimbot, flying, flinging |
| Doxxing / real-life threats | Permanent | — | — | Sharing personal info / threats |
| Racism / hate speech / slurs | 14 Day Ban | 60 Day Ban | Permanent | Slurs, hateful conduct |
| Other discrimination | 14 Day Ban | 30 Day Ban | 60 Day Ban | Homophobia, sexism, ableism |
| NSFW actions / ERP | 14 Day Ban | 30 Day Ban | Permanent | Sexual roleplay or content |
| Extremism / recreating tragedies | 14 Day Ban | 30 Day Ban | 60 Day Ban | Recreating real-world attacks |
| Banned roleplay (TOS) | 7 Day Ban | 14 Day Ban | 30 Day Ban | Bomb, terror, torture RP |
| Ban evasion (alts) | Extend + 14 Day | 30 Day Ban | Permanent | Using an alt to evade |
| Bypassing chat filter | 5 Day Ban | 10 Day Ban | 30 Day Ban | Evading the filter to slur/insult |
| Rejoining before a kick ends | 5 Day Ban | 10 Day Ban | 30 Day Ban | Returning before the timer is up |
| Leaving to avoid punishment | 5 Day Ban | 14 Day Ban | 30 Day Ban | Leaving to dodge staff action |
If an offence isn't listed, apply the closest match and use your judgement, or ask an HR+. Never make up your own values.
08 HR Guide (High Rank) +
High Rank (Supervisory & Management) leads the team day-to-day, reports to SHR, and is the first tier with ban authority and training authority.
Responsibilities
- Lead and supervise Moderators, Administrators, and Internal Affairs.
- Handle bans. When a Mod/Admin escalates a ban, confirm the evidence and apply it in Melonly — or apply bans directly when handling situations yourself.
- Train new staff (or assign Staff Trainers) and run training sessions.
- Recruit — review Melonly applications, interview, and decide who enters training.
- Handle escalations beyond LR/MR authority.
- Run activity checks, enforce quotas via Melonly shift time, and approve LOA requests.
- Promote/demote lower staff within cooldowns, and log every change with a reason.
- Issue staff strikes in Melonly's Infractions module and investigate staff reports from IA.
- Report upward to SHR on team health, problem cases, and policy questions.
Best practices
- Log everything in Melonly — promotions, demotions, strikes, and bans, each with a clear reason.
- Be consistent. Apply the rules to staff exactly as you'd want them applied to you.
- Mentor before you punish. New staff make mistakes — coach first, discipline if it continues.
- Escalate the big calls — community-wide policy, mass incidents, and permanent bans go to SHR.
- Strike 1 — formal warning (logged in Melonly).
- Strike 2 — second warning + record note. Blocks promotion for MR+.
- Strike 3 — demotion review (applies through to SHR).
- Severe misconduct (abuse, leaks, bribes) — immediate removal review by SHR.
09 Promotion Cooldowns +
Minimum wait between promotions. Don't ask or hint for one.
- Moderator & Administrator — 3 days
- Internal Affairs — 5 days
- High Rank — 1 week
- Management / SHR — 2 weeks
For MR and above, 2 strikes blocks a promotion and 3 strikes triggers a demotion review — all the way up to SHR. A demotion for max strikes resets the count.
10 Worked Scenarios +
These walk through the rules above in real situations. None of them introduce new rules — they just show how to apply the ladder, the command rules, and the escalation path. When your own situation isn't listed, match it to the closest one here or in the ladder.
In-game One player shoots another for no reason
Respond to the mod call and observe first — don't act on the report alone. Confirm with your own eyes or a clip that there was no RP reason. Greet both players. This is Minor RDM, 1st offence → Warning + Jail. Apply it, then log it in Melonly with the reason and evidence. If the same player does it again the same session, it's the 2nd column (Kick 30m).
In-game A suspect respawns in the middle of their arrest
That's Respawn/leave to avoid arrest (Major), 1st offence → Kick 30m. Confirm it happened, apply the kick, and log it. Because it's a Major offence, a Mod/Admin still handles the kick — only the 3rd column (1 Day Ban) goes to HR+.
Discord A member types a slur in chat
This is a Severe offence (Racism / hate speech / slurs). As a Mod/Admin you do not ban — screenshot it, document the evidence, and report to an HR+ immediately so they can apply the 14-Day Ban and log it. Stay calm and don't argue in chat. Removing the message is fine; issuing the ban is not your call.
Session You've warned the same player three times this session
The session rule kicks in: three warnings in one session = an automatic 30-minute kick. Apply the kick and log it. The count resets when a new session starts — don't carry it over.
In-game Someone is driving a hypercar
That's a Restricted vehicle (Minor), 1st offence → Verbal Warning. Politely ask them to switch to a road-legal vehicle. Log the verbal warning. Only if they refuse and keep going does it move up the columns (Warning, then Kick 30m).
In-game A group is mass-RDMing five or more players
This is the one case where all/others is allowed: you may run :heal all to undo the mass-RDM damage. Then deal with the offender under Repeated RDM / VDM (Major) — Kick 1h on the 1st offence, escalating to HR+ for the ban columns. Log everything. Running all/others in any other situation is treated as raiding and gets you blacklisted.
Ticket Two players each say the other RDM'd first
Claim the ticket and stay neutral. Ask both sides for clips, usernames, and timestamps, and verify the evidence is real and in context. If the evidence clearly shows who broke the rule, apply the matching tier and log it. If it's genuinely unclear and no evidence exists, don't guess — a punishment without evidence isn't valid. Note the outcome and close the ticket calmly.
Judgement The "rule break" turns out to be allowed RP
Not everything reported is a violation. If a player shot someone as part of an established, valid roleplay reason, that's not RDM — don't punish it. Explain the call, thank the reporter, and move on. Punishing allowed roleplay is itself a mistake that lands on your record.
Judgement The situation involves you or a friend
Step back. You never moderate a situation you're part of or angry about, and you don't give friends a pass. Hand it to another on-duty staff member and let them handle it neutrally.
Trainee Section
For members who've been accepted and are awaiting or in training.
Trainee Section
Welcome to the team-in-waiting. You've been accepted and marked Awaiting Training. You're not a moderator yet — but you're close. This section walks you through exactly what to do before your session, what training covers, and the kinds of situations you'll be asked to handle.
What to do while you wait
- Read every Community section of this handbook — Server Rules, Discord Rules, In-Game Rules, and the Chain of Command. These are the rules you'll be enforcing, so read them twice.
- Learn the Glossary cold. You'll be expected to know RDM, VDM, FailRP, NLR, Fear RP, metagaming, and powergaming by heart — not just the letters, but what each one looks like in-game.
- Set up Melonly. Open a ticket to get added to the dashboard and link your Roblox account so you're ready to log from day one.
- Stay active and professional in the server. Trainers notice who's engaged, calm, and helpful — and who isn't.
- Be patient. A Staff Trainer will reach out to schedule your session — don't ping HR asking for it.
Study checklist
Before your session, make sure you can answer each of these without looking:
- Define the core rules — RDM, VDM, FailRP, Fear RP, NLR, powergaming, metagaming, and cop-baiting.
- Know the difference between a Verbal Warning, a Warning, a Jail, and a Kick, and roughly where each sits on the ladder.
- Know the session rule — three warnings in one session becomes an automatic 30-minute kick.
- Know who can ban. Moderators and Administrators warn, jail, and kick only; bans are escalated to HR+.
- Know the "all/others" rule — those commands are banned except
:heal allduring a confirmed 5+ mass-RDM or with explicit HR+ authorisation. - Know how to gather evidence — a clip or screenshot with usernames, before you act.
What training will cover
- The rules and definitions — and how to apply them fairly.
- Commands — the username letter requirements and the all/others rule.
- On-duty conduct — shifts, professionalism, greetings, and SPaG.
- Melonly logging — starting shifts and logging every punishment.
- Live practice — mock scenarios where you respond while your trainer watches.
Example scenarios you'll be tested on
Your trainer will put you through mock situations like these. There's no trick to them beyond following the process: observe, confirm with evidence, greet, apply the correct tier, log it, and escalate bans to HR+. Here's how to approach the common ones.
Mock A player is RDMing
Don't punish on the report alone. Watch it happen or ask for a clip, greet the players, then apply Minor RDM (Warning + Jail) for a first offence and log it in Melonly. Saying your reasoning out loud helps your trainer see you understand it.
Mock A toxic member in Discord
Claim the ticket, stay calm, and apply the right tier for the behaviour (mild disrespect is Minor; constant abuse is Major). Keep good SPaG and never fire back. Log the action.
Mock A "he-said-she-said" RDM dispute
This tests neutrality and evidence. Ask both sides for clips and timestamps. If the evidence is clear, act on it and log it. If there's genuinely no evidence, don't guess — an unproven punishment isn't valid.
Mock A situation that needs a ban
This checks whether you know your limits. As a trainee-turned-Trial-Moderator you don't ban — you document the evidence and escalate to an HR+. Trying to ban is the wrong move here.
Mock A trick scenario where nothing was actually broken
Sometimes the "rule break" is allowed RP. The right answer is to not punish, explain why, and move on. Punishing allowed roleplay is a mistake.
How to pass
There's no written test. You pass by showing your trainer you understand the rules and can handle situations calmly, fairly, and professionally in the mock scenarios. Know your definitions, keep good SPaG, gather evidence before acting, and ask when you're unsure.
Trainer Section
For staff who hold the Staff Trainer role.
Trainer Guide
For staff with the Staff Trainer role. Your job is to turn an Awaiting-Training member into a confident Trial Moderator. A trainee must not moderate alone until you've passed them. This guide covers the full session, each mock scenario in detail, how to score, and the mistakes to watch for.
Before the session
- Confirm the trainee has read the Community sections and the Glossary.
- Make sure they're set up in Melonly with a linked Roblox account.
- Schedule a time and make sure they can join the staff VC and the ER:LC server.
The session, phase by phase
1 Theory +
2 Commands & tools +
3 Melonly logging +
:log, and auto-logged kicks). Have them log a practice punishment themselves.4 Shadowing +
5 Hands-on (supervised) +
6 Evaluation & sign-off +
Mock scenarios in detail
Run each of these live and grade what the trainee actually does. For every scenario you have the situation, what a pass looks like, and the mistakes that mean they need more practice.
1 · RDM A player is RDMing
What they should do: observe or ask for a clip, greet the players, apply Minor RDM (Warning + Jail) for a 1st offence, and log it in Melonly.
Pass looks like: they confirm before acting, pick the right tier, and log with a reason.
Common mistakes: punishing on the report alone, skipping the greeting, or forgetting to log.
2 · Discord A toxic member in a ticket
What they should do: claim the ticket, stay neutral and calm, apply the right tier (mild = Minor disrespect; constant abuse = Major), and log it.
Pass looks like: good SPaG, no arguing, correct tier.
Common mistakes: firing back at the member, over-punishing mild toxicity, or leaving the ticket unclaimed.
3 · Dispute A "he-said-she-said" RDM
What they should do: ask both sides for clips and timestamps, verify context, act only on evidence.
Pass looks like: genuine neutrality and a refusal to guess without proof.
Common mistakes: siding with whoever spoke first, or handing out a punishment with no evidence.
4 · Escalation A situation that needs a ban
What they should do: document the evidence and escalate to an HR+ — they don't ban as a Trial Moderator.
Pass looks like: they recognise the limit of their authority and hand it up cleanly.
Common mistakes: trying to issue the ban themselves, or not collecting evidence before escalating.
5 · Trick The "rule break" is actually allowed
What they should do: recognise there was a valid RP reason, not punish, explain the call, and move on.
Pass looks like: they resist the urge to act and can say why it's allowed.
Common mistakes: punishing anyway to "be safe" — which is itself a mistake.
Scoring rubric
A trainee should pass only if they meet all of these. If any is shaky, re-train rather than pass.
| Area | Pass | Needs re-training |
|---|---|---|
| Rules & definitions | Defines the core terms cold and recognises them in-game | Hesitates or mixes up RDM/VDM/FailRP/NLR |
| Commands | Uses letter requirements correctly; never touches all/others | Uses wrong letter counts or reaches for all/others |
| Evidence | Always confirms with a clip/screenshot before acting | Acts on reports alone |
| Correct tier | Matches the ladder and escalates bans to HR+ | Invents punishments or over-reaches on bans |
| Logging | Starts/ends shifts and logs every action in Melonly | Forgets to log or to go on shift |
| Conduct | Calm, neutral, professional, good SPaG | Argues, plays favourites, or uses slang on duty |
Common trainee mistakes to watch for
- Acting on the report, not the evidence. The single most common one — coach them to confirm first, every time.
- Over-punishing. Jumping to a kick when a warning fits. Walk them back down the ladder.
- Trying to ban. Remind them Mods/Admins escalate bans to HR+.
- Forgetting to log. "If it isn't in Melonly, it didn't happen."
- Dropping professionalism when a member gets rude. The standard doesn't move.
SHR Section
Senior High Rank and above only.
SHR Section
For Senior High Rank and above — the Board of Executives, the Board of Directors, and Ownership. You set direction, make the final calls below Leadership, and manage the HR team. This section groups your responsibilities, sets out decision principles, and walks through the escalations that reach your desk.
Managing the team
- Manage the HR team — support, oversee, and where necessary remove HRs.
- Promote and demote across the staff team, and keep every change logged in Melonly with a reason.
- Oversee every department and tier of the community.
- Run activity and quality checks on HR, the same way HR checks the ranks below them.
Discipline & final calls
- Approve major and permanent bans, blacklists, and staff removals.
- Make the final decision on major disputes and escalated ban appeals.
- Set and update policy, including this handbook.
Infrastructure & representation
- Manage infrastructure — the Melonly dashboard, bots, integrations, and configuration (or delegate to a dev team).
- Handle partnerships and external representation.
- Lead crisis response — raids, mass rule-breaks, leaks, and major drama. Melonly's raid-revert tools are your friend here.
Decision principles
- Lead by example. The standard you walk past is the standard you set.
- Empower HR; don't micromanage. Let HR run the team and step in for the big calls.
- Keep decisions documented and consistent so the community trusts the process.
- Stay calm in a crisis. Decisions made while angry damage the community.
- Review this handbook regularly and keep it current.
- Real-life safety overrides everything — doxxing, threats, and predatory behaviour are handled immediately and may be reported to platform authorities.
Escalations that reach you
These are the situations HR and below hand upward. None of them change the rules — they're the existing policy applied at your level.
Review An HR applied the wrong ban length
Pull the Melonly log and the evidence. Compare the action against the punishment ladder. If it's wrong, correct the ban length, note the correction in the log, and quietly coach the HR — mentor before you discipline. If it was a genuine judgement call within range, back your HR and explain why to anyone appealing.
Crisis The server is being raided
Stay calm and lead. Use Melonly's raid-revert tools to undo mass damage, get on-duty staff coordinated in one channel, and deal with offenders under the Severe tier (exploiting, mass-RDM). Document everything as you go so the follow-up bans and reports are clean. This is exactly the kind of call that sits with SHR, not LR/MR.
Appeal A permanently-banned member appeals
Permanent-ban appeals are an SHR-level decision. Read the original evidence and log, check whether the punishment matched the ladder, and weigh the member's history. Decide, record the outcome and your reasoning, and communicate it calmly. Keep it consistent with past appeals so the process stays fair.
Policy HR proposes a rule change
HR can propose; changing policy and this handbook is an SHR/Leadership call. Weigh it against how the community actually plays, decide, and if you adopt it, update the handbook so there's a single source of truth. Don't let unwritten rules drift into use.
Who can do what
| Action | LR | MR | HR | SHR | LS |
|---|---|---|---|---|---|
| Warn / jail / kick | ✅ | ✅ | ✅ | ✅ | ✅ |
| Apply a ban | ❌ escalate | ❌ escalate | ✅ | ✅ | ✅ |
| Permanent ban / blacklist | ❌ | ❌ | ⚠️ w/ SHR sign-off | ✅ | ✅ |
| Review ban appeals | ❌ | ✅ minor | ✅ | ✅ all | ✅ |
| Promote / demote staff | ❌ | ❌ | ✅ lower | ✅ | ✅ |
| Issue staff strikes | ❌ | ⚠️ report | ✅ | ✅ | ✅ |
| Change policy / handbook | ❌ | ❌ | ⚠️ propose | ✅ | ✅ |