/archive/donations/plugins/ · last edited 15 Aug 2020 · Billing
A recent incident occurred when a critical world file was accidentally overwritten during a routine server update. This happened because the update process didn't properly check for existing backup files before replacing them, leading to the loss of several hours of player progress and custom structures. The issue was discovered when players reported missing builds and NPCs after the update was applied.
The root cause was a misconfiguration in the automated update script used by the moderators. The script was set to replace world files without first verifying if backups were in place. This was an oversight during the initial setup, and no manual checks were in place to confirm the integrity of the backups before applying changes.
As a result, the team has since implemented a new protocol that requires all automated scripts to pause and verify the presence of valid backup files before making any changes. Additionally, a new backup schedule has been introduced, ensuring that multiple copies of the world files are saved at different intervals throughout the day. This should help prevent similar incidents in the future and provide a more reliable way to restore the server if needed.
Moderators are now required to review and confirm the backup process manually before initiating any updates. This change adds an extra layer of protection and ensures that even if an automated process fails, the human oversight step can catch potential issues before they cause damage. Overall, the incident has led to a more robust and cautious approach to server maintenance.