Mod version not displayed correctly on mods page
BluSpring opened this issue ยท 9 comments
On versions later than 1.12.2, the mod's version is not displayed correctly as "22.18.1" on the mods page or in the Prism Launcher mods list. This is caused by the META-INF/MANIFEST.MF file not storing the Implementation-Version, and as such the mods.toml's ${file.jarVersion} doesn't get replaced with the correct version, instead displaying 0.0NONE (or NONE on Prism Launcher).

@DonBruce64 this often causes an error in which people weren't able to join servers. This is a long-standing issue

Wonder why it only happens sometimes for some people and not for all people...?
@DonBruce64 it would be nice if you find time to return to MTS and continue bug fixing, because only those people can tell you, I never had a server nor do I join servers.
@BluSpring do you know how to get the Mainifest.mf file to generate with that value? Cause I don't create that file. That gets created by the compiler.
You need to add "Implementation-Version": project.version to the manifest attributes here:
Forge's MDK has an example showcasing this behaviour too. This needs to be added for all versions past 1.12.2.
I tried this, and ,"Implementation-Version": project.mod_version, but neither seems to do the trick?
What if you try filling out the fields like this?
https://github.com/bonsaistudi0s/Winter-Overhaul/blob/master/build.gradle#L95-L101