Promote node to give groups the right to promote? (permissions 3.1.5)

Discussion in 'Bukkit Help' started by TheFusion998, Jun 18, 2011.

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

    TheFusion998

    I use Permissions 3.1.5.
    how can i add the permission to promote a user to another group?

    psl reply me:(
     
  2. Offline

    pauldemonkey

    Syntax: /permissions <target> (w:<world>) promote <parent> (w:<parentworld>) <track>
    Permission node: permissions.promote.<track>
    Description: This commands promotes the user along the specified parent's track.

    Syntax: /permissions <target> (w:<world>) demote <parent> (w:<parentworld>) <track>
    Permission node: permissions.promote.<track>
    Description: This commands demotes the user along the specified parent's track.
     
  3. Offline

    TheFusion998

    ok thx, but how do these tracks work? what are they and what do i have to do?
     
  4. Offline

    pauldemonkey

  5. Offline

    ViruSpreadeR

  6. Offline

    TheFusion998

    ok maybe this really works, but what the **** are tracks? pls explain how they work and what they do :(

    is it just that i specify the order? and with every promote the user jumps one up?
     
  7. Offline

    Jeyge

    A track is just the path you want a user to take when they are promoted. So if you have a basic server and you want people to stay in the Default group for 2 weeks then they move on to Builder and eventually Moderator, you would set up your tracks like this:
    Code:
    tracks:
        DefaultTrack:
        - Default
        - Builder
        - Moderator
    
    This can then be modified or added to based on what type of server you have. Another example for a RPG server might be:
    Code:
    tracks:
        FighterTrack:
        - Unarmed
        - Swords
        - DualSwords
        - Tank
    
     
  8. Offline

    ViruSpreadeR

    so what you saying is they cant be promoted to other groups other than their corresponding tracks?
    edit:lots of things is still not clear
    this was your example groups.yml (open)

    Code:
    groups:
        Guest:
            permissions: null
            inheritance: null
        Builder:
            permissions: null
            inheritance: null
        SuperBuilder:
            permissions: null
            inheritance: null
        Donor1:
            permissions: null
            inheritance: null
        Donor2:
            permissions: null
            inheritance: null
        MiniModerator:
            permissions: null
            inheritance: null
        Moderator:
            permissions: null
            inheritance: null
        Admin:
            permissions: null
            inheritance: null
        SuperAdmin:
            permissions: null
            inheritance: null
    tracks:
        BuilderTrack:
        - Guest
        - Builder
        - SuperBuilder
        - MiniModerator
        DonorTrack:
        - Guest
        - Builder
        - SuperBuilder
        - Donor1
        - Donor2
        - MiniModerator
        AdminTrack:
        - MiniModerator
        - Moderator
        - Admin
        - SuperAdmin

    1. what if i used the command
    /permissions Jeyge w:TestWorld promote <parent> w:TestWorld BuilderTrack
    then /permissions Jeyge w:TestWorld promote <parent> w:TestWorld DonorTrack
    what will happen?
    2. and in the command /permissions <target> (w:<world>) promote <parent> (w:<parentworld>) <track>, what do you put in <parent>?the group ur currently in?or the group of what u want the user to be promoted?
     
  9. Offline

    pauldemonkey

    i haven't tested this myself but my assumption is that its the group you want the user to be promoted to because the yml file already knows what group he is currently in so it would seem pointless to type it in. But once again, speculation.
     
  10. Offline

    ViruSpreadeR

    that was i thinking...if the <parent> in the command (/permissions <target> (w:<world>) promote <parent> (w:<parentworld>) <track>) is supposed to be the group you want the user to be promoted in...whats the point of the tracks?
     
  11. Offline

    TheFusion998

    thats exactly what i thought :p
     
  12. Offline

    Jeyge

    Parent is the group you want the user to be promoted from and is needed because Permissions 3.x is multi-group aware. You have to say exactly which set of groups (tracks) you want them promoted in. This, using another rpg example, allows you to give a user the Sword, Dagger and Wands groups and promote them into things like DualSwords, DualDaggers and IceWands.

    They can be promoted to anything that your mind can dream up. Using my example above, if I were to say be in the Guest group, I could be promoted using either the BuilderTrack or DonorTrack. Now lets say I was promoted in the BuilderTrack using "/pr Jeyge w:world promote Guest BuilderTrack", I would now be in the Builder group. If someone were to then type "/pr Jeyge w:world promote Builder DonorTrack", I would then be in the SuperBuilder group. One more promotion in the BuilderTrack would take me to MiniModerator or one more in the DonorTrack would take me to Donor1. Once in MiniModerator, I would be able to be promoted in the AdminTrack.

    Overall though, my example is extremely simple and can be expanded on in any way a user wants or a server needs.

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

    ViruSpreadeR

    so i guess the <parent> in the promotion command is your current group right?now it make sense...but why put the <parent> command if the permissions already know what group the user has?or maybe it doesnt know so i have to put the group he is in?hmmm...i remembered that permissions has multigroup now...so thats why i have to put the groups he is in...thx for clarifying...one more question...whats the exact order in the tracks groups?from least to higher or from higher to least?

    EDIT:didnt see your other post...nvm the <parent> problem...can u answer the last question?
     
  14. Offline

    Jeyge

    It would be from lowest to highest.
     
  15. Offline

    ViruSpreadeR

    cool...thx
     
  16. Offline

    brzavr

    problem!
    Moderators can not use comand
    Code:
    /pr nick promote t:invite
    /pr nick demote t:invite
    "you do not have permissions to use this command"


    Admin at all ok - tracks work, but at the moderators - there is no :(

    this part of groups.yml

    Code:
         default:
            default: true
            info:
                prefix: '&7[-]'
                suffix: '&f'
                build: false
            inheritance:
            permissions:
        member:
            default: false
            info:
                prefix: '[+]'
                suffix: ''
                build: true
            inheritance:
                - default
            permissions:
        moderator:
            default: false
            info:
                prefix: '&9[mod]'
                suffix: '&f'
                build: true
            inheritance:
                - member
            permissions:
                - 'permissions.promote.invite'
                - 'permissions.demote.invite'
        admins:
            default: false
            info:
                prefix: '&4[adm]'
                suffix: '&f'
                build: true
            inheritance:
            permissions:
                - '*'
    tracks:
        invite:
            - default
            - member
     
  17. Offline

    Coops

    sup bros Im very new to permissions :) I wanna know how to promote someone who is ranked at Hobo (lowest rank) to say Citizen or something like that. How do i promote? because everytime i try its says Permissions User/Group does not exist

    BUMP ^^

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 16, 2016
Thread Status:
Not open for further replies.

Share This Page