File Details
EliteEssentials-1.1.19.jar
- R
- Mar 9, 2026
- 1.16 MB
- 656
- Early Access
File Name
EliteEssentials-1.1.19.jar
Supported Versions
- Early Access
1.1.19 - 2026-03-09
Added
- Multi-spawn behavior options — When
spawn.perWorld = trueand a world has multiple spawn points (from/setspawn <name>), you can choose how/spawnand death respawn pick a spawn:- Default (both off): Everyone goes to the primary spawn for that world. Same as before.
spawn.multiNearbySpawn: true—/spawnand death respawn send the player to the nearest spawn to their current (or death) position. Good for large worlds with several spawn areas.spawn.multiRandomSpawn: true—/spawnand death respawn send the player to a random spawn in that world. Good for variety or minigames. If both are enabled, random takes priority.- Config keys:
spawn.multiNearbySpawn(defaultfalse),spawn.multiRandomSpawn(defaultfalse). No change for existing servers until you turn one on.
- IP history — player files (
data/players/{uuid}.json) now recordipHistory: a list of IP addresses withlastUsedtimestamps- Updated on each join; existing IPs get
lastUsedrefreshed; new IPs added; capped at 50 entries - Format:
"ipHistory": [{"ip": "XX.XX.XX.XX", "lastUsed": 1773012653552}] - Useful for moderation, alt detection, and auditing
- Updated on each join; existing IPs get
- Group sync — sync groups between LuckPerms/HyperPerms and EliteEssentials config
/ee groupsync lp-to-ee— copy LuckPerms groups into config.json (chatFormat, warps.groupLimits)/ee groupsync hp-to-ee— copy HyperPerms groups into config.json/ee groupsync ee-to-lp— create missing EE config groups in LuckPerms/ee groupsync ee-to-hp— create missing EE config groups in HyperPerms/ee groupsync— shows detailed help with all directions and what gets synced- Permission:
eliteessentials.admin.groupsync(Admin in simple mode; grant via LuckPerms in advanced mode)
- Greetings — rule-based conditional welcome messages. Server owners define rules in
greetings.jsonto send different messages to different players based on group, permission, world, spawn point, or first-join status- Triggers:
server_join(player connects),world_enter(player changes world),respawn(player respawns after death) - Conditions (AND between types, OR within lists):
groups(LuckPerms groups),permissions(permission nodes),worlds(world names with*wildcards),spawns(named spawn points),firstJoin(true/false) - Features: per-rule delay (
delaySeconds),stopAfterMatchto prevent lower rules from firing,showOnceto only fire once per session, unlimited message lines per rule, full placeholder support ({player},{world},{server},{playercount},{group},{spawn}, PlaceholderAPI) - Config:
greetings.enabled(default:false— opt-in, won't affect existing servers). Rules stored ingreetings.json - Permission:
eliteessentials.admin.greetings(Admin) — for future management commands - Coexists with MOTD: greetings run independently from the existing MOTD system. Server owners can use both, or disable MOTD and use greetings exclusively
- Reloadable:
greetings.jsonis reloaded on/ee reload
- Triggers:
- First-join spawn — teleport new players to a dedicated spawn point (e.g. a tutorial island) on their first join. Completely independent from the regular spawn system
/setfirstjoinspawn— stand at the desired location and run the command. New players will be teleported there on first join/delfirstjoinspawn— remove the first-join spawn point (new players will use Hytale's default spawn)- Config:
firstJoinSpawn.enabled(default:true),firstJoinSpawn.delaySeconds(default:2— delay before teleporting to let the player fully load) - Permissions:
eliteessentials.command.spawn.setfirstjoin(Admin),eliteessentials.command.spawn.delfirstjoin(Admin) - Messages:
firstJoinSpawnSet,firstJoinSpawnDeleted,firstJoinSpawnNotSet,firstJoinSpawnTeleported - No conflict with
teleportOnEveryLogin: first-join teleport happens at login, every-login rewrite happens at disconnect. First session goes to tutorial, second login onwards goes to regular spawn - Storage: Saved in
firstjoinspawn.json(separate fromspawn.json), supports cross-world teleport
- Migration force mode —
/eemigration <source> forceoverwrites existing data with source data instead of skipping. Useful when re-migrating after a failed or partial migration- Usage:
/eemigration essentialscore forceor/eemigration essentialsplus force - Without
force, existing data is preserved (same behavior as before) /eemigrationwith no args now shows full usage help with all sources and options
- Usage:
Fixed
- EssentialsCore migration (
/eemigration essentialscore): fixed several missing data migrations- Kit cooldowns — player kit cooldowns from
players/{uuid}.jsonare now migrated so claimed-kit timers carry over - Spawn —
spawn.jsonis now imported as the primary spawn for its world (skipped if a spawn already exists) - Player names — reads
uuids.jsonto resolve player names instead of defaulting to "Unknown" for migrated player files - Migration result now reports player files found, players skipped (already migrated), spawns imported, and kit cooldowns imported
- Kit cooldowns — player kit cooldowns from
- EssentialsPlus migration (
/eemigration essentialsplus): expanded to match current EssentialsPlus data format- Spawns — imports
spawns.json(array of spawns withmainSpawnflag); grouped by world with primary spawn detection - User profiles — imports
users/{uuid}.json: balance, playtime (ms→s), firstJoin/lastSeen timestamps, ipHistory, ignoredPlayers - Kit cooldowns —
lastClaimedfrom each kit file is migrated to player kit cooldowns - Force mode —
/eemigration essentialsplus forceoverwrites existing warps, kits, homes, spawns, and player data (same as EssentialScore)
- Spawns — imports
- Home GUI crash — fixed
NullPointerExceptioninHomeSelectionPagewhen sorting homes with a null name (could occur with corrupted or partially-migrated home data). Sort is now null-safe