Project setup
Installation
Section titled “Installation”Settings
Section titled “Settings”Most common configuration options Hygradle supports are changed at the settings level, through the Hygradle settings plugin. Apply it to your project settings, and configure your targeted Hytale version.
pluginManagement { repositories { mavenCentral() }}
plugins { id("dev.hygradle.settings") version "0.0.4" }
rootProject.name = "example-plugin"
hygradle { hytale { version = "2026.02.19-1a311a592" }}Source decompilation
Section titled “Source decompilation”If you would like Hygradle to decompile the server source and make it available in your IDE, enable decompilation:
hygradle { hytale { decompile = true }}Prerelease versions
Section titled “Prerelease versions”By default, Hygradle will target the release patchline. If you would like to target a pre-release version, ensure you configure it:
hygradle { hytale { patchline = Patchline.PRERELEASE }}Build script
Section titled “Build script”Specific plugins and game runs are configured per-project. This separation allows Hygradle to properly support project isolation, and enables some cool cross-project interaction for multi-plugin projects. Apply the project plugin:
plugins { id("dev.hygradle")}Repositories
Section titled “Repositories”Gradle currently has two supports methods of declaring Maven repositories for dependencies. You can either manage them per-project, or at the settings level. Hygradle is unopinionated about which approach you use, and instead provides a repository handler extension you must call, and supply your intended patchline:
import dev.hygradle.dsl.settings.hytaleimport dev.hygradle.dsl.hytale.Patchline
// Project repositoryrepositories { hytale(Patchline.RELEASE)}
// Central repositoriesdependencyResolutionManagement { repositories { hytale(Patchline.RELEASE) }}