* LeBoOo sets mode: -meo LeBoOo
Once that happends, in the nicklist.. it still shows that 'LeBoOo' is opped.
Thanks for your time..

This is more than likely, due to the fact you are using switch -e with no parameters, so the 'LeBoOo' belongs to -e, and as a result there is no parameter for the -o mode..

Try: /mode #channel -meo LeBoOo LeBoOo

Eamonn.

When using the /mode command you must specify the nickname the same amount of times that you change the mode for a user...

So if you set mode -eo on a user then you must use /mode #channel -eo nickname nickname because you have changed TWO modes. So in your example, use:

/mode #channel -meo LeBoOo LeBoOo

and all should be fine. If it's still displaying the user as opped then it's more likely to be a bug in the IRCd and not with mIRC.

Regards,

It should be noted that the IRCd this bug was caused on was Austhex which to it +e is a no parameter command (event channel).
mIRC assumes it is an exempt and treats it as such when parsing the mode string

mIRC doesn't parse the mode string however, it simple forwards it onto the server. And since you mention different modes, is M the default "Moderated" mode, or is it a mode requiring an associated parameter?

m is moderated.
o is op (in case you do wonder .. it does take a parameter of course ;p)

mIRC does parse the string sent back from the server to the client, in order to know if it should change user prefixes (o/v). as well as keeping its internal ban list and exempt list in tack (as well as invite lists for those networks as well..)

We'd have to see the raw 005 CHANMODES token for that server to know for sure it's a bug or not.

I'm pretty certain this is the reason mIRC doesn't translate it correctly when doing usermode and internal list changes.

Austhex doesn't send 005.

This shows up when the server sends the modes to mIRC (see for yourself with /debug -pt @debug); the server sends the modes to you even if you set them (unlike messages you send). mIRC assumes that channel mode e takes an argument (as it usually does), so "LeBoOo" is used for that. There are no arguments left to apply to channel mode o, so mIRC doesn't know who was deopped.

The server needs to send CHANMODES, since it is using an unusual meaning for channel mode e.

As a fix, you could write a script (using on rawmode event) which detects this problem, and automatically sends a /names $chan, so that mirc can update the nicklist (and remove the misplaced @'s)