Another Question ~ SuperPerms

Discussion in 'Bukkit Help' started by ArrowToTheKnee, Jan 11, 2012.

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

    ArrowToTheKnee

    So, I know that SuperPerms is the Bukkit Permission System. But, I don't understand what the permissions.yml is in the root of Bukkit, not the permissions.yml in my PEX folder.
    Alas, Factions AND HomeSpawnPlus have these permissions that are for example, factions.kit.mod
    This includes multiple permissions. But, it doesn't work, and I'm suspecting since the guide says "only for SuperPerms," I'm guessing it has something to do with it...Exactly what do they mean by only SuperPerms?
    Yes, I'm confused.

    Ahhhhh...
    I see I must edit the permissions.yml in the root. All I need to know is if that will work in perfect harmony with PEX, AND how to setup the parent nodes :D.

    Oh I see...
    The root .yml file makes custom parent nodes. So, all I need to do is setup these parent nodes? And I can name the parent node anything I want, right, but must use specific children nodes? For example:
    Code:
    factions.kit.halfplayer:
        children:
            Any children nodes here?
    Is this CORRECT?

    Bump.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 23, 2016
  2. Offline

    sillyrosster

    I have been trying to figure this out for a long time. Did this work for you?
     
  3. Offline

    ArrowToTheKnee

    Old thread, but,
    factions.kit.halfplayer
    is a defined parent node, and you will get errors if you try to define it.
    I've learned that only for SuperPerms means for permissions plugins that support SuperPerms. HOWEVER,
    PEX doesn't allow the negation of parent nodes, but bPermissions does.
    That is why I switched.
    Pex doesn't have FULL support but,
    bPermissions does.
     
  4. Offline

    sillyrosster

    I use PermissionsBukkit. SuperPerms is fully supported for that. I have been wanting to figure out how to use bukkits permissions.yml, but I haven't been able to find anything, anywhere I look it up. Until this post.
     
  5. Offline

    zipron

    Hey, if you use a permission plugin, just ignore the permissions.yml in the root folder navigate to: <root>/plugins/<permission_plugin>/...
    Somewhere there is the correct permission file. The easiest permission plugin imo is essentialsGM, you can find a link to a complete guide in my signature down below =)

    zip
     
  6. Offline

    sillyrosster

    I have been doing this since Bukkit started, I think I know what I'm doing. I was trying to figure out how to get Bukkits permissions.yml working so that it can make my job easier. With Bukkits permissions.yml you can make a parent node, insert child nodes and then insert that parent node you made up in your Permissions/config.yml file. This makes your config.yml much cleaner and easier to work with.
     
  7. Offline

    zipron

    Ok; but I think that is also possible with perm plugins =) with some research you'll get there =) And remember you can always assign all node of a plugin by using "*": - essentials.* gives all essentials commands, - worldedit.brushes.* gives all brushes. It's the same idea as parent-child I think

    zip
     
  8. Offline

    sillyrosster

    Not to be rude, but did you read what I posted. Lol. I clearly stated I have been doing this for a LONG time and know what I'm doing. Bukkits permissions.yml simply makes writing the permissions config easier/cleaner. You put tons of nodes into one node = awesomeness.
     
  9. Offline

    zipron

    Ok, than I can say it's as easy to use plugin parent nodes, have you tried use them? And you never stated you did this for a LONG time, you said you were confused, so I tried to help =)

    zip
     
  10. Offline

    sillyrosster

    That counts as saying "a long time" :p
     
  11. Offline

    zipron

    ok you win =)
     
Thread Status:
Not open for further replies.

Share This Page