The mangling(where?) of code was specifically to show how mIRC's internals will NOT trigger the specified events at all if they do not match the "!command" specified in the event handler. My 'setup' code does exactly as your code does -- only continue with the script if the user is op and a specific !command was issued -- just differently. What part did I overlook/ignore?
Why is 'my' method better than 'yours'? 'My' scripted event body ONLY triggers for the specified command; it makes use of mIRC's internal event handling to eliminate messages -- as best as possible -- that do not fit with what I wish to do.
Where as a catch-all event will still trigger for EVERY message received; even if there is no command to process. Yes you exit at the first possible moment, but that still requires invocation of the script engine for EVERY message received.
---
As far as multiple-event parsing: mIRC, internally, registers scripted events when mIRC/scripts are first loaded. It does NOT scan each file at the time of an event and figure out which event(s) to trigger. It already has them registered and knows which to trigger for a given received message
What if someone is using a script that sends out color codes when they type something? What if there are 30 or so events? Each time you make a new event, you have to duplicate a lot of code to ensure it works when it's supposed and how it's supposed to.
