Alternative Mods path directory (forge/fabric)...

[TwinShards]

I made this suggestion in Fabric's discord as well
*YES I KNOW THERE IS ALREADY MOD/(VERSION) WITH FORGE BUT WHAT I'M SUGGESTING IS NOT A THING YET...
Currently looking if future Forge Loader could have a primary mod folder directory and if none present fallback to the vanilla way...

I am aware and already using The:

Quote

- Laucher → Profile → Game directory → {new path}
But doing so cause other following issues such as:
- Ressource pack
- (Optifine, and soon Sodium) Shader pack
- Server list
To all become split, and as such, if i want to use the same ressource/shader pack i must copy the entire pack and waste hard drive space. Or must copy my server list to the other directory to stay up to date with my server list that i change overtime

To work around this issue and free up hard drive space the following behavior Forge Loader could use is:

Quote

When initialling the loading of mods:
*folder name version example "1.16.1"
*Forge/Fabric personnal path "forge"
- mods → 1.16.1 → forge → (mods placed here)
If missing "forge" fallback to already in place behavior
- mods → 1.16.1 → (mods placed here)
If missing "version X" fallback to already in place behavior
- mods → (mods placed here)

If both Forge and Fabric would implement this behavior then it would make both easily compatible without the need  to make a game directory for each version.
*Understandably this would probably take some time for you guys to do so because that would require to update each forge's version

Edited August 11, 2020 by TwinShards

[diesieben07]

This is working under the assumption that it's a good idea to just dump everything in the same game directory.

It is not. You are mixing config files, game settings (potentially for incompatible versions) and most importantly worlds (these can irreparably break if you open them with the wrong version).

 

This will not be implemented.

[TwinShards]

Most recent version show the world's version in quit visible red font so unless you do not pay attention this isn't rly an issue.

Also just to be sure i was not missing something...

I do not know in which version it lost this ability but (atleast with 1.16.1) YOU CANNOT USE mods/1.16.1/*mods* anymore

So the quick F.A.Q on the "Read first" post is a bit outdated.

What i understand from your reply is it's just double edge sword, there will always be draw back if not used correctly. (RE)adding this feature has no draw back however. It's up to the user to still split every game version and waste ton of hard drive space.

Some version of minecraft has the same option.exe layout, so making let's say 1.14.4 & 1.15.2 into the same game directory wont be an issue for the game setting.

Edited August 11, 2020 by TwinShards

[diesieben07]

9 minutes ago, TwinShards said:

Most recent version show the world's version in quit visible red font so unless you do not pay attention this isn't rly an issue.

Not if you are loading a 1.15.2 modded world on 1.15.2 vanilla.

 

10 minutes ago, TwinShards said:

I do not know in which version it lost this ability but (atleast with 1.16.1) YOU CANNOT USE mods/1.16.1/*mods* anymore

1.13 is I think when it was removed.

 

10 minutes ago, TwinShards said:

So the quick F.A.Q on the "Read first" post is a bit outdated.

I know, I need to finish updating it.

[LexManos]

The ENTIRE point is that you use the game directory option in the launcher and split your configs/worlds/whatever.

It is kinda annoying that you also split your resource packs, as those typically arnt damaging if you apply the wrong version.

But it's a happy cost for the benefit of not screwing up your worlds.

[Alpvax]

If you are really desperate to share your resource packs, I believe that using symbolic links should work.