i installed luckperms on bungee, when a user try to login, (i got authme and authmebungee that kick if the name is not equal in same format (example bOb instead Bob), if bOb will enter and wiill be kicked from authme but the incorect UUID is being saved by luckperms and trow the warn (https://gist.github.com/xion87/5f0085ac3d2c84ee3fca57b5872d0ed1).

In my bungee i have use-server-uuids: false, instead all servers have use-server-uuids: true
(both bungee and servers are in offline mode)

That's because users are given different UUIDs depending on the capitalisation of their username. That's just something you're going to have to accept if you run a cracked server.

I don't see what I could do to "fix" this in LuckPerms.

so my config is correct? you can just make some delay if user will say online like 10s after login before updating the UUID on table?

Why would I do that - it's not going to solve the root cause?

because the user with wrong name is not going to enter in server (is kicked by authme, so it stay online for like 1s), user with correct name will not kicked and the luckperms will have alway the correct UUID

If you don't want users with incorrect UUIDs to even be processed by the server, then AuthMe needs to kick them at a protocol level, before their profile is handled by plugins.

posssibly using authmebungee so, ok i got it

@lucko Can't you just treat usernames as case sensitive?

No, Mojang considers them case-insensitive, so LuckPerms does the same.

@lucko maybe make it configurable? I can't implement that into authmebungee in the current state, as it doesn't have any access over the db, it uses plugin messaging only.

Not easy to make that sort of handling configurable.

users are given different UUIDs depending on the capitalisation of their username. That's just something you're going to have to accept if you run a cracked server

As I said before ^^, I don't believe this is an issue LP should be responsible for solving.