Update : The public recommended pack for Direwolf20 is 1.1.3 with a test 1.1.4 version. If you are using 1.1.2 or earlier swapping to this pack will require a world restart. If you were using the previously released private 1.1.3 pack with the code " iwanttorestartmyworld" you world should swap to the new public 1.1.3 just fine. (baring acts of aliens, computer derps, java derps or other unforeseen difficulties) If you want to keep a 1.1.2 or earlier world you will need to use the private pack code "DW20"to access the older versions. Those versions of the pack will not be updated, upgraded or changed. If you stay on 1.1.2 or earlier the only way to fix bugs is to manually update mods yourself or convert to the 1.1.3 public pack knowing you will more then likely need to restart your world. Spoiler Update: DW20 is available for testing on the launcher under the private pack code Iwanttorestartmyworld , Using this pack before a tool is released to convert worlds will require a world reset. This pack brings DW20 ID's in line with Unleashed ID's. DW20 and Unleashed now use Master Configs. This means they have configs for all the mods in Unleashed ,Unhinged and DW20. You should be able to take a mod from Unhinged or DW20 and put it in Unleashed etc. Unhinged does not use the Master configs, you will not be able to put a mod from Unleashed or DW20 into Unhinged and have it work. Please post any bugs we need to look at in the bug report thread. Spoiler Update: Unleashed 1.1.3 is now the recommended version. DW20 1.1.3 is still up for testing as we are waiting on a bug fix. Once DW20 1.1.3 is pushed to recommended world ID mismatches will occur with worlds created with 1.1.2 . Future versions of DW20 will work off the id's used for 1.1.3. So as I am sure a lot of people have realised now. There are problems with the Direwolf20 Modpack that is currently out there. There are a number of fixes we can do to resolve this, however I do not want to make this decision without consulting the community. First Let me try and explain how this has happened. So initially the aim is that configs from Unleashed should match the configs from all our packs. This means that the configs from BoP in Unleashed should as far as ids go, match the configs of DW20. They are meant to be identical in order to help prevent mistakes like what has just happened. However, an error was made and this never happened this time. However the mistake wasn't realised until we updated the config of BoP in the unleashed pack and as always just copy it over into the DW20 pack in order to maintain this consistency. This would have been fine, except the configs were different right from the first day. So we had this. 1.1.0 DW20 I:"Holy Dirt ID"=170 I:"Holy Grass ID"=169 Ender: block.id=254 Unleashed I:"Holy Dirt ID"=254 I:"Holy Grass ID"=255 Ender:block.id=252 1.1.1 DW20 I:"Holy Dirt ID"=170 I:"Holy Grass ID"=169 Ender:block.id=254 Unleashed I:"Holy Dirt ID"=254 I:"Holy Grass ID"=255 Ender:block.id=252 1.1.2 DW20 I:"Holy Dirt ID"=254 I:"Holy Grass ID"=255 Ender:block.id=254 Unleashed I:"Holy Dirt ID"=254 I:"Holy Grass ID"=255 Enderblock.id=252 As you can see, individually both configs work on their own until you mix them as happened in 1.1.2. Then the second error was made. Normally the procedure is to turn on all the disabled mods in the launcher and then the same in the server and run both and then log into the server to check for ID conflicts. This never happened, probably because the people involved were tired and had been up all night checking configs and updating the pack etc. No matter what the reason, this leads us on to now. After doing a full check, it seems that there are more instances where the configs of the pack dont match up. These do not seem to be causing any further ID Conflicts however it means the packs have different conflicts which isnt good. On top of this it appears that 3 Mods may need to be rolled back to earlier versions due to problems with the versions we have in our packs. So where does this leave us. Essentially with 2 choices, we can do a band aid patch on the DW20 pack, fixing just the conflict and backdating the relevent mods. Or we can do a full fix and bring the packs back to where they should be. So the question then is what are the consequences. First the band Aid: This should leave most DW20 1.5 worlds mostly intact (esp if you have not been to the promised land) and even in that case, reasonably easy to repair. However then the 2 packs would be out of synch. The second is a proper repair, getting DW20 pack back to where it should be, however there would be enough changes done to IDs. that world restarts may be needed. This is a pretty important decision though and one that needs input from the affected community. On a final note. I wont be giving out names or who was involved or anything. It was a mistake, mistakes happen especially when people are tired. I also dont want to see anyone else trying to assign blame in this, it doesnt accomplish anything. What I really need here is input on which of the steps you feel we should take. Thanks Slowpoke. New Update: We have decided to go with the full fix. There is a delay currently. We have the configs set up and the new mod updates tested to load without crashing.While we finish testing we are working on finding a way to make it less likely for worlds to need resets on the DW20 pack. We are hoping to have a solution to prevent unnecessary restarts. Update : The new packs are ready for community testing however right now we are having issues uploading them to the repo (server) the launcher accesses. This is something we have no control over. When we can get them on the launcher we will.