Putting a halt/haltdef after the second one, will prefent the text from being displayed, but will not prevent the first on text event there to trigger. If we would want that our first event does not trigger, after another event used a halt/haltdef, we need to modify it a bit. In particular, we need to prefix it with the & event prefix.
on &*:text:*:#: msg # nr 1
on ^*:text:*:#: msg # nr 2
Now what happens when we say somethign on the channel? It messages again first nr 2, then nr 1. When we add a halt/haltdef to the second on text event like this:
on &*:text:*:#: msg # nr 1
on ^*:text:*:#: msg # nr 2 | haltdef
The second on text event is now the only one triggered when something is said on a channel, whilst the first one is ignored.
OMG I should really read the help file closer
I have a bunch of
ON ^*:TEXT:*:*{ if (!halted) { ....
/me goes and kicks a can around the yard while mumbling under my breath... grumble grumble events grumble grumble prefixs grumble grumble
* Very nice breakdown of events by the way.
