Allowing Resourcepacks With Illegal Paths in CIT Resewn

guide

CIT Resewn reads custom item textures from resourcepacks, and its configuration screen controls how strictly it treats pack contents. This guide covers the Allow broken paths in resourcepacks setting and the warning you will see on packs that need it.

What Broken Paths Are

A resourcepack normally stores its files under paths that follow the game's naming rules. Some packs ship files under paths that break those rules. The game's own loader rejects such packs outright, which means none of their contents — including their custom item textures — ever get applied.

Allow broken paths in resourcepacks changes that. Its description reads: allows packs with illegal resource paths to load, and it carries the caution that this may cause issues. Turning it on lets CIT Resewn accept a pack whose internal paths would otherwise be refused, so the pack can load and its cits can be injected.

Because the setting deliberately bypasses a safety check, treat it as a compatibility escape hatch rather than something to leave on permanently. Enable it when a specific pack requires it, and disable it once you no longer need that pack.

The Broken Paths Warning

When a pack contains illegal resource paths, CIT Resewn flags it in the pack list with the marker (Contains broken paths). Hovering or selecting that pack also shows a longer notice:

The pack holds broken paths.
Support for packs like it may be removed in a future release.
The pack author should be contacted so the warning can be eliminated.

The notice is signed by CIT Resewn. It is informational — it tells you the pack is relying on lenient path handling, not that the pack has failed to load.

If you want the pack to keep working, turn on Allow broken paths in resourcepacks. If you would rather not depend on a setting that could disappear later, ask the pack's author to fix the offending paths. Either way, the warning itself is not an error and does not need to be silenced.

Two settings control how much noise CIT Resewn makes about cit problems:

Mute loading errors — when enabled, cit errors are not written to the log.
Mute loading warnings — when enabled, cit warnings are not written to the log.

These affect logging only. They do not change whether a pack loads, and they do not remove the broken-paths marker from the pack list. Use them if your log is cluttered; leave them off while diagnosing a pack.

Other Configuration Entries

The configuration screen also holds:

Should CIT Resewn load and inject cits from resourcepacks — the master switch for the mod's core behaviour. With it off, no cits are read from packs at all.
A cache refresh interval setting. Its description explains that a higher value improves performance, a lower value makes cits update sooner, and the REALTIME option drops the cache completely so items are checked for cits every frame.

Operating the Settings

Open the CIT Resewn configuration screen and toggle the entries described above. No crafting, items, or in-game objects are involved — everything is handled through the interface.

The mod's actions are also bound to hotkeys. To trigger an action by key, assign the corresponding hotkey in the controls menu; no default binding is assumed here.

Practical Order of Operations

Notice (Contains broken paths) next to a pack, or read the full warning text.
Decide whether you trust the pack enough to relax path checking.
Enable Allow broken paths in resourcepacks if you do.
Leave Mute loading errors and Mute loading warnings off while testing.
If the pack misbehaves, disable the setting again and report the paths to its author.

Keeping the setting off by default and enabling it only for packs that genuinely need it avoids the issues the description warns about.