Mods folder for different versions

[Lucas8x]

wanted to know if it is possible to have different folder for different versions of minecraft

 

example

 

Minecraft Forge 1.6.2 uses 1.6.2 mods folder

and

Minecraft Forge 1.5.2 uses 1.5.2 mods folder

[Lethman427]

Yessir. just make a folder inside the mods folder and name it after the version. Example

 

.minecraft

    - mods

        -1.6.2

            -Foo

            -Bar

        -1.5.2

            -Blah

            -ModName

[Lucas8x]

  On 7/26/2013 at 8:01 PM, Lethman427 said:

Yessir. just make a folder inside the mods folder and name it after the version. Example

 

.minecraft

    - mods

        -1.6.2

            -Foo

            -Bar

        -1.5.2

            -Blah

            -ModName

I tried but did not work

[Lethman427]

Hmm, that's odd. Are you running the latest version of forge?

[Lucas8x]

  On 7/26/2013 at 9:42 PM, Lethman427 said:

Hmm, that's odd. Are you running the latest version of forge?

yes I am

 

1.5.2-7-8.1.737

and

1.6.2-9.10.0.789

[LexManos]

Profiles have a gamedir option for a reason use it.

[Vyrasa]

  On 7/27/2013 at 2:03 AM, LexManos said:

Profiles have a gamedir option for a reason use it.

Forge for MC152 (1.5.2-7.8.1.738) doesn't seem to adhere to the gamedir option, as far as I can tell.  It expects the Forge-related folders (mods/coremods, config, lib, etc) to be in %APPDATA%\.minecraft as with the old launcher.

 

Is this something that would need to change in Forge for MC152, or am I just not setting up the profile correctly?

    "Mod52_Seek": {
      "name": "Mod52_Seek",
      "gameDir": "C:\\Games\\Minecraft\\Mod52_Seek",
      "lastVersionId": "1.5.2.forge",
      "javaArgs": "-Xincgc -Xmx1G",
      "playerUUID": (censored),
      "useHopperCrashService": false,
      "launcherVisibilityOnGameClose": "keep the launcher open"
    }

 

With the Forge'd Minecraft version using the default launch parameters,

"minecraftArguments": "${auth_player_name} ${auth_session} --gameDir ${game_directory} --assetsDir ${game_assets}",

[Vyrasa]

I found a crude workaround that appears to work.  If there's a better way to do this, I'd love to know it, but in the meantime:

 

In the Profile, add to the JVM arguments

-Dminecraft.applet.TargetDirectory=<dir>

where <dir> is your desired equivalent to %APPDATA%\.minecraft .

 

For example, if you use

-Dminecraft.applet.TargetDirectory=c:\Games\Minecraft\MC152_Clouds

Then the Mods folder will be at

c:\Games\Minecraft\MC152_Clouds\Mods\

(and config, coremods, etc will be in c:\Games\Minecraft\MC152_Clouds too)

 

Note that this will override the profile's gameDir setting, so the saves directory and vanilla configuration files will be moved as well.

 

(this was based on another, tangential LexManos post pointing out the JVM option, and some hunting in the Forge source for how it acquired its base directory)

[LexManos]

Launching the game for 1.5.2 needs to go through the LegacyLauncher so make sure you copy 1.5.2's version folder not 1.6's

 

I tested last night and it worked fine iirc