Lifesaver

Lifesaver

Lifesaver adds server chat announcements for moments where players protect or save each other in combat. It watches recent combat, credits the player who finishes off a threat, and can announce either a normal protection or a stronger save when the victim was close to death.

It works out of the box with YAML history storage and also supports SQLite, MySQL, and MariaDB for larger servers.

Features

• Announces when a player protects another player from a recent attacker.
• Announces stronger save messages when the victim would have died or was left on low health.
• Tracks player attackers, hostile mobs, and optional neutral mobs.
• Resolves projectiles, TNT, evoker fangs, area effect clouds, and other Bukkit-supported damage sources back to the responsible entity.
• Can credit tamed mob damage and kills to the online owner.
• Requires recent protector damage by default, with optional direct-killer fallback.
• Supports grouped victim messages or a recent save-focused message.
• Configurable save health threshold, absorption handling, tracking window, victim history size, and kill-credit timing.
• Per-player cooldowns can apply to protectors, victims, or both to prevent repeated message spam.
• World blacklist or whitelist support.
• Ignores creative, spectator, dead, vanished, and NPC players.
• Clears recent victim records for Totem of Undying style self-resurrections so they do not count as saves.
• Custom message text, colours, delivery mode, victim formatting, and console logging.
• Delivery can be global or limited to the involved players.
• Optional protection and save rewards with separate cooldowns.
• Rewards can run console commands, run player commands, and send private reward messages.
• Persistent history records delivered protection and save announcements.
• History powers recent event views, per-player stats, and top lifesaver lists.
• History can be saved, backed up, pruned by age, and checked through diagnostics.
• Storage health is visible through status and audit commands.
• Database connections use the shared secure storage layer, including safer default TLS settings for MySQL/MariaDB and redacted credential handling.

Integrations

• Alignments: can consume LifesaverProtectionEvent and award reputation for saves and protections.
• StormEconomy: can reward Lifesaver protection and save events when Lifesaver rewards are enabled in StormEconomy.
• Bodyguard: can send bodyguard protections through Lifesaver's external announcement API, so bodyguard saves use Lifesaver delivery, cooldown, event, reward, and history behaviour.
• Bukkit permissions: works with standard permission plugins, including ThunderPerms-managed permission setups.

Lifesaver also registers LifesaverApi so other plugins can announce external protections, inspect recent history, read player stats, and check history storage health.

Commands

Main command:

• /lifesaver

Common commands:

• /lifesaver status
• /lifesaver audit
• /lifesaver stats [player|uuid]
• /lifesaver top [all|protections|saves] [limit]
• /lifesaver history [limit]
• /lifesaver save
• /lifesaver backup
• /lifesaver prune <age>
• /lifesaver reload

Permissions

• lifesaver.use
• lifesaver.reload
• lifesaver.stats
• lifesaver.history
• lifesaver.save
• lifesaver.backup
• lifesaver.prune
• lifesaver.admin

Notes

Lifesaver is observational only.

It does not change combat damage, revive players, freeze combat, or give gameplay advantages by itself.

Rewards are disabled by default.

The default storage backend is YAML. SQLite, MySQL, and MariaDB are optional.

Lifesaver does not require Alignments, StormEconomy, Bodyguard, PlaceholderAPI, WorldGuard, or a database.