kaenganxt

We finally updated our own modpack to 1.7.10 (from 1.6.4) and tried to convert our world. But Forge seems to have trouble with that. It is replacing all the vanilla blocks with mod specific blocks. The Apatite block from Forestry for example is getting the id 0. So the map is getting unplayable. The log can be found here: https://gist.github.com/kaenganxt/099b98faef7f5ce0afe4 It is very long, but i already wrote out some important lines using the stone block as an example. At first, the registration seems to work: [main/TRACE] [FML/]: Registry add: minecraft:air 0 net.minecraft.block.BlockAir@1e4473dc (req. id 0) After the start of the conversion, the following line seems to be a bit weird: [server thread/WARN] [FML/]: Found unlabelled item in world save, this may cause problems. The item type net.minecraft.block.BlockStone:0 will not be present After confirming the removal of some blocks (we removed two mods), the conversion starts and here are some lines that show really wrong behaviour: At first it is registrating an ic2 block for the id 1: [server thread/TRACE] [FML/]: Registry add: IC2:fluidSuperheatedSteam 1 ic2.core.block.BlockIC2Fluid@3af7ddc (req. id 456) [server thread/INFO] [FML/]: Injected new block/item IC2:fluidSuperheatedSteam: 456 (init) -> 1 (map). And the stone is then put on the id 8: [server thread/TRACE] [FML/]: Registry add: minecraft:stone 8 net.minecraft.block.BlockStone@2192bcac (req. id 1) [server thread/INFO] [FML/]: Injected new block/item minecraft:stone: 1 (init) -> 8 (map). We are using the latest forge version. At first we had minechem installed, and all the blocks (air, stone, etc.) were minechem blocks. After removing minechem, the blocks were replaced with forestry/ic2 blocks, so the problem doesn't seem to be mod-specific. Any ideas on how to solve this problem? Thanks for your help. kaenganxt