The mcmod.info file is shipped with the mod jar and includes metadata for the use for tools. One example is the MultiMC launcher:

Unfortunately, Draconic Evolution's mcmod.info is disabled at the moment, and Brandons Core's file is still from the example project, listing it as "Example Mod" as can be seen in the above screenshot.

I dont use the mcmod.info instead i specify this information at startup like so https://github.com/brandon3055/Draconic-Evolution/blob/master/src/main/java/com/brandon3055/draconicevolution/DraconicEvolution.java#L52-L60
The reason i do it like this is it means i dont have to update it every time i release a new version.

And i guess i just completely forgot about that in BrandonsCore.

If i ever get around to figuring out custom build scripts i will fix this.

The reason i do it like this is it means i dont have to update it every time i release a new version.

You don't have to update it every time. ForgeGradle takes care of that. You just have to fill in the file once. There is substitution for version numbers. The file gets automatically included in your jar with gradle build.

Here's an example:

[
{
  "modid": "DraconicEvolution",
  "name": "DraconicEvolution",
  "description": "This is a mod originally made for the Tolkiencraft mod pack",
  "version": "${version}",
  "mcversion": "${mcversion}",
  "url": "http://www.tolkiencraft.com/draconic-evolution/",
  "updateUrl": "",
  "authorList": ["brandon3055"],
  "credits": "",
  "logoFile": "banner.png",
  "screenshots": [],
  "dependencies": []
}
]

The Draconic Evolution gradle build script already includes the necessary parts to have a mcmod.info file automatically included and updated with the correct version infomation.