☰

Custom Model Data Crash

An item with custom model data fails to render or errors, usually from a resource pack or a plugin assigning models. The model reference is invalid or missing for that item.

What does this error mean?
CustomModelData lets one item display different models based on a number. An 'invalid custom model' issue means the pack does not define a model for the value used, or the model JSON is malformed, so the item cannot render correctly. 
Invalid custom model
Most Common Causes
  • A resource pack missing the model for a CustomModelData value.
  • Malformed model JSON for the custom item.
  • A plugin assigning a CustomModelData the pack does not have.
  • Wrong model paths or names.
  • A pack_format mismatch hiding the model.
How To Diagnose
  1. Identify the item and CustomModelData value involved.
  2. Check the pack's item model JSON for that value's override.
  3. Confirm the referenced model file exists.
  4. Validate the model JSON.
Recommended Fixes
  • Add the model override
    Define the CustomModelData override in the item's model JSON, pointing to a real model.
  • Fix the model JSON
    Correct syntax and paths so the custom model loads.
  • Align plugin and pack
    Make sure the plugin uses CustomModelData values the pack actually defines.
  • Match pack_format
    Set the correct format so overrides load on your version.
Analyze My Log
Frequently Asked Questions

An item tag (a number) that tells a resource pack which custom model to show for that item.

Usually the pack has no override for that number, or the model file/path is wrong.

Models render client-side, but a plugin often sets the value server-side, both must agree.