#327 Crash

  • * in TV presenter voice
    This is Blaster's "Minecraft Boot up" tutorial


    1. Remove all mods except Forge and test. If you can load Forge without any problems, move to step 2
    2. Re install your core mods. while you are testing, NEI is very helpful as it can show you any broken recepies and help with ID conflicts
    3. Install in mods that go into the mods folder one at a time, in order to find out the mod that is causing the problem


    Once you find the problematic mod, the first thing to do is, once again, remove all the mods except the problematic on. to find out if it is a clash with the mods.
    Then, UPDATE FORGE (this is your problem), if problem persists. Downgrade to the recommended version of the Forge forums. if the problem still exists, downgrade to the recommended forge version on the mod in question's forum. If you still have the problem, complain to the mod author/s to get it fixed and if it sais that it's fixed, but you are still having the problem. You should probably stop making a mod pack and play a custom one.


    This has been Blaster's "Minecraft Boot up" tutorial. For all your bug fixing need.
    */ in tv presenter voice


    Seriously though, updating Forge should be your first step. I have had this problem several times while I have been working (slowly) on the Shrine Runner mod pack.

  • I'm not an idiot. I have done that. If you cared enough to read my crash log you would see it had nothing to do with items ID's just the api. The load order of mods is stopping it. I dont know how to change the load order, please help.

  • you have an other mod installed that isn't updated yet to the new IC2 API