Dependencies

Dependencies

Use the Hytale-specific dependency configurations when possible when pulling other mods/plugins:

dependencies {
    // Runtime dependency: available when running the server locally
    vineImplementation 'com.example:some-runtime-mod:1.0.0'

    // Compile-time only dependency: available to your code, but not bundled
    vineCompileOnly 'curse.maven:hexcodes-1448311:8166165'

    // Optional IDE source attachment target
    vineDecompileTargets 'curse.maven:hexcodes-1448311:8166165'

    // Example of Modtale dependency.
    // Alias can be anything but `_`, usually good to name the mod being used here. Ex: `LevelingCore`
    // ProjectID found on right side of project
    // Version can be found from Changelog button
    vineImplementation 'modtale:Alias_ProjectID:Version'
    
    // Example of Modifold dependency. 
    // Alias can be anything but `_`, usually good to name the mod being used here. Ex: `LevelingCore`
    // Can be found from link like so: https://modifold.com/mod/projectSlug/version/versionID
    vineImplementation 'modifold:Alias_projectSlug:versionID'
}

vineCompileOnly is usually preferred over plain compileOnly for mod/plugin dependencies, because dependencies declared in vineCompileOnly, vineImplementation, and vineDecompileTargets can participate in the plugin’s decompilation/source attachment flow.

---

Home | Task Reference | Troubleshooting