Server Notice Routing

IRC operators receive raw server notices (SNOTICEs) that are unstructured text varying by IRCd. The /snotice command lets you match, reformat, and route these notices to dedicated buffers — all from within the client.

Adding Rules

/snotice add --match <regex> [--format <fmt>] [--buffer <name>] [--suppress]

Options

Flag	Description
`--match <regex>`	Regex pattern to match against notice text (required)
`--format <fmt>`	Reformat using `${1}` `${2}` capture groups
`--buffer <name>`	Route to a named buffer (auto-created)
`--suppress`	Drop the notice entirely

Examples

Route connection notices to a dedicated buffer:

/snotice add --match "Client connecting.*?: (\S+) \((\S+)@(\S+)\) \[(\S+)\]" --format "[connect] ${1} (${2}@${3}) from ${4}" --buffer snotice-connections

Route disconnections to the same buffer:

/snotice add --match "Client exiting: (\S+) \((\S+)@(\S+)\)" --format "[disconnect] ${1} (${2}@${3})" --buffer snotice-connections

Route nick changes to their own buffer:

/snotice add --match "Nick change: (\S+) -> (\S+)" --format "[nick] ${1} -> ${2}" --buffer snotice-nicks

Suppress noisy notices:

/snotice add --match "Oper-up notice" --suppress

Simple routing without reformatting:

/snotice add --match "KILL message" --buffer snotice-kills

Listing Rules

/snotice list

Shows all rules with their index number:

Snotice rules:
  1: match="Client connecting.*?" format="[connect] ${1}" buffer="snotice-connections"
  2: match="Oper-up" suppress

Suppressing by Literal Text

/snotice suppress <text>

Shorthand for adding a suppress rule with an auto-escaped regex. Useful when the notice text contains regex-special characters that would be tedious to escape manually.

/snotice suppress Oper-up notice from admin

This is equivalent to:

/snotice add --match "Oper\-up notice from admin" --suppress

Viewing Recent Notices

/snotice last [--route --buffer <name>] [--format <fmt>]

Show the most recent raw server notice. Useful for crafting regex patterns — see the raw text, then build a rule from it. With --route, takes the last notice and creates a routing rule for it:

/snotice last --route --buffer snotice-conn --format "[connect] ${1}"

Testing Rules

/snotice test <notice text>

Test your rules against a sample notice to see which rule matches and what the output would be. Paste the exact notice text.

Removing Rules

/snotice remove <number or range>

Remove by the index shown in /snotice list. Supports single numbers, ranges, and comma-separated combinations:

/snotice remove 3
/snotice remove 3-7
/snotice remove 1,4,5
/snotice remove 1,3-5,8

Saving Rules

/snotice save

Persists rules to ~/.config/flume/snotice.toml. Rules are loaded from this file on startup.

File Format

Rules are stored in ~/.config/flume/snotice.toml:

[[rule]]
match = 'Client connecting.*?: (\S+) \((\S+)@(\S+)\) \[(\S+)\]'
format = "[connect] ${1} (${2}@${3}) from ${4}"
buffer = "snotice-connections"

[[rule]]
match = 'Client exiting: (\S+) \((\S+)@(\S+)\)'
format = "[disconnect] ${1} (${2}@${3})"
buffer = "snotice-connections"

[[rule]]
match = "Oper-up"
suppress = true

Capture Groups

Regex capture groups are available as variables in the format string:

Variable	Description
`${0}`	The full match
`${1}`	First capture group
`${2}`	Second capture group
`${3}`	Third capture group
…	And so on

How It Works

Server notices are matched against rules in order
The first matching rule wins
If the rule has a format, the text is reformatted using capture groups
If the rule has a buffer, the notice is routed to that named buffer (auto-created in the buffer list)
If suppress is true, the notice is dropped entirely
Unmatched notices use the default server_notice format from [formats]

IRCd-Specific Examples

UnrealIRCd

/snotice add --match "Client connecting: (\S+) \((\S+)@(\S+)\)" --format "[connect] ${1} ${2}@${3}" --buffer snotice-conn
/snotice add --match "Client exiting: (\S+) \((\S+)@(\S+)\)" --format "[exit] ${1} ${2}@${3}" --buffer snotice-conn

InspIRCd

/snotice add --match "CONNECT: Client connecting on port \d+: (\S+)!(\S+)@(\S+)" --format "[connect] ${1} ${2}@${3}" --buffer snotice-conn

charybdis / solanum (Libera Chat)

/snotice add --match "Client connecting: (\S+) \((\S+)@(\S+)\) \[(\S+)\]" --format "[connect] ${1} (${2}@${3}) [${4}]" --buffer snotice-conn

Rules take effect immediately on add/remove — no restart needed. Use /snotice save to persist across sessions. Flume detects duplicate patterns and will tell you if a rule already exists. /snotice last shows the most recent notice from the active server only.

Getting Started

Configuration

Scripting

Commands

Server Notice Routing

Adding Rules

Options

Examples

Listing Rules

Suppressing by Literal Text

Viewing Recent Notices

Testing Rules

Removing Rules

Saving Rules

File Format

Capture Groups

How It Works

IRCd-Specific Examples

UnrealIRCd

InspIRCd

charybdis / solanum (Libera Chat)

​Adding Rules

​Options

​Examples

​Listing Rules

​Suppressing by Literal Text

​Viewing Recent Notices

​Testing Rules

​Removing Rules

​Saving Rules

​File Format

​Capture Groups

​How It Works

​IRCd-Specific Examples

​UnrealIRCd

​InspIRCd

​charybdis / solanum (Libera Chat)

Adding Rules

Options

Examples

Listing Rules

Suppressing by Literal Text

Viewing Recent Notices

Testing Rules

Removing Rules

Saving Rules

File Format

Capture Groups

How It Works

IRCd-Specific Examples

UnrealIRCd

InspIRCd

charybdis / solanum (Libera Chat)