Started by an SCM change36128c0aada922ad2a510b00b4f0b7e0399c8cc824628c0aada922ad2a510b00b4f0b7e0399c8cc8246refs/remotes/origin/master28c0aada922ad2a510b00b4f0b7e0399c8cc824628c0aada922ad2a510b00b4f0b7e0399c8cc8246refs/remotes/origin/master28c0aada922ad2a510b00b4f0b7e0399c8cc824628c0aada922ad2a510b00b4f0b7e0399c8cc8246refs/remotes/origin/masterhttps://github.com/mcMMO-Dev/mcMMO.gitmcMMO.jarmcMMO.jartarget/mcMMO.jaroriginal-mcMMO.jaroriginal-mcMMO.jartarget/original-mcMMO.jarfalse#3617461166807mcMMO #361361falsefalse361308SUCCESS1790124554034https://popicraft.net/jenkins/job/mcMMO/361/Buildersrc/main/java/com/gmail/nossr50/database/FlatFileDatabaseManager.javasrc/test/java/com/gmail/nossr50/database/FlatFileDatabaseManagerTest.java7af1f86d31d9007157477d1f4ad934b825761f4a1789611309000https://popicraft.net/jenkins/user/127477265+cyrne1-7208127477265+cyrne1-7208127477265+cyrne1-7208@users.noreply.github.comFix FlatFile database truncation on read failure In FlatFileDatabaseManager, methods that read the database before writing (newUser, purgePowerlessUsers, purgeOldUsers, removeUser, saveUserUUID, saveUserUUIDs, and checkFileHealthAndStructure) previously continued to write or rewrite the database file even when reading encountered an IOException. This caused partial or empty contents to overwrite mcmmo.users, resulting in data loss / truncation. This change: - Guards newUser() by returning an unloaded PlayerProfile on IOException, preventing the subsequent FileWriter block from overwriting the database. - Guards purgePowerlessUsers() by returning 0 on IOException without writing. - Guards rewriteUsersFile() to return false on IOException without writing, and updates its callers (purgeOldUsers, removeUser, saveUserUUIDs) to abort early on read failure. - Guards saveUserUUID() to return false on exception without writing. - Guards checkFileHealthAndStructure() to return null on validation IOException, preventing the subsequent update block from overwriting the database. - Adds comprehensive unit tests verifying that a mid-stream read failure leaves the database file byte-for-byte identical across all operations. Signed-off-by: Cyrne1_7208 <127477265+cyrne1-7208@users.noreply.github.com> 2026-09-17 02:15:09 +00007af1f86d31d9007157477d1f4ad934b825761f4aFix FlatFile database truncation on read failureeditsrc/main/java/com/gmail/nossr50/database/FlatFileDatabaseManager.javaeditsrc/test/java/com/gmail/nossr50/database/FlatFileDatabaseManagerTest.javagithttps://popicraft.net/jenkins/user/127477265+cyrne1-7208127477265+cyrne1-7208