Jump to content

skwerl56767

Members
  • Posts

    4
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

skwerl56767's Achievements

Tree Puncher

Tree Puncher (2/8)

0

Reputation

  1. I'm running everything with 1.6.4 stuff, that's why I was confused and asked about it, because it makes no sense. I guess I could re-download everything again, but I doubt much would change. Thanks though. If I get a different log I'll post it.
  2. Yeah, I know, I fixed that. There are no 1.7.2 mods inside of the folder; I even re-downloaded the right versions and tried it then. I did not edit the .jar. And I didn't see anything in the crash report that I knew what to do with, which is why I posted it, because I was trying the run Minecraft 1.6.4. And no, I never said I wanted to run mods of different versions in the same Forge/Minecraft version, because I know that doesn't work. I was simply suggesting that in case of a mistake like mine, Forge could tell you the different mods' versions so you know who the outliers were and could fix it, instead of it telling you that you need to update just because one mod is newer than the others.
  3. I can't update, the average version of all of the mods I want to use is 1.6.4. I did find a mod that was actually the wrong version, but when I started everything back up it gave me this error: Not sure how to troubleshoot this one, but it sounds bizarre. And yes, I did try restarting and other versions of Forge. As a side note, is it possible so that Forge recognizes the version that each mod was built for, then creates percentages(or numbers, whichever works best) and shows them to the player when it tries to start up so they know which mods are the wrong version? When it told me I needed to update Forge, instead of telling me that one mod out of 30 others is too new, I thought it was preventing me from starting up an old version of Forge and that I had to painfully wait for every mod to *probably* update.
  4. So, I have a question. I'm trying to make a modpack, and all of the mods I want are at most version 1.6.4. Fine by me, but once I put everything together Minecraft Forge tells me that I need Forge version 10.12.1.1074, but that version is for Minecraft 1.7.2. The version of Forge I'm trying to run with this modpack is 9.11.1.953, for Minecraft 1.6.4. If I change it, Forge complains that all of the mods are out of date, obviously, because I need to run Minecraft 1.7.2 to have Forge 10.12.1.1074. But if I do nothing, it just keeps telling me over and over that the minimum version required is the wrong version I need. There is no way to override the notification. All I can do is shut Minecraft down. Is this really necessary? Is there a way to fix this, or am I stuck without my mods and forced to use the latest version? I guess the main question is, is there a way I can use the Forge version I need without having this silly issue?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.