Java 8 update 20 changed the way Collections.sort works, no longer cloning a List but modifying it in-place. Now for the technical details of what this does, for those interested. Then just copy the class file you downloaded into the appropriate place in the JAR. You won't want to erase all of META-INF or the server won't launch, just deleting FORGE.DSA is enough according to DAOWAce's post below. In this case, Forge will already be in the server JAR. I have no easy fix for this at this time, because it automatically redownloads the Forge JAR after it detects modification, which is both nice and annoying depending on the situation! So do the above mentioned process to patch the JAR, and the pack should be fixed. Find the instance you want to repair, then go into jarmods. Go to your ATLauncher directory, then into instances. Follow the process of above for patching the JAR, of deleting META-INF and adding the class file into the appropriate place, and your pack should now run again.Īgain, this is slightly different, requiring you to fix per-instance like Technic. So navigate into tekkitmain, then into bin. For this example we'll use the main Tekkit. Now go into whichever pack you want to fix. For Windows this is: %appdata%\.technic\modpacks For this, first go into your packs directory.
![minecraft forge build 9.11.1.965 does not work minecraft forge build 9.11.1.965 does not work](https://static.planetminecraft.com/files/resource_media/screenshot/screenshot-1-1574181407.png)
And every time a pack is updated, you'll probably have to patch it again. Then do the same process as above, and this should fix every related pack on the launcher. The only difference is that you have to find the libraries directory inside your FTB directory instead. This is relatively identical to the above instructions. Just drop this patched version on top, and you should be good to go! You should see a CoreModManager.class in here. Now navigate your way through cpw/mods/fml/relauncher. First, go ahead and delete the META-INF directory in the root of the JAR, or you'll get a crash related to security, just like in the old JAR-modding days. But now open up the JAR in WinRAR or what ever program you use for such things. You can make a backup of the JAR if you want at this point.
![minecraft forge build 9.11.1.965 does not work minecraft forge build 9.11.1.965 does not work](https://i.ytimg.com/vi/xPXpjPy9168/maxresdefault.jpg)
And if you use OSX, then I'm sure someone else can help you find it, but I imagine that your base Minecraft directory is in your home directory somewhere as well like Linux. If you use Linux then you know your way around your home directory. (or switch 1147 for the version you're using)įor 1.7.10: %appdata%\.minecraft\libraries\net\minecraftforge\forge\1.7.10-10. On Windows, the direct route would be:įor 1.6.4: %appdata%\.minecraft\libraries\net\minecraftforge\minecraftforge\9.11.1.965įor 1.7.2: %appdata%\.minecraft\libraries\net\minecraftforge\forge\1.7.2-10. I'm going to assume you already have Forge installed into the vanilla launcher for these instructions.įrom here you need to find your way into your libraries directory for Forge. Only one file is the problem, so that's all you need:ĬoreModManager.class, for Forge #965 for Minecraft 1.6.4.ĬoreModManager.class, for Forge #1121 / #1147 for Minecraft 1.7.2ĬoreModManager.class, for Forge #1208 for Minecraft 1.7.10 But for future-proofing sake, in case someone wants to run Java 8 but a security issue is discovered at some point in the future which makes update 11 not very safe, I decided to just fix Forge. You could easily just use Java 7, or Java 8 update 11, and not be affected by this bug. But 1.6.4 and 1.7.2 are still affected, as are many versions for 1.7.10 still in use. Fortunately, later versions of Forge for 1.7.10 correct the issue. This appears to affect both Minecraft 1.6 and 1.7. So you may have heard that as of Java 8 update 20, a bug came to light in Forge which causes a crash at startup. Fortunately this post details how to fix it. The changelog can be found on Confluence.Minecraft Forge 1.7.2 stopped working with a new Java update. It is considered to be the 1.6.4 recreation of FTB Unleashed. It is the largest official FTB modpack created for 1.6.4, having 123 mods.
![minecraft forge build 9.11.1.965 does not work minecraft forge build 9.11.1.965 does not work](http://minecraftea.com/wp-content/uploads/2018/03/2018-03-13_00-1.png)
It combines technical and magical mods into one monster sized pack. Monster is a Feed The Beast and CurseForge modpack created by the FTB Team. A 1.6.4 modpack for players that want a little bit of everything.