If something goes wrong, a short debug session is usually enough to collect useful information for an issue report.

Easy NPC currently exposes these debug commands:

/easy_npc debug core <true|false>
/easy_npc debug npc <NPC>
/easy_npc debug config <true|false>

Use debug core for the main mod logic. Use debug npc when one specific NPC behaves differently from what the server claims. Use debug config for the Config UI module.

Enable debug only while reproducing the problem, then disable it again.

/easy_npc debug npc <NPC> prints the current server-side state for the selected NPC.

This is especially useful for multiplayer or dedicated-server issues where:

• a name change reports success but does not update visually
• a skin change appears to do nothing
• scaling or height changes feel out of sync

The command includes:

• custom name
• name visibility flag and attribute
• skin type, name, URL, UUID, and layer state
• current variant
• root scale and root rotation
• effective entity dimensions and bounding box height

For sync issues, it helps to run the command before and after reproducing the problem and then attach the output from latest.log or debug.log.

Check these files after reproducing the issue:

• logs/latest.log
• logs/debug.log

If the issue is tied to one NPC, you can often help by providing:

• the relevant preset export
• the exact commands used
• the output of /easy_npc debug npc <NPC>
• the NPC data copied with F3 + I while looking at the entity

Some of these actions require operator permissions.

Try to include:

• Minecraft version
• mod loader
• Easy NPC version
• other relevant mods
• exact steps to reproduce
• affected commands, dialogs, or presets
• latest.log or debug.log if useful

• check if the issue already exists
• test with the smallest possible mod list
• verify whether the problem also happens in a fresh test world