Permissions Code Help

Discussion in 'Bukkit Help' started by HollowTheDragon, Aug 6, 2012.

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

    HollowTheDragon

    Hey guys,

    I'm new to using Bukkit servers, and just recently set up my own server on my laptop, and I'm having some issues with setting up permissions. I have friends that logon my server, but some of them I don't quite trust with certain plugins / commands. I'd like to install more plugins in the future, like WorldGuard, and other things in the future, but for now all I have installed on the server is WorldEdit. I tried setting up my permissions code so that only certain groups of users can access WorldEdit, some can only build traditionally, and users that I don't have assigned to a group yet set to not have the permission to build anything. I've tried setting it up so that one of my friends can use WorldEdit, but I can't get that to work out, and a friend who I didn't have assigned to a group could break and place blocks. The only way right now I can give anyone else access to WorldEdit commands is to Op them, and like I said some of them I don't trust being able to create a skyscraper made of TNT. I've tried a few things, and I know it has to be something with my permissions.yml file and the way I wrote it. I've looked around and tried sampling from other people's code I've seen, but nothing really seems to work. :/

    Here is a screenshot I took of the code: http://i1232.photobucket.com/albums/ff367/HollowTheDragon/permissionsYML.png

    Any help / advice anyone could share with me would be great! :D
     
  2. Offline

    fugue2005

    you need to get a permissions plugin.

    bukkit itself does not handle permissions
    the permissions.yml in the root of the server is for grouping permissions together to create a parent node that has lots of child nodes in it.
     
  3. Offline

    HollowTheDragon

    Ahh I see. Just watched a youtube video that explains quite a bit, haha. Will give a plugin a shot and see how it goes.
     
Thread Status:
Not open for further replies.

Share This Page