Difference between revisions of "Ctcp"
From Scriptwiki
m (Category..commands is lower cased) |
|||
| Line 1: | Line 1: | ||
| + | CTCP extends the IRC protocol's existing PRIVMSG by adding $chr(1) at the start and at the end of the message. | ||
| + | PRIVMSG NICK :?version? | ||
| + | or | ||
| + | PRIVMSG NICK $+(:,$chr(1),version,$chr(1)) | ||
| + | |||
| + | Most clients can handle CTCP's as their own commands and events, like mIRC. | ||
| + | Most common CTCP commands, recognised by majority of clients are: | ||
| + | * VERSION | ||
| + | * TIME | ||
| + | * PING | ||
| + | |||
| + | |||
Sends a CTCP (Client to Client Protocol) request to the user. | Sends a CTCP (Client to Client Protocol) request to the user. | ||
| − | + | /ctcp <nick> <request> | |
| − | ctcp <nick> <request> | ||
==See Also== | ==See Also== | ||
Latest revision as of 20:06, 27 November 2014
CTCP extends the IRC protocol's existing PRIVMSG by adding $chr(1) at the start and at the end of the message.
PRIVMSG NICK :?version?
or
PRIVMSG NICK $+(:,$chr(1),version,$chr(1))
Most clients can handle CTCP's as their own commands and events, like mIRC. Most common CTCP commands, recognised by majority of clients are:
- VERSION
- TIME
- PING
Sends a CTCP (Client to Client Protocol) request to the user.
/ctcp <nick> <request>
