A content pack's first start rewrote 19 per-state tables one after another
and reopened each zip mod's archive for every file it copied (its whole
index each time). Every start then decoded the atlases' mod textures and
parsed the mods' block models one file at a time on the main thread: with
ATM10's 42 data mods that was about 70 % of the sampled startup.
- mod_content: the tables are rewritten on up to three threads, largest
first; a zip mod's archive is opened once for all its files
(horizon-mods' Content::reader).
- hud::atlas_sprites and ParsedModels::load list their files first, then
decode and parse them on every core (par::par_map, results in the input
order). The sprites come out in the order the one-by-one loop gave, and
the content root is byte-identical.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
With the wide state ids, ATM10's 42 data-tier mods (193,762 states)
reach the world once these loaders stop refusing them:
- Block sprites: eight texture arrays of 2048 layers instead of four
(9,790 block textures for the 42).
- Per-state tables read as NBT: the table limits cover 2^20 states, and
the collision table in level data uses them.
- Worldgen block tags: 2^20 blocks instead of 8,192 (mineable/pickaxe
holds every stone block of a pack).
- As vanilla's loaders do, a blockstate definition that does not bind,
a missing or broken block model of a mod, and a recipe that does not
parse are logged and skipped instead of dropping every mod (or
stopping the game).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>