ddc115e969
Loading seven real NeoForge mods carried over by horizon-port-pack (about 1,000 blocks) broke the content root in four places: - The per-state NBT tables (cached collision, occlusion, movement, worldgen block properties and support) passed the NBT reader's 1M-node cap once mod states were appended. They are trusted prepared tables with a row per state, so they now read and write with Limits::tables() (16M nodes, 256 MiB) everywhere they are loaded. - The overlay linked the base root by the path it was given, so a relative base gave dangling links. The base is made absolute first. - Carried-over tags name blocks the port left out and other mods' items. Vanilla fails such a tag as a whole; entries naming ids nobody registers (or tags nobody defines) are now dropped, so the rest loads. - Mods use the convention tags (c:dyes/red, c:glass_blocks/colorless). Content mods may add to data/c/tags/ as to vanilla's, and with content mods loaded the tag loaders read the c namespace and the mods' own. Stonecutter and smithing recipes in mod namespaces load too (ids <ns>:<name>), as crafting and cooking ones already did. With no content mod nothing changes: the loaders read the minecraft namespace only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>