IRC Documentation · Beginner
NOTICE command: send a notification without a response loop
NOTICE carries a notification. It resembles PRIVMSG on the wire, but its response rule is different: a client should not produce an automatic response to a NOTICE. This distinction avoids loops between bots and services.
Dialova Team · Verified on
Syntax and Parameters #
NOTICE <cible>{,<cible>} :<texte>| Parameter | Meaning |
|---|---|
| target | Nickname or channel according to server rules. |
| text | Notification intended to be displayed; the interface decides its presentation. |
Commented Example #
C: NOTICE Bob :Le traitement est terminé.
S: :Alice!alice@cloak.example NOTICE Bob :Le traitement est terminé.Nicknames, hosts, and text in this exchange are fictional. The client may display responses in a more readable format than the presented frames.
Possible Responses and Errors #
| Response | Understanding |
|---|---|
| NOTICE | Notification transmitted to the authorized recipient. |
| Error | Typical Cause |
|---|---|
| No automatic error response | The command should not trigger an automatic response; do not rely on a failure numeric to drive a bot. |
Rights, Compatibility, and Precautions #
NOTICE is not a channel reserved for administrators and does not make a message authentic. An ordinary sender can send one; verify account identity and the origin of sensitive requests.
On-screen placement depends on the client: server window, active conversation, or dedicated message. On Dialova, a NOTICE does not open a new private conversation like a chat message.
Frequently Asked Questions #
Is a NOTICE more confidential? No: the choice of command does not encrypt anything.
Can my bot automatically reply "received"? Not to a NOTICE. Reserve automatic interactions for messages and events intended for them, with their anti-loop limits.
Sources & Verification
Examples use pseudonyms and fictional domains, except for explicitly documented connection points. Network-specific extensions and settings are noted in the text.
- Modern IRC — spécification du protocole client ↗Source Specification · consulted on 2026-10-29
- RFC 2812 — Client Protocol (2000) ↗Source Historical · consulted on 2026-10-29