bPermissions Custom Nodes - WorldEdit/HSP Not Granting Perms

Discussion in 'Plugin Development' started by Favorlock, Dec 30, 2012.

Thread Status:
Not open for further replies.
  1. Offline

    Favorlock

    So recently I pushed a commit to bPermissions to fix the custom nodes and that did work, however I've noticed that HomeSpawnPlus and WorldEdit perms simply do not work with custom nodes. They do work when specified in the groups.yml file.

    Example: groups.yml:
    Code:
    default: Newborn
    groups:
      Newborn:
        permissions:
        - custom.node
        - custom.homespawnplus
        groups: []
        meta: []
    Example: custom_nodes.yml:
    Code:
    permissions:
        custom.node:
        - worldedit.selection.pos
        - worldedit.wand
        - worldedit.hpos
        - worldedit.wand.toggle
        node.homespawnplus:
        - hsp.command.home
        - hsp.command.sethome
    As you can see, in custom_nodes.yml we have to custom nodes (custom.node & node.homespawnlus). Normally (like with essentials) we would have those six nodes specified in the two custom nodes and would then be able to give ourself the WE wand with //wand and use /sethome and /home from HSP. However, all these plugin nodes are not being granted when specified. I know for a fact that a majority of the plugins do work. It just seems that their are some plugins not granting perms.

    Does anybody know a solution to this problem? You can see all my changes to bPermissions by visiting my github fork @ https://github.com/Favorlock/bPermissions

    Thanks for any assistance.
     
  2. Offline

    Nitnelave

    Maybe try to post that on the plugin page or forum? You'll find more people aware of the problem. Have you tried looking at the WE code for permissions?
     
  3. Offline

    codename_B

Thread Status:
Not open for further replies.

Share This Page