Offering help with Permissions plugins.

Discussion in 'Bukkit Help' started by TheHank, Feb 4, 2011.

?

Was this usefull?

  1. Yes

    100.0%
  2. No

    0 vote(s)
    0.0%
Thread Status:
Not open for further replies.
  1. Offline

    TheHank

    So I've looked a bit on this forum, especially around the plugins that are supported by Permissions, and I see that alot of people are having trouble to set up their own config, and allow different people to use specific commands.

    Now that I know how to do this well enough, I'm offering people that need help, my own help. If you have problems with setting it up, just post in this thread or send me a PM and we can discuss it further.

    I hope that offering my help privately to other people isn't bad or against the rules, otherwise just tell me so.

    Contact information:
    Skype: ozzzit
    E-Mail: giorgio_f.u@live.nl
     
  2. Offline

    chill1977

    You have your's set up close but not correct as you list every node under every group and have inheritance set. I have written a guide that has a file formatted correctly and it is posted on both the permissions and essentials forums. It doesnt get any easier than this.

    First make sure you have the latest TESTED version of Permissions and Essentials.
    Next put the Permissions and Essentials .jar in the plugins folder and the corresponding folders with each plugin in the plugins folder. Run minecraft to generate any files that need to be generated, then shut it down again. You then need to edit your Essentials config.yml that is found in plugins/Essentials/config.yml.

    Essentials comes with certain commands already under the restricted commands list. I don't believe these still work as of the new updates and Bukkit changing the way it handles the commands. But none the leass delete those commands that are there to save yourself headeache later. Below is a basic Essentials config.yml that should work for most everyone.
    Code:
    # A color code between 0-9 or a-f. Set to 'none' to disable.
    ops-name-color: 'none'
    # The character(s) to prefix all nicknames, so that you know they are not true usernames.
    nickname-prefix: '~'
    # The delay, in seconds, required between /home, /tp, /warp, etc.
    teleport-cooldown:
    # The delay, in seconds, required between /heal attempts
    heal-cooldown:
    # The number of items given if the quantity parameter is left out in /item or /give.
    default-stack-size: 1
    # The message of the day, displayed on connect and by typing /motd.
    motd:
      - '&cWelcome, {PLAYER}&c!'
      - '&fType &c/help&f for a list of commands.'
    # The server rules, available by typing /rules
    rules:
      - '[1] Be respectful'
      - '[2] Be ethical'
      - '[3] Use common sense'
    # Disabled commands will be completelly unavailable on the server.
    disabled-commands:
    # Restricted commands will only be available to ops.
    # These will have NO EFFECT if you have Permissions installed!
    # These are here only if you want something simpler than Permissions.
    restricted-commands:
    # Note: All items MUST be followed by a quantity!
    # Times are measured in seconds.
    kits:
      tools:
        delay: 10
        items:
          - 277 1
          - 278 1
          - 279 1
    # End of File
    A few rules that apply for .yml files.
    1) If you edit the .yml file keep the same format, this means same amount of spaces from the edge of paper. Doesn't seem like a big deal but it is!
    2) Do not use the apostrophe in the text you want displayed. Example : - '[1] Be respectful of chill's stuff.' This comes across that the code that starts before [1] and should end after chill. Thus, throwing the rest of your command line starts and stops off throughout the file and leaving an open command at the end of the file.
    3) Be sure to wrapped all commands in apostrophes. Some of them are not required but it doesn't hurt and will save you a headache later.
    4) Leave a space after every colon, before every command starts.
    5) Do not use tabs. Use the spacebar. If you are using notepad++ there is a setting in the settings at the top that lets you use spaces when tab is hit instead of actually tabbing.
    Every plugin will be required to change their commands so that other plugins using the same commands won't try to load over them causing neither to work but for now here is how you disable the commands you don't want Essentials to have priority over.
    1) Open the Essentials.jar with winrar or winzip.
    2) Open the plugin.yml in notepad or notepad++.
    3) Delete the commands that you don't want to use Essentials for.
    4) Save file and close, at this time you should be prompted as to whether or not you want the file updated in the .jar, click yes.

    Now that you have Essentials set up we will move to Permissions.
    Before you do any editing to this file, I suggest you start Minecraft and make sure there are no errors. If there is then you need to update Permissions, Craftbukkit, and Essentials.
    Do not say you already have. They are changing versions rather quickly and you can bet the one you downloaded 3 hrs ago is not the newest one.
    If it loads ok then close the server. Do not try the commands and say it doesn't work, at this point you have no commands.
    Navigate to plugins/Permissions/config.yml and open in notepad.
    Same rules apply to this as Essentials as stated above. Basic format follows 4,8, and 12 spaces from the margin, once again NO TABS.
    It comes with a basic format of what it should look like.
    Now that you have the Permissions config.yml open let's start the editing.
    You can change the group names to suit your needs. If you want to add new groups to the existing ones, do not use copy and paste.
    This may work sometimes but more times than not it will cause errors.
    My suggestion is that each time you change anything you test it at http://yaml-online-parser.appspot.com/ to make sure you did that part correctly before moving on. This will make it easier to find errors.
    This is an example group with color which I will explain later.
    Code:
        Member:
            default: false
            info:
                prefix: '&cMember'
                suffix: '&c'
                build: true
            inheritance:
                - Default
            permissions:
                - 'essentials.me'
                - 'essentials.clearinventory'
                - 'essentials.afk'
                - 'essentials.sell'
                - 'essentials.warp'
                - 'essentials.home'
                - 'essentials.sethome'
                - 'essentials.accept'
                - 'essentials.tp'
                - 'essentials.item'
                - 'magiccarpet.mc'
                - 'woolcolor.spawn'
    You must add the permission nodes to the group that you want to have access to that command. Each plugin that is compatible with Permissions will have the nodes listed on the forum or in a wiki linked on the respective forum.
    You must have an apostrophe at the beginning of each line of command and at the end.
    You must have a space after each dash.
    You must have a space after each colon.
    After you add each group you are going to add then check it in the parser linked above
    Your highest group should simply have permissions: '*' , this will give them access to all commands.
    You see in the code that this group has inheritance: -Default. This gives the users of this group all the permissions listed for this group as well as those permissions listed for the Default group.
    This allows each permission "node" to be used only once per document unless you have a group that you do not want to use inheritance. In simplicity each group should inherite from the group below it. 1 group not 3 or 4 that are blowe it. Members will inherite from Default, Mods will inherite from Members, Admin will inherite from Mods.
    Now you can edit the users.
    Default is the base level anyone that joins your server level. For small servers that want protection against greifers. I suggest you use this level to stop people from building until they are added to a higher group. In order to stop people from building you must have the Antibuild plugin and set build: false
    As for bigger servers that have thousands of people joining per hour this is not realistic, so you set the Default as the basic can build member and have other plugins installed to control greifing like WorldGuard/WorldEdit, BigBrother or numerous others in the forum.
    The new version of Permissions allows you to edit per user colors. While I am not positive, I would assume this will over-ride the group seetings of that user. I know that permissions given in the user area add to those permissions given to that users group for that user.
    Code:
    users:
        chill1977:
            group: Mod
            info:
                prefix: '&aMOd'
                suffix: '&a'
            permissions: 
                - 'essentials.banip' 
    This code says that the user chill1977 is in the Mod group, which means he has access to the permissions given to that group plus any group it inherites from (Members and Default) plus the command /banip. This enables you to give special commands to certain people without giving them to the whole group.
    It also adds color and the word Mod before his name.
    You do not add users that you want to use the Default group. They will automatically use the DEfault group when they log in.
    In order to use color you need a plugin that enables and formats the color. I suggest iChat, while there are others, this pluign is made by the Permissions author which means it is more liely to work with permissions, plus it very easy to use.
    Here is the code that I use for iChat.
    Code:
    message-format: '+prefix+suffix +name: +message'
    Once you have everything set up like you want it, hopefully you have listened and been testing the file throughout the editing process using the online parser and have no errors, then this should work. This is an example of my config.yml for permissions with basic Essentials commands.
    Code:
    plugin:
        permissions:
            system: default
    groups:
        Default:
            default: true
            info:
                prefix: 'New'
                suffix:
                build: false
            inheritance: 
            permissions:
                - 'essentials.spawn'
                - 'essentials.motd'
                - 'essentials.help'
        Member:
            default: false
            info:
                prefix: '&cMember'
                suffix: '&c'
                build: true
            inheritance:
                - Default
            permissions:
                - 'essentials.me'
                - 'essentials.clearinventory'
                - 'essentials.afk'
                - 'essentials.sell'
                - 'essentials.warp'
                - 'essentials.home'
                - 'essentials.sethome'
                - 'essentials.accept'
                - 'essentials.tp'
                - 'essentials.item'
        VIP:
            default: false
            info:
                prefix: '&cVIP'
                suffix: '&c'
                build: true
            inheritance:
                - Member
            permissions:
                - 'essentials.mail'
                - 'essentials.mail.send'
                - 'essentials.time'
                - 'essentials.msg'
                - 'essentials.getpos'
                - 'essentials.tree'
                - 'essentials.bigtree'
                - 'essentials.sell'
                - 'essentials.setwarp'
        Mod:
            default: false
            info:
                prefix: '&1Mod'
                suffix: '&1'
                build: true
            inheritance:
                - VIP
            permissions:
                - 'essentials.list'
                - 'essentials.kick'
                - 'essentials.tphere'
                - 'essentials.give'
                - 'essentials.heal'
                - 'essentials.heal'
                - 'essentials.ban'
                - 'essentials.helpop'
                - 'essentials.unban'
                - 'essentials.banip'
                - 'essentials.unbanip'
        Admin:
            default: false
            info:
                prefix: '&aAdmin'
                suffix: '&a'
                build: true
            inheritance:
                - Mod
            permissions:
                - '*'
    users:
        chill1977:
            group: Admin
            info:
               prefix:
               suffix
            permissions:
    I have removed all of the ## lines as these are just comment tags and have no bearing on the file. This makes it easier to look through the file.
    If I have missed anything or you have any suggestions to add then please send me a convo with proposed ideas. Thanks.
     
  3. Offline

    TnT

    These guides will surely be apprechiated by anyone using these plugins.

    I cannot wait until built in permissions replaces the need to use these shitty yml files. I would like to see yml burned in a fire while it's children watch hopelessly from a distance.

    Why anyone thought using yml for this is beyond me. It is clearly where the majority of people get stuck when setting up those permissions that use it.
     
  4. Offline

    mughi

    you're doing it wrong.. burn the children first
     
  5. Offline

    TnT

    I didn't want to get mean. Burning yml is more of a mercy killing than anything.
     
  6. Offline

    Pezmantbh

    I haven't read through all of that, but +internets to you anyway :)
     
Thread Status:
Not open for further replies.

Share This Page