From WikiChip
Editing mirc/raw events
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
This page supports semantic in-text annotations (e.g. "[[Is specified as::World Heritage Site]]") to build structured and queryable content provided by Semantic MediaWiki. For a comprehensive description on how to use annotations or the #ask parser function, please have a look at the getting started, in-text annotation, or inline queries help pages.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
− | {{ | + | {{mIRC Guide}} |
'''Raw events''' allow you to handle IRC event in their native, unmodified, format. Every message you receive from the server before mIRC processes it is called a '''raw message'''. And it might look a little different from the one you see after it gets parsed. | '''Raw events''' allow you to handle IRC event in their native, unmodified, format. Every message you receive from the server before mIRC processes it is called a '''raw message'''. And it might look a little different from the one you see after it gets parsed. | ||
Line 16: | Line 16: | ||
== /debug == | == /debug == | ||
− | Before we can talk about the actual events themselves it's important that | + | Before we can talk about the actual events themselves it's important that get a better understanding on what these raw messages look like. mIRC provides a continent way to do just that with the use of the /debug command. The '''/debug command''' can be used to display all the raw messages that gets passed between you and the server. The debug command can be called using the following syntax: |
<syntaxhighlight lang="mIRC">/debug <@window></syntaxhighlight> | <syntaxhighlight lang="mIRC">/debug <@window></syntaxhighlight> | ||
− | We suggest you create a window with an editbox so that you can execute commands from within the same window. | + | We suggest you create a window with an editbox so that you can execute commands from within the same window. |
− | |||
− | |||
<syntaxhighlight lang="mIRC">//window -e @raw | debug @raw</syntaxhighlight> | <syntaxhighlight lang="mIRC">//window -e @raw | debug @raw</syntaxhighlight> | ||
Line 51: | Line 49: | ||
'''Note:''' The on raw event triggers every time a raw numeric and a pattern matched, regardless of who or what caused the event to happen. | '''Note:''' The on raw event triggers every time a raw numeric and a pattern matched, regardless of who or what caused the event to happen. | ||
− | You can see how the numeric is a very important part of a raw event. The matchtext can be a | + | You can see how the numeric is a very important part of a raw event. The matchtext can be a wildcard pattern by which mIRC will try to match against. |
Recall that raw 319 is the list of channel the user is you whoised is on: | Recall that raw 319 is the list of channel the user is you whoised is on: | ||
Line 96: | Line 94: | ||
== Non-Numeric Raw Event == | == Non-Numeric Raw Event == | ||
− | + | Has we have seen, not ever raw event has a numeric value. The syntax for such events are: | |
<syntaxhighlight lang="mIRC">raw <event>:<matchtext>:{ | <syntaxhighlight lang="mIRC">raw <event>:<matchtext>:{ | ||
Line 107: | Line 105: | ||
raw cap:* ls *:{ } | raw cap:* ls *:{ } | ||
raw authenticate:*:{ }</syntaxhighlight> | raw authenticate:*:{ }</syntaxhighlight> | ||
− | |||
− |