on_ctcp_request
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
— | on_ctcp_request [2013/02/25 17:16] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ======Synopsis: | ||
+ | [[on]] ctcp_request | ||
+ | |||
+ | ======Description: | ||
+ | This hook is triggered when the client receives a [[CTCP]] request. | ||
+ | |||
+ | It's important to understand the difference between this and [[on ctcp]]. | ||
+ | The [[on ctcp]] event is thrown for when the client has already handled | ||
+ | the request and wants to tell the user. | ||
+ | But [[on ctcp_request]] is thrown " | ||
+ | the request, before the client does anything. | ||
+ | If you handle [[on ctcp_request]] you will suppress the client' | ||
+ | handling of that [[ctcp]] so don't suppress stuff like [[ctcp dcc|dcc]]. | ||
+ | |||
+ | The only appropriate response to a [[on ctcp_request]] is a [[ctcp]] command | ||
+ | that is sent as a proper reply (the client handles that). | ||
+ | a [[msg]] the client will convert it to a [[notice]]. | ||
+ | |||
+ | ======Parameters: | ||
+ | |$0 |nickname of [[CTCP]] message sender | ||
+ | |$1 |target of [[CTCP]] (client' | ||
+ | |$2 |type of CTCP | | ||
+ | |$3- | ||
+ | |||
+ | ======Examples: | ||
+ | To customize [[CTCP]] [[ctcp VERSION|VERSION]] replies: | ||
+ | on ^ctcp_request "% % VERSION*" | ||
+ | ctcp $sender VERSION ircII $J + myscript; | ||
+ | }; | ||
+ | |||
+ | ======History: | ||
+ | |||
+ | # $EPIC: on_ctcp_request.txt, | ||
on_ctcp_request.txt · Last modified: 2013/02/25 17:16 by 127.0.0.1