Migrate to new Hytale plugin template structure
Replaces the previous Kotlin-based Gradle build and template files with a new Java-based Gradle build system and updated example plugin code. Removes old build scripts, plugin template, and configuration, and introduces a new ExamplePlugin with updated manifest, command, and recipe example. Updates documentation and project configuration to match the new structure and usage.
This commit is contained in:
@@ -1,10 +1,32 @@
|
||||
# Project Information
|
||||
pluginGroup=com.example
|
||||
pluginVersion=1.0.0
|
||||
pluginDescription=A Hytale plugin template with best practices
|
||||
# The current version of your project. Please use semantic versioning!
|
||||
version=0.0.2
|
||||
|
||||
# Gradle Configuration
|
||||
org.gradle.parallel=true
|
||||
org.gradle.caching=true
|
||||
org.gradle.daemon=true
|
||||
org.gradle.jvmargs=-Xmx2048m -XX:MaxMetaspaceSize=512m
|
||||
# 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.example
|
||||
|
||||
# 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
|
||||
|
||||
# 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
|
||||
Reference in New Issue
Block a user