Dead Body

Instead of letting every death dissolve into a loose item pile, Dead Body keeps the scene readable. That is better for gameplay, better for atmosphere, and much easier to design around on combat-heavy servers.

It is especially strong on servers that want looting, body recovery, or corpse presentation to feel like part of the combat identity.

After first boot, the main files live in plugins/DeadBody/dead-body.yml and plugins/DeadBody/combat-bodies.yml. That gives you one place for the general corpse rules and one place for the optional combat-log layer.

Start with player corpses and normal cleanup first. Once that feels right, add the combat-body module and optional high-fidelity mob or player models if the server benefits from them.

LibsDisguises enables higher-fidelity player-model and mob-corpse presentation. MythicMobs makes it easier to filter or override corpse behavior for custom mobs. ProtocolLib and WorldGuard stay optional instead of bloating the install path on day one.

That gives you a simple rollout path: get the core death loop right first, then add the richer visual or ecosystem layers only where they are worth maintaining.

Use the gallery to show one player corpse scene, one mob corpse or advanced model example, and one admin-facing cleanup or config surface.

That tells buyers the plugin is both atmospheric and practical to run.