forked from Build-9/Hytale-Example-Project
-
Notifications
You must be signed in to change notification settings - Fork 2
Expand file tree
/
Copy pathgradle.properties
More file actions
35 lines (28 loc) · 1.42 KB
/
Copy pathgradle.properties
File metadata and controls
35 lines (28 loc) · 1.42 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
# The current version of your project. Please use semantic versioning!
version=0.5.0
# The group ID used for maven publishing. Usually the same as your package name
# but not the same as your plugin group!
maven_group=org.hytaledevlib
# The version of Java used by your plugin. The game is built on Java 21 but
# actually runs on Java 25.
java_version=25
# Determines if your plugin should also be loaded as an asset pack. If your
# pack contains assets, or you intend to use the in-game asset editor, you
# want this to be true.
includes_pack=true
# The release channel your plugin should be built and ran against. This is
# usually release or pre-release. You can verify your settings in the
# official launcher.
patchline=release
# The exact Hytale build to compile against. Use the build string from the
# launcher (format YYYY.MM.DD-<hash>) so Gradle pulls the matching server jar
# for your selected patchline.
hytale_build=2026.02.17-255364b8e
# Determines if the development server should also load mods from the user's
# standard mods folder. This lets you test mods by installing them where a
# normal player would, instead of adding them as dependencies or adding them
# to the development server manually.
load_user_mods=false
# Force Gradle itself (daemon/buildscript runtime) to use Java 25 for this
# project. This avoids IDE/environment fallback to older Java installations.
org.gradle.java.home=C:/Users/shane/.jdks/openjdk-25.0.2