Laser remapping still borked?
bdew opened this issue ยท 2 comments
No idea what's going on here but it looks like the laser remapping thing (#2064) is still borked.
This is what i get updating from 6.1.2 to current (as of 0b4ec5b) code.
The relevant part:
[21:44:15] [Server thread/DEBUG] [FML/]: The Block BuildCraft|Silicon:null is being remapped to BuildCraft|Silicon:laserBlock.
[21:44:15] [Server thread/DEBUG] [FML/]: Found matching ItemBlock buildcraft.core.ItemBlockBuildCraft@6dc239c7 for Block buildcraft.silicon.BlockLaser@4bde45f2 at id 415
[21:44:15] [Server thread/WARN] [FML/]: ****************************************
[21:44:15] [Server thread/WARN] [FML/]: * The object buildcraft.silicon.BlockLaser@4bde45f2 has been registered twice for the same name BuildCraft|Silicon:laserBlock.
[21:44:15] [Server thread/WARN] [FML/]: * at cpw.mods.fml.common.registry.FMLControlledNamespacedRegistry.add(FMLControlledNamespacedRegistry.java:350)
[21:44:15] [Server thread/WARN] [FML/]: * at cpw.mods.fml.common.registry.GameData.registerBlock(GameData.java:835)
[21:44:15] [Server thread/WARN] [FML/]: * at cpw.mods.fml.common.registry.GameData.processIdRematches(GameData.java:570)
[21:44:15] [Server thread/WARN] [FML/]: * at cpw.mods.fml.common.Loader.fireMissingMappingEvent(Loader.java:929)
[21:44:15] [Server thread/WARN] [FML/]: * at cpw.mods.fml.common.registry.GameData.injectWorldIDMap(GameData.java:493)
[21:44:15] [Server thread/WARN] [FML/]: * at cpw.mods.fml.common.FMLContainer.readData(FMLContainer.java:237)...
[21:44:15] [Server thread/WARN] [FML/]: ****************************************
[21:44:15] [Server thread/TRACE] [FML/]: Registry alias: BuildCraft|Silicon:null -> BuildCraft|Silicon:laserBlock
[21:46:24] [Server thread/DEBUG] [FML/]: Reverting to frozen data state.
Forge then shows that "using backup level.dat" screen and proceeds to rebuild the id map trashing the save.
The full log is here: https://dl.dropboxusercontent.com/s/zgt4d8b8ivujtz2/fml-client-latest.log
I'm going to look at this on Wednesday. Or perhaps you could, @AEnterprise?
Should be fixed by #2070 (Sorry @AEnterprise!)
Turns out that the remap was pointed towards the laser block while the original null name was actually the assembly table, thus when it remapped between incompatible items it caused a fatal error. (The assembly table has a custom item for some reason)