Skip to content

Manifest dependency fields

AzureDoom edited this page Jun 8, 2026 · 1 revision

Manifest dependency fields

Use manifestDependencies when your mod requires another plugin or module to be present at runtime.

hytaleTools {
    manifestDependencies = 'Hytale:AssetModule=*,MoreMagicSpell:Rippod.Hexcode=*,Group:Name=Version'
}

Use manifestOptionalDependencies when your mod can integrate with another plugin if it is present, but does not require that plugin in order to load.

hytaleTools {
    manifestOptionalDependencies = 'MoreMagicSpell:Rippod.Hexcode=*,Group:Name=Version'
}

Manifest dependency values use this format:

Group:Name=Version

Where:

  • Group is the dependency group or namespace.
  • Name is the dependency/plugin/module name.
  • Version is the required version or version range.
  • * means any compatible version.

Multiple dependencies must be separated with commas and should not include spaces:

hytaleTools {
    manifestDependencies = 'GroupOne:DependencyOne=*,GroupTwo:DependencyTwo=1.0.0,GroupThree:DependencyThree=>=2.0.0'
}

Do not write spaces after commas:

// Correct
manifestDependencies = 'Hytale:AssetModule=*,MoreMagicSpell:Rippod.Hexcode=*'

// Incorrect
manifestDependencies = 'Hytale:AssetModule=*, MoreMagicSpell:Rippod.Hexcode=*'

A dependency should be placed in manifestDependencies if your mod cannot function without it. A dependency should be placed in manifestOptionalDependencies if your mod only adds support for it when it is available.

For example, if your mod directly requires Hexcode to load:

hytaleTools {
    manifestDependencies = 'Hytale:AssetModule=*,MoreMagicSpell:Rippod.Hexcode=*'
}

If your mod only enables extra Hexcode integration when Hexcode is installed:

hytaleTools {
    manifestOptionalDependencies = 'MoreMagicSpell:Rippod.Hexcode=*'
}

Home | Task Reference | Troubleshooting

Clone this wiki locally