Skip to content

Commit 24f7cc0

Browse files
authored
[Savestates] Fix index being set to 0 when using fullplay (#257)
This is a temporary fix until the indexing system is reworked... My plan is to use the indexing system from LoTAS-Light at some point, where this issue is fixed... Sets the index to the latest index instead of 0 when savestate 0 is loaded. Not ideal, but this minimizes the chance of accidentally overwriting something.
2 parents d14da99 + a6d3cc7 commit 24f7cc0

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

src/main/java/com/minecrafttas/tasmod/savestates/SavestateHandlerServer.java

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -239,7 +239,7 @@ public void saveState(int savestateIndex, boolean tickrate0, boolean changeIndex
239239
server.getPlayerList().sendMessage(new TextComponentString(TextFormatting.GREEN + "Savestate " + indexToSave + " saved"));
240240

241241
try {
242-
// close GuiSavestateScreen
242+
// Close GuiSavestateScreen
243243
TASmod.server.sendToAll(new TASmodBufferBuilder(TASmodPackets.CLEAR_SCREEN));
244244
} catch (Exception e) {
245245
e.printStackTrace();
@@ -700,8 +700,10 @@ public void loadCurrentIndexFromFile() {
700700
file.load(savestateDat);
701701

702702
index = Integer.parseInt(file.get(DataValues.INDEX));
703-
704-
setCurrentIndex(index);
703+
if (index != 0)
704+
setCurrentIndex(index);
705+
else
706+
setCurrentIndex(latestIndex);
705707
}
706708
}
707709

0 commit comments

Comments
 (0)