Alright.
The regex itself is doing the match, and if the regex matches, there must be a matching string or word. And the backreferance will just put that into the memory so you can read it later on.
Here\'s my version:
on $^*:hotlink:/[+-][ohvbeIsklim]/:#: scon -r $iif($nick(#,$me,@%),return,halt)
on $*:hotlink:/([+-][ohvbeIsklim])/:#: mode # $replacex($regml(1),+,-,-,+)
I see how you approached it, I didn\'t realize you could use parenthesis that way, nice code. :D However, I don\'t understand how it would set user modes because you would also need to match the target. That would work for channel modes, but not user modes. Unless I am missing something. :o
Thanks guys for the positive feedback!
if you made that regex, you should know how to create a back referance, and how to use it. Of course I created that regex, I can\'t imagine something as simple as the regex I use is extremely hard to create. I\'m not a leecher. :/
The purpose of that regex is to just match the modes, I myself am not that skilled in regex, and as stated above, the regex I made is very simple. However, I don\'t understand how you could use a back reference in this case, as I primarily use tokens to locate the position of the mode in the string. Normally, without any themes, an mIRC user should have mIRC\'s default event text (<NICK1 sets mode: ). This one uses %b to find and %c to find , I don\'t understand how back referencing could achieve that, unless I added or something to the regex.
If you could show me how it would be done, that\'d be great. I\'m not particularly great at regex. :(