Ctcp: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
No edit summary |
||
| (One intermediate revision by one other user not shown) | |||
| 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== | ||
| Line 8: | Line 19: | ||
[[Category:Commands]] | [[Category:Commands]] | ||
[[Category:Undocumented | [[Category:Undocumented commands]] | ||
Latest revision as of 19: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>