On ctcpreply: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
m Cail moved page Ctcpreply to On ctcpreply without leaving a redirect: new name |
||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
The on CTCPREPLY event triggers when a user sends a standard [[ctcp|CTCP]] reply to a [[ctcp|CTCP]] that you initiated. | |||
on <level>:CTCPREPLY:<matchtext>:<commands> | |||
Examples: | |||
on 1:CTCPREPLY:VERSION*:/echo $nick is using IRC client: $1- | |||
This is triggered when a client replies to a [[ctcp|CTCP]] VERSION request that you sent. | |||
on 1:CTCPREPLY:PING*:/echo $nick replied to my ping! | |||
This is triggered when a client replies to a [[ctcp|CTCP]] PING request that you sent. | |||
==See Also== | ==See Also== |
Latest revision as of 23:46, 22 June 2013
The on CTCPREPLY event triggers when a user sends a standard CTCP reply to a CTCP that you initiated.
on <level>:CTCPREPLY:<matchtext>:<commands>
Examples:
on 1:CTCPREPLY:VERSION*:/echo $nick is using IRC client: $1-
This is triggered when a client replies to a CTCP VERSION request that you sent.
on 1:CTCPREPLY:PING*:/echo $nick replied to my ping!
This is triggered when a client replies to a CTCP PING request that you sent.