Bukkit

@RivePlays

I don't know of any reason why this shouldn't work in 1.9 or 1.10. No updates should be necessary, unless the API has been broken, in which case it might be worth reporting to the Spigot team.

@5pencer5

That is incorrect.

The number of slashes before a command is irrelevant. To Bukkit an extra slash is just another character. I don't know why you think this is an issue, it is not.

The command name is not the same as the permission node. You do not enter the name of the command, you enter the permission node for that command.

The WorldEdit (double-slash) wand command has a Permission listed in their documentation that I linked you to earlier: http://wiki.sk89q.com/wiki/WorldEdit/Permissions. See it about half-way down the page. You can press Ctrl+F in your browser to search and type wand, it will find it quickly. The permission node listed is "worldedit.wand" (without the quotes, obviously). Use that permission node in the command, not the command name.

This works the same for every permissions plugin. I suggest you read the information in the articles I linked earlier if you still don't understand. Otherwise you will run into the same issues you had with this plugin with any and every other permissions plugin you try.

@5pencer5

http://wiki.sk89q.com/wiki/WorldEdit/Permissions

Look up the Permission node next to the command. Every plugin sets their own permission nodes, so I can't tell you what the permission nodes are. You will notice that permission nodes do not contain spaces, instead they contain dots.

Since you seem to be very new to this, you should also read this article about Understanding Permissions. The Bukkit Permission FAQ may also be helpful.

@5pencer5

If you don't yet have an Admin group:

/GroupCreate Admin

To make yourself part of this group:

/GroupAddPlayer Admin 5pencer5 (or whatever your minecraft IGN is)

To grant the admins permission for that command:

/GroupGrantPerms Admin whatever.the.permission.node.is

To find the permission node you need, you will have to look it up on your kit plugin. They should have documentation available on their plugin page. Look for commands and/or permissions.

@Jayden2116

You will need to check the documentation for your plots plugin. It should contain a list of permissions for claiming, building and breaking etc.

Assuming you have already created a group for these players, you can add these permissions to that group using the /GroupGrantPerms command.

If these permissions are not registered you should double check they have been typed exactly correctly before proceeding. If necessary you can use the /RegisterPerm command to register this permission manually.

If you have not yet created a group, bear in mind that you can use the 'all' group. These permissions apply to all players on the server including Ops. If you don't want that you can use the /GroupCreate or /GroupAddPlayer commands to create a group and add players to it.

Best of luck with your server!

@Prodigy_W2K19

Short answer, no.

You can use the * wildcard to match a single term in a permission node, so with several commands you grant all registered permissions. E.g. *, *.*, *.*.*, *.*.*.* and so on. However that will only grant registered permissions. Not all plugins register their permissions, as sometimes it is impractical, and some authors don't know any better.

Giving someone every possible permission isn't very practical, as a number of plugins have permissions that provide actions that you don't necessarily want. E.g. simplyvanish can make you start invisible on signing in, but you might not really want that.

If you want someone to have access to all commands and features that an administrator should have, then using /op is the best way to achieve that. Plugins default to giving all permissions to ops, and only don't when the authors specifically exclude it (E.g. simplyvanish's auto-vanishing permission). Once you have op status, there are probably only a handful of extra permissions that you need.

@DiamondWolfGamer

The numbers just impose a priority for if a player belongs to multiple groups with a rank attached. The problem is that you haven't granted the permission to those groups.

If you create a rank called "Alpha", and you have a group called "alpha_players", you would type: /GroupGrantPerms alpha_players ranks.membership.Alpha

@DiamondWolfGamer

I see the problem. None of your groups have any "ranks.membership.[whatever the rank ID is for that rank]" permission. Check out the last section in the tutorial for help on doing this: http://dev.bukkit.org/bukkit-plugins/rankdisplaynames/pages/tutorial/