Install and First Boot

Use this page when you are setting Dead Body up on a server for the first time.

Requirements and soft dependencies

Dead Body is built for modern Paper 1.21.4+ servers and Java 21.

Optional integrations:

• WorldGuard
• LibsDisguises
• ProtocolLib
• MythicMobs
• DeathPlus
• Citizens
• Nexo

If those plugins are missing, Dead Body still boots. Optional bridges and render paths simply stay inactive.

Basic install flow

1. Stop the server.
2. Drop the Dead Body jar into plugins/.
3. Start the server once.
4. Let Dead Body generate its folder and defaults.
5. Stop the server again before doing serious config work.

Files Dead Body writes on first boot

The first boot creates the main plugin folder and installs the starter defaults. The important public files are:

• dead-body.yml
• combat-bodies.yml
• dead-body.db.yml only after persistence is enabled and corpses are saved

First boot checklist

Confirm the plugin actually loaded

Look for the Dead Body startup output in console. If the plugin does not load:

• check the Paper version
• check the Java version
• check whether another plugin is failing before or during startup
• check for YAML syntax damage in edited files

Test the base commands

Dead Body registers:

• /deadbody
• /body
• /combatbodies
• /logout

If /deadbody or /body do not exist, the plugin did not load correctly yet.

Force a simple live test

After first boot, test the default loop before you touch advanced settings:

• die once as a normal player
• confirm a corpse actually spawns
• confirm the container opens
• confirm the corpse despawns on the expected timer

Do that before you spend time on visuals, MythicMobs, or CombatBodies.

Safe first edits

These are the best low-risk changes to review early:

• worlds-enabled
• max-corpses
• lifetime-minutes
• container-size
• interaction.loot-access.*
• visuals.mode
• visuals.nameplate.enabled

Generated defaults matter

Dead Body is designed around fresh generated defaults. If you delete the plugin folder and reboot, the plugin will regenerate the default YAML files.

That means server owners should expect new settings to appear in the generated defaults with clear comments when the plugin is updated.

What to review before launch

Before opening the server to real players, review:

• corpse lifetime and cleanup behavior
• loot access rules
• your chosen visual mode
• whether mob corpses are enabled
• whether CombatBodies is enabled
• WorldGuard region behavior in protected areas

After install

When the plugin boots cleanly, move into:

• config Files, Runtime, and Persistence
• admin Commands and Permissions
• visual Modes, Nameplates, and Renderers