Forums Feature Suggestions on hop/sop

Hey everyone,

Thought these would be a nice idea:

on *:SOP:
and
on *:HOP:
There is an on op and on voice, and i just thought it would make sense if those existed as well.

Cheerio,
-Zelda4ever
aka "The Big 'Z'"

on *:hop: exists (if hop = halfop), on *:help, on *:dehelp.

not sure what you mean by on *:sop, as ive only seen 'sop' in chanserv, and mirc wouldnt have a way of knowing if someone was added to the sop list.

I wonder if it's possible to have "on *:FOUNDER:#:code"

Since some networks have ! or . or & for founder status.

Some networks, such as PhaZeNet for example (sorry if its against the rules to advertise networks), use sop as an additional in channel mode, like +o or +v on DALnet, Undernet, EFnet, etc. Sops usually have status that appears as ! or +a; As ops have @ or +o, hops have % or +h, and voices have + or +v.

I hope I got the point across.
-Zelda4ever
aka "The Big 'Z'"

Thats a good thought too... Never thought of that.

-Zelda4ever
aka "The Big 'Z'"

The problem there is the 'some' networks. And in this case, it is the large minority.

As tidy said, if ON SOP is referring to the Super Op status then that is built into ChanServ (I haven't yet seen a channel service bot such as X/Q/L with that status). I have a vague memory from another thread of an 'SOP' status being set via a mode, but it's not a commonly accepted mode, yet.

Founder status is the same thing, it depends if the network has channel services or not. Whilst you are suggesting it for networks that prefix a character to an owner's nickname, *most* networks do not do this. Most networks that have a Founder status will simply have it via the channel service.

In my opinion these modes for founders/sops/etc. are simply "vanity" modes and don't really serve an actual purpose. +h halfop could be considered one too, however, I do support it because it's a way to give a voice some extra tools to moderate the channel, whilst at the same time not giving them full op rights, it sort of fills the void between voice/op.

I'm not so much against the idea, I just don't really see the point of it if it's only going to help people who use these "lesser known" networks and probably make newbie scripters get confused - Especially as some networks have channel service SOP support, then they'll be wondering why the ON SOP event doesn't work with (for example) ChanServ, then it needs to be explained it only works with the SOP mode that exists on some networks...and other such scenarios.

My 2 cents.

I agree that it is not a common thing to have on an IRC network, but it is still on *some* networks, which would make it a heck of a lot easier for us scripters on those networks. And for people that are unfamiliar with Sop status, couldn't you just include that in the mIRC .hlp ? Sorry if it seems as if I am arguing with you, but again, it is still something used on some IRC networks.

-Zelda4ever
aka "The Big 'Z'"

on *:owner:#:{

works for . (+q) (or used to)

It's not in the help.. So it's either a 'hidden' feature that's available or it's not there.