Server Notice Masks (SNOMASK)
m |
|||
| Line 1: | Line 1: | ||
Service notice masks (snomask) allow clients to specify which types of server notices they'd like to receive while they have usermode +s. The mask may optionally be omitted, and reasonable defaults will be used by the server. | Service notice masks (snomask) allow clients to specify which types of server notices they'd like to receive while they have usermode +s. The mask may optionally be omitted, and reasonable defaults will be used by the server. | ||
| - | The descriptions given below are probably best understood by those who are familiar with C syntax. Additionally, this document makes no attempt to explain the hexadecimal values given below. It is assumed the reader has familiarity with | + | The descriptions given below are probably best understood by those who are familiar with C syntax. Additionally, this document makes no attempt to explain the hexadecimal values given below. It is assumed the reader has familiarity with both. |
Usage: /mode <nick> +s [+/-][mask] | Usage: /mode <nick> +s [+/-][mask] | ||
Revision as of 06:34, 6 April 2008
Service notice masks (snomask) allow clients to specify which types of server notices they'd like to receive while they have usermode +s. The mask may optionally be omitted, and reasonable defaults will be used by the server.
The descriptions given below are probably best understood by those who are familiar with C syntax. Additionally, this document makes no attempt to explain the hexadecimal values given below. It is assumed the reader has familiarity with both.
Usage: /mode <nick> +s [+/-][mask]
| Mask | Hex Value | Description | |
|---|---|---|---|
| 1 | SNO_OLDSNO | 0x1 | Old unsorted messages. |
| 2 | SNO_SERVKILL | 0x2 | Server Kills (nick collisions). |
| 4 | SNO_OPERKILL | 0x4 | Oper Kills. |
| 8 | SNO_HACK2 | 0x8 | Desync messages. |
| 16 | SNO_HACK3 | 0x10 | Temporary desync messages. |
| 32 | SNO_UNAUTH | 0x20 | Unauthorized connection messages. |
| 64 | SNO_TCPCOMMON | 0x40 | Common TCP or socket errors. |
| 128 | SNO_TOOMANY | 0x80 | Too many connections messages. |
| 256 | SNO_HACK4 | 0x100 | Services actions on channels (ChanServ/OperServ). |
| 512 | SNO_GLINE | 0x200 | G-line notifications. |
| 1024 | SNO_NETWORK | 0x400 | Net join/break notices, etc. |
| 2048 | SNO_IPMISMATCH | 0x800 | IP mismatch notifications. |
| 4096 | SNO_THROTTLE | 0x1000 | Host throttle add/remove notices. |
| 8192 | SNO_OLDREALOP | 0x2000 | Old oper-only messages (/oper attempts, etc). |
| 16384 | SNO_CONNEXIT | 0x4000 | Client connect/disconnect notices. |
Default Masks
- standard +s: has no effect on DareNET
- standard +s when opered (+o/O): SNO_DEFAULT | SNO_HACK2 | SNO_HACK4 | SNO_OLDSNO
Example Usage
If you wanted to receive only operkills, you would use the following:
/mode <nick> +s 4
To receive both operkills and glines, you would add the values together (operkills = 4, glines = 512 (see table above for values), sp 512+4-516):
/mode <nick> +s 516
If you are already receiving notices, and you'd like to add an additional notice, for example SNO_NETWORK (e.g. netjoins/breaks), you'd just use its value:
/mode <nick> +s +1024
If you would like to stop receiving such notices, for example SNO_NETWORK, but continue receiving other notices, you'd use:
/mode <nick> +s -1024 or /mode <nick> -s +1024
While users can set +s, they will not receive any notices on DareNET. Opers who set +s will automatically receive netjoins/breaks, operkills, glines and HACK notices.
