You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So in this commit: 6e90348 That was added into forge version 1.8.9-11.15.0.1666
Forge/FML started saving dummy block and item entry's into the level.dat.
Line 309 Of the readData method of FMLContainer.java: if (!regs.getCompoundTag(key).hasKey("dummied")) return;
Checks to see if the dummied tag is present (it is not in 1.8 worlds) if it is not, it then returns thus exiting the reading of the block/item id mappings. (aka level.dat)
This was probably meant to be a continue;.
I've build forge my self and tested the fix. The level.dat is successfully loaded when you change line 309 to if (!regs.getCompoundTag(key).hasKey("dummied")) continue;
The text was updated successfully, but these errors were encountered:
This is indeed the case, thanks for catching this. There are other parts where there are issues in the registry code. If you can come up with any other cases where things mess up let us know.
So in this commit: 6e90348 That was added into forge version 1.8.9-11.15.0.1666
Forge/FML started saving dummy block and item entry's into the level.dat.
Line 309 Of the readData method of FMLContainer.java:
if (!regs.getCompoundTag(key).hasKey("dummied")) return;
Checks to see if the dummied tag is present (it is not in 1.8 worlds) if it is not, it then returns thus exiting the reading of the block/item id mappings. (aka level.dat)
This was probably meant to be a
continue;
.I've build forge my self and tested the fix. The level.dat is successfully loaded when you change line 309 to
if (!regs.getCompoundTag(key).hasKey("dummied")) continue;
The text was updated successfully, but these errors were encountered: