Fixing Broken Models and Animations with Citadel

Most players only learn Citadel exists when something built on top of it misbehaves. If a mob from a Citadel-based mod is invisible, frozen, stretched, or stuck in a default pose, the problem is almost always in how the model or animation was loaded, not in your world.

Diagnosing the symptom

• Invisible or missing model: the model file failed to load. Check your log for parsing errors mentioning the mod's asset path.
• T-pose or frozen animation: the animation controller never received a state change. This usually means a missing or malformed animation definition.
• Wrong scale or offset: the model's pivot or scale values are off, often after a mod update.

What you can actually do

As a player, your leverage is limited — Citadel is a library, and the model data lives in the dependent mod. Your job is to isolate the problem cleanly:

1. Reproduce the issue in a fresh world with only Citadel and the one affected mod installed.

2. Grab the Citadel Debugger and inspect the broken entity to capture its reported state.

3. Check the log for the specific asset path that failed.

4. Report the mod name, the entity, the log line, and the debugger output.

If the issue disappears with only those two mods loaded, another mod is interfering. If it persists, it is a bug in the dependent mod's assets, and the author needs your log.