Troubleshooting¶
Custom content fails in a small number of ways, and each has a distinct look.
Items render as a plain chest, paper or barrel¶
The dispatch entry was pruned, or the item's assets were never copied.
Check the startup log for the Pruned count. Then confirm the pack layout is
one Ember Forge reads — resourcepack/assets/<ns>/ or resourcepack/<ns>/ —
and that models and textures actually sit under that namespace.
Items render as magenta-and-black checks¶
A model resolved but its texture is missing. Ember Forge prunes these before publishing, so seeing this means the pack was built by something else, or the texture is referenced from a model the validator could not parse.
Vanilla items are invisible¶
A pack overrode a vanilla model — say models/item/iron_pickaxe.json — and
pointed it at a texture it does not ship. Every plain iron pickaxe then renders
as nothing, in inventories and in hand.
Ember Forge deletes such overrides so the client falls back to its own model. If you see this, something else is building your pack.
The ItemsAdder ia:NNN case
ItemsAdder rewrites texture paths to a short ia:NNN form when
short_texture_references is enabled, and only emits that namespace when
texture protection is on. Enable one without the other and every reference
is dead. If you have uninstalled ItemsAdder, nothing will ever regenerate
them — read contents/ instead of its generated.zip.
The pack downloads, then nothing changes¶
The client cached a pack with the same hash. Confirm the served hash matches:
"Failed to download resource pack"¶
Usually the URL is unreachable from outside, or the hash does not match the bytes. Fetch the URL from a machine that is not the server.
Nothing was scanned¶
scan-paths is wrong, or the configs are not where the format expects:
ItemsAdder uses <pack>/configs/*.yml, Oraxen and Nexo use <pack>/items/*.yml.