Wiki
Dead Body Wiki
Public setup, corpse visuals, loot rules, integrations, and troubleshooting for Dead Body.
Getting Started
Start here for install, first boot, generated files, and the main runtime settings to review first.
Core Corpse Setup
Choose the right corpse visual mode, set loot rules, and tune mob-body behavior without guessing from raw YAML.
Optional Systems
Add combat logging, external integrations, and troubleshooting only after the main corpse loop is already stable.
This page covers the public admin surface for Dead Body: the main commands, the important aliases, and the permission nodes that matter on live servers.
Base commands
Dead Body registers:
/deadbody
/body
/combatbodies
/logoutMain command lanes
The root Dead Body command currently includes these public lanes:
helpguidisplayposeitemposelistclearnearkillreload
Most useful commands day to day
GUI
Use /deadbody gui for the main runtime editor. This is the easiest way to review visual mode, interaction, despawn, and loot settings without digging through YAML first.
Display and pose tools
Use these while authoring or tuning visuals:
/deadbody display/deadbody pose .../deadbody itempose ...
Runtime tools
Use these when testing or cleaning up:
/deadbody list/deadbody clearnear [radius]/deadbody kill <player>/deadbody reload
CombatBodies tools
Use:
/combatbodies/logout
/logout is the safe player-side exit command when the CombatBodies module is enabled.
Core permissions
Dead Body defines these public permission nodes:
deadbody.commanddeadbody.admindeadbody.guideadbody.displaydeadbody.posedeadbody.itemposedeadbody.reloaddeadbody.listdeadbody.clearneardeadbody.killdeadbody.lootdeadbody.loot.playerdeadbody.loot.mobdeadbody.loot.bypasscombatbodies.admincombatbodies.logout
What they are for
deadbody.admin
Administrative control over the Dead Body tool surface. This includes the main admin permissions for GUI, studios, reload, and cleanup flows.
deadbody.command
Allows using /deadbody and /body.
studio permissions
These are split so staff can be granted only the editor surfaces they actually need:
deadbody.guideadbody.displaydeadbody.posedeadbody.itempose
loot permissions
Loot permissions matter only when the matching config checks are enabled.
By default, public looting is still friendly:
interaction.loot-access.player-corpses-require-permission: falseinteraction.loot-access.mob-corpses-require-permission: false
That means normal players can loot corpses unless you intentionally tighten the rules.
deadbody.loot.bypass
Bypasses corpse loot checks when interaction.loot-access.admin-bypass-enabled is enabled.
CombatBodies permissions
combatbodies.adminfor the module admin surfacecombatbodies.logoutfor/logout
Recommended role split
Normal players
- no admin permissions
- optional
combatbodies.logoutif the module is enabled
Staff
deadbody.commanddeadbody.gui- any studio permissions they actually use
Admins
deadbody.admincombatbodies.admin
Testing account
If you need to test edge cases, add deadbody.loot.bypass so you can separate a permission problem from a region or interaction problem.
Best practice
Keep one non-op test account
If you only test as op, you will miss real permission and region behavior.
Test loot with live config rules
If you are changing interaction.loot-access.*, verify the behavior with a player account that matches the real permissions you plan to give on the server.
Reload after meaningful file edits
Do not assume the server picked up a config change automatically.