Forge throws WARNs about versioning/metadata
C0rn3j opened this issue ยท 6 comments
[11:46:34] [main/WARN] [FML]: The coremod lain.mods.skins.asm.Plugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft
[22:19:31] [main/WARN] [offlineskins]: Mod offlineskins is missing the required element 'version' and a version.properties file could not be found. Falling back to metadata version 1.12.2-v2
Apparently these things will be enforced in Forge 1.13 so you may as well fix it now to avoid having it annoy you later ^^
"MCVersion annotation forge documentation" <- googling this brought me here
https://mcforge.readthedocs.io/en/latest/gettingstarted/structuring/
which seems like what you need
also this may be of interest
https://github.com/BuildCraft/BuildCraft/blob/8.0.x/build.gradle#L171
https://github.com/BuildCraft/BuildCraft/blob/8.0.x/build.gradle#L74
I did try to add one for my mods before. But i couldn't find any information about it.
Could you point me to a proper documentation?
This is actually a different thing to what i thought you were referring. I thought you were talking about version.properties.
About MCVersion annotation in coremod, I need it to be missing/empty to make a single coremod load on multiple minecraft versions. (If a version is specified in this annotation, the coremod won't load on any other minecraft versions even if they are subversions)
About missing element 'version', it was purposely left undefined to make use of mcmod.info's metadata, the warning can be safely ignored.
If i put a version string in that, forge will try to match it with current minecraft version, if they are exactly same(1.12 and 1.12.2 does not match in this case), then forge will load the coremod, otherwise no. And a version range doesn't work in that.
I need it to be missing/empty to make a single coremod load on multiple minecraft versions.
How about just throwing 1.12 all the way to 1.12.5 to it? Would still work on all 1.12.x versions and would get rid of the annoying warning I assume. Or perhaps I'm misunderstanding this.
This is actually a different thing to what i thought you were referring. I thought you were talking about version.properties.
There seem to be 2 errors, I accidentally created issue with only one of them and edited it later.