UUID Update

BanManager has been re-written from the ground up.

This build has not been tested with offline servers, it is intended for online servers ONLY

Update from v4

  1. BACKUP YOUR DATABASE AND CONFIG
  2. BACKUP YOUR DATABASE AND CONFIG doesn't hurt to make sure you have more than one backup.
  3. Ensure your server or the network you will be doing the conversion with is able to make connections to api.mojang.com
  4. Delete your plugins/BanManager folder (You should have a backup so this is ok)
  5. Delete the v4 version and upload the v5.8 jar to your server.
  6. Start the server.
  7. Stop the server.
  8. Open the plugins/BanManager/config.yml
  9. Disable offlineAutoComplete by setting it to false.
  10. Add in your database connection details to databases.local.
  11. ENSURE THE TABLE NAMES ARE DIFFERENT FROM THE v4 config AND THAT THEY DON'T ALREADY EXIST
  12. New table structure, and the UUID conversion simply reads from the old tables, so it is paramount they do not conflict.
  13. Set local.enabled to true.
  14. Start up the server (do not fill in conversion database details yet).
  15. Check your database, ensure the tables are created.
  16. Stop the server.
  17. Add in the conversion database connection details in the config.yml file, under databases.convert. Ensure it is enabled, and that ALL the tables are correct.
  18. If any tables are wrong, the conversion process will fail, or be left in a half finished state. If this happens, re-create the new tables. Unfortunately Mojang's API is rate limited, for an unknown period of time. Therefore, you should wait at least a couple of hours before retrying again.
  19. Start the server.
  20. The conversion process will begin, and will inform you of any problems it encounters.
  21. If successful, restart the server. If not, read carefully through the logs. Any names that weren't converted may not exist, or the Mojang API may have not given back any data for some unfathomable reason.
  22. If you reach the rate limit for Mojang's API, re-enable the convertor and run as many times as necessary.
  23. Report any bugs you find on the GitHub repo.