The !Rules Command: Keep Chat Rules One Trigger Away

What Does the !Rules Command Do?

The !rules command posts your chat rules into chat when anyone types the trigger. That's the whole feature, and its value comes entirely from location. Your rules probably already exist somewhere — a Twitch panel below the player, a Discord channel, a line in your About section — and all of those places share a problem: they're not where people are when they break a rule.

Consider how a new viewer actually arrives. They click your channel from the directory or land in a raid, the player fills the screen, and chat is moving. Nothing about that experience involves scrolling below the video player to read panels, and on mobile the panels are behind another tap entirely. Then they type something that violates a rule they had no realistic way of knowing about, and a mod deletes it. From their side, they got punished by an invisible standard.

A command closes that gap in both directions. A curious viewer can check the rules themselves before participating, and a mod can post the rules at someone in one keystroke rather than typing out an explanation while three other things need attention. Both of those are worth more than the thirty seconds the setup costs.

It's a static command with a fixed response, so it's technically identical to !discord or !socials. The difficulty is entirely in the writing: compressing a moderation philosophy into one chat line that a stranger can parse in two seconds.

Rules in Chat Beat Rules in a Panel

There's a moderation principle underneath this that's worth stating directly: enforcement without visible standards feels arbitrary, and arbitrary enforcement is what makes people leave a community angry rather than quietly. A timeout for something the viewer didn't know was against the rules reads as the streamer or a mod being on a power trip, even when the rule is completely reasonable. The same timeout, delivered after the rules were posted in front of them, reads as fair. Nothing changed except whether the standard was visible first.

That matters most for the people you'd actually want to keep. A dedicated troll doesn't care what your rules say and will get banned regardless. The person who benefits from a !rules command is the ordinary viewer who dropped a link, spoiled a game, argued about politics, or backseated the whole boss fight without realising it was unwelcome. Those people usually adjust immediately when told — but only if the telling happens before the punishment.

There's a self-protective angle too. Writing your rules down forces you to decide what they are, and streamers who haven't done that end up moderating by mood: the same joke is fine on a good night and gets a timeout on a bad one. Inconsistency is corrosive because chat notices, and it puts your mods in an impossible position — they can't enforce a standard you haven't articulated. A written line, even a short one, gives your mod team something to point at instead of having to guess what you'd want.

Keep the command's response short and keep the long version elsewhere. A chat message is not the place for eleven numbered clauses; it's the place for the three or four things people actually get wrong, plus a link to the full version for anyone who wants it. Panels and Discord channels remain useful as the detailed reference — the command is the summary that reaches people at the moment it's relevant.

One nuance if you stream to more than one platform at a time: the same chat isn't really the same chat. Twitch, YouTube Live and Kick have different native moderation defaults, different community norms and often noticeably different behaviour in your own chat. A rules command that runs across all of them via a multistream bot at least guarantees a single standard applies everywhere, which is far easier to defend than enforcing different rules in each room. If one platform's audience consistently needs a different emphasis, adjust the wording per platform rather than the rules themselves.

Using !Rules as a First Warning

The most effective way to use this command isn't as a reference — it's as the first step in a moderation ladder. When someone crosses a line for the first time, a mod types !rules instead of issuing a timeout. The message posts publicly, the offender sees the standard, and everyone else in chat sees that the standard exists and is enforced. It's a warning that costs the viewer nothing and costs your mod one keystroke.

Formalise the ladder so your mods don't have to improvise. A workable default: first offence gets !rules, second gets a short timeout (60 to 600 seconds), third gets a long timeout or a ban. Anything on the zero-tolerance list — slurs, harassment, sexual content involving minors, doxxing, scam links — skips straight to a ban with no warning at all. Writing that ladder down for your mod team, even as a pinned note in your Discord, removes almost all of the second-guessing that makes moderating stressful.

Some bots let you fire the rules message at a specific user, which is worth using when you have it: “@newviewer — chat rules: …” lands more precisely than a general post and is less likely to feel like a public shaming than a mod typing out a personal correction. Where that's not supported, a plain !rules immediately after the offending message is clear enough from context.

Consider a timer for the first stretch of a broadcast. Posting the rules automatically every 20 to 30 minutes for the first hour catches arrivals who would never type the command, then backs off once your regulars have settled in. This is particularly worth doing on raid-heavy nights, where you get bursts of forty unfamiliar people arriving with no idea of your norms — pair it with a shoutout command so the raid gets both the welcome and the ground rules in the same minute.

Automated moderation is the layer underneath all of this, and it works best when the human layer is already defined. AutoMod on Twitch and equivalent filters elsewhere catch the obvious cases before a human sees them, while an AI chat bot can flag borderline messages — the sarcasm, the escalating argument, the hostility that a keyword filter reads as harmless — for a mod to judge. The rules command is what makes that enforcement legible to the person on the receiving end: the filter blocks the message, the command explains why.

Two practical settings to get right. Give !rules a global cooldown of around 30 seconds so it can't be weaponised by someone spamming it at chat, but do not restrict it to mods — a viewer who wants to check the rules before participating is exactly the person you want to make it easy for. And keep the response current: rules you no longer enforce are worse than no rules, because they teach chat that the list is decorative.