Magic

Magic

190k Downloads

Permissions "Magic.commands.*" and "Magic.create.*" do not work!

k-jiang opened this issue ยท 4 comments

commented

Platform: Spigot 1.12 build 1171
Magic 6.9.11
zPermissions 1.4 https://www.spigotmc.org/resources/zpermissions.11736/updates

FYI: those two permissions are not found in plugins.yml. In fact I could not found any of permission that comes with a wildcard "*". I have no choice but to manually add every single permission by hand.

Please fix it. Thank you so much.

commented

This is fixed now.

I'm sure it took way too long to matter to you, and I apologize for that. But, in my defense, this was kind of a pain in the butt and every single other permission manager seemed to be fine without it.

commented

Wildcards are generally handled by the permissions system. If zPermissions doesn't support them, you should consider getting a better permission plugin. PEx works great. GroupManager as well.

I'll leave this open for now but I don't really plan on added specific support in Magic for wildcards since most permission plugins handle it fine on their own.

commented

There are reason for ppl to choice a different permission system. For me zPermissions because it is the only permission that provide a per-world, per-region, bug-free, well-organized MySQL support (AKA the almost perfect permission), unlike PEx which has intention to put every chaos in a single SQL table. It makes life so much easier, especially when you trying to develop some custom api that suit your website / multi-server needs.
Beside, switching permission is never an easy task. We have thousands of permissions node set in 5 servers. I don't want to make things complected.

So how to fix it? This is what a section of EssentialsX's plugin.yml, "the (step)Father of GroupManager" looks like:

permissions:
  essentials.*:
    default: op
    description: Give players with op everything by default
    children:
      essentials.gamemode.*: true
  # These permissions can't be assigned from player-commands for compatibility reasons
  essentials.teleport.cooldown.bypass.tpa:
    default: true
    description: If the player does not have this permission, /tpa will have cooldown even with the parent bypass perm

See it is not that hard to fix it.

commented

I will leave this open and see what I can do. There are a couple dozen different commands with sub-commands but maybe adding wildcards is doable.