Metadata

Configuration

The metadata block sets values used for template expansion and JAR naming.

prism {
    metadata {
        modId = "mymod"
        name = "My Mod"
        description = "Does things."
        license = "MIT"
        author("Alice")
        author("Bob")
        credit("Charlie")
    }
}

Property	Required	Description
modId	Yes	Mod identifier, used in file names and templates
name	Yes	Display name
description	No	Mod description
license	No	License identifier (MIT, GPL-3.0, etc.)
version	No	Mod version. Defaults to project.version
group	No	Maven group. Defaults to project.group

author() and credit() can be called multiple times.

Writing metadata files

Prism does not generate fabric.mod.json, mods.toml, or neoforge.mods.toml for you. You write these files yourself and place them in the loader's src/main/resources/ directory.

Prism expands ${variable} placeholders in these files during the build. See Template Variables for the full list.

JAR naming

Output JARs follow the format:

{modId}-{mcVersion}-{Loader}-{version}.jar

Examples:

mymod-1.20.1-Fabric-1.0.0.jar
mymod-1.21.1-Neoforge-1.0.0.jar