Having a mod compatible with 1.9/1.10 without a new file.

[spazzmods]

So, if at all possible, could this be done in the same line?

 

@Mod(modid = Reference.MOD_ID, name = Reference.NAME, version = Reference.VERSION, acceptedMinecraftVersions = "[1.9.4]")

 

I tried adding a comma, a dash, even a forward slash. but none of that actually worked.

[Choonster]

Forge for 1.10.2 will load any mod that accepts Minecraft 1.9.4.

 

The doc comment of

VersionRange#createFromVersionSpec

briefly explains the version range format, the doc comment of

VersionParser

links to more detailed documentation of the format.

[spazzmods]

Let me rephrase, I'm running a 1.9.4 workspace and I'm co-writing a 1.10.2 mod. Instead of constantly changing the version to 1.9.4 because that line states 1.10.2 is required, what could I add to make it so the mod will run without changing the version?

[Choonster]

I don't quite understand your question.

 

If you want a mod to load on both 1.9.4 and 1.10.2, you can either accept only 1.9.4 (

acceptedMinecraftVersions = "[1.9.4]"

) or both 1.9.4 and 1.10.2 (

acceptedMinecraftVersions = "[1.9.4, 1.10.2]"

). Forge for 1.10.2 will automatically replace the former with the latter when it loads your mod.

 

 

[spazzmods]

  On 7/20/2016 at 5:20 AM, Choonster said:

  or both 1.9.4 and 1.10.2 (

acceptedMinecraftVersions = "[1.9.4, 1.10.2]"

).

 

That right there answers my question, I didn't know that both values needed to be inside the brackets.

[Leviathan143]

Why not update your workspace?