Chanop cheat sheet#
For channel operators (+o). You have partyline access, so partyline
(.command) forms lead; the in-channel IRC equivalents are shown alongside.
(See Joining the partyline if
you’re not connected yet.)
<chan> is #motorcycles unless you’re acting on another channel the bot sits
on.
Getting opped#
Ask the bot to op you:
/msg <bot> op <password>On the partyline, .op <yournick> #motorcycles does the same thing.
If nothing happens — the bot doesn’t reply and you stay deopped — it’s almost always one of:
- The bot doesn’t recognize you. A changed hostmask (dynamic IP, VPN, a different nick) means the bot can’t match you to your record. Ident first with
/msg <bot> ident <password>(see the user cheat sheet), then retryop.- No password set, or it’s wrong. Set one with
/msg <bot> pass <newpass>(or.pass <newpass>on the partyline).
Kick#
.kick <chan> <nick> [reason] (partyline — goes through the bot)Ban#
Use the bot’s .+ban for any ban you want the bot to remember (with expiry,
logging, and sticky/dynamic behavior — see
ban maintenance):
.+ban <hostmask> [chan] [%Xh] [reason] (partyline — bot-managed)
.-ban <hostmask|number> (remove a bot ban)
.bans [all] (list the bot's bans)For a one-off you don’t need the bot to track, a raw server ban works too:
/mode <chan> +b <hostmask> (IRC — not remembered by the bot)If a ban isn’t sticking — it keeps disappearing, or comes back — read ban maintenance. It’s the dynamic vs sticky distinction: dynamic bans expire (default 5 hours on this fleet!) and get cleaned up; sticky bans persist. You almost always want
.+ban+.stickfor a troll, not/mode +b.
Op / deop / voice#
In channel (IRC):
/mode <chan> +o <nick> op someone
/mode <chan> -o <nick> deop
/mode <chan> +v <nick> voiceVia the bot (partyline):
.op <nick> <chan>
.deop <nick> <chan>
.voice <nick> <chan>
.devoice <nick> <chan>Finding a user’s record#
To see if someone has a bot record, their flags, and their hostmasks:
.whois <nick> (partyline — looks up the nick's record)
.match <handle> (partyline — find a record by handle).whois is the quick check; .match finds records by handle or pattern.
Finding a botmaster#
You can’t add or fix a user record yourself (that’s a botmaster job), but you can find one:
.match +m lists all users with +m (master) flag.match +m lists everyone with a master flag on their user record; ask them
(via partyline or in channel) to add or fix a member’s record.
Quick reference#
| Task | Partyline (lead) | In-channel IRC |
|---|---|---|
| Kick | .kick <chan> <nick> [reason] | /kick <chan> <nick> [reason] |
| Ban (persistent) | .+ban <hostmask> [chan] [%Xh] [reason] | — (use .+ban) |
| Ban (one-off) | — | /mode <chan> +b <hostmask> |
| Remove a bot ban | .-ban <hostmask|number> | — |
| List bans | .bans [all] | /mode <chan> +b (server bans only) |
| Stick a ban (don’t dynamically remove) | .stick <number | - |
| Op / deop | .op <nick> <chan> / .deop <nick> <chan> | /mode <chan> ±o <nick> |
| Find a record | .whois <nick> / .match <handle> | — |
| Find a botmaster | .match +m | — |