EliteEssentials | Everything Your Server Needs and More!

2.0.11 - 2026-08-27

Compatibility release for Hytale server 0.6.1. If you have updated your server to 0.6.x, this release is required. Older builds crash the world the moment a player finishes connecting, which leaves the server unjoinable. Nothing in your config, permissions, or data files needs to change; drop the new jar in and restart.

This build targets 0.6.1 and will not load on a 0.5.x server. Stay on 2.0.10 until you update your server.

Fixed

• The world crashed as soon as a player joined - on a 0.6.1 server, every join killed the world the player was joining. The player was disconnected with "The world you were on has crashed (possibly caused by com.eliteessentials:EliteEssentials)", the server reloaded the world, and the next join did it again, so nobody could get on. The console showed NoSuchMethodError for ServerPlayerListPlayer pointing at EliteEssentials. Cause was the tab list entry format: 0.6.1 added a spectator flag and a lives counter to it, so the older call no longer existed on the new server. Every place the plugin writes a tab list entry (nicknames, permission prefixes, AFK status, and unvanishing) was updated to the new format
• /fly and timed flight on 0.6.1 - the server replaced its flight on/off switch with a three-state mode (disabled, allowed, forced). /fly for yourself and for another player, /fly used through a command alias, and the automatic shutoff for timed flight all read and write the new mode. Fly speed and /flyspeed are unaffected
• spawn.teleportOnEveryLogin overwrote your saved position in other worlds - on a multi-world server, logging out of one world wrote the spawn coordinates into that world's saved position as well as the spawn world's. Login still put you at spawn correctly, but walking back through a portal into the world you had logged out of dropped you at the spawn world's raw coordinates in that world instead of where you left off, which on differently shaped worlds could mean mid-air, underground, or in water. Only the spawn world's saved position is rewritten now, so every other world keeps the position you left it at. If a player has never visited the spawn world, that entry is created rather than skipped, so the first login after enabling the setting lands at spawn instead of the spawn world's own default spawn point. Single-world servers and spawn.perWorld = true were never affected, and /back is unaffected either way since it keeps its own history. Reported by a server owner running 2.0.10

Changed

• Requires Hytale server 0.6.1 or newer 0.6.x - the plugin now declares ^0.6.1, so a 0.5.x server will refuse to load it rather than starting up and failing later
• /fly now reports flight correctly in game modes that force it - creative and any mode configured to force flight are treated as flight already being on, so your first /fly press turns it off instead of appearing to do nothing. Previously a forced-flight mode could report flight as off
• Internal permission handling updated for the new server API - the way commands opt out of the server's automatic permission nodes changed in 0.6.1, and every EliteEssentials command was migrated. No permission node was added, removed, or renamed, so no LuckPerms or config changes are needed. /kit create and /kit delete keep their own dedicated nodes as before

Known issues

• Hardcore lives and the spectator marker can go missing from the tab list - 0.6.1 shows a lives counter (on hardcore worlds) and a spectator marker in the player list. When EliteEssentials rewrites a player's tab list entry to show a nickname, a permission prefix, or AFK status, those two markers are cleared for that player until the server sends its own update. Only affects servers running hardcore or using spectator mode, and only the tab list display; lives and spectating themselves work normally
• A nickname or prefix can briefly drop off the tab list on a hardcore world - when the server broadcasts a lives change, it resends its own version of the player list, which overwrites the nickname or prefix until the next refresh

Note

• Check your admin group if admins lose access to commands after updating - 0.6.1 tightened which permission nodes the server accepts and now rejects a bare * node inside a group, logging Skipping invalid permission node '*' in group '<group>' at startup. This is a Hytale change, not an EliteEssentials one, but it can take admin rights away from anyone who was made an admin with a bare *. Replace it with explicit nodes such as eliteessentials.admin.*, which is still accepted