If you try to evaluate $nick from a remote context event with the wrong eventid number, $nick doesn't evaluate to $null but to the plain text "$nick" (just like in the editboxes), rather than $null, which is wrong.
This sounds like a simple case of "don't do that then." There is no legitimate case for passing in the wrong event ID, so when you do,
you (the DLL writer) are at fault, and anything that mIRC does as a result can at most be classified as "undefined behavior."
Why is mIRC using this method instead of a simple bool value?
Have you considered that mirc supports nested event execution? (
link to give you some idea of what that means)
