chillout___:

Type /debug @debug and watch the window as you type /wrrite

You will see which raw numeric pops up when the SERVER (yes, the server) sees an unknown command. For reference, it's 421. You can then script those raw events with /help raw events

I never said "* unable to resolve server" was a server error. This one is in fact internal. However, again, I'm not sure what benefit catching this error would have besides theming error messages. Note that you can sort-of catch this one with ON DISCONNECT.


- argv[0] on EFnet #mIRC
- "Life is a pointer to an integer without a cast"