-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
Start with logs/latest.log — search it for [CIT]. Those lines are the mod's whole conversion run: which pack files it saw, which it recognised, and what it built. They answer most of what's below.
A healthy startup with the Mizuno packs installed looks roughly like this:
[CIT] found pack Mizunos_16_Craft_JE_CIT_1.19.4-1.1.zip (cit entries: 2792, minecraft textures: 0)
[CIT] pack Mizunos_16_Craft_JE_CIT_1.19.4-1.1.zip classified as 'mizuno' (cit entries: 2792, ...)
[CIT] scan complete: 2 pack(s), classified: [mizuno], ...
[CIT] basepack textures embedded: 134 | models rewritten: 887 | unresolved vanilla refs kept: 3
[CIT] model pipeline: ... jobs converted, 0 skipped, ... models total
Almost always: no supported pack is in the resourcepacks folder. When you join a world the mod says so in chat, and the log contains:
[CIT] no supported CIT pack installed - furniture disabled (put the Mizuno CIT resource pack into <path>)
Check, in order:
- The pack
.zipfiles are in the folder that warning names — that's the one the game is actually using, which may not be the instance you were looking at. - They are still
.zipfiles. An unzipped folder is not read. - You restarted the game after adding them. Packs are scanned once at startup.
- The pack is one of the supported ones — see Supported Packs.
Enabling the packs in the in-game pack menu is not required, so that isn't the problem.
If the log has a found pack line but no matching classified as line, you'll see:
[CIT] CIT pack <file>.zip matches no supported pack fingerprint
The mod recognises supported packs by their contents, not their file names. This message means the file is a CIT pack it doesn't have support for — either a pack that isn't supported at all, or an edited/very old copy of one that is. Try a fresh download from the official page.
(One matches no supported pack fingerprint line for the regular Mizuno pack is normal and harmless — that pack is used for its textures, not its furniture.)
Each pack you don't have is reported at the end of registration:
[CIT] pack 'Heritage Deco': 145 blocks not available (pack not installed or models missing)
That's expected for packs you simply haven't installed. If a pack you did install shows up here, it wasn't classified — see the section above.
You're missing the regular Mizuno's 16 Craft pack. Some CIT furniture reuses textures from it, and without it those pieces fall back to vanilla ones. Watch this line:
[CIT] basepack textures embedded: 134 | models rewritten: 887 | unresolved vanilla refs kept: 3
With the regular pack present, embedded is a large number and unresolved is small. embedded: 0 with a high unresolved count means the regular pack isn't being found. Both Mizuno packs need to be in the folder — see Installation.
A handful of unresolved references is normal; some packs reference texture names that don't exist in their own files.
The server has no packs, so it registered zero furniture blocks — it rejects every placement and the client rolls it back. The server log will contain:
[CIT] resourcepacks directory not found: <path>
[CIT] no supported CIT pack installed - furniture disabled
Fix: put the pack zips in a resourcepacks folder at the server root and restart. Full layout and steps: Multiplayer.
Common cause on hosted servers (Exaroton, Aternos, Apex...): the packs were added through the panel's "resource pack" option. That's Minecraft's push-to-players feature — a different system the mod can't see. The packs must be files in the folder.
A flood of server-log errors like Couldn't parse element mizunodeco:blocks/... is the same problem (loot data for blocks that never got registered) and disappears with the fix.
Check the crash report for the first Caused by line.
-
Fabric:
fabric-apimissing — install Fabric API. - Forge: not supported. Use NeoForge or Fabric.
- Anything else: please open an issue with the crash report and
latest.logattached.
Blocks only exist while the pack that defines them is installed. Remove a pack and its furniture is gone from your world, and the game reports unknown block entries when loading it. Put the pack back and the furniture returns — nothing is lost as long as you don't play on and save the world without it.
For the same reason, keep your pack set stable in worlds you care about, and back up before removing a pack.
Open an issue with:
- Loader and version, mod version, Minecraft version
- Which packs are in your
resourcepacksfolder -
logs/latest.logattached (and the crash report if it crashed)
The log is the important one — without it most reports can't be diagnosed.