Mods Version Range Fix — no longer maintained

⚠ Do not install this on Hytale 0.6.3 or later

Hytale now does this natively, and better. This mod is obsolete and will not be updated

What it did

Up to the February 2026 builds, the server compared a mod's declared ServerVersion against its own build stamp with a plain string comparison. A mod built for 2026.02.17-255364b8e therefore refused to load on 2026.02.19-1a311a592, even though nothing relevant had changed. This mod intercepted that comparison and evaluated the declared value as a semver range instead

Why it is retired

Re-verified against Hytale 0.6.3 build 26 on 13 September 2026, by reading the server's own code and running its version classes

Hytale 0.6.3 implements the whole thing itself:

• ServerVersion is parsed by a codec into a real version range, so ">=0.6.0 <0.7.0" and "*" work out of the box
• The old YYYY.MM.DD-<sha> format is explicitly recognised and treated as a wildcard.
• An incompatible version no longer blocks loading at all. It produces a warning in the log and a notice in game, and the mod loads anyway
• The string comparison this mod hooked no longer exists, so on 0.6.3 it would match nothing and patch nothing

Forcing the new compatibility check to always report "compatible" was considered and rejected: it would hide the warnings that explain why a genuinely stale mod is about to misbehave

What to do instead

Mod authors — declare a real range in your manifest.json:

"ServerVersion": ">=0.6.0 <0.7.0"

Players seeing the outdated-mods warning — it is informational, and the mod has loaded. To silence it, start the server with -Dhytale.allow_outdated_mods

If you have this mod installed — remove the jar

Not because it is merely idle. The patch looks for a String.equals call inside the server's dependency check, and that method still contains exactly one — except it is now the test that compares a plugin's group name against "Hytale", which has nothing to do with versions. So the patch still applies, still reports success, and is attached to the wrong thing. It happens to stay harmless, because its own guards expect something version-shaped and a group name is not. That is luck, not design, and it is not a state to leave a published mod in

Thanks to everyone who used it. The right outcome for a compatibility shim is for the thing it shimmed to get fixed upstream, and that is what happened