Ok I figured out what was going on. I didn't realize that the on ^*:TABCOMP:*: event ONLY triggered when mIRC actually changes the text in the editbox (and there is in fact an event *to* halt), while the on *:TABCOMP:*: event triggered pretty much any time the TAB key is pressed.
So, when I changed my event to a ^ event, nothing was processing because it wasn't something that mIRC thought should have been completed. So, to modify my original post, since as starbucks_mafia explained, all of those identifiers I was looking for are present. Instead, the help file is not very clear in this section as to what triggers each of the events. It could also use some information to point users to key identifiers that would be used here.
Thanks again.
Edit: What's also interesting is the way the ^ event works with the regular event. If there is both a ^ event and a regular event, the ^ event will trigger first, and then the regular event will also trigger, unless haltdef/halt is used in the ^ event.
Last edited by KilledInAction; 20/09/07 05:37 PM.