Toribash
Original Post
Safety Commands
I'm thinking two new commands should be added. /deny and /allow

Here's a example : Say you want to op someone but your not entirely sure they will take your server or change the owner password. That where /deny comes in. "/deny [player name] [command]" and then they will no longer be able to use the said command, If you want to re-allow the player to use the command you would use /allow [player name] [command]. Lemme act this out...

Chilledon:You sure you wont deop me?
Jerk: Yep.
Chilledon:kk
Chilledon: /deny Jerk deop
Chilledon: /op Jerk
Jerk: /deop Chilledon
Jerk: WTF!!!??
Jerk: It wont work!!!
Chilledon: /kick Jerk
[My Replays] | [Aether] | [PM Me For Request Mods] | [Tricktionary]
[Static] | [Xioi] | [♥2WC♥] | [iFred] | [Oblivion]
I still have 0 clue why I have to come into rooms to fix these problems. Why are you giving OP in rooms to ... anyone? When I didn't have ~ I never OP'd anyone, even friends, unless it was essentially really needed.

If you want them to change a mod, just tell them to tell you what the mod is. Set an owner password too people.
Need help?
Creati0n says: still my favorite. <3
I sacrificed my firstborn for this great human being to join (M) ~R
Just Use Thunder!
Then it could be a optional command, for those dumb enough to op someone in the first place.
[My Replays] | [Aether] | [PM Me For Request Mods] | [Tricktionary]
[Static] | [Xioi] | [♥2WC♥] | [iFred] | [Oblivion]
Your problem is the op command, not the deop command or any other command.

There might be something done with op sometime, like auto op for the room owner. It won't take priority over anything because the immediate solution is very, if not even more, effective. That is, if you don't want people messing with your server, don't make them an operator. This is your responsibility.