Docs The bot
Moderation and protection
Bans, temporary bans, kicks, timeouts and warnings, each a numbered case in one mod log, in Discord and in game. Plus notes, a warning ladder, Ban BOLOs, appeals, anti-nuke and anti-raid.
Moderation actions
/ban, /kick, /timeout, /softban and /warn work from Discord. Every action becomes a numbered case, and the member gets a DM saying what happened and why.
- Temporary bans. Give
/bana length such as12h,7dor2w. The ban lifts itself when it ends. Leave the length empty for a permanent ban./mod tempbanslists the ones still running. - In-game bans. Add their Roblox username to
/banand County Control runs:banin your ER:LC server too. When the ban ends, or you/unbanthem, the in-game ban is lifted for the same name. - Bans by ID.
/bantakes a user ID, so you can ban someone who already left.
The mod log
Pick one channel for the mod log on the dashboard's Moderation page or with /mod settings. Every case is posted there as the same card: who, which moderator, the reason, the length, whether the DM arrived and whether the in-game ban worked. Purges, channel locks and anti-nuke alerts go there too.
Bans, kicks and timeouts done from Discord's own menus become cases as well, marked as done outside the bot. County Control needs the View Audit Log permission for that. You can turn it off.
Cases and history
/logs (or /mod history) opens a member's record: every case, newest first, a page at a time, with their notes on a second tab. The History button on any card in the mod log opens the same thing. /case opens one case by number and /reason corrects its reason, which updates the card in the mod log.
/mod void marks a case made in error. It stays on record, struck through, and counts for nothing. Voiding does not lift a ban or a timeout.
The warning ladder
Repeat warnings can act on their own. Out of the box, 3 warnings means a 1 hour timeout, 5 means a kick and 7 means a permanent ban. You can change each step, add a fourth, or switch them off, on the dashboard or with /mod ladder.
| Setting | Default | What it does |
|---|---|---|
| Steps 1 to 4 | 3, 5, 7, off | How many active warnings trigger each step, and what it does: a timeout, a kick, a ban for a set time, or a permanent ban. |
| Warnings stop counting after | Never | Older warnings drop out of the count. They stay on record. |
Only active warnings count. /mod pardon takes one warning out of the count, for example after a successful appeal. The step that fires is its own case, linked to the warning that caused it.
Notes
/mod note adds a private note to a member's record, something staff should know that is not a punishment. Notes never DM anyone. /mod delnote removes one.
Appeals
Set an appeal link on the dashboard (an https link to a form or an appeals server). Members who are banned get an Appeal button in their DM.
In-game moderation
Warnings, kicks and bans on Roblox players get a record of their own, kept per player and found by username. They use the same numbered cases and the same mod log, so /case, /reason and /mod void work on them too.
| Command | What it does |
|---|---|
/erlc warn | Records a warning and sends the player an in-game message with the reason. |
/erlc kick | Kicks the player in game and records it. |
/erlc ban | Bans the player in game. Add a length such as 7d for a ban that lifts itself. |
/erlc unban | Lifts an in-game ban and records it. |
/erlc bolo | A Ban BOLO: the player is banned the next time they join. For someone who left before you could ban them. |
/erlc note | A staff note on the player. They are not told. |
/erlc lookup | The player's history a page at a time, whether they are in the server now (team, callsign, wanted stars, where they are), their linked Discord account, and how many previous punishments they have. |
You can name several players at once, separated by commas. For someone in the server, part of the name is enough, as in game. Each command needs the same access as its Discord version: /warn for warnings, /kick for kicks and /ban for bans, unbans and BOLOs.
Previous punishments counts a player's warnings and kicks since their last ban. A ban starts the count again.
From the game
- Kicks and bans run in game are recorded. When your staff run
:kickor:banin the server, it becomes a case with their name on it. Add the reason later with/reason. - The :log command. Staff type
:log warn PlayerName reasonin game (orkick,ban,bolo,note) to record a case without running anything. County Control replies with an in-game message. It is off until you turn it on, because Melonly uses the same command and you would get every log twice. - Ban BOLOs are enforced. A player with an active BOLO is banned as soon as they join.
- Kick rejoin timer. Set a number of minutes and a kicked player who comes back sooner is kicked again, or banned.
Every setting is on the dashboard's Moderation page under In-game moderation.
Protection
/antinuke enable watches for mass deletes and bans by a compromised account and stops it with a ban or by stripping roles. Trusted users and roles are set with /antinuke whitelist. /antiraid protects against mass joins. Both report to the mod log, and an anti-nuke ban is a case like any other.
Something unclear or out of date? Tell us in the support server.