Added

• Hologram orphan cleanup command: /lifesteal hologram cleanup [radius] (player-only, requires lifesteal.scoreboard.remove or lifesteal.hologram or lifesteal.admin). Scans nearby entities within the given radius (default 10, clamped to 1–64) and removes armor stands that look like EzLifesteal hologram lines but are no longer tracked by the manager. Useful after unexpected server crashes that leave ghost stands in the world.
• PersistentDataContainer tagging — every armor stand spawned by TopHologramManager is now tagged with a NamespacedKey("hologram_line") PDC entry. This makes orphan detection reliable across server restarts. Pre-existing untagged stands are identified via a heuristic (marker, invisible, no gravity, small, custom-name-visible, no base-plate, no arms).
• Language keys hologram-cleanup-removed and hologram-cleanup-none added to all 8 locale files (en, de, es, fr, nl, pt, ru, zh).
• EzCountdown 2.0.1: richer countdown configuration — bumped the EzCountdown dependency to 2.0.1 and exposed six new CountdownBuilder fields through revive-beacon.yml under spawn.countdown:
  • start-message: server-wide broadcast sent when the countdown starts (leave blank to disable).
  • end-message: server-wide broadcast sent when the countdown ends (leave blank to disable).
  • end-commands: list of console commands dispatched when the countdown ends; supports {name} placeholder for the countdown ID.
  • update-interval-seconds: how often EzCountdown refreshes the display in seconds (default 1; increase to reduce load on high-player-count servers).
  • visibility-permission: permission node required to see the countdown overlay; leave blank to show to all players.
  • ephemeral: when true (default) the countdown lives only in memory and is never written to EzCountdown's countdowns.yml, preventing orphaned entries after a server restart.

Changed

• EzCountdownBeaconHook now catches DuplicateCountdownException separately (reuses an existing countdown by name rather than silently dropping it) and catches the base EzCountdownException for all other EzCountdown errors, with distinct log messages for easier diagnosis.

Added

• Bumped project version to 1.1.1.
• Short-term fix for team-bank persistence: perform a compensating rollback of a player's profile when a subsequent team-bank save fails, preventing inconsistent state between player hearts and the team bank.
• Added focused unit tests that exercise team-bank rollback and atomicity paths to address patch-level coverage requirements; JaCoCo checks pass locally.

Changed

• Bumped dependency versions (WorldEdit, WorldGuard, EzCountdown, Testcontainers, JUnit, Awaitility, SLF4J and others) per dependabot updates.

Fixed

• Resolved a patch-coverage failure by adding targeted tests for TeamBankService and TeamBankAdminService; coverage for modified lines now meets project rules.

What's new in 1.1.0: shared Team Heart Bank (requires TeamsAPI), automated revive beacon placement with scheduling and random regions, WorldGuard protection for auto-spawned beacons, EzCountdown support for beacon warm-up timers, and an expanded interactive beacon GUI. Several bug fixes for bans, beacons, and the team bank.

Added
Team Heart Bank (requires TeamsAPI)
Teams can now pool hearts into a shared bank. Players deposit and withdraw hearts; admins can inspect or adjust any team's balance directly from the console or in-game.

Check full changelog

Beacon Auto-Spawn
The plugin can now place revive beacons in the world automatically — on a recurring timer, on demand via command, or at a random location within a configured bounding box or weighted region list.





New /beacon command — top-level alias for /lifesteal beacon — with three new subcommands:

Command Description
/beacon spawn [world x y z] Place a beacon at explicit coordinates, or a random location
/beacon despawn <id|all> Remove one or all active plugin-spawned beacons
/beacon spawns List all active plugin-spawned beacons and their status
New revive-beacon.yml keys under spawn.

Check full changelog

WorldGuard integration (optional)
A WorldGuard region is automatically created around each plugin-spawned beacon to prevent players from breaking or tampering with it. The region is removed when the beacon despawns. Configurable radius and flag overrides: deny-build, deny-pvp, deny-mob-damage, deny-explosions. Silently skipped when WorldGuard is not installed.

EzCountdown integration (optional)
An EzCountdown timer is shown while a beacon warms up before becoming available. Supports ACTION_BAR, BOSS_BAR, CHAT, TITLE, and SCOREBOARD display types. Falls back to an internal timer when EzCountdown is not installed.

Soft dependencies
WorldGuard, EzCountdown, and TeamsAPI are now listed as softdepend in plugin.yml. The plugin loads and works fully without any of them — each integration is silently skipped when its dependency is absent.

Translations
All new messages (team bank player/admin commands, beacon auto-spawn announcements) are translated in all eight bundled locales: en, de, es, fr, nl, pt, ru, zh.

Fixed

• Players were not banned at zero hearts when using the default min-hearts setting — the zero-heart ban check ran against an already-floored value, so players reaching zero hearts were never banned under the default min-hearts: 1.0. Ban now fires correctly.
• /pardon <player> was reversed on server restart — manually pardoning a player (via /pardon or by editing banned-players.json) was undone the next time the server started, because the plugin re-applied the stored ban. Bukkit's ban list is now treated as authoritative: if a ban is missing there, it is removed from storage too.
• Crash on Paper 26.1.2 when banning players — an incompatibility with the Paper 26.1.2 ban API caused a ClassCastException whenever the plugin tried to issue a ban. Fixed.
• Revive beacon GUI opened when holding a revive voucher — right-clicking a beacon with a valid voucher in hand should trigger a revive, not open the info GUI. The GUI was opening anyway due to listener priority ordering. Fixed.
• Beacon availability broadcast and effects not fired for instant-availability beacons — beacons with no countdown (immediate availability) skipped the availability event entirely, so no server broadcast, title overlay, particles, or fireworks were shown. Fixed.
• Team bank returned "invalid amount" instead of "feature disabled" — when the team bank was turned off, deposit/withdraw validated the heart amount before checking whether the feature was enabled, returning a misleading error. Corrected to check enabled-state first.
• Overflow heart items dropped at the victim's respawn point instead of the kill location — when a killer's inventory was full, the extra heart item spawned at the victim's new respawn position rather than at the kill site. Now dropped at the killer's location.
• Team-bank messages missing from non-English locales — de, es, fr, nl, pt, ru, and zh locale files were missing the team-bank message keys introduced in earlier builds. All locale files are now complete.

Changed

• Beacon info GUI expanded from 27 to 54 slots: rows 4–5 now list eliminated players (click to select a revive target); row 6 has pagination and a direct "Use Beacon" button — players no longer need to close and reopen the beacon to perform a revive.
• team-kill-bypass-with-teams-api flat key superseded by the new team-kill-bypass section (see Added above). The old flat key is still read as a fallback — no immediate action required.

Migration notes
No breaking changes. Existing configs continue to work without modification. One key is superseded but remains backward-compatible:

Old key (lifesteal-core.yml) Replacement Notes
team-kill-bypass-with-teams-api: true/false team-kill-bypass.enabled: true/false Old key still works as a fallback

Developer API
Four Bukkit events are fired during the plugin-spawned beacon lifecycle (package com.skyblockexp.ezlifesteal.api.event): More info

• Published Github source code on Github: https://github.com/ez-plugins/EzLifesteal
• Added online documentation: https://ez-plugins.github.io/EzLifesteal/
• Rewritten Markdown topic
• Rewritten bbcode topic
• Added unit test CI
  • Added unit tests
• Added feature test CI
  • Added feature tests
• Added test coverage CI
• Rewritten main plugin class
• Made EzSeasons integration optional
  • Refactored integration to use new EzSeasons 1.0.0 SeasonResetEvent
• Split the lifesteal.yml configuration file
  • Added lifesteal-killstreak.yml configuration file
  • Added lifesteal-core.yml configuration file
  • Added lifesteal-drops.yml configuration file
  • Added lifesteal-worlds.yml configuration file
• Removed messages.yml, all configurable messages are now in languages/*.yml
• Added craftable recipes for existing vouchers in EzLifesteal

• Added %ezlifesteal_is_banned% placeholder in EzLifesteal
• Added %ezlifesteal_is_banned_<player>% placeholder (returns true or false)
• Added storage for ban information besides default Bukkit ban storage
• Added profile information to storage
  • Added LifestealPlayer POJO
• Refactored all subcommands to a file per subcommand structure
• Improved performance for large-scale data handling (large amounts of players)
  • Added local data caching through LifestealPlayer POJO to prevent database calls where possible
• Added /lifesteal help subcommand
  • Routed /lifesteal to /lifesteal help
• Added /lifesteal info subcommand
• Added beacon revive feature
• Added /lifesteal beacon add
• Added /lifesteal beacon clear
• Added /lifesteal beacon list
• Added /lifesteal beacon remove

• Added option to prevent losing hearts from deaths by mobs

• Added option to set mimimum hearts required to lose 1 heart when killed by a mob. -1 can be used to disable.

• Fixed issue in heart vouchers not being dropped on death
• Fixed pojectile deaths losing hearths, ignoring the settings

• Added option to enable/disable losing hearts when players get killed by mobs. Default this is set to true when not configured in the lifesteal.yml

• Improved autocomplete of the /lifesteal command on Paper servers
• Fixed issue causing the /lifesteal command to show usage message