Creators
Details
Licensed MIT
Published 9 months ago
Updated 3 months ago
All versions
1.1.2
Release
EzLifesteal 1.1.25 months ago 282
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Purpur
Changes
Added
- Hologram orphan cleanup command:
/lifesteal hologram cleanup [radius](player-only, requireslifesteal.scoreboard.removeorlifesteal.hologramorlifesteal.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
TopHologramManageris now tagged with aNamespacedKey("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-removedandhologram-cleanup-noneadded 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
CountdownBuilderfields throughrevive-beacon.ymlunderspawn.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 (default1; 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: whentrue(default) the countdown lives only in memory and is never written to EzCountdown'scountdowns.yml, preventing orphaned entries after a server restart.
Changed
EzCountdownBeaconHooknow catchesDuplicateCountdownExceptionseparately (reuses an existing countdown by name rather than silently dropping it) and catches the baseEzCountdownExceptionfor all other EzCountdown errors, with distinct log messages for easier diagnosis.
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:wPNdCkBA:7pyckKnK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wPNdCkBA:7pyckKnK"
}

