1.10/1.11 compatibility

[TheUnlocked]

Not sure if I'm posting this in the right place. Feel free to move it if not.

 

Correct me if I'm wrong, but I don't think much changed behind the scenes between 1.10 and 1.11. Seeing as there are some mods that claim to use the same jar for both versions, simple (or maybe even not simple) mods shouldn't need to be changed much or at all between 1.10 and 1.11.

 

The issue is that I can't just use the same jar for 1.10 as I use for 1.11, because forge rejects anything with the wrong version number. I assume that It doesn't reject forwards-compatible mods (using a 1.10.2 mod with 1.11.2 forge), but from my very quick tests it does reject backwards-compatible mods (using a 1.11.2 mod with 1.10.2 forge). Is there a way to resolve that issue (I'd like my 1.11.2 mod to be usable in 1.10.2 modpacks) without recreating the development environment for 1.10 forge, or do I need to re-generate my dev environment?

 

Note: I tried changing the minecraft version in build.gradle, but then it threw an error when I tried to build it, so I don't think it's that easy.

Edited April 5, 2017 by TheUnlocked

[Matryoshika]

The major thing between 1.10 & 1.11 is that ItemStacks can no longer be null in 1.11. This means that whenever you call ItemStack.EMPTY in your 1.11 code, you need to switch to null-checking & setting in 1.10.

The 1.10<->1.11 compatability is almost exclusively for those that use the CompatLayer API, made by McJty.
Because of the nature, this means a hard dependency.
 

Edited April 5, 2017 by Matryoshika

[TheUnlocked]

Oh, okay. Thanks.

[Choonster]

You can set the acceptedMinecraftVersions property of your @Mod annotation to change which versions of Minecraft are allowed to run your mod. If your mod isn't actually compatible with a Minecraft version, it will likely crash at runtime when it encounters an incompatibility.

 

Look at VersionRange.createFromVersionSpec for brief documentation of the version range format. Look at FMLModContainer#bindMetadata to see how FML replaces some specific version ranges with others (where multiple versions are compatible with each other).

Edited April 5, 2017 by Choonster