32f5f01e22
The harness the modpack design calls for, for data-tier mods: - tools/neoforge_oracle.py installs a NeoForge 21.1.259 server (ATM10's) under .local/neoforge-oracle, builds the exporter in mods/horizon/src/neoforge-oracle (our code, never shipped), runs it headless with the user's jars and writes every block (class chain, states, per-state hardness, light, tool need, map colour, sounds, outline and collision; drops for hand, diamond tools, shears and silk touch; placement; BlockSetType and WoodType), item, recipe and tag of the mods' namespaces, plus the vanilla blocks for templates. About 30 s. - examples/mod_port_probe.rs builds the content root from the carried mods and dumps what Horizon's loaders make of the same things. - tools/mod_port_harness.py compares them per mod and writes <work>/mods/<id>/harness/result.json. 1.21.1 sound events map to 26.3's through vanilla blocks both have, and vanilla items newer than 1.21.1 are not counted against a recipe. On ATM10's own jars (MIT): Macaw's Trapdoors passes everything; Doors, Fences, Paths, Glassential, Factory Blocks and Cloud Glass pass every drop, recipe, tag and placement and fail only on what API 0.2 cannot say (shapes and sound events of their own, blocks of classes no vanilla block shares). Jars, facts and results stay in the work folder. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>