Latest revision as of 13:02, 20 October 2018

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 Messages[edit]

Below is an example of a typical raw irc message that is received when a user talks in a channel:

:Kevin!bncworld@I-Have.a.cool.vhost.com PRIVMSG #mIRC :I feel lucky today

What most of us would see would look a little different. In my case it looks like this:

15:43 <@Kevin> I feel lucky today

As you can see, mIRC has processed the raw message and displayed it in a convenient manner. There are many occasions where we might want to override this behavior or even handle messages that mIRC might not natively support. In this article we will see at least two such cases.

/debug[edit]

Before we can talk about the actual events themselves it's important that we 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:

/debug <@window>

We suggest you create a window with an editbox so that you can execute commands from within the same window.

Note: The message are shown undecoded (utf8)

//window -e @raw | debug @raw

Raw Numeric[edit]

Using the debug window we have open. Let’s execute a /whois command on someone in our channel. You might see something similar to this:

 -> :irc.server.name WHOIS foo
 <- :irc.server.name 311 bar foo ~Ident name-B21D62.lolhat.com :Foo Jenkins
 <- :irc.server.name 319 bar foo :+#foobar @#kekelar %#scripting
 <- :irc.server.name 312 bar foo irc.server.name :Server Description
 <- :irc.server.name 307 bar foo :has identified for this nick
 <- :irc.server.name 335 bar foo :is a Bot on name 
 <- :irc.server.name 671 bar foo :is using a Secure Connection
 <- :irc.server.name 318 bar foo :End of /WHOIS list.

You may have noticed that following the server’s name there is a strange number: 311, 319, 312, 307... These numbers are known as raw numeric. Most, but not all, raw messages will have a number that we can use to uniquely identify the message. For example 318 will always mean "End of /WHOIS list." Raw numeric 319 will always give us a list of channels the user is on. That number will prove to be invaluable in writing scripts that deal with raw message.

Numeric Raw Event[edit]

The syntax for the raw event is:

raw <numeric>:<matchtext>:{
   ; code to handle the message
}

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 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:

:irc.my-irc-network.net 319 <myname> <nick> :<[mode]#channe> <[mode]#channe2> <[mode]#channe3>...

Our raw event will look like this:

raw 319:*:{
  ; $1 = <myname>
  ; $2 = <nick>
  ; $3 = <[mode]#channel 1>
  ; $4 = <[mode]#channel 2>
  ; $5 = <[mode]#channel 3>
  ; $6 ...
}

Example: Channels-On-Join[edit]

In this example we will create a script that will message all the channels a user is on. Our example will be composed of two parts: an on join event and an on raw event.

We will need to use the on join event to be able to know when the user joins a channel. Recall that the raw event will trigger whenever any matching raw message is received. To ensure our raw event only happens when we want it to we will set a variable to indicate it.

The on join part:

on *:join:#:{
   ; make a variable called "%whois.nick" to the channel's name 
   ; We will use this variable later on in the raw event. 
   set %whois. $+ $nick $chan 
   ; whois the user
   whois $nick
}

Recall that $2 is the user we whoised. We will need that to check if %whois.nick is set. Our code will look like this:

raw 319:*:{
   ;We indicated that the event should trigger on the server's numeric value of 319
   if (%whois. [ $+ [ $2 ] ]) {
     ;In the if statement we check if we actually /whoised this user 
     msg %whois. [ $+ [ $2 ] ] [WHOIS] $2 is on $3-.
     unset %whois. $+ $2
   } 
 }

Non-Numeric Raw Event[edit]

As we have seen, not every raw event has a numeric value. The syntax for such events are:

raw <event>:<matchtext>:{
   ; code to handle the message
}

An example of using it is for SASL authentication. Where the following events will be used (on a network like FreeNode):

raw cap:* ack sasl *:{ }
raw cap:* ls *:{ }
raw authenticate:*:{ }