I had an old Minecraft install on my old PC some time ago. It was a heavily modded 1.4.6 with a very developed world. I gave MC away for a while and now I'm trying to get the old version and games back (before you ask, some of the mods aren't available anymore). I'm also now on a Mac (OSX).
I've installed the new MC installer and have an unmodded 1.8.1 install. I also setup a 1.7.10 profile to test loading mods on the new installer and that's running fine.
I've setup a new 1.4.6 profile, loaded the old modified minecraft jar and it seems to find the embedded mods (from the ForgeModLoader-client-0.log):
2014-12-15 18:28:44 [FINE] [ForgeModLoader] mcp(Minecraft Coder Pack:7.25): minecraft.jar (NO VALID CERTIFICATE FOUND)
2014-12-15 18:28:44 [FINE] [ForgeModLoader] FML(Forge Mod Loader:4.6.12.511): coremods (NO VALID CERTIFICATE FOUND)
2014-12-15 18:28:44 [FINE] [ForgeModLoader] Forge(Minecraft Forge:6.5.0.473): coremods (NO VALID CERTIFICATE FOUND)
BUT, the launcher/loader is not finding any of my mods.
I can see from the same log that it's finds the game directory;
2014-12-15 18:28:43 [INFO] [STDOUT] Setting gameDir to: /Users/davidedw/Library/Application Support/minecraft-1.4.6-modded
But it's looking for mods in the wrong directory;
2014-12-15 18:28:43 [FINE] [ForgeModLoader] Minecraft jar mods loaded successfully
2014-12-15 18:28:43 [INFO] [ForgeModLoader] Searching /Users/davidedw/Library/Application Support/minecraft/mods for mods
I would have expected that it would look in the gamedir for the mods folder not the default/main folder. Is this a function of the old ForgeModLoader?
The old way of modding has changed since the new launcher came out. Now modding is done exclusively by popping mods into the forge created mod folder and that's what the new launcher is going to follow. If you're running off of a real old minecraft.jar that's been patched the old way, the new launcher is not going to work with it too well. But I'd imagine you'd have issues trying to run the patched jar, and then after, modding any of the later minecraft versions like 1.7.10. I would think you'd need to keep the patched jar 1.4.7 and the new jar with the new launcher separate if you want trouble free experience. Treat it as two separate games, to be started independently.
I've found a partial solution. It seems that the old ForgeModLoader doesn't use the gameDir setting (and never will according to a post I found), it will always default to the vanilla mine craft directory. So I created a new directory for the current (e.g. 1.8.1) version, modified my 1.4.6 profile to use the vanilla directory as the gameDir (not really necessary) and put all of my old 1.4.6 mods and coremods into it. I can now access one of my old games (still working on the other).
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I've installed the new MC installer and have an unmodded 1.8.1 install. I also setup a 1.7.10 profile to test loading mods on the new installer and that's running fine.
I've setup a new 1.4.6 profile, loaded the old modified minecraft jar and it seems to find the embedded mods (from the ForgeModLoader-client-0.log):
BUT, the launcher/loader is not finding any of my mods.
I can see from the same log that it's finds the game directory;
But it's looking for mods in the wrong directory;
I would have expected that it would look in the gamedir for the mods folder not the default/main folder. Is this a function of the old ForgeModLoader?
Any ideas?
I've found a partial solution. It seems that the old ForgeModLoader doesn't use the gameDir setting (and never will according to a post I found), it will always default to the vanilla mine craft directory. So I created a new directory for the current (e.g. 1.8.1) version, modified my 1.4.6 profile to use the vanilla directory as the gameDir (not really necessary) and put all of my old 1.4.6 mods and coremods into it. I can now access one of my old games (still working on the other).