KubeJS recipe or tag silently does nothing

The failure mode nobody notices

You write a recipe, a tag, or a quest reward referencing minecraft:diamond_swrd. Nothing crashes. Nothing appears in the log. The recipe simply does not exist, and you find out when a player asks why the quest gives nothing.

This is the worst class of modpack bug precisely because it is silent. A crash tells you where to look; this tells you nothing at all.

Why it is silent

Most registry lookups resolve an ID to "absent" rather than throwing. A recipe referencing a missing item is skipped. A tag entry pointing at nothing contributes nothing. From the game's point of view nothing went wrong — you asked for a thing that does not exist, and it obliged.

Where these hide

• Diet and food tags — a typo means a food has no diet category. Entirely invisible until someone notices their nutrition never fills.
• Quest rewards — the quest completes and gives nothing.
• Recipe inputs — the recipe is absent from JEI; most people assume it was never added.
• IDs from a mod you removed — every reference to it is now dead, and there may be hundreds.

Finding them

The reliable method is to build an index of every ID your installed jars actually register, then check everything your scripts, configs, datapacks and quests reference against it.

Two things make the difference between a useful report and noise:

• Only compare the path, not the whole ID. A shared namespace contributes identical characters to both strings and inflates every similarity score. Comparing whole IDs on a real pack produced 169 "typos", most of them nonsense like alicepack → icepick (0.905 on the full ID, 0.750 on the path alone). Path-only comparison cut that to 63.
• Know that packs register their own content. KubeJS startup scripts create items that exist in no jar. Treating those as unknown IDs buries the real findings.

Tag namespaces are not registries

forge: and c: are tag namespaces. IDs in them legitimately do not correspond to any registered item, so reporting them as missing produces pure noise. Likewise a leading # means a tag reference, not an item.

Pack Doctor does this — the free edition inventories your mods and catches duplicate jars; the full version validates every referenced ID.

Doing this automatically

Forge Server Doctor performs the whole procedure above — reads the report, finds the real cause under the wrappers, skips the vanilla frames, and names the mod jar. 24 failure modes, each with its fix. The free edition covers the six most common startup failures.