Forums Bug Reports on *:MODE:*: Bug

The " on MODE " event doesn't work if you're using it for a channel that contains any "-" in the name.
For example #---={SyberCorp}=---

Any way around this would be appreciated. Otherwise, I think It's a new bug.

It works for me.

I noticed that you didn't tell me what you did.

Also, I tested this problem over 20 times using different scripts but with the same base
( on *:MODE:#---={SyberCorp}=---:/echo -a $nick changed the modes in $chan to $1- )

And each time it DID NOT work. I have no other on MODE scripts, so it's not a conflict, I have all Remote options enabled, and I have no other problems in any of my scripts.

I see now what you mean.
Here you have a workaround:

ON *:MODE:*: {
if ($chan == #---={SyberCorp}=---) { ........ }
}

Thanx. Forgot about that. I'm a bit tired right now. So, you agree that there is a bug there, and that you would have to use the workaround. Thank you for the effort you put into this.

Any time you have lots of those special (non-alphanumeric) characters in a channel name, it's ALWAYS best to put the check inside the code rather than leaving it in the event header - you never know what will happen if you had (for example) a channel with a $ in it.

It's actually the braces ("{" & "}") not the "-" char

Oh. Thanx. I didn't think about that before, but that actually makes more sense. Still, that is something that should be fixed. I mean, if it's going to ackknowledge that channels exist with {}'s or -'s in the name, then I think it's only right if the variables can handle those characters too. Even if by only somehow making use of quotation marks, so that it knows waht the exact string is, instead of beginning/ending it at the {}'s. I still say it's something to be improved on in the next version of mIRC.