1.2

📝 Changelog – v1.2

Added configurable elimination behavior for players who reach 0 lives.
- New elimination.mode option in config.yml:
  - BAN (default) — preserves hardcore behavior.
  - SPECTATOR — keeps eliminated players online in spectator mode.
Added spectator elimination system.
- Eliminated players in SPECTATOR mode:
  - Are placed into spectator mode instead of being banned.
  - Are fully restricted from interacting with the world.
  - Persist across server restarts.
  - Appear in the revive menu as normal.
Added spectator revival handling.
- When revived, spectator players:
  - Are restored to survival mode.
  - Receive revive lives as configured.
  - Are teleported to the server spawn.
Added LIFE_STAR drop limit configuration.
- Prevents LIFE_STAR drops once a player reaches a set number of lives.
Added LIFE_STAR crafting limit configuration.
- Prevents crafting LIFE_STAR once a player reaches a configured life threshold.
Added respawn action bar message.
- Displays remaining lives when a player respawns after death.
Added unified action bar messaging system.
- Action bar messages are now configurable in messages.yml:
  - actionbar.join
  - actionbar.respawn
  - actionbar.revive

LIFE_STAR crafting and drop behavior now dynamically updates per player based on current lives.
Revive GUI dynamically adapts based on elimination mode (BAN vs SPECTATOR).
Action bar messages safely fail if missing or empty.
Improved internal validation when reviving players.

Fixed an issue where server-banned players could appear in the revive menu.
Fixed LIFE_STAR drops still triggering when players were above the configured life limit.
Fixed revive GUI logic inconsistencies for eliminated players.

Added spectator protection to prevent eliminated spectators from bypassing restrictions.
Internal logic cleanup and stability improvements.
Improved handling of edge cases related to lives, revives, and elimination states.
Made with ❤️ by Kai
Support & community on Discord: https://discord.gg/Ha3FHZBX5Q