# $EPIC: on_ctcp_reply.txt,v 1.5 2012/07/04 06:30:23 jnelson Exp $
======Synopsis:======
[[on]] [<modes>]ctcp_reply [<serial#>] [-|^]<match> { <action> }

======Summary:======
Triggered when people answer your [[CTCP]] requests

======Description:======
This hook is triggered whenever the client receives a CTCP reply from
another client.  Note that the client doesn't necessarily need to send
any [[CTCP]] messages to receive a "reply".

======Parameters:======
|$0    |nickname of user sending reply |
|$1    |target of [[CTCP]] command |
|$2    |[[CTCP]] command being replied to |
|$3-   |actual reply to [[CTCP]] command (varies, depends on $1) |

======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, etc.) to the sender with
this hook are explicitly prohibited.  The protocol disallows it, and the client
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:======