challenger1_

My modpack seems to be having problems....

8 posts in this topic

Hello, So a couple of days ago, I decided it was finally time to update my modpack from 1.7.10 to 1.10.2. So, having created modpacks before and having updated to newer versions several times in the past, I did the same thing that I normally did to update my modpack - deleted all the mods and forge and redownloaded the newer version of them. Unsurprisingly, things did not all work perfectly the first time. But what was surprising was that pretty much nothing worked. When I had all my mods that I wanted and then launched the pack by replacing another pack's mods (obviously mc version 1.10.2) with my own mods, the technic launcher reopened as soon as it closed. There was no crash report, but there was some info in the latest log here. So I thought that was weird, but I figured I should try adding one mod at a time and see if it was a problem with certain mods. There were a couple of mods that would work, but pretty much anytime I got more than three mods, I always got a crash report that was something like this. Also, occasionally some of the mods would say that they needed another mod for them to work, but then wouldn't list another mod like here. Considering the number of mods that seem to have this problem, it made me wonder if it was something wrong with my minecraft forge. So I redownloaded forge but nothing changed. Confused at this point, I decided to try the unupdated version of my modpack, which worked perfectly fine. I then exchanged the mods from the updated and the un-updated, neither of which worked (unsurprisingly since they are different mc versions). Desperate for something to work, I redownloaded all of my mods, restarted from scratch and used Luke's modpack making guide from the very beginning, and even downloaded another modpack of the same version and tried using their mods (which worked in their modpack), but nothing changed the ultimate failure of my updated modpack. So, I want to know what in the world happened? Did I do something wrong? Did something about making modpacks change? Why does it seem like my modpack is the only one being dumb like this? I am continuing to run tests on just trying one mod at a time, but it seems random as to whether the game will crash, need another mod, or just quit as soon as it starts. Thanks a bunch to all who respond!

Share this post


Link to post
Share on other sites

Posted (edited)

Had a quick look at your first log you linked and saw this:  OpenBlocks-1.7.10-1.6.jar

Make sure ALL your mods are 1.10.2

provide a dropbox link to your modpack if you still need help

Edited by AetherPirate

Share this post


Link to post
Share on other sites

Here is a copy of the modpack, note that this is not the modpack I was testing with, but a copy of the bin, mods, coremods, and config folder. None of the other folders matter to my knowledge. 

But in response to the 1.7.10 mod, I don't know where I first heard this, but I thought that you were still able to put in mods of previous versions of minecraft in with a later version of minecraft (i.e. a 1.7.10 mod into 1.10.2 minecraft). Is this not true? Or is there some legitimacy to this, it just depends on the circumstances? 

Share this post


Link to post
Share on other sites

Ok, so i added in IC2, but COFHCore still said it needs another mod, and upon removing it and its mods, Galacticraft said it needs another mod, and upon removing it and its mods, IchunUtil said the same thing, then finally, I got something. It says Mantle needs Forge 12.18.1.2011 or above, and the fml-client-latest.log said similar:

"The mod mantle (Mantle) requires mod versions [Forge@[12.18.1.2011,)] to be available
[10:25:40] [Client thread/ERROR] [FML/]: net.minecraftforge.fml.common.MissingModsException: Mod mantle (Mantle) requires [Forge@[12.18.1.2011,)]"

When I downloaded Forge, I downloaded  version 12.18.3.2316

So now I will try downloading 12.18.1.2001 and see what happens

 

Share this post


Link to post
Share on other sites

So of course, I tried replacing the modpack.jar with the older version of forge, and now Tree Chopper says it needs a higher version of forge. So I got the slightly higher version, and the pack crashed. Here is the report, but the main thing is that it said that Progressive Automation does not have a class definition, so I tried downloading a different version of the mod and then it crashed again, but this time it was due to ExtraUtilities2 as seen here. So I again got an older version to try again and then it crashed, creating a similar crash report as the second one. This caused me to remove extrautilities. thenn..... IT WORKED!!!!! I started adding mods back one at a time, but the first one i added, galacticraft, also needed another mod. 

Upon further inspection of the fml-client-latest log i found this: 
"[11:07:55] [Client thread/ERROR] [FML/]: The mod galacticraftcore (Galacticraft Core) requires mod versions [Forge@[12.18.2.2171,)] to be available
[11:07:55] [Client thread/ERROR] [FML/]: net.minecraftforge.fml.common.MissingModsException: Mod galacticraftcore (Galacticraft Core) requires [Forge@[12.18.2.2171,)]"

So now I will individually add all the mods back and see if they are just needing a different version of Forge

Share this post


Link to post
Share on other sites

So, each mod that "needed another mod" actually just required a different version of forge, so I incrementally upgraded forge starting with the oldest version required and working my way up to the newest version required. Now it works with all the mods. So apparently I don't know why this was necessary, but apparently I just needed to use a little magic.

Share this post


Link to post
Share on other sites
23 minutes ago, challenger1_ said:

"[11:07:55] [Client thread/ERROR] [FML/]: The mod galacticraftcore (Galacticraft Core) requires mod versions [Forge@[12.18.2.2171,)] to be available

[11:07:55] [Client thread/ERROR] [FML/]: net.minecraftforge.fml.common.MissingModsException: Mod galacticraftcore (Galacticraft Core) requires [Forge@[12.18.2.2171,)]"

So now I will individually add all the mods back and see if they are just needing a different version of Forge

They usually do. Also this: FML: MCP 9.32 Powered by Forge 12.18.1.2017

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Similar Content

    • By Trigufy
      I've made a Tekkit Classic Server. I'm having trouble adding plugins. I'm aware its due to Tekkit classic is a older version of minecraft. I'd like to know how I can add these plugins or what I have to do.
    • By Mr.Redstone
      Hello fellow Modders/Programmers/Players
      I would like to know how I can Code my own mods I know a bit of Java and Think I might be able to do it but I don't know how to get started I have searched and searched the web but can't find anything   Please help.
      Signed, Mr.Redstone
    • By CookieMan833
      Hi everyone!
      First forum post, here goes.
      So I've just created my first Modpack!
      I'm having an issue where, having made it and uploaded it, I download it from Technic Launcher and start it up. Initially it goes well, Minecraft opens in 1.6.4 as I had intended. But the game doesn't actually load up with any mods, despite the fact that there are loads in the pack (well, actually not loads, maybe ten or so). I was wondering if anyone could help me fix this. I've left a link to the pack's page and a link to the download (basically so people can see what I've done and tell me where I've gone wrong lol). I've also described what I did below in case it makes any difference.
       
      Modpack: https://www.technicpack.net/modpack/to-the-moon-or-bust-copy.1067411
      Modpack location: https://www.dropbox.com/s/2rgovwj5m8qz8p8/Making the Modpack.zip?dl=1
       
       
      I created a new directory for minecraft to run in, and installed Forge Installer in it (for 1.6.4, the intended version to be played with). I also made a folder with three subfolders inside it, bin, mods, and config, which is the second link. I installed Forge Universal for 1.6.4 in the bin file and renamed it modpack.jar Next I, in turn, downloaded each mod that I wanted one by one in 1.6.4, put it in the mods folder in the Forge Game Directory, ran it, copied the config files from the Forge Game Directory to the Modpack config Subfolder, and moved the mod from the Forge Game Directory to the Modpack mods Subfolder. I repeated this with every mod I wanted until it was all done.
      After this I compressed it into a zip file and uploaded it to dropbox, and then changed the end of the dropbox sharing link to =1 not =0. I then put in the settings of the new modpack, putting the link in and selecting 1.6.4
       
      Yeah that's what happened. I'd be super grateful if anyone could help me? Obviously I'm really really new to all of this and this was my first time, so there's probably something obvious I've missed, but yeah, let me know!
       
       
      UPDATE: In the time writing this, I tried deleting the pack from my launcher and installing it again. I installed it, but for some reason the install button shows instead of the play button next to the delete modpack button. I press install again, and within seconds it just goes back to the same problem, no play, just install. Anyone able to help me out?
       
      Further update: Disregard the UPDATE - turns out I was being an idiot and I was trying to load it whilst I had it open. Still got original issue though
    • By Mr.Redstone
      Whenever I load up my modpack everything seems fine EXCEPT when i load up the game it says at the bottom left corner: Minecraft 1.11.2/${version_type} and doesn't load ANY of my 32 mods Please Help!! (I attached the latest log for the modpack.)
      latest.log 
      -- Modpack log
      https://www.dropbox.com/s/mgvty11i2zuo36z/Launcher Log.zip?dl=0 e
      -- Launcher Log
      https://www.dropbox.com/s/yn4c8s0k94r1yfn/2017-07-24.png?dl=0
      -- Screenshot of Problem