Data inconsistency warning with incorrectly set-up bungeecord networks

[AuroraLS3]

Describe the issue

When BungeeCord is not properly set-up, some servers might use offline uuids while the bungeecord uses online UUIDs. This can lead to a case, where a single player has two UUIDs in a Plan database - the server stores data with the offline UUID but it is inaccessible via the bungee web interface because it is using the other UUID.

Server information

This can occur if IP forwarding is set to false on bungeecord

What I would like to happen

• The server should pop out a warning about uuids being inconsistent and instructions on how to resolve the underlying issue.
• Plan would use the existing UUID in the database (Unknown if this is possible because Player#getUniqueId returns wrong UUID)
  • Possibly run a correction task on Bungeecord to fix entries with incorrect UUIDs when the player leaves

[AuroraLS3]

TODO

• Write a task that runs when Plan enables on Bungeecord
• The task should check if any player name has 2 uuids in the Plan database
• If there are, a large warning should be printed to console with a link to https://www.spigotmc.org/wiki/bungeecord-installation/#post-installation
• Get the UUID of the player with UUIDFetcher - note that this only gets online UUIDs, but it should not be a problem since offline-mode bungeecord should only store offline mode uuids.
• Correct the data
  • Sessions and kills should update the rows with wrong uuid to the correct uuid
  • plan_users and plan_user_info entries for the wrong uuid should be removed from the database (update oldest registration date for the correct row though)
  • extension data for the wrong uuid should be pointed to the correct uuid