on_ctcp_reply
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
— | on_ctcp_reply [2012/07/04 06:30] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | # $EPIC: on_ctcp_reply.txt, | ||
+ | ======Synopsis: | ||
+ | [[on]] [< | ||
+ | |||
+ | ======Summary: | ||
+ | Triggered when people answer your [[CTCP]] requests | ||
+ | |||
+ | ======Description: | ||
+ | This hook is triggered whenever the client receives a CTCP reply from | ||
+ | another client. | ||
+ | any [[CTCP]] messages to receive a " | ||
+ | |||
+ | ======Parameters: | ||
+ | |$0 |nickname of user sending reply | | ||
+ | |$1 |target of [[CTCP]] command | | ||
+ | |$2 |[[CTCP]] command being replied to | | ||
+ | |$3- | ||
+ | |||
+ | ======Default Action: | ||
+ | If you don't suppress this event, the client will format the message and | ||
+ | display it to the screen. | ||
+ | |||
+ | ======Examples: | ||
+ | To customize the appearance of [[CTCP]] reply strings: | ||
+ | on ^ctcp_reply * (sender, recvr, ctcp, stuff) { | ||
+ | echo *** Reply from $sender to $recvr for CTCP $ctcp request: $stuff; | ||
+ | }; | ||
+ | |||
+ | ======Restrictions: | ||
+ | Automatic replies ([[MSG]]s, [[CTCP]]s, [[NOTICE]]s, | ||
+ | this hook are explicitly prohibited. | ||
+ | will do everything in its power to prevent it. Any attempt will result in an | ||
+ | error message. | ||
+ | |||
+ | ======Compatibility: | ||
+ | This hook was recently changed, so that the $1 argument is now the | ||
+ | actual target of the [[CTCP]] reply. This potentially breaks older scripts. | ||
+ | This was changed in CVS at commit level 140, on 15 November 2001. | ||
+ | All releases, development versions, and CVS non-releases before this | ||
+ | date use the OLD format for this hook. All releases, snapshots, etc | ||
+ | use the new format. | ||
+ | |||
+ | ======History: | ||
on_ctcp_reply.txt · Last modified: 2012/07/04 06:30 by 127.0.0.1