I have PermissionEX installed on my server and I am a noob at using it. Whenever I do /pex user CommanderSilver group set Default, it says users groups set, but I still have permissions to commands that i shouldn't have, and I still don't have my prefix. Here is my permissions.yml: http://pastebin.com/98YsjwKQ
You're probably in a higher group and it's not registering the lower group. This happened to me. Go to the config and change your group to the lower rank by deleting the other one. Hope this helped!
Prefixes and suffixes will only work if you have a chat manager plugin. As stated above make sure you're not an op, and also make sure you don't use tab, and have the correct spacing. Also, in newer versions, all groups, even the default, have to have an inheritance. Other than that, I can't think of anything else to try. Maybe post on the pex forums and see if they can help over there. I hope you have already figured out the problem.
Yes! This is likely the problem. I suggest using ChatEx, a plugin made specifically (mostly) for PermissionsEx. If this is not installed, or any other chat plugin, then PEX prefixes and suffixes will not work.
You're probably in a higher group and it's not registering the lower group. This happened to me. Go to the config and change your group to the lower rank by deleting the other one. Hope this helped!
When I restarted my server, the scripts reappeared after I deleted them. Doesn't work. But thanks anyways...
I ran your pastebin file in a YAML parser, and there are two errors.
Output
ERROR:
while parsing a block collection
in "<unicode string>", line 1, column 1:
-
^
expected <block end>, but found '?'
in "<unicode string>", line 163, column 1:
schema-version: 1
That said, it's a mess. Your user record shows as admin, so your group set did not take effect. Captain is spelled as I indicated, not Captian. Your inheritance is also configured incorrectly. Captain inherits from default, so Commander only needs to inherit Captain not Captain and default. Moderator inherits Commander, so it doesn't need to inherit Captain & default. Admin, Coowner and Owner all have root wildcard permissions so having them inherit is pointless. Speaking of pointless, why do you have those co-owner and captain groups? Remove those and rename Captian to Captain. Also, using root wildcard is lazy and can cause problems with certain plugins. Bear that in mind if you install a plugin and strange things happen.
Change your user record to Default (it's case sensitive, so capitalize the D), ensure you aren't in ops.json then start the server and if you have a valid chat manager you should see the default prefix.
Hello,
I have PermissionEX installed on my server and I am a noob at using it. Whenever I do /pex user CommanderSilver group set Default, it says users groups set, but I still have permissions to commands that i shouldn't have, and I still don't have my prefix. Here is my permissions.yml: http://pastebin.com/98YsjwKQ
You are likely opped. Drop yourself to make it work (Being operator messes with PEX).
That's not the problem. But thanks anyways.
I need help....
hello?
You're probably in a higher group and it's not registering the lower group. This happened to me. Go to the config and change your group to the lower rank by deleting the other one. Hope this helped!
Yes! This is likely the problem. I suggest using ChatEx, a plugin made specifically (mostly) for PermissionsEx. If this is not installed, or any other chat plugin, then PEX prefixes and suffixes will not work.
I use EssentialsChat. If you have essentials, you can add this on without adding anything extra.
When I restarted my server, the scripts reappeared after I deleted them. Doesn't work. But thanks anyways...
I am.
Try changing permissions directly in the PEX permissions.yml file, and see if it will work.
Use the command /pex reload to reload the permissions and config instead of reloading the server.
What's it mean when it talks about line x column x? I get this problem too but in other plugins.
How do you fix it?
why is "-" and "schema-version" incorrect?
Odd, I ran your permissions through http://yaml-online-parser.appspot.com and it validated with no errors.
That said, it's a mess. Your user record shows as admin, so your group set did not take effect. Captain is spelled as I indicated, not Captian. Your inheritance is also configured incorrectly. Captain inherits from default, so Commander only needs to inherit Captain not Captain and default. Moderator inherits Commander, so it doesn't need to inherit Captain & default. Admin, Coowner and Owner all have root wildcard permissions so having them inherit is pointless. Speaking of pointless, why do you have those co-owner and captain groups? Remove those and rename Captian to Captain. Also, using root wildcard is lazy and can cause problems with certain plugins. Bear that in mind if you install a plugin and strange things happen.
Change your user record to Default (it's case sensitive, so capitalize the D), ensure you aren't in ops.json then start the server and if you have a valid chat manager you should see the default prefix.
Oh... How embarrassing.... Thanks.