The upgrade from beta 31 to beta 37 causes world corruption
Cisien opened this issue ยท 3 comments
The interesting part of the startup (before /fml confirm and the world ends): http://paste.cisien.com/f/b8b07b73.txt
The full log, including after /fml confirm:
http://paste.cisien.com/f/9e63b3b2.txt
I was able to "work around" this issue by removing 31, cycling the server, then adding 37. The side effect is that I lose all botania-related items/blocks.
I have an instance that can reproduce this. I can provide the instance if you need it. I'm not linking it now since the zip will contain all of the mods in use, which i don't have perms to distribute. Ping me on IRC (under this name) if you would like it.
That's interesting, I managed to update just fine, could you try without "Weee! Flowers"?
This is the reason:
[20:04:33] [Server thread/WARN] [FML]: ****************************************
[20:04:33] [Server thread/WARN] [FML]: * The object com.pam.weeeflowers.BlockPamFlower@2c65db1a has been registered twice for the same name weeeflower
s:Flower.
[20:04:33] [Server thread/WARN] [FML]: * at cpw.mods.fml.common.registry.FMLControlledNamespacedRegistry.add(FMLControlledNamespacedRegistry.java:350
)
[20:04:33] [Server thread/WARN] [FML]: * at cpw.mods.fml.common.registry.GameData.registerBlock(GameData.java:813)
[20:04:33] [Server thread/WARN] [FML]: * at cpw.mods.fml.common.registry.GameData.processIdRematches(GameData.java:559)
[20:04:33] [Server thread/WARN] [FML]: * at cpw.mods.fml.common.Loader.fireMissingMappingEvent(Loader.java:925)
[20:04:33] [Server thread/WARN] [FML]: * at cpw.mods.fml.common.registry.GameData.injectWorldIDMap(GameData.java:484)
[20:04:33] [Server thread/WARN] [FML]: * at cpw.mods.fml.common.FMLContainer.readData(FMLContainer.java:237)...
[20:04:33] [Server thread/WARN] [FML]: ****************************************
Keeping Botania in, and removing weee flowers lets me cleanly upgrade the world mappings