First, "RAW" does trigger for all events, not just numerics. This issue that gave rise to this feature request is that with CAP gaining popularity scripters have(had; see the second part of this post) no way to make use of these CAP modules without breaking mIRC's internal event handling.
Code:
raw *:*:{
  echo -s $rawmsg
}


Second, the request has been implemented in the closed beta for testing:
Quote:
29.Added on PARSELINE event, triggers before incoming/outgoing server
lines are received/sent and allows a script to modify them.

on *:PARSELINE:<in|out|*>:matchtext:echo $parsetype $parseline

The line can be modified using the following command:

/parseline -iotbqpnuN [text|&binvar]

-i or -o = required to specify an in/out line.

-t or -b = required to specify text or &binvar.

-q = add a new line to the end of the in/out queue. It can be used
inside and outside the PARSELINE event. New lines are processed
after the script/event exits.

-p = use with -q to indicate that the new line should trigger the
PARSELINE event.

-n = add a CRLF to the end of the line if it does not have one.

-uN = where N is 0 or 1 and either disables or enables UTF-8
encoding/decoding for the line.

Notes:

1) A script must check $parseutf to know whether mIRC will be UTF-8
encoding/decoding a line. For outgoing lines, if $parseutf is $true,
after the PARSELINE event, mIRC will UTF-8 encode the line before
sending it to the server. You can prevent this by using -u0. For
incoming lines, if $parseutf is $true, after the PARSELINE event,
mIRC will UTF-8 decode the line before processing it. You can prevent
this by using -u0.

2) mIRC maintains internal states based on incoming and outgoing
lines. If lines are modified, mIRC may not work correctly. This
feature should only be used, for example, to support features
and/or protocols that mIRC does not already support, not to modify
standard lines.

Last edited by FroggieDaFrog; 15/07/15 06:30 AM.

I am SReject
My Stuff