PermissionEX (permission.yml issues)

Discussion in 'Bukkit Help' started by Hem, Oct 12, 2013.

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

    Hem

    Hello,

    Since the developer on my server has gone into hibernation I have been faced with modify the permission.yml myself... It Isn't going very well...

    Anyway, I have currently made 5 groups Default/member, VIP, Moderator, Admin and Owner all seem to be working except the default one. I keep getting the same error with the prefix, I have tried so many different prefix combination's and known of them work? I do have the chatmanager enabled in the config.

    Also, I'am trying to get it so only the vips can warp to the vip as at the moment all the groups can warp there. But I don't want to disable to warp on all the other groups if you know what I mean?

    PasteBin :- http://pastebin.com/j1ehZVzW

    Thanks, Hem.
     
  2. You made a mistake at line 5, it needs to be permissions: and you have permissions without a colon.
     
  3. Offline

    Hem

    Well that fixed one issue, but what about the one:
    • Line 4 is: ····prefix:·'&f[&3Member&f]'
    And also
    to get it so only the vips can warp to the vip as at the moment all the groups can warp there. But I don't want to disable to warp on all the other groups if you know what I mean?

    EDIT:
    Fixed it, I simply forgot some spaces and colons.
     
  4. Offline

    random_username

    I corrected yaml format: http://pastebin.com/qdkTXdQy
    Also, if what you mean is that you want a specific group to be able to go to a warp, if you are using essentials, there is an option to make the permissions per warp. That's how you could add to the VIPs essentials.warps.<name> :)
     
  5. Offline

    Hem

    Hello,
    I actually already fixed it all myself after spotting some pretty stupid mistakes but the moderators where too late to approve the post.
    Anyway, about your idea with the warp I actually already have that on now although I haven't been able to get some else on the server to test it out so I'am not sure if it works or not?
    This is how it looks:
    Code:
    default group:
     
        - essentials.warp.hub
        - essentials.warp.pvp
        - essentials.warp.shop
     
    VIP group:
     
        - essentials.warp.vip
    
    Although that's all done, I have come across another problem... this time with the prefixs! I have added all the prefixs and enabled them to work with the chatmanager although whenever I set myself in a different group it still shows up the default groups prefix so for example I change myself to the owner group and then in game i talk it says 'user'_hem_: bla bla when it is really meant to say 'owner'_hem_: bla bla... You see what I mean?
    list of the prefixs:
    Code:
    default group:
        prefix: '&7[User]&f'
        suffix: '' 
    VIP:
        prefix: '&6[VIP]&f' 
        suffix: '' 
    moderator:
        prefix: '&a[Moderator]&f'
        suffix: ''
    admin:
        prefix: '&1[Admin]&f'
        suffix: ''
    owner:
        prefix: '&4[Admin]&f'
        suffix: '' 
     
    
    and then the first config in the permissionEX file:
    Code:
    enable: true
    message-format: <%prefix%player%suffix> %message
    global-message-format: <%prefix%player%suffix> &e%message
    ranged-mode: true
    chat-range: 100.0
    More help would be appreciated!

    Thanks, Hem.

    Hello,

    I'am have a some problem... with prefixs! I have added all the prefixs and enabled them to work with the chatmanager although whenever I add myself into a different group it still shows up the default groups prefix so for example I change myself to the owner group and then in game I talk it says 'user'_hem_: bla bla when it is really meant to say 'owner'_hem_: bla bla...
    So basically whatever group I'am in it still show's up with the default groups prefix...

    You see what I mean?

    list of the prefixs:

    Code:
    default group:
        prefix: '&7[User]&f'
        suffix: ''
    VIP:
        prefix: '&6[VIP]&f'
        suffix: ''
    moderator:
        prefix: '&a[Moderator]&f'
        suffix: ''
    admin:
        prefix: '&1[Admin]&f'
        suffix: ''
    owner:
        prefix: '&4[Admin]&f'
        suffix: ''
     
    
    and then the first config in the permissionEX file:

    Code:
    enable: true
    message-format: <%prefix%player%suffix> %message
    global-message-format: <%prefix%player%suffix> &e%message
    ranged-mode: true
    chat-range: 100.0
    Help would be appreciated!

    Thanks, Hem.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Jun 4, 2016
  6. Offline

    PolarCraft

    Please use pastebin.com to paste the whole permissions.yml.
     
  7. Offline

    Hem

  8. Offline

    jacklin213

    Hem did you change yourself to owner using a command? or just changed it in the file
     
  9. Offline

    Hem

    Commands in-game... So I spawned as a default player and then changed to owner.
     
  10. Offline

    jacklin213

    just going to point out
    Code:
    - essentials.warps.hub
    - essentials.warp
    the second node is to use the /warp command and to not mix the permission nodes up Essentials have made warp nodes with a S at the end
     
  11. Offline

    Hem



    Ah right,

    so it should look like this:

    Code:
    default group:
     
        - essentials.warps.hub
        - essentials.warps.pvp
        - essentials.warps.shop
     
    VIP group:
     
        - essentials.warps.vip
    Thanks.
     
  12. Offline

    jacklin213

    it should look like this
    Code:
    groups:
      default:
        default: true
        prefix: '&7[User]&f'
        suffix: ''
        permissions:
        - essentials.warp
        - essentials.warps.hub
        - essentials.warps.pvp
        - essentials.warps.shop
     
  13. Offline

    Hem

    Right and the VIP should be:

    Code:
    - essentials.warps.vip
    
    Although I'am still having trouble with my other issue:


     
  14. Offline

    jacklin213

    @Hem what other issue?
     
  15. Offline

    Hem

    Sorry, everything is fixed now.
    Thanks for your help.
     
Thread Status:
Not open for further replies.

Share This Page