HeruEdhel
7a4a0bd4bd
feat: Expand PlayersApi with new endpoints for better player management feat: Update ServerApi to include new instance-related endpoints feat: Add new endpoints to ServiceAccountsApi for improved service account management fix: Update TokensRotateEndpoint and TokensStoreEndpoint to include new validation rules feat: Introduce ControlPlaneHttpClient for handling HTTP requests to the control plane feat: Implement PathBuilder for dynamic URI resolution feat: Add PlayerEntitlement and PlayerSessionProfile models for player data handling feat: Create server-related models including HeartbeatPayload, PresenceState, and ReadinessState feat: Develop RegistrationPayload and ServerInstance models for server management feat: Add ServerProfile model to encapsulate server instance details refactor: Update network class to include builder method for ControlPlaneClient chore: Update manifest.json for plugin metadata and dependencies
38 lines
1.5 KiB
Properties
38 lines
1.5 KiB
Properties
# The current version of your project. Please use semantic versioning!
|
|
version=0.0.2
|
|
|
|
# The group ID used for maven publishing. Usually the same as your package name
|
|
# but not the same as your plugin group!
|
|
maven_group=net.kewwbec
|
|
|
|
# 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.01.27-734d39026
|
|
|
|
# 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
|
|
|
|
# If Hytale was installed to a custom location, you must set the home path
|
|
# manually. You may also want to use a custom path if you are building in
|
|
# a non-standard environment like a build server. The home path should
|
|
# the folder that contains the install and UserData folder.
|
|
# hytale_home=./test-file
|