Repo-Mirror/HuskSync
9
0
Fork 0
mirror of https://github.com/WiIIiam278/HuskSync.git synced 2025-12-19 14:59:21 +00:00
Code Issues Releases Activity

docs: document steps to reset a server

Browse Source
This commit is contained in:
William
2025-06-25 20:31:48 +01:00
committed by GitHub
parent 2ada0497ec
commit 39ebd0dc4f
1 changed files with 14 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/Troubleshooting.md
View File

@@ -26,6 +26,19 @@ If you are hosting your [[Redis]] server on the same node as your servers, you n
### Database connection problems on Pterodactyl / Pelican
If you have more than one [[Database]] server connected to your panel, you may need to set `useSSL=true` in the parameters.
### Unable to reset my server / wipe all player data
The following steps are required to completely wipe all HuskSync data and prepare your server for a reset. HuskSync stores data in MySQL and caches it in Redis, so if you are experiencing players getting their items back when they shouldn't be it's because data wasn't cleared in one of the two.
- Turn OFF ALL Minecraft servers and proxy
- Turn OFF your Redis server completely.
- It MUST be completely offline.
- Make sure data persistence is OFF and that it does not restore state following a reboot
- Access your MySQL Database using MySQL Workbench or similar. DROP your `husksync` database, or at the very least DROP ALL husksync tables.
- Double check you have done this
- On ALL Minecraft servers, DELETE the `playerdata` and `advancement` data directories WITHIN EVERY WORLD folder
- Deleting the world folders themselves works too if you are resetting these as well.
- ONLY THEN can you finally re-start ALL servers
### Issues with player data going out of sync during a server restart
This can happen due to the way in which your server restarts. If your server uses either:
@@ -38,4 +51,4 @@ These are **not compatible** with HuskSync in most cases due to the way in which
* A cronjob to send a stop command / Power Action program stopcode, listen for the service to fully terminate, and then execute your startup command
* For manual restarts, executing `/stop` and starting your server up with the startup command is totally fine.
It's not a great idea to use a plugin to handle restarts. Plugins are only able to operate when your server is turned on and must rely on scripts which don't safely shutdown servers when restarting.
It's not a great idea to use a plugin to handle restarts. Plugins are only able to operate when your server is turned on and must rely on scripts which don't safely shutdown servers when restarting.