⚠️ Warning: Hyinit is NOT a standard early plugin! Please read the instructions carefully.
🚀 Hyinit
Hyinit launches Hytale with Fabric Mixin and MixinExtras.
You run Hyinit in place of HytaleServer.jar, and it sets up Mixin before the server starts. Mods get the full Mixin and MixinExtras feature set and can transform classes that a standard early plugin cannot reach.
Mods written for the Hyxin manifest format still load.
✅ Installation
Do not put Hyinit in the earlyplugins folder. Keep Hyinit-X.X.X.jar and HytaleServer.jar in the same directory and start Hyinit instead of the server. Java 25 is required.
If you normally start the server like this:
java -Xms10G -Xmx10G -jar HytaleServer.jar --assets=../Assets.zip
Start it through Hyinit instead:
java -Xms10G -Xmx10G -jar Hyinit-X.X.X.jar --assets=../Assets.zip
Then put the mods that need Hyinit into the earlyplugins folder.
| Option | What it does |
|---|---|
--server-jar=<path> |
Use a specific server JAR instead of the one found automatically. |
--early-plugins=<dir1,dir2> |
Load early plugins from extra directories. |
--check-mixins |
Check that every Mixin applies, then exit without starting the server. Run it after updating Hytale, Hyinit or a mod. |
❓ Why not just an early plugin?
The server loads standard early plugins after its own class loading has begun. That limits which Mixin features work and which classes a mod can change. Hyinit starts first and loads the server itself, so:
- All Mixin and MixinExtras features work, including
@Accessor,@Invokerand interface injection. - One JAR can contain both Mixins and a normal plugin.
📖 For mod developers
List your Mixin config in manifest.json and ship the JAR in earlyplugins:
{
"Main": "yourmodid.YourPlugin",
"Mixins": ["yourmodid.mixins.json"]
}
Main is optional. With it, the same JAR is also loaded as a normal plugin, so there is no need to split it across earlyplugins and mods.
Reference: Launching · manifest.json · Changelog
