Default Rank #163


  • New
  • Enhancment
Open
Assigned to _ForgeUser1494830
  • _ForgeUser6842193 created this issue Aug 21, 2014

    I'm currently setting up new servers and I'm using the default permissions group but also additional groups such as VIP and Moderator.
    The problem: When people get assigned an "additional" rank like VIP, the default-rank (with all the fancy default-permissions) vanishes. To prevent that you can just set the parent of VIP to default. That only works for the permission nodes though and not for the prefix which I want my players to keep.

    My suggestions to fix this: Edit an option to make the default rank a "full rank". That might, of course, result in having to save more player records, but would fix my issue.
    Any other suggestions concering this problem are greatly appreciated.

  • _ForgeUser6842193 added the tags New Enhancment Aug 21, 2014
  • _ForgeUser1494830 posted a comment Aug 21, 2014

    See ticket #161.

    Same issue, already solved in a dev build, would appreciate more testers/feedback.


    Edited Aug 21, 2014
  • _ForgeUser6842193 posted a comment Aug 21, 2014

    @ZerothAngel: Go

    Thank you very much. Sorry, I couldn't tell from the headline. Will test the dev-build.

  • _ForgeUser6842193 posted a comment Aug 21, 2014

    @ZerothAngel: Go

    Is this compatible with SQL-shared permissions? Doesn't seem to work for me :/. What I did: Removed all groups from the player, added default group, then added VIP.

    default vanishes, VIP stays.

    EDIT: This only happens with existing players. Works fine with new players. :) I only have issues with the chat-prefix vanishing when the player is in more than two groups. If group #1 doesn't have a prefix but group #2 does. Will #1 override with the empty prefix or will the plugin just use the prefix from #2?


    Edited Aug 21, 2014
  • _ForgeUser1494830 posted a comment Aug 21, 2014

    @Tallcraft: Go

    I've only tested with database storage so far, but maybe there's some misunderstanding.

    This is what the new option does:

    1. New user logs in
    2. If they are brand new to your server, they will be added to the default group
    3. If explicit-default-group-membership is false, then it's just like before: they are considered a member of the default group as long as they are not a member of any group. No database change is made.
    4. If explicit-default-group-membership is true, then a database change is made. They are now explicitly a member of your default group. If you then later add them to additional groups, they will not lose their original membership to the default group.

    So any existing users will have to be manually added to the default group. There's no way for me to know that if they're in VIP or whatever that they should also be added to default. (If all of your existing users should be added to the default group, then that's something you can possibly do with a script.)

    However, new users (and really, anyone who is not a member of any group) will have the explicit default membership when they log in - a "full rank" as you say.

  • _ForgeUser1494830 posted a comment Aug 21, 2014

    As to your chat-prefix question, I believe it's the same as permissions. Group weights will determine the order they are applied. So the solution would be to give group #1 (which is probably your default group?) a lower weight. Negative weight would be fine as well.

    If it doesn't already work this way, there is a switch or two.

    Unfortunately, I can't give definite answers since I'm at work and don't have access to my dev environment at the moment.

    Edit: Forgot I could just look on github. :P It's the inherited-metadata switch. Make sure it's true and then metadata like prefixes/suffixes will follow the same rules as permissions.


    Edited Aug 21, 2014
  • _ForgeUser6842193 posted a comment Aug 22, 2014

    @ZerothAngel: Go

    Thanks! :)


To post a comment, please login or register a new account.