A new event prefix - mIRC Discussion Forums

I request a new event prefix, in this case "if only I trigger this event". There are a number of workarounds, of course.

However I've noted in the help file with the ! prefix, which does something similar but is the exact opposite.

A few of the workarounds I know are:

set yourself a user level above 1, and then use that user level to trigger events.

There's also to watch it constantly and have the event trigger and check if ($nick == $me) { }

But that just doesn't seem efficient.

try the undocumented me prefix

examples
on me:*:JOIN:#:
on me:*:OP:#:

I think this will only not work with
ON TEXT, ON ACTION & ON NOTICE.

Quote from Khaled ...
"I don't think I ever added it to the help file... one of those quirky prefixes that I had planned to remove at some point but which seems to have survived all these years. The last reference to it in versions.txt was for mIRC v4.7"

Works with ON NOTICE. Won't work with ON TEXT/ACTION since they're reserved to other people.

Actually, all three worked as private & none worked public.

Code:

on me:*:TEXT:*:*:echo -a $me TEXT
on me:*:ACTION:*:*:echo -a $me ACTION
on me:*:NOTICE:*:*:echo -a $me NOTICE

//msg $me test
[09:53] -> *RoCk* test
RoCk TEXT

//describe $me test
[09:53] -> *RoCk* test
RoCk ACTION

//notice $me test
[09:53] -> -RoCk- test
RoCk NOTICE

Weird behaviour, thanks, I assumed it wouldn't work privately as well. However, I did test ON NOTICE privately, which worked.. I guess it's the habit.

Quote:

try the undocumented me prefix

Yet more evidence that it really IS time to overhaul the documentation - as a paying customer, the need to go through what is essentially a technical file to find any mention of some features is the single most annoying feature of mIRC.

PastMaster

Quote:

Weird behaviour, I assumed it wouldn't work privately as well

Why weird? When you private message yourself, the message is in fact being sent back to you, triggering those events. Of course this isn't the case with messages you are sending to a channel.

Quote:

Of course this isn't the case with channel messages

I've always thought it should be though .. it would be so much nicer to be able to trigger these events myself rather than using ON INPUT

That's why I found it weird, because I thought it was about me being the sender, not necessarily me being the target.

lol, figures as to why I can't find it. Nice.

i find it entirly amazing that *normaly* on text won't trigger for yourself (why bot commands wont work) yet you say as soon as you ad "me:" it works? that's "weird"

on text works for your own Private messages (to yourself), but not for your own channel messages.

It doesn't trigger on the message's outbound journey, but triggers when it comes back to you.

the me:*: prefix works *exactly* the same as if ( $nick == $me ), in every event.

- Raccoon

But I assume that on me:*: is faster than checking ALL events with the runtime script?

correct. I would assume this aswell.