From what I understand, the ^ prefix makes the event trigger before mIRC has done its internal processing, as opposed to regular events which are triggered after mIRC's internal processing. (Anyone correct me if I'm wrong here.)
Thats somewhat correct, however in some events some things are already been updated, one i can think of is ...
ON ^*:TEXT:*:#:{ echo $chan ********** ********** $nick is about to say something , they have not said anything for $nick($chan,$nick) seconds ********** ********** }
That in theory should show the idle time of the nick since he said something, but always replies with zero, since the idle has already been reset by the user saying something, even tho were intercepting the event before mirc displays anything. (this is kinda explained somwehere in the help, in that the ^ triggers before mircs default action on an event or something like that)
