From a6d3cc7dbf408d5ae914281f3c58cec4e7760cd7 Mon Sep 17 00:00:00 2001 From: Scribble Date: Sat, 19 Jul 2025 19:57:56 +0200 Subject: [PATCH] [Savestates] Fixed index being set to 0 when using fullplay A temporary fix that just sets the index to the latest index, this is not entirely correct. But this at least minimizes the chance that you accidentally overwrite something. Fixing this requires a bit of a indexing redesign --- .../tasmod/savestates/SavestateHandlerServer.java | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/src/main/java/com/minecrafttas/tasmod/savestates/SavestateHandlerServer.java b/src/main/java/com/minecrafttas/tasmod/savestates/SavestateHandlerServer.java index 05f91369..6ba4b3e7 100644 --- a/src/main/java/com/minecrafttas/tasmod/savestates/SavestateHandlerServer.java +++ b/src/main/java/com/minecrafttas/tasmod/savestates/SavestateHandlerServer.java @@ -239,7 +239,7 @@ public void saveState(int savestateIndex, boolean tickrate0, boolean changeIndex server.getPlayerList().sendMessage(new TextComponentString(TextFormatting.GREEN + "Savestate " + indexToSave + " saved")); try { - // close GuiSavestateScreen + // Close GuiSavestateScreen TASmod.server.sendToAll(new TASmodBufferBuilder(TASmodPackets.CLEAR_SCREEN)); } catch (Exception e) { e.printStackTrace(); @@ -700,8 +700,10 @@ public void loadCurrentIndexFromFile() { file.load(savestateDat); index = Integer.parseInt(file.get(DataValues.INDEX)); - - setCurrentIndex(index); + if (index != 0) + setCurrentIndex(index); + else + setCurrentIndex(latestIndex); } }