Bukkit

Describe to us the issue that you're having:
In a nutshell, the promote command needs to let you specify a world; or default to the current world, it is allowing ranks outside of tracks set in permissions to be altered. On worlds which a player has no access to. It is also creating duplicate ranks in other worlds as a side effect.

This could for example be used by junior staff to revoke other senior staff members access and set them to the lowest possible rank on all other worlds.

If I specify different rank tracks relevant to different worlds - and only give one rank track to a particular rank, on a particular world - on them using the promote command their rank changes on all worlds and all tracks. Where ranks don't exist on other worlds it also creates blank ranks of the same name, and appears to try to promote players to the lowest available rank on other worlds instead of the rank we wanted.

For example permission node tracks.mars

If that player then uses /promote player mars  it promotes them on next "mars" rank (correct) then reverts them on all other worlds and tracks to the lowest track rank applicable to that world - even if that track isn't the one you gave them access to.

So a player might be "default" on world "world" and "guard" on world "mars".  These two worlds have different ranks. And the staff member is only permitted to promote on the mars world and mars track.

If they are promoted  bpermissions sets the promoted player to "restricted" rank on all the other worlds, and upgrades them to "warden" in mars

Which steps will reproduce this problem?:
1) create two worlds, given them different ranks and permissions for each world
2) create two different rank tracks containing the unique ranks on particular worlds eg restricted, default, soldier, and restricted, prisoner, guard
3) on the second world give access to only the second rank track to a player
4) if that player attempts to promote only on that world, what happens is target gets promote on that world (corect), but on all other worlds they get dropped to the lowest rank; or ir creates a blank rank and drops the player in that rank on other worlds.

Do you have an error log of what happened?
Difficult to show but basically on worlds that dont have the rank you get a blank rank added:
  rank:
    permissions: []
    groups: []

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

Which version of CraftBukkit?: (Please don't say "latest"!!!)
2013-01-23 14:51:29 [INFO] This server is running CraftBukkit version git-Bukkit-1.4.6-R0.3-b2586jnks (MC: 1.4.6) (Implementing API version 1.4.6-R0.3)

Which OS?
Linux

Any other information we may need (plugins, configs, etc):
Although you could use the /world  etc commands of bpermissions; these require allowing much higher access to bpermissions, effectively rendering it pointless (may as well /op them for all the good it does)  the only commands commonly used by staff is /promote and /demote restricted by both permissions on a particular world; and using the tracks.trackname permissions - but for some reason this area of bpermissions has been neglected to the point of negligence, and has had functionality removed according to your historical user documentation.

Given the promote/demote functionality is what is primarily used on any permission plugin the removal of such, and the player notification of promotion/demotion has reduced long term usefulness of this plugin to the point most servers will probably need to look at changing to another permissions plugin.  In my case i swtiched to bpermissions from yeti when it was discontimued for its promote track functionality but soon discovered all advanced features in this area had been removed in a prior version.

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