I play in both a server and single player. For single player I used Forge to get the mods I wanted (like Zan's minimap) but that required the Forge profile based on 1.7.2. The server I use seems to be using 1.7.9, so I used my "current version" profile for it and the mods don't activate (probably because they are 1.72).
I looked at the mods folder and it is a single one, not one per version.
So, how does Minecraft identify what mods to use for what profile/version?
I noticed that the forge mod .jars seem to follow a naming convention that contains the version number. Is this a Forge convention, or is it a global naming convention that minecraft uses in order to pick the mods to activate? For example, if I were to put a 1.7.9 minimap .jar in the mods folder... would minecraft be smart enough to use the 1.7.9 in my 1.7.9 profile but use the 1.7.2 in my forge profile?
If no, how do I handle different mod versions for different profile versions?
I looked at the mods folder and it is a single one, not one per version.
So, how does Minecraft identify what mods to use for what profile/version?
I noticed that the forge mod .jars seem to follow a naming convention that contains the version number. Is this a Forge convention, or is it a global naming convention that minecraft uses in order to pick the mods to activate? For example, if I were to put a 1.7.9 minimap .jar in the mods folder... would minecraft be smart enough to use the 1.7.9 in my 1.7.9 profile but use the 1.7.2 in my forge profile?
If no, how do I handle different mod versions for different profile versions?
- Use 1.7.9 servers and mods and forget about Forge.
or
- Use Forge and be limited to servers that work with the version supported by Forge at the time.
That is disappointing. I thought Forge was a great idea, but my favorite server stays a lot more current with versions than Forge.
I might just have to drop Forge until Minecraft profiles get associated with version-based mods subfolders.. Mojang... hint, hint.