[SOLVED][1.9.4/1.10.2] Issues with restricting versions of Minecraft to my mods

[NovaViper]

Hey, I'm trying to restrict my mods' accepted minecraft versions. For some reason I have the mod set to 1.9.4, but it still activates in 1.10.2. I'm trying to figure out how to make the two versions restricted from running each other

 

 

Here is the Source code:

Main Library Mod: https://github.com/NovaViper/Cryogenic-Library

New Mod using the Library Mod: https://github.com/NovaViper/TetraCraft

[loordgek]

that is done by forge https://github.com/MinecraftForge/MinecraftForge/blob/373fa8f7a3d905a8878e851e0553f561579bd237/src/main/java/net/minecraftforge/fml/common/FMLModContainer.java#L226-L232

[NovaViper]

that is done by forge https://github.com/MinecraftForge/MinecraftForge/blob/373fa8f7a3d905a8878e851e0553f561579bd237/src/main/java/net/minecraftforge/fml/common/FMLModContainer.java#L226-L232

 

Oh ok, so that means that 1.9.4 is compatible with 1.10.2, right?

[Ernio]

Generally saying - yes. Apparently there are plenty of mods that work on both versions, but I doubt all can be guaranteed.

[NovaViper]

Ah ok. I was just wondering why it wasn't saying that it only works with 1.9.4 and vice versa with 1.10.2

[LexManos]

1.9.4, 1.10, and 1.10.2 all are 99.99% compatible with eachother so we have decided to force load the ones that state they are specfically for that version on the others.

This is the power of reobfusicating to SRG names.

I work hard to make this work.

 

If you MUST keep your version to a specific version, then you can set your compatiblity to something that ISNT the default [MCVER]

So, [MCVER,MCVER] would work to hardcode it to one version.