-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recipes being deleted between world shutdown and world startup #170
Comments
I added some additional logging to the serialization method: @Override
public CompoundTag serializeNBT() {
CompoundTag tag = container.getRecord().serialize();
JustEnoughCalculation.logger.info("Serializing recipes to NBT: " + tag, new RuntimeException("Trace"));
return tag;
} and some additional logging to the deserialization method: @Override
public void deserializeNBT(CompoundTag nbt) {
JustEnoughCalculation.logger.info("Deserializing recipes from NBT: " + nbt, new RuntimeException("Trace"));
boolean s = LPlaceholder.state;
LPlaceholder.state = false;
container.setRecord(new RecordPlayer(nbt));
LPlaceholder.state = s;
} and got this log message after launching a singleplayer world:
It seems to indicate that there's an issue when the mod goes to read the recipe records from the
Looking at the I'm unsure whether the issue is the deserialization process that reads the recipes in the
|
I'm not sure what's causing this, but occasionally when I exit a world and then re-enter it later, recipes are deleted from the calculator's memory. For example, last night this was what my calculator recipes looked like:
When I opened my world again this is what my calculator contained:
It seems like something about exiting and re-entering the world causes the calculator to lose recipes (sometimes 100% of them), but I'm not sure what causes it. I'm utilizing ATM9 as the base modpack, but more info is below.
jecalculation-forge-1.20.1-4.0.4.jar
C:/Program Files/Java/jdk-17.0.4/bin/java.exe
.txt
extension for working hyperlinks:modlist.html.txt
debug.log
debug-1.log.gz
May look at adding some additional logging around the init code to see if I can figure out what's going wrong, but I saw #156 and wanted to provide more context for the issue. I've had this bug in the past and was hoping it would be patched by now, so hopefully this new info helps.
The text was updated successfully, but these errors were encountered: