Mods/Version - Forge not detecting

[jonathanpecany]

So I am having trouble with this feature in the new 1.15.2 version. Before I could store the mods in the version it belongs to and be able to run it like a mod for 1.10 goes in the folder 1.10 in the mods folder and mods for like 1.12.2 in their correct version folder and it works but for 1.15.2 if I put it in the folder it doesn't detect it. This is really irritating when going back to like 1.12.2 and I have to move the mods somewhere else. Can you explain as to why this is or if this is just a bug of some sort? I do hope I have this in the right category.

[Ugdhar]

This feature was removed as the launcher installations are the preferred method of separating mods for different versions.

[jonathanpecany]

  On 6/20/2020 at 9:51 PM, Ugdhar said:

This feature was removed as the launcher installations are the preferred method of separating mods for different versions.

Expand  

That's stupid, really stupid in my opinion. Now I have to move the mods to a different version now just to play a lower version like 1.12.2, I don't like that, I really don't like that. Especially when minecarft versions become higher, it is going to get too confusion. What minecraft version did they remove the feature? Just curious as the last version I played that was modded was 1.12.2.

[Ugdhar]

I am not completely sure to be honest, I've always kept my installations separate to avoid potential world corruption, so that wasn't a feature I myself used, sorry!

[jonathanpecany]

  On 6/20/2020 at 9:59 PM, Ugdhar said:

I am not completely sure to be honest, I've always kept my installations separate to avoid potential world corruption, so that wasn't a feature I myself used, sorry!

Expand  

Okay than, thanks anyway for at least answering. I was sure hoping it could of been a bug.

 

  On 6/20/2020 at 9:59 PM, diesieben07 said:

Make separate installations in the launcher and choose a separate game directory for each. Voila.

Expand  

How do you do that as I actually never did that, I always used folders.
Also, your lucky number must be number 7, isn't it?

[jonathanpecany]

  On 6/20/2020 at 10:07 PM, diesieben07 said:

Expand  

Before Test:

Oh, never really thought of that. I still don't like it. I'll try that and report back.

 

After Test:

After testing it, I think you might be confused now as it didn't work, just created the whole minecraft file service in the folder.

Directory 1 = %appdata%/.minecraft/mods/1.12.2 - When placing mods for minecraft version 1.12.2 in this directory it works.

Directory 2 = %appdata%/.minecraft/mods/1.7.10 - When placing the mods with version 1.7.10 in this folder, it works when still having the 1.12.2 mods in Directory 1.

Directory 3 = %appdata%/.minecraft/mods/1.15.2 - Now when I place the 1.15.2 mods in here, it doesn't seem to like to find them in this specific folder, I have to place them in the %appdata%/.minecraft/mods directory for it to work. I even tried 1.15 to see if it works but no.

Hopefully this clears things out more. 

 

Unless you think you know what I meant and said to add them in different directories, if that is the case, worst feature ever and too frustration just to do that for every minecraft version. That will take too long, most players will just wanna play and not set all of this up. But this opinion is towards if you know what I meant.

[jonathanpecany]

  On 6/20/2020 at 10:23 PM, diesieben07 said:

The directory you specify there will become your "new .minecraft". It will be where the saves, mods, configs, etc. directories go.

Expand  

Okay, I think I know what you mean but I don't like the idea because with the previous saves and configs and stuff but I understand, I think.

 

Thanks

Edited June 20, 2020 by jonathanpecany

[DaemonUmbra]

The idea is that you shouldn't be carrying saves across packs, as this risks opening the save with the wrong pack or even vanilla (which, unlike Forge, doesn't have a mechanism to detect, warn the user about, and preserve what it sees as invalid data).

[jonathanpecany]

  On 6/21/2020 at 3:48 AM, DaemonUmbra said:

The idea is that you shouldn't be carrying saves across packs, as this risks opening the save with the wrong pack or even vanilla (which, unlike Forge, doesn't have a mechanism to detect, warn the user about, and preserve what it sees as invalid data).

Expand  

That isn't what I was talking about.

[DaemonUmbra]

Then I don't know what you were saying, it sounded to me like you were complaining about not having all your saves and configs in once place anymore

[jonathanpecany]

  On 6/21/2020 at 4:14 PM, DaemonUmbra said:

Then I don't know what you were saying, it sounded to me like you were complaining about not having all your saves and configs in once place anymore

Expand  

I already got my answer is what I am saying thereby don't really need further response. Plus don't know what you are saying really. Changing directory will add in new folders that the .minecraft folder has and thereby in a newer version of minecraft I'll have to move the save file which in my opinion is not safe as some files of mind are over 1 GBs which is using mods and take forever but I could changed the directory to that directory but than I would have to move mods around which includes lots of creating of folders and deleting to not be confused with it. It is too much work, too much possibilities and those two things added will cause confusion time wasted and more. Like to also mention thinking as well as some children, or maybe most children use mods and they probably used my method and hate it as well.

 

But in shorter words, not user-friendly.