on_server_notice
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
| — | on_server_notice [2008/02/20 03:41] (current) – created - external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | # $EPIC: on_server_notice.txt, | ||
| + | ======Synopsis: | ||
| + | [[on]] [< | ||
| + | |||
| + | ======Description: | ||
| + | This event is thrown when the server you are connected to sends you a | ||
| + | [[notice]] and you didn't handle it in a more specific way. If a remote | ||
| + | server sends you a [[NOTICE]] it will be treated like a notice from another | ||
| + | irc user and routed through [[on general_notice]]. | ||
| + | |||
| + | There are several different type of server notices, and they are processed | ||
| + | differently by the client. | ||
| + | |||
| + | A kill notice starts with "*** Notice -- Received KILL message for" and | ||
| + | that will throw an [[on kill]] event, | ||
| + | treat it as an oper notice. | ||
| + | |||
| + | An oper notice starts with "*** Notice --" and that will throw an | ||
| + | [[on oper_notice]] event, and if you don't catch that, it will treat it | ||
| + | as a general notice. | ||
| + | |||
| + | A server notice will throw an [[on general_notice]] event. | ||
| + | catch it, it will throw an [[on server_notice]] event. | ||
| + | that, it will format the message and display it to your SNOTE window. | ||
| + | |||
| + | ======Parameters: | ||
| + | |$0 |server sending the message| | ||
| + | |$1 |first word of the actual message (usually " | ||
| + | |$2- |remainder of message| | ||
| + | |||
| + | |||
on_server_notice.txt · Last modified: 2008/02/20 03:41 by 127.0.0.1
