Case Sensetivity

[Sleaker]

The way you're handling case-sensetivity is causing massive amounts of issues with people attempting to use your plugin.Confusion in what needs to be set, which plugins use uppercase-partially in their permission checks, and in plugins that need to add permissions transiently. I suggest going back to what Bukkit does, instead of breaking functionality from what bukkit already provides, like what certain other permission developers do...

Secondarily. Why would you possibly want case-sensitivity on them, when are you going to use 2 permissions that are identical but differently cased?

[mlow]

^ That one ^ Time to give up your terrible love for case sensitivity. :3

[codename-B]

Superperms automagically lowercases permissions - only if you're using override-player: true will that be an issue. bPermissions (playernames etc) can be lowercased via an option in config.yml

[Sleaker]

what about offline permissions that don't get handled through the override? also - I can't seem to find the override anymore, looks like that option was removed.

[codename-B]

@Sleaker

https://github.com/codename-B/bPermissions/blob/master/src/de/bananaco/permissions/Permissions.java#L546

lowercase-all: true/false

I don't know of any "offline permissions" that check against the bPermissions API however.

[Sleaker]

Vault does :-/ and I was referring to override-player. I don't see that option anymore. - Heroes also adds lowercased permissions, and people have a tendency to reference them using uppercase, this causes issues when doing the permission tests.

[codename-B]

Alright Sleaker, I'll get that added - but only for the hasPermission check - I'm afraid that the getAllPermissions should return (correctly cased) all permissions

[Sleaker]

why can't you just strip casing when you load the permissions from file? :o

You wouldn't need any of those casecheck statements during runtime either, I guess I just get confused on how stuff is getting set through.

[codename-B]

Because people might want cased prefix/suffixes etcetera.

Casing is a very tricky thing to deal with :/

[Sleaker]

and this is exactly why using permission nodes for chat info is not a good idea.

[codename-B]

Until metadata is implemented it's the only option that fits nicely with my system (even after it's implemented I may keep it)

[codename-B]

So I've whacked metadata into its own section.