Semiconductor & Computer Engineering
m |
Maroonbells (talk | contribs) |
||
| Line 19: | Line 19: | ||
== Examples == | == Examples == | ||
| + | triggers when someone sends a private ctcp "test", which is a privmsg, and then use /ctcpreply, which sends a notice, this will trigger the {{mIRC|on events/on ctcpreply|on ctcpreply}} event for that user. | ||
<syntaxhighlight lang="mIRC"> | <syntaxhighlight lang="mIRC"> | ||
ctcp *:test:?:ctcpreply $nick success | ctcp *:test:?:ctcpreply $nick success | ||
</syntaxhighlight> | </syntaxhighlight> | ||
| − | + | ||
| + | You can use the CTCP event to either halt or replace the default time reply. This example sends a substitute reply at a random time within a 24 hour window, then halts mIRC from returning the default reply containing your true time. If you want to block the TIME reply only, remove the /ctcpreply but keep the /halt | ||
| + | |||
| + | <syntaxhighlight lang="mIRC"> | ||
| + | ctcp *:time:{ ctcpreply $nick TIME $asctime($calc($ctime -43200+ $r(0,86400) )) | halt } | ||
| + | </syntaxhighlight> | ||
| + | |||
| + | However, mIRC doesn't allow the CTCP event to suppress the default version reply. If you do the same thing as above, this would send a second reply to the standard ctcp version, but it does not block the default reply. | ||
<syntaxhighlight lang="mIRC"> | <syntaxhighlight lang="mIRC"> | ||
| − | ctcp *:version:?:ctcpreply $nick mIRC 12.5!! | + | ctcp *:version:?:{ ctcpreply $nick mIRC 12.5!! | halt } |
| − | </syntaxhighlight> | + | </syntaxhighlight> |
| + | Formerly, you could block the ctcp reply only by using /ignore -t to block *all* incoming ctcp. But with the ON PARSELINE event, you can replace the outbound message. Note that the reply used to be always using NOTICE, but in newer versions there can be some situations where your version reply is made as a CNOTICE, so you should detect both types now. You can modify any part between but not including the $regml(1) and the $+ $chr(1) | ||
| + | <syntaxhighlight lang="mIRC"> | ||
| + | On $*:PARSELINE:out:/^((NOTICE|CNOTICE \S+) \S+ :\x01VERSION) mIRC/:{ .parseline -otn $regml(1) Not mIRC $version $+ $iif($beta,. $+ $v1) $+ $chr(1) } ; modify of SReject 2017 | ||
| + | </syntaxhighlight> | ||
== Compatibility == | == Compatibility == | ||
{{mIRC compatibility|3.5}} | {{mIRC compatibility|3.5}} | ||
| − | |||
== See also == | == See also == | ||
| + | * {{mIRC|on parseline}} | ||
* [[List of on events - mIRC|mIRC Events]] | * [[List of on events - mIRC|mIRC Events]] | ||
| − | |||
| − | |||
Latest revision as of 11:45, 24 November 2020
- On events
- Access levels
- Raw Events
- Ctcp Events
CTCP stands for Client-To-Client-Protocol which is a special type of communication between IRC Clients. By creating CTCP events, you can make your mIRC react to commands or requests from other users.
For example when you want to know the version of the client used by an user, you type /ctcp <user> version, this actually send a privmsg
Contents
Format[edit]
The CTCP event has the following format:
ctcp <level>:<matchtext>:<*|#|?>:<commands>
- <level> - The corresponding access levels for the event to trigger.
- <matchtext> - The corresponding matchtext for the event to trigger.
- <*><?><#> - The place, or places where the event listens, you can specify specific name of window, seperate them by comma.
- * - Any query/channel window
- ? - Any query windows
- # - Any channel window
- <commands> - The commands to be performed when the event triggers
Examples[edit]
triggers when someone sends a private ctcp "test", which is a privmsg, and then use /ctcpreply, which sends a notice, this will trigger the on ctcpreply event for that user.
ctcp *:test:?:ctcpreply $nick success
You can use the CTCP event to either halt or replace the default time reply. This example sends a substitute reply at a random time within a 24 hour window, then halts mIRC from returning the default reply containing your true time. If you want to block the TIME reply only, remove the /ctcpreply but keep the /halt
ctcp *:time:{ ctcpreply $nick TIME $asctime($calc($ctime -43200+ $r(0,86400) )) | halt }
However, mIRC doesn't allow the CTCP event to suppress the default version reply. If you do the same thing as above, this would send a second reply to the standard ctcp version, but it does not block the default reply.
ctcp *:version:?:{ ctcpreply $nick mIRC 12.5!! | halt }
Formerly, you could block the ctcp reply only by using /ignore -t to block *all* incoming ctcp. But with the ON PARSELINE event, you can replace the outbound message. Note that the reply used to be always using NOTICE, but in newer versions there can be some situations where your version reply is made as a CNOTICE, so you should detect both types now. You can modify any part between but not including the $regml(1) and the $+ $chr(1)
On $*:PARSELINE:out:/^((NOTICE|CNOTICE \S+) \S+ :\x01VERSION) mIRC/:{ .parseline -otn $regml(1) Not mIRC $version $+ $iif($beta,. $+ $v1) $+ $chr(1) } ; modify of SReject 2017
Compatibility[edit]
Added: mIRC v3.5
Added on: 07 Aug 1995
Note: Unless otherwise stated, this was the date of original functionality.
Further enhancements may have been made in later versions.