The only plugins I have installed on my server that could make this problem are Group Manager and Essentials.
In Group Manager's permissions or somewhere in Essentials, is there a setting that makes it so that even op-ed, '*' permissions cannot kick, ban, or jail un-oped, moderator/admin-level people? I thought I fixed this, but then today I had an argument that needed to end in a jail, kick, or ban, but not even the CONSOLE could /kick, /ban, or /jail the person.
Not even the console could /kick, /ban or /jail ? That's not good O_O
There might be a setting in Essentials somewhere (I dont' remember exactly) that makes certain groups(ex: ops) un-kick/ban/jail-able.
Look through the config, check for any lines that mention ops. . .
Rollback Post to RevisionRollBack
"If we put our lobster bibs on backwards and swam around in the ocean, would crabs come over to us and think we were some kind of god-king?" - towely10, 2/22/13
This is the console's version of a new player inserted to the group in question.
26.03 01:14:27 [Server] INFO Error: You can not kick that person.
26.03 01:14:21 [Server] INFO NOCG Staff [name]: lol
26.03 01:14:17 [Server] INFO [DispenserReFill] Refresh finished
26.03 01:14:12 [Server] INFO You changed player '[name]' group to 'NOCG'.
26.03 01:14:12 [Server] INFO Couldn't retrieve your world. Default world 'nocgserver' selected.
26.03 01:13:57 [Server] INFO Connected players:[name]
26.03 01:13:56 [Server] WARNING [name] was denied access to command.
26.03 01:13:56 [Server] INFO [PLAYER_COMMAND] [name]: /gm
26.03 01:13:49 [Multicraft] [name] ran command Message of the Day
26.03 01:13:49 [Connect] User [name], IP ***.**.***.***
26.03 01:13:49 [Server] INFO Creating empty config: /userdata/[name].yml
26.03 01:13:29 [Server] INFO CONSOLE: Added [name] to white-list
I did censor a few things as I was not on my main account, and I also deleted most of each of the files so that anyone reading this wasn't as swamped with code.
"If we put our lobster bibs on backwards and swam around in the ocean, would crabs come over to us and think we were some kind of god-king?" - towely10, 2/22/13
I'm actually having the same issue.. I can't Kick, Ban or Jail any of my Admins.. And when I try to find the essentials.kick.exempt ect, I can't. Is there a different folder I should be looking in or something? Thanks.
What permissions plugin are you using?
the essentials.kick.exempt, etc. permission nodes won't be there by default, you'll need to manually add them to each group. Here is a link to the list of every essentials permission node.
Rollback Post to RevisionRollBack
"If we put our lobster bibs on backwards and swam around in the ocean, would crabs come over to us and think we were some kind of god-king?" - towely10, 2/22/13
Ah right, I see.. But I still can't kick Admins? What should I do? Or is there a better Permissions Plugin I can use?
I use PermissionsEX (for some reason I find it easier.) Make sure that whomever you're trying to kick/ban etc isn't an OP. Permissions systems render the op/not-op system obselete.
Are you using any other plugins that mess with permissions?
Rollback Post to RevisionRollBack
"If we put our lobster bibs on backwards and swam around in the ocean, would crabs come over to us and think we were some kind of god-king?" - towely10, 2/22/13
Yes, permissionsEX uses the same permissions as GroupManager(ex: essentials.kick, essentials.warp, essentials.ban.ip, etc.)
Rollback Post to RevisionRollBack
"If we put our lobster bibs on backwards and swam around in the ocean, would crabs come over to us and think we were some kind of god-king?" - towely10, 2/22/13
In Group Manager's permissions or somewhere in Essentials, is there a setting that makes it so that even op-ed, '*' permissions cannot kick, ban, or jail un-oped, moderator/admin-level people? I thought I fixed this, but then today I had an argument that needed to end in a jail, kick, or ban, but not even the CONSOLE could /kick, /ban, or /jail the person.
How do I fix this?
There might be a setting in Essentials somewhere (I dont' remember exactly) that makes certain groups(ex: ops) un-kick/ban/jail-able.
Look through the config, check for any lines that mention ops. . .
This is the permissions file for that group.
I did censor a few things as I was not on my main account, and I also deleted most of each of the files so that anyone reading this wasn't as swamped with code.
For those with similar issues, the answer is essentials.kick.exempt, .ban.exempt, etc.
http://ess.khhq.net/wiki/Command_Reference/Perm
^^ There's a link to every permission that deals with essentials if you need it again!
What permissions plugin are you using?
the essentials.kick.exempt, etc. permission nodes won't be there by default, you'll need to manually add them to each group.
Here is a link to the list of every essentials permission node.
I use PermissionsEX (for some reason I find it easier.) Make sure that whomever you're trying to kick/ban etc isn't an OP. Permissions systems render the op/not-op system obselete.
Are you using any other plugins that mess with permissions?