Removing reliquary and loading a world causes mod blocks and items to be scrambled

[Scorch-Mechanic]

An error that is apparently related to the ghost of the lilypad of fertility.

This message shows up in the console when the game is loaded with reliquary installed:
[01:16:08 INFO]: Client> [01:16:08] [Client thread/WARN] [FML]: **************************************** [01:16:08 INFO]: Client> [01:16:08] [Client thread/WARN] [FML]: * Block <-> ItemBlock name mismatch, block name minecraft:air, item name xreliquary:lilypad [01:16:08 INFO]: Client> [01:16:08] [Client thread/WARN] [FML]: * at cpw.mods.fml.common.registry.GameData.verifyItemBlockName(GameData.java:909) [01:16:08 INFO]: Client> [01:16:08] [Client thread/WARN] [FML]: * at cpw.mods.fml.common.registry.GameData.registerItem(GameData.java:777) [01:16:08 INFO]: Client> [01:16:08] [Client thread/WARN] [FML]: * at cpw.mods.fml.common.registry.GameData.registerItem(GameData.java:740) [01:16:08 INFO]: Client> [01:16:08] [Client thread/WARN] [FML]: * at cpw.mods.fml.common.registry.GameRegistry.registerBlock(GameRegistry.java:215) [01:16:08 INFO]: Client> [01:16:08] [Client thread/WARN] [FML]: * at cpw.mods.fml.common.registry.GameRegistry.registerBlock(GameRegistry.java:171) [01:16:08 INFO]: Client> [01:16:08] [Client thread/WARN] [FML]: * at xreliquary.init.ContentHandler.checkAndRegister(ContentHandler.java:49)... [01:16:08 INFO]: Client> [01:16:08] [Client thread/WARN] [FML]: ****************************************

This message shows up in the console when I attempt to load a world that I had previously used with reliquary, after removing reliquary:
[01:08:56 INFO]: Client> [01:08:56] [Server thread/ERROR] [FML]: This world contains block and item mappings that may cause world breakage [01:08:56 INFO]: Client> java.lang.IllegalStateException: Registry entry for block net.minecraft.block.BlockAir@4f186450, id 0, name minecraft:air, marked as dangling. [01:08:56 INFO]: Client> at cpw.mods.fml.common.registry.FMLControlledNamespacedRegistry.validateContent(FMLControlledNamespacedRegistry.java:67) [01:08:56 INFO]: Client> at cpw.mods.fml.common.registry.GameData.testConsistency(GameData.java:928) [01:08:56 INFO]: Client> at cpw.mods.fml.common.registry.GameData.injectWorldIDMap(GameData.java:527) [01:08:56 INFO]: Client> at cpw.mods.fml.common.FMLContainer.readData(FMLContainer.java:237) [01:08:56 INFO]: Client> at cpw.mods.fml.common.FMLCommonHandler.handleWorldDataLoad(FMLCommonHandler.java:402) [01:08:56 INFO]: Client> at net.minecraft.world.storage.SaveHandler.func_75757_d(SaveHandler.java:122) [01:08:56 INFO]: Client> at net.minecraft.world.World.<init>(World.java:218) [01:08:56 INFO]: Client> at net.minecraft.world.WorldServer.<init>(WorldServer.java:96) [01:08:56 INFO]: Client> at net.minecraft.server.integrated.IntegratedServer.func_71247_a(IntegratedServer.java:62) [01:08:56 INFO]: Client> at net.minecraft.server.integrated.IntegratedServer.func_71197_b(IntegratedServer.java:92) [01:08:56 INFO]: Client> at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:374) [01:08:56 INFO]: Client> at net.minecraft.server.MinecraftServer$2.run(MinecraftServer.java:669)

Yes the timestamps are mismatched but that doesn't matter. The same error messages show up every time. The results of loading are indeed "world breakage". All mod items and blocks are completely scrambled, rendering the world firmly broken.

[TrainerGuy22]

I believe this issue is in FML/Forge, not our code. Needs verifying though, I'll look into it.

[Peach774]

I just got this after updating. messed up my whole world. Mine happened when updating from Build 103 to Build 104. Broke everything. Definitley a reliquary issue.

[TrainerGuy22]

That was due to bug #44, I believe. The item block for the Lilypad wasn't doing it's job right, so it made the Lilypad move to block 0, hence the error. The Lilypad was restored in build 104. That was probably the problem. Should be good from now on.

I'm really sorry about your world, but there was a clear warning about using the source builds. Please tell me if you experience any more of this moving to further builds, and I'll try to get it fixed ASAP.

Also, thanks for taking the time to report all these bugs for Reliquary, it's really appreciated.