Config Files, Runtime, and Persistence

This page maps the generated Dead Body files to the jobs they actually do.

Main public files

dead-body.yml

This is the main plugin config. It controls:

• branding
• world enable list
• corpse lifetimes and caps
• container titles and sizing
• corpse visual mode
• nameplates
• pose definitions
• interaction rules
• despawn behavior
• persistence
• mob corpse rules
• pose-studio behavior

combat-bodies.yml

This is the optional combat-logging module config. It controls:

• combat tagging
• logout proxy spawn behavior
• safe zones
• login blocking while a body still exists
• logout countdown effects and messages

dead-body.db.yml

This file is written only when persistence is enabled and live corpses are saved.

Main runtime settings to review first

world scope

Start by confirming:

worlds-enabled:
  - world

If a world is not listed, corpse spawning will not happen there.

corpse count and lifetime

These are the first two cleanup controls most servers care about:

max-corpses: 150
lifetime-minutes: 10

container surface

Review:

• container-title-format
• container-size
• displayed held items and armor presentation

interaction rules

Most live-server behavior comes from interaction.*, especially:

• interaction.loot-access.*
• open delay
• grounded requirements
• empty auto-remove and grace
• WorldGuard compatibility

visuals and nameplates

Most player-side appearance comes from visuals.*, especially:

• visuals.mode
• visuals.nameplate.*
• visuals.player-model.*
• visuals.item-display.*

despawn and persistence

Review:

• despawn.*
• persistence.*

Persistence behavior

Dead Body can save and restore live corpses across restarts.

Important keys:

• persistence.enabled
• persistence.autosave-seconds
• persistence.defer-until-chunk-loaded

Use persistence only if you actually want corpses to survive a restart. If you prefer a clean slate each boot, leave it disabled.

Safe first-edit checklist

Use this sequence:

1. world list
2. corpse lifetime and max corpses
3. loot rules
4. visual mode
5. nameplate on or off
6. mob corpses on or off
7. persistence on or off
8. CombatBodies on or off

Good default mindset

For most public servers, the safest early choices are:

• start with player corpses only
• leave loot open by default unless you need strict permission gating
• start in ARMOR_STAND or ITEM_DISPLAY
• enable PLAYER_MODEL only after you verify the dependency path you want
• leave persistence off until the base gameplay loop feels correct

Files to keep open while working

For day-to-day operation, the main files are:

• dead-body.yml
• combat-bodies.yml
• plugin.yml only when you are checking commands or permissions in the source

Next pages

• visual Modes, Nameplates, and Renderers
• player Corpses, Loot Rules, and Containers
• mob Corpses, MythicMobs, and Models