Integrations and Troubleshooting

This page collects the setup problems Dead Body servers are most likely to hit first.

WorldGuard and protected-region looting

If players have the right Dead Body permissions but still cannot open a corpse in a protected region, check WorldGuard first.

The common issue is:

• build: deny

That flag can block corpse interaction even when the player has the Dead Body permission to loot.

If you want anti-grief while still allowing corpse looting, prefer:

• block-break: deny
• block-place: deny

Dead Body also includes compatibility settings under:

• interaction.worldguard.allow-open-on-cancelled-interact
• interaction.worldguard.require-plugin-present

PlayerModel shows only a marker or fallback body

If PLAYER_MODEL is selected but admins only see the fallback marker or safety marker:

• verify the intended backend is actually installed
• prefer LibsDisguises for the most reliable full-body result
• treat ProtocolLib-only PlayerModel as the less reliable path
• switch to ARMOR_STAND or ITEM_DISPLAY if you need the most predictable public release behavior

Dead Body logs warnings at startup and when admins select PLAYER_MODEL in the GUI if the dependency path is missing or weak.

Nexo glyph tags show a fallback character instead of the icon

If a nameplate format like this:

format: "&f<glyph:skull> {player} &7(&f{mmss}&7)"

shows a fallback character instead of the glyph:

• make sure Nexo is installed and enabled
• make sure the player has the resource pack
• make sure the glyph ID really exists in the expected font
• make sure the nameplate is being rendered by a build that includes Nexo nameplate support

Dead Body supports literal Unicode/custom glyph characters when the client has the matching font, and it also supports Nexo <glyph:id> and <shift:value> tags when Nexo is installed.

Permissions look correct but players still cannot loot

Check these in order:

1. whether interaction.loot-access.enabled is on
2. whether the relevant require-permission toggle is on
3. whether the player actually has the matching permission node
4. whether a region or another plugin is cancelling the interaction
5. whether you only tested as op instead of as a normal player

MythicMobs filtering does not behave as expected

Check these in order:

1. whether MythicMobs is installed and enabled
2. whether you are using the real internal MythicMob ID
3. whether the filter mode is WHITELIST or BLACKLIST
4. whether you are accidentally testing with a vanilla mob instead of a MythicMob

Mob corpses vanish too early

If disguised mob bodies are disappearing early, review:

• disguise-side tracking assumptions
• view-range choices where relevant
• live server entity tracking settings

Dead Body includes anchor-side mitigation, but live testing still matters when disguise plugins are involved.

Corpse interaction feels inconsistent

Review:

• grounded requirement
• open delay
• post-landing delay
• empty auto-remove
• any other plugin touching entity interaction events

DeathPlus compatibility

Dead Body marks corpse anchors for DeathPlus lookup compatibility. If DeathPlus still fails to focus the corpse correctly, verify the mode you are using and confirm the Dead Body corpse actually exists in the world at the time of the lookup.

Good debug habit

Use one normal player account and one admin account while testing. That separates renderer problems, permission problems, and region problems much faster.

Next pages

• admin Commands and Permissions
• visual Modes, Nameplates, and Renderers
• player Corpses, Loot Rules, and Containers