There's a version number in 3 locations:

• the @Mod annotation
  
• the build.gradle file
  
• the mcmod.info file
  

 

I wondered, should they all be the same, real version number?

I'm already using the ${version} replacement for the mcmod.info

I've also seen mods where the @Mod version is always 1.0, or other weird combinations.

 

When I omit the version in @Mod, I get a log message saying:

Mod TeNNoX_CustomSelectionBox is missing the required element 'version' and a version.properties file could not be found. Falling back to metadata version ${version}

Does that mean I could add a version.properties file with ${version}?

 

What is the correct/best behaviour?

(Is it possible to just have the version number in build.gradle?)

So, if I understand that correctly...

 

minecraft {
    version = "1.7.10-10.13.2.1291"
    runDir = "eclipse"
    assetDir = "eclipse/assets"
    replace "{@modVersion}" "1.2.3"
}

 

Would search my source files for

"{@modVersion}"

(which it would find in my @Mod annotation) and replace it with

"1.2.3"

?

Yes.

 

Awesome.  I've been looking for just that.

I'd figured out how to specify variables in the build script (which handled the mcmod.info file) but not how to get it to fiddle the source.

 

Might be time for another Version Refactoring (e.g. aligning my version numbers to a(n even more) sensible format).

I think the notation for multiple replacements is off.

 

replace "key": "val", "key2", "val2"

 

The first key/value pair is separated by a colon, the second by a comma.  And is the

minecraft{...}

portion required, eg.

 

minecraft {
    version = "1.7.10-10.13.2.1291"
    runDir = "eclipse"
    assetDir = "eclipse/assets"
    minecraft { replace "key": "val", "key2", "val2" }
}

 

Or is it referring to the already-existent minecraft{...} block?

Which means my first code block is also wrong. 

replace "{@modVersion}" "1.2.3"

should be

replace "{@modVersion}", "1.2.3"

(note the comma).

 

Thanks much.