Strange behavior with multiverse #284


  • New
  • Defect
Open
  • _ForgeUser7400629 created this issue Apr 19, 2012

    Describe to us the issue that you're having:
    I labeled the issue as a defect for lack of a better selection. This may have nothing to do with bPerms but I figured i should log it. It concerns how permissions are applied in a multi world situation. I've come up with a scenario that changes the "how"the permissions apply to the players.

    Which steps will reproduce this problem?:
    1) boot a server with MV2, Commandbook, bPermissions
    2) test your current world permsissions. ( should work as expected )
    3) enter a different world
    4) test your 2nd world permissions. ( you should recieve a permissions set that matches that worlds deffinition )
    4) go back to your 1st world
    5) use the /reload command from commandbook to reload all plugins.
    6) test your 1st world permissions ( they should still work as expected )
    7) head to your 2nd world
    8) now if you test your 2nd world permissions, instead of recieving the expected permissios your user will have the 1st world permissions with the 2nd world permissions ADDED to them.

    ....

    Do you have an error log of what happened?
    No errors generate, not sure this is even really an error.

    Which version of bPermissions are you using?: (Please don't say "latest"!!!)
    v2.9.1

    Which version of CraftBukkit?: (Please don't say "latest"!!!)
    [INFO] This server is running CraftBukkit version git-Bukkit-1.2.5-R1.0-b2149jnks (MC: 1.2.5) (Implementing API version 1.2.5-R1.0)

    Commandbook version:
    [INFO] CommandBook version 468-bbd5396

    Any other information we may need (plugins, configs, etc):
    Like i said earlier. I'm not sure if this would be considered a "bug". For me its determinately unexpected as the application of the permissions in a per world situation changes from replacement to additive. I suppose if I had to make an un-edgucated guess maybe superperms is storing the current permissions set into its data storage method on the /reload command ( not sure if object or memory array or what ) but if that's the case I can still engineer the proper result via negating nodes from other world permissions files.

    If I've left anything out or you would like more debug info I'll get on it ASAP. Assuming its even an issue worth tracking down :)

    Please fill out this form properly! Failing to do so may result in your ticket being marked invalid.

  • _ForgeUser7400629 added the tags New Defect Apr 19, 2012
  • _ForgeUser7854525 posted a comment Apr 25, 2012

    I have mv and i don't get the problem but i did get other, but with MySQL.

    Q. Do you user global groups? And does it happen with commandbook only?

  • _ForgeUser7400629 posted a comment Apr 30, 2012

    Two things

    1 im not certain its a "problem" it was just unexpected for me

    2 no i dont use global groups but i do utilize inheritance quite a bit.

    Oh and i was wrong bout /reload being a commandbook command, /reload is a bukkit command.


    Edited Apr 30, 2012
  • codename_B posted a comment May 3, 2012

    This does seem like a bukkit bug - I'll do my best to update bPermissions so it absolutely wipes out each and every permissions reference on a /reload.

  • _ForgeUser7400629 posted a comment May 11, 2012

    @codename_B: Go

    Cool. Its not urgent cuz i can manage it with per-world group inheritance. Thanks for the hard work B.


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