Original Post
OP-er OP
So, when you create a room you're automatically assigned as an OP of that server.
If you give someone else OP, he can /deop you and the server has been taken.
Sure, you can create another room and the problem is solved. But what if the room you created is a bet room with 28 players and a decapprize worth of 30k?
The player that you opped thinking he would help you, can ban everyone and rig the DP.
Sure, he can get reported and banned, but it's a useless sink.
My suggestion:
- Make the person who created the room immune to other op's he gave out, so they can't /deop him.
A lead/super op.
- You can also set up a password for it (same with the /owner *pass*) just for the Room owner, if you accidentally quit.
Example : /leadop 123123. Yes it's a bad name for a command, but you get the idea. <- Optional.
- Other OP's you gave can't deop you, but can deop each other.
Benefits:
- Less reports for server takeovers.
For example, if someone starts banning/deoping everyone, you, as the room creator and the lead op can stop him and unban everyone, and solve the issue.
The lead op is immune to any normal OP's influence.
If you give someone else OP, he can /deop you and the server has been taken.
Sure, you can create another room and the problem is solved. But what if the room you created is a bet room with 28 players and a decapprize worth of 30k?
The player that you opped thinking he would help you, can ban everyone and rig the DP.
Sure, he can get reported and banned, but it's a useless sink.
My suggestion:
- Make the person who created the room immune to other op's he gave out, so they can't /deop him.
A lead/super op.
- You can also set up a password for it (same with the /owner *pass*) just for the Room owner, if you accidentally quit.
Example : /leadop 123123. Yes it's a bad name for a command, but you get the idea. <- Optional.
- Other OP's you gave can't deop you, but can deop each other.
Benefits:
- Less reports for server takeovers.
For example, if someone starts banning/deoping everyone, you, as the room creator and the lead op can stop him and unban everyone, and solve the issue.
The lead op is immune to any normal OP's influence.
Last edited by Money; Dec 10, 2015 at 02:59 PM.
[SIGPIC][/SIGPIC]
I'm a ToriAgent, got any questions? Send me a private message here.
If you give someone else OP, he can /deop you and the server has been taken.
Sure, you can create another room and the problem is solved. But what if the room you created is a bet room with 28 players and a decapprize worth of 30k?
The player that you opped thinking he would help you, can ban everyone and rig the DP.
The exact opposite can happen; the OP can /deop every OP, do the very same thing and rig the decap/abuse the power and so on.
- Make the person who created the room immune to other op's he gave out, so they can't /deop him.
Nothing would change anyways, other then the fact that it would make him immune to the ex-OPs, letting him have all the fun he likes while doing naughty things, like banning everyone in a betting server, setting a /passwd and then rigging the decap with an alt in the very same mod. [referring to first quotes' answer]
(Even though the moderators can stop him [and most likely ban him], he could get away with it as long as there are no evidences, or at least I think that's how it worked.)
- You can also set up a password for it (same with the /owner *pass*) just for the Room owner, if you accidentally quit. <- Optional.
If you accidentally quit, you can just come back and use the /owner.
If no /owner was set then it is your own fault and you should learn to place one. You can either ask the other OP(s) to /op you, or you could try getting someone who has powers in-game, like a GM, to OP you. And I am pretty sure at LEAST one GM would be available - should only take seconds to use a command anyways.
Also sometimes, people who take over servers would just ban you, so trying to come back with an alt wouldn't work, implying that the command is set just for the server creator. [aka one account name]
Even if this works by detecting and setting your IP address as the server creator, it can have flaws especially with dynamic IP addresses, since they tend to change.
Benefits:
- Less reports for server takeovers.
Ironically, it can increase even more reports about server creators abusing this command, thus causing even more reports.
So overall, I don't really support this mechanism.
I don't think you get what I am saying, please re-read what I wrote.
I can't even reply to what you said here because I don't get the "ex-Ops" and stuff.
Also you automatically get the "lead op" when you make the room, since its yours.
There doesn't need to be a command if that's a problem i guess lmao, it can be a one time thing until you leave, as i said its optional.
He can already do that without my suggestion of the "Lead op", hence why I requested this idea, to prevent this.
It's only for the person who created the room.
No one else can have it. Ever.
Pretty sure I already know this stuff and never said anything about the command we already have.
I said it would be a diffrent command that's something like the original /owner
Re-read.
That's why I said the lead op can't be banned, thus preventing the people who take over the server to ban you.
Please, read the whole post before jumping to conclusions next time.
Thank you.
I can't even reply to what you said here because I don't get the "ex-Ops" and stuff.
Also you automatically get the "lead op" when you make the room, since its yours.
There doesn't need to be a command if that's a problem i guess lmao, it can be a one time thing until you leave, as i said its optional.
Originally Posted by NoKi1119
The exact opposite can happen; the OP can /deop every OP, do the very same thing and rig the decap/abuse the power and so on.
He can already do that without my suggestion of the "Lead op", hence why I requested this idea, to prevent this.
It's only for the person who created the room.
No one else can have it. Ever.
Originally Posted by NoKi1119
If you accidentally quit, you can just come back and use the /owner.
If no /owner was set then it is your own fault and you should learn to place one. You can either ask the other OP(s) to /op you, or you could try getting someone who has powers in-game, like a GM, to OP you. And I am pretty sure at LEAST one GM would be available - should only take seconds to use a command anyways.
Also sometimes, people who take over servers would just ban you, so trying to come back with an alt wouldn't work, implying that the command is set just for the server creator. [aka one account name]
Even if this works by detecting and setting your IP address as the server creator, it can have flaws especially with dynamic IP addresses, since they tend to change.
[/B]
Pretty sure I already know this stuff and never said anything about the command we already have.
I said it would be a diffrent command that's something like the original /owner
Re-read.
Originally Posted by NoKi1119
Also sometimes, people who take over servers would just ban you, so trying to come back with an alt wouldn't work, implying that the command is set just for the server creator. [aka one account name]
Even if this works by detecting and setting your IP address as the server creator, it can have flaws especially with dynamic IP addresses, since they tend to change.
That's why I said the lead op can't be banned, thus preventing the people who take over the server to ban you.
Please, read the whole post before jumping to conclusions next time.
Thank you.
Last edited by Money; Oct 31, 2015 at 06:22 PM.
Reason: <24 hour edit/bump
[SIGPIC][/SIGPIC]
I'm a ToriAgent, got any questions? Send me a private message here.
This is a fair idea (supported).
IRC actually has this already (toribash's ingame power heirachy is based on IRC... even has the same default symbols and everything). In IRC, there are 6 basic levels:
Owner (~) : Admin of the room -> We have this ingame already
Super Op (&) : The role you're suggesting be implemented
Op (@) : Operator of the room -> We have this ingame already
HOP (%) : Half-Operator of the room -> We have this ingame already (trial gms)
VOP (+) : Voiced Operator (although they don't really operate anything...)
Default user () : Normal user with no privileges -> Obviously, we have this already
I don't see the harm in the room creator being made a SOP, being able to OP other users without the threat of a takeover. This user could even SOP other users if they really wanted (not much reason to though?).
As for a colour, why not imperial blue? Seems to be the most-used IRC default.
In fact, wouldnt it be possible to implement auto OP and SOP lists to rooms? I mean, account names ingame are, by definition, registered. Why not just have
/AOP add <name>
/AOP del <name>
/SOP add <name>
/SOP del <name>
Seems pretty beneficial to me?
IRC actually has this already (toribash's ingame power heirachy is based on IRC... even has the same default symbols and everything). In IRC, there are 6 basic levels:
Owner (~) : Admin of the room -> We have this ingame already
Super Op (&) : The role you're suggesting be implemented
Op (@) : Operator of the room -> We have this ingame already
HOP (%) : Half-Operator of the room -> We have this ingame already (trial gms)
VOP (+) : Voiced Operator (although they don't really operate anything...)
Default user () : Normal user with no privileges -> Obviously, we have this already
I don't see the harm in the room creator being made a SOP, being able to OP other users without the threat of a takeover. This user could even SOP other users if they really wanted (not much reason to though?).
As for a colour, why not imperial blue? Seems to be the most-used IRC default.
In fact, wouldnt it be possible to implement auto OP and SOP lists to rooms? I mean, account names ingame are, by definition, registered. Why not just have
/AOP add <name>
/AOP del <name>
/SOP add <name>
/SOP del <name>
Seems pretty beneficial to me?
Last edited by Fear; Oct 31, 2015 at 09:50 PM.
