Forums Feature Suggestions if ($nick isadmin $chan && $nick isfounder $chan)

Please implement this. My nickstyler shows SOPs and Founders as [@OP] instead of [&SOP] or [~Founder].

There has been discussions on isadmin before and the short version is that admins (and founders) aren't the same on every ircd (the server software). As such, there's no way to make it work on every network in the same way as isop or isvoice, which are standardized.

That said, you can easily check the $nick's modes to determine what level the nick is and based on the network's choice of symbol(s) for the higher "ranks," you can change the colors in that way. Just remember that what you set up on one network may not be the same for another network.

For admins:



For founders/owners:



-or-

Or, on some networks for admins:


Just to show how they are different from network to network.

Not wanting to put a damper on the situation, but I've encountered a couple of networks where founders/owners and admin just show in the nicklist as Ops (@), although the network recognizes the difference between them.

How would mIRC tell if the user is an admin/founder on these networks, then?

This is a server's option, where the server is never sending any informations about owner and admin in a /name reply, there's no way to tell the difference on such network.

Right. So those servers would omit that information at their own peril. I would see no problem with this.

I think having admin and owner support like we have op halfop and voice support could only be a good thing, the problem is just about standard, mIRC can't just implement only one way to recognize owner/admin, mIRC will also fail for the case I just described in my previous post (no information about +q/+a in a /names reply), so that's not something mIRC has to implement, users have to.

Would it not repeat them in the PREFIX= section of raw 005? PREFIX=@@@%+

mIRC *can* implement that method if it wanted.

I think the issue here is the definition of "owner", "admin" and "founder". On some networks this is defined by the server, is an inherent concept in the network and therefore has a mode (+q/+a) associated with it. This kind of network is what mIRC should target.

On other networks, channel founder/admin is implemented exclusively through a proxy services bot like ChanServ, but has no actual effect on the server. In the latter case we're not really talking about the same definition of "founder" (the definition as implemented by the IRC server). The latter definition of founder is just some toggle in a services bot-- ie. you're a founder to the bot, but it is not recognized by the server/network.

I don't see how ignoring the second situation would make the implementation inconsistent. Although they have the same functionality, the latter case isn't really the same thing.

If there is some third situation where there *is* in fact a server mode (+a/+q/etc) but it doesn't show up in PREFIX as a unique symbol, that's even moreso the server's fault. mIRC should not bother with this situation either. Instead, the maintainers of the IRCd in question should be educated on implementing a proper server that is usable by clients. mIRC shouldn't be responsible for working around shoddy implementations.

Are you talking about checking +a/+q mode and ~/& prefix ?

Fact is that the RFC indicate what irc servers and irc client *should do/implement*, and that +q/+a modes isn't in that list.

Of course an irc's maintener can implement whatever he wants to since that's his server, and if people think that what he implemented sucks or what, they just don't use it and it's fine.
But imo it make no sense for an irc client to implement something related to X% of irc server if X isn't 100.
Now I have nothing against the implementation of any method, but then people will complain that either there's a mIRC bug because people are +q/+a but mIRC is saying the contrary (because the server isn't sending any prefix to difference owner/admin), either because the prefix isn't what mIRC is looking for.

I just tend to use something like this:



which allows you to check if a certain nick has a certain ranking, but also allows you to compare the powers of 2 nicks:



*shrug*

Rather than use $iif(), you could just zero pad the outcome, like this:



(this also adds support for the IRCX "." (owner) prefix)

Really?



mIRC also has isowner (undocumented). In fact, I've yet to be on an IRC that supports either of those, so those modes are not related to 100% of IRC servers. I'd say the greater majority is good enough.

Halfop is something very common today . I never heard about a server that is using +h mode with a character different from '%' whereas it is known different servers use different characters for owner/admin.
Now as I said I'm not against the suggestion, a support for owner/admin would be good, I just think there are problems with this implementation, first one is that there's already a support for owner for IRCX server, second is different servers use different characters for these modes.