Can I automate versioning?

[riderj]

Do I have to change the build.gradle file every time to reflect the version change? If so what's the point of the @Mod annotation? I'm still new at modding minecraft using forge, so please give me some slack.

 

 

Side Question: Why is the recommended build, 1.6.4-Recommended 9.11.1.965 1.6.4, not ForgeGradle? Though .964 is

[luacs1998]

Because 965 was a build to fix some problems with 953. Gradle builds also do not have the Modloader compatibility layer.

[riderj]

Because 965 was a build to fix some problems with 953. Gradle builds also do not have the Modloader compatibility layer.

 

How big of a problem is the incompatibility with the Modloader? Will it hinder my mod development?

[luacs1998]

No.

 

And for the main topic: I don't know how it's done, but there is a way to put the version into your @mod from the build.gradle.

[GotoLink]

You can have "auto versioning".

I believe that is what the default build.gradle shipped with Forge tries to do with the mcmod.info:

processResources
{
    // replace stuff in mcmod.info, nothing else
    from(sourceSets.main.resources.srcDirs) {
        include 'mcmod/info'
                
        // replace version and mcversion
        expand 'version':project.version, 'mcversion':project.minecraft.version
    }

 

So you can replace the values in files on building with

expand

. Or use an Ant Filter.

And you can set a property value with

gradle build -Pversion=NewVersion

[riderj]

None of the solutions worked for me, probably due to my incompetence, so I guess I'll manually do it until I have time to read up on gradle and learn about it.