Mod info Manifest

[RX14]

We should have a manifest file for each mod, which allows external tools such as MultiMC to load metadata about the mod without reading class files.

This metadata should be passed on to forge etc. too, because there is currently no way to add a mod logo for example.

I think should encode this in META-INF/MANIFEST.MF, with NovaGradle encoding the data from the build file:

nova {
    mod {
        version = "1.0.1"
        logofile = "mod.jpg"
        // etc...
    }
}

[ghost]

Are you using hocon in your example?

[RX14]

No, it's a snippet from build.gradle.

[RX14]

NovaGradle will read the metadata in the build.gradle, and add it to the manifest in K: v form such as (for the example above):

NOVA-Mod-Version: 1.0.1
NOVA-Mod-Logofile: mod.jpg
# etc...

[gjgfuj]

Sounds like a good plan. +1
On 19 Sep 2015 23:58, "Chris Hobbs" [email protected] wrote:

NovaGradle will read the metadata in the build.gradle, and add it to the
manifest in K: v form such as (for the example above):

NOVA-Mod-Version: 1.0.1
NOVA-Mod-Logofile: mod.jpg

etc...

—
Reply to this email directly or view it on GitHub
#199 (comment)
.

[ExE-Boss]

We could also use a JSON file in the root directory (or in the META-INF directory) called novamod.info formatted as such:

{
    "version": "1",
    "mods": [{
        "id": "mod_id",
        "name": "Mod Name",
        "version": "1.0",
        "novaVersion": "0.1.0",
        "description": "Description here.\nWith multi-line support.",
        "logoFile": "/assets/mod_id/textures/logo.png",
        "dependencies": [
            "[email protected]",
            "[email protected]"
        ],
        "authors": ["Your name here"]
    }]
}

We could add additional information to the file later.
dependencies get merged with the dependencies defined in the @Mod annotation, with the newest version overriding older versions.