Might anyone know if the new OSX stand-alone Minecraft launcher stores files in a place other than /Library/Application Support/minecraft ?
I was wanting to play a modded single-player game and followed these steps:
1. Created a launcher profile for Minecraft 1.7.10 and hit Play.
2. Downloaded the Forge installer for the recommended release 1448 and ran it (Client install).
3. Relaunched Minecraft, found the new Forge profile, and hit Play (launched without issue, shows 3 mods loaded).
So far everything seems to be fine, however, I did noticed that within the minecraft files folder neither the configs folder nor the mods folder were automatically created. I manually created the mods folder and dropped the latest Buildcraft release into it, then restarted the game. It is not seeing the mod at all, let alone attempting to load it. I have used these steps before in the Windows environment without issue, but it isn't working out this time. Might someone have an idea of what I am doing wrong, or am missing?
Just to be clear, Minecraft with Forge is launching and I can play it, it just isn't seeing any additional mods I try to add.
And... I think I figured it out. Maybe. Well, it's working now at least.
After banging my head and raging a bit (which included the making of this thread) I went back and completely removed the /Library/Application Support/minecraft folder. Ran the stand-alone launcher and let it rebuild absolutely everything from scratch. Then went through the steps I had mentioned above, and it did create the additional configs and mods folders, and is seeing the mods I am trying to add in.
My best guess is that there was an incompatability between the older-style linux minecraft application / launcher and the new stand-alone launcher. They both use the same location to store files and libraries, and something likely got "blended" or some such. Not really sure, but it sounds like a good theory.
Might anyone know if the new OSX stand-alone Minecraft launcher stores files in a place other than /Library/Application Support/minecraft ?
I was wanting to play a modded single-player game and followed these steps:
1. Created a launcher profile for Minecraft 1.7.10 and hit Play.
2. Downloaded the Forge installer for the recommended release 1448 and ran it (Client install).
3. Relaunched Minecraft, found the new Forge profile, and hit Play (launched without issue, shows 3 mods loaded).
So far everything seems to be fine, however, I did noticed that within the minecraft files folder neither the configs folder nor the mods folder were automatically created. I manually created the mods folder and dropped the latest Buildcraft release into it, then restarted the game. It is not seeing the mod at all, let alone attempting to load it. I have used these steps before in the Windows environment without issue, but it isn't working out this time. Might someone have an idea of what I am doing wrong, or am missing?
Just to be clear, Minecraft with Forge is launching and I can play it, it just isn't seeing any additional mods I try to add.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [ RESOLVED ] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
And... I think I figured it out. Maybe. Well, it's working now at least.
After banging my head and raging a bit (which included the making of this thread) I went back and completely removed the /Library/Application Support/minecraft folder. Ran the stand-alone launcher and let it rebuild absolutely everything from scratch. Then went through the steps I had mentioned above, and it did create the additional configs and mods folders, and is seeing the mods I am trying to add in.
My best guess is that there was an incompatability between the older-style linux minecraft application / launcher and the new stand-alone launcher. They both use the same location to store files and libraries, and something likely got "blended" or some such. Not really sure, but it sounds like a good theory.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [ RESOLVED ] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .