config.yml explained
track-type
There are three options for this configuration. "multi", "single", and "lump".
This affects the behavior of the "promote" command. When set to "multi", "/promote" adds the next group in a track to the player. When set to "single", "/promote" sets the player's group to the next group in a track. When set to "lump", "/promote" adds all groups in a track to a player.
auto-save
A boolean option. Setting to "true" will make bPermissions save to file every single time you alter a permission, group, player or meta data. Setting to "false" will make it so in order for command changes to be saved (after no matter how many commands), you must do "/permissions save"
The config did not generate any section for configuring the SQL Databases. Would you mind providing more information that covers this area?
@codename_B Can you complete this please? there are some lines of the config file that are not explained here, like override-player, and enable-mcma
What happend to the config.yml?
@Knight_Hawk3
It got shorter since 2.3.
What about allow-offline? Any other parameters available?
@allbad1
It's like the 'Offlinemode' switch in the main server.properties file
@JoshGreen1996
what is the point in another offlinemode switch when bukkit already has one?
Can this be updated please? there are 3 more parts to the file that are not mentioned here.
@XeonG8
Offline-mode servers aren't officially/directly supported by/throuh bPermissions.
That's why you'll have to enable it, yourself.
well now it says track does (admin) does bot exist why the track is there
What is use-global for?
@nurwin22
You got one thing wrong.
use-global-files: true/false
@trainphreak
This sux, because if you set use-global-files: true users.yml and groups.yml files are still generated and the permissions are not the global ones maybe this is a bug
@ciulic
Like it generates an empty users.yml and groups.yml in the world folders and it overrides the global files making everyone not have a permission?
Hello. Can anyone explain ? Why /perm example files generates empty files ? (Instead of /helpme ? (was on late builds) it generates all av perm on server)
@ciulic
We're seeing the same thing, we have use-global-files: true but the world files are getting generated by the plugin and over-riding the global files.
@paulj1x
I concur. I've also trying to have bPermissions ONLY use global files. I don't care about per-world permissions. From the looks of the comments here, this isn't possible?
@ukAdamR
You can use the mirror feature to mirror all other worlds to the main world, and then just use the main world's files as the "global files". That's what I do. The global files are used for new world generations, i.e. if a SkyBlock server creates new worlds for individual player to play on.
@ukAdamR
I find it's pretty much impossible to get global perms working correctly when you have it enabled in the config, the closest I've gotten to is by using the /exec commands to modify perms, it'll modify all worlds perms if you don't specify a world. By what I know you can't do that with the normal /world command, even /world * doesn't work for modifying all files, that'll just modify the global files, but that's not much use anyways either way with the global perms config on or off.
The only way to use the normal commands and have them effect all the worlds is by using the world mirroring feature.
The only way that global perms would work correctly that I see is if it was changed from overriding the global file for the worlds file to adding onto the perms of the global file where negation takes precedence over the global file for nodes and groups. Negation could be done for groups to, like setting a group for a player for one world where doing something like setgroup ^default and addgroup vip, to remove them from the default group and add them to vip for that world. You'd still have to be careful when modifying a users groups like this though. And not to write anything to the world files unless you actually modify the perms.