How do we handle different versions of the same mod?

williambl commented 7 years ago

Currently, for Forge, we just have different versions using their own JSONs. But this seems a bit annoying - perhaps we could instead have a generic JSON, such as this:

{
    "Name":"MinecraftForge",
    "Link":"http://files.minecraftforge.net/maven/net/minecraftforge/forge/<mc-version>-<version>/forge-<mc-version>-<version>-installer.jar",
    "Author":"github.com/MinecraftForge/",
    "Desc":" Modifications to the Minecraft base files to assist in compatibility between mods.",
    "License":"MinecraftForgePublicLicence",
    "Requirements":[],
    "Incompatibilities":[],
    "Recommended":[],
    "Type":"Installer",
    "Unstable":"false",
    "InstallerName":"Forgeinstaller"
}

and then have other JSONs which just look like this:

{
    "Version":"13.20.1.2386",
    "MCVersion":["1.11.2"]

}

How does that sound to everyone?

lewisakura commented 7 years ago

wew just remembered that this was a thing.

Yeah, seems to be a nice format.

williambl commented 7 years ago

OK, I'm working on it in the new-syntax branch.

williambl commented 7 years ago

I'm going to change it again so that each version has its own link instead of formatting an existing link - this is to make links to curse, which uses seemingly random numbers to differentiate versions, compatible.

Valiec commented 5 years ago

Curse has different dependencies for different versions, that'll need to be added too (I'll handle it).

mcdelta-project / deltamc-archive

How do we handle different versions of the same mod? #5