This site works best with JavaScript enabled. Please enable JavaScript to get the best experience from this site.
Describe to us the issue that you're having:user Nug907 is my test account. When nug has a lone group of ( rank0 - rank9 ) and the group ( modr1 ) is added it applied group modr1's permissions apply properly. If nug has a lone group of (rank0-rank7) and group ( modr2 - modr4 ) are added then they will apply correctly. If nug has a lone group of (rank8 - rank9 ) and the group modr1 is added it applies correctly. If nug has a lone group of ( rank8 -rank9 ) and group (modr2 - modr4) are added then they fail to apply any effect at all.
I've yet to nail down a cause in the permissions them selves that would cause the behavior. I'll provide any other requested debug info.
Which steps will reproduce this problem?:1)2)3)....
Do you have an error log of what happened?No errors
Which version of bPermissions are you using?: (Please don't say "latest"!!!)v2.9.1
Which version of CraftBukkit?: (Please don't say "latest"!!!)This server is running CraftBukkit version git-Bukkit-1.2.5-R0.1-1-g32aa5ac-b2144jnks (MC: 1.2.5) (Implementing API version 1.2.5-R0.2-SNAPSHOT)
Which OS?unknown
Any other information we may need (plugins, configs, etc):I will attach the appropriate files for diagnostic work to be done.
Please fill out this form properly! Failing to do so may result in your ticket being marked invalid.
What are these "superperm" permission nodes?
@codename_B: Go
I prefix all of my node groups in the permissions.yml file with that to give a visual queue that that particular permissions node is defined in the super permissions file. They are just an organization tool for me.
Could it be perhaps that they're not defined properly in permissions.yml
I had thought that as well. My test for that was to apply the modr2-4 to the lower ranks andy i got the expected outcome. The issue seems to occur with groups using more than 6 levels of inheritance. That seemed to me to rule out impropper node configuration in permissions.yml
@Digitalink2008: Go
Hm, that's wierd as I run unit tests with up to 1000 levels of inheritance and it all applies correctly.
Could you perhaps run the /user has permission.node test and that'll help us track down if it's a superperms thing or not.
Will do. I'll log all the console output for you and submit it after some tests.
To post a comment, please login or register a new account.