Configurations

Configurations

Configuration	Purpose
vineServerJar	Hytale server binary; auto-injected unless you declare one explicitly
vineImplementation	Compile/runtime dependency. Plugins are staged into run/mods and the shared classpath; ordinary libraries are shared-classpath only
vineCompileOnly	Compile-time dependency that is not staged for local runtime
requiredDependency	Alias for a required compile/runtime dependency; extends implementation and participates in decompilation
optionalDependency	Alias for an optional compile-time integration; extends compileOnly and participates in decompilation
vineMod	Runtime Hytale plugin copied into run/mods as a complete jar, without adding it to the shared classpath
vineDecompileTargets	Extra dependencies to decompile for IDE source attachment
hytaleBundledRuntime	Runtime dependency automatically added and optionally bundled into the final mod jar

Internal configurations such as vineImplementationJars, vineModJars, vineDependencyJars, vineDecompileClasspath, and vineflowerTool support resolution, staging, and decompilation. Projects normally declare dependencies using the public configurations above.

requiredDependency and optionalDependency are dependency-bucket aliases. They do not automatically edit manifest.json; you must still declare the matching plugin identifiers in manifestDependencies or manifestOptionalDependencies.

compileOnly automatically includes:

• vineCompileOnly
• vineServerJar
• hytaleAssets for IDE asset browsing

implementation includes vineImplementation, requiredDependency, and hytaleBundledRuntime.

compileOnly includes vineCompileOnly, optionalDependency, vineServerJar, and hytaleAssets.

Both aliases also feed the decompilation/source-attachment configurations.

This lets you write mods against the Hytale server API without manually declaring the server dependency.

---

Home | Task Reference | Troubleshooting