002cfcd859
horizon_client::mod_content builds the resource root for content mods as an overlay over the base root (vanilla, or the resource-pack overlay): - the base is linked; - the block and item tables are rewritten, each mod block getting its template's rows appended. That covers 13 JSON tables (facts, gameplay, behaviours, models, render, landing, items, command registries, mob data, worldgen flags, structure, survival) and 6 NBT ones (occlusion, collision, support, movement, worldgen block properties). Names, translation keys and in-table state ids move over, and the declared overrides apply; - each mod's own assets/ and data/ are copied in; - tag additions are merged into the tag files and both block-tag bundles. Vanilla state ids never move: mod states come after them, mods and blocks in id order. Rewritten JSON keeps its key order. With no content mod the root is the base itself. The game doesn't call this yet. Tested over the real prepared resources: every loader reads the overlay (Assets, BlockFacts, Items, collision, visibility, light, motion, worldgen GeneratorData). The mod blocks carry their templates' facts with the overrides applied, and vanilla's rows and ids are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>