How-to

Warn or ban a player

Give weighted warnings, set up the automatic ban, and ban for a set time without typos.

This page shows you how to warn players, let the bot ban them when their warnings add up, and ban someone for the right length of time. You need the Scrim Supervisor or Scrim Manager role. The server owner and anyone with Administrator or Manage Server can do it too. !warn, !ban and !warnings answer in public, so use a staff channel.

Warn a player

1. Type !warn @player reason. You must give a reason. This warning weighs 1.
2. For something serious, put a weight from 1 to 100 before the reason: !warn @player 8 threw the game.
3. The reply shows the case number and the player's total weight out of the limit (10 by default). The player also gets a DM.
4. When they reach the limit, the bot bans them from scrims for 3 days and gives them Scrim Banned. By default, their warnings then start again from zero.
5. !warnings @player lists their warnings and their total weight out of the limit. A warning that weighs more than 1 shows its weight. To take one back, run /removewarn player:@name and pick it. Only you see that reply. Removing a warning doesn't lift a ban the player already has.

If a player doesn't ready up in a ranked match, the bot warns them by itself with weight 1. It only warns for casual no-shows if you turn that on. It never warns in tournament matches.

Rules for repeat no-shows

The same players missing ready checks night after night can be handled harder. On the dashboard's Settings page, open No-shows. Everything there is off until you set it, so on its own every no-show weighs the same.

• Free no-shows: the first ones in a row cost nothing but a reminder DM.
• Bigger warnings for repeat no-shows: with No-shows before warnings grow at 2, no-shows weigh 1, 1, 2, 2, 3, 3, up to Most points for one no-show. Repeat no-shows reach the automatic ban much sooner.
• Days to forget no-shows: a player who goes that many days without one starts over.
• Queue timeout after a no-show: the player can't join any queue for a while. It starts at First timeout and grows by Timeout growth with each repeat, up to Longest timeout. It works even with warnings off.

The bot says in the DM and in the match channel which no-show in a row it was, what it weighed, and when the player can queue again. !warnings @player and /warnings show the run and what the next one would cost. !clearnoshows @player forgets a player's no-shows and ends a timeout. Their warnings stay.

Set up the automatic ban

The dashboard is only for Managers: the server owner, the Scrim Manager role, and anyone with Administrator or Manage Server. Supervisors can't open it. On the dashboard's Settings page, open Moderation & access to change Warning points before a ban. No-shows has Warning points for a no-show, Warn no-shows in casual too and the rules for repeat no-shows. Punishments has Auto-ban length (days) and Clear warnings after a ban. Then press Save settings. A Manager can also type !set maxwarnings 15.

If you untick Clear warnings after a ban, the player stays at the limit. Then every new warning bans them again.

To turn warnings off, untick Warnings on the Features page and press Save. Then !warn stops working and no-shows aren't warned.

Ban a player

1. Type !ban @player 7d reason. Use days and hours only, like 24h or 2d12h. Put days before hours, with no space.
2. For a permanent ban, leave the time out: !ban @player reason.
3. The bot gives the player Scrim Banned, sends them a DM and logs a case. The queue checks for this role when a player joins.
4. The player can check their ban with /banstatus. Timed bans end by themselves. The bot checks for ended bans every 5 minutes.
5. To lift a ban early, type !unban @player. A user ID works too. To see who is banned right now, type !mod and press View Bans.
6. Managers can also do this on the dashboard's Players page. The Scrim bans card lists everyone banned right now. Press Lift ban next to a name, and the page asks first. On paid servers the card also shows recent bans and unbans. Banning is still done with !ban in Discord.

Things that go wrong

• The bot doesn't read 1w, 30m or 7 days as a time. It makes the ban permanent and puts the typo at the start of the reason. With 1d 12h, it bans for 1 day and puts 12h in the reason. Ban again with the right time. The new ban replaces the old one.
• If a warning reason starts with a number from 1 to 100 and more words follow, the bot reads the number as the weight. !warn @player 3 no-shows weighs 3, and the reason is just "no-shows".
• If the bot says it couldn't give the role, open Server Settings, then Roles. Drag the BrawlScrims role above Scrim Banned, then ban again. An automatic ban doesn't tell you when this happens, so check the player has the role. You can rename Scrim Banned. The bot finds it by the role it saved, not by its name. To use another role, pick it as Scrim Banned role on the Setup page, under Channels and roles the bot uses.
• If a player who is already banned reaches the warning limit, the bot keeps the longer ban. A permanent ban stays permanent.
• A ban takes the player out of the queue they're waiting in, together with their party.
• If a player isn't in the server, a warning is still saved, but it can't start the automatic ban. If you ban someone who isn't in the server, they get the Scrim Banned role when they join.

You can find more commands in Staff powers. To see what players see, read Warnings and bans.