Forge Update JSON file.

example.json

{
  "homepage": "http://files.minecraftforge.net/maven/net/minecraftforge/forge/",
  "promos": {
    "1.8-latest": "11.14.3.1543",
    "1.8-recommended": "11.14.3.1450"
  },
  "1.8": {
    "11.14.3.1543": "fry: Fix color multiplier applied incorrectly for items.\nfry: OBJ loader: fixed another whitespace-related issue; removed unused "modifyUVs" property for now; added the "flip-v" property to switch between OpenGL-style and DirextX-style model UVs; fixed normals - they are now correct in-world, still a bit strange for the items; fixed normals a little bit for B3D models too.",
    "11.14.3.1532": "fry: Fixed normal calculation for vanilla models, fixed the grass darkening and simular issues.\nfry: More lighting fixes, flat lighting now works correctly for grass and torches."
  }
}

update.json

{
  //URL to display in ModList GUI when an update is avalible
  "homepage": "",
  "promos": {
    "{MinecraftVersion}-latest"     : "version",
    "{MinecraftVersion}-recomended" : "version"
  },
  "{MinecraftVersion}" : {
    // The changelog will be a ordered list of all entries in this this whos key is >= CURRENT_VERSION && <= TARGET version
    "version" : "Changelog seince last build",
    "version2" : "Changelog seince last build"
  }
}

Could there be a config to show latest as an update, instead of always just recommended? What's the point of latest if the GUI only ever shows rec? Or am I missing something. (see: http://assets.tterrag.com/updatetest.json and http://puu.sh/lRfIf.png)

I haven't decided how I wanted to implement latest in the GUI yet. I marked it out as the same structure Forge uses. Adding a option to use latest, or recommended would be reasonable, if it was implemented right.

If I tweak the example.json a little bit, do you think that it would work for 1.16. (I'm guessing it won't because this is 5 years old, but there is always hope in old stuff)