2822d4e1b7
Loading the eight carried-over mods in the game (not only the probe) showed two limits real packs reach. Block textures past 2048 layers are another PR; this one handles block states and measures a pack. - Chunk sections store a block state in 16 bits. Vanilla 26.3 has 35,723 states; Macaw's four mods add 36,154, the eight 41,389. Past 65,536 ids wrapped onto other blocks (a trapdoor became a hanging sign). mod_content::build now refuses a set of mods past MAX_STATES and names the states per mod; the game then starts without content mods, as for any refused content. - tools/mod_port_harness.py probes each mod on its own against vanilla, as a player adding it would load it. - tools/perf_bench.py --game neoforge: Minecraft 1.21.1 on NeoForge 21.1.259 with --mod-jars and --deps, driven by a dev-only NeoForge port of the bench mod (mods/horizon/src/neoforge-bench); --port-work loads a work folder's carried-over mods into Horizon. tools/neoforge_oracle.py installs the client once under .local/neoforge-oracle (the installer, then the vanilla libraries it inherits, sha1-checked) and builds the driver. A NeoForge start that crashes before the driver loads (FML reading fml.toml while creating it) is retried once. Measured (docs/modpacks.md): six ported mods in Horizon against the same mods on NeoForge, Mac mini M4 Pro, 2 games per row on a loaded machine. The world is ready 3.1x sooner at 8 and 16 chunks, the flights run 1.7x and 3.6x the frames, and Horizon's RSS is not lower (+1.1 GB with the mods). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Horizon documentation
To play, use the launcher; the project site is playhorizon.dev. These pages are for developers.
Build and run
- Build from source: your own copy of the game, resource preparation,
cargo run. - Native client: options, controls, the dedicated server,
horizon-ctlscripting, packaging, architecture. - Agent control: what AI agents can drive in the launcher and the game, and the design of the control socket,
horizon-ctland MCP. - Graphics: the Simple and Advanced graphics settings, the graphics benchmark and what it measured.
- Benchmark: Horizon against vanilla 26.3 and vanilla with performance mods, on the same machine, world, path and settings: what is measured, how it is kept fair, how to reproduce it.
- Shader packs: how the renderer draws a frame, the Horizon WGSL shader pack format (stages, uniforms,
pack.toml, hot reload), and the plan to translate OptiFine/Iris packs. - Extras: optional zoom, minimap, FPS and keystroke overlays and auto-reconnect, all off by default.
- Mods: Horizon's own mod system (Rust, sandboxed WebAssembly), how to make and install mods, and what carries over from Java mods.
- Modpacks: porting whole packs (ATM10 and smaller): import, inventory, carry-over, an agent per mod with a harness against the Java original, coverage, and how "10x" is measured.
- Launcher: installs, updates and starts builds; its CLI and MCP server; releasing it.
- Resource packs: everything a 26.3 resource pack can change, whether Horizon honours it, and the proof.
- Opt-in data collection: the consent, exactly what is sent, how it is stored and sent.
- Benchmark report format: the versioned JSON every benchmark writes (game, launcher,
tools/perf_bench.py), the local log and, with consent, the upload. - Menus: the title, world list, create world, multiplayer, options and pause screens share the launcher's design tokens and fonts (
crates/horizon-theme), drawn byui_themeover a live frozen backdrop (game/backdrop.rs, blurred and graded bypost.rs). Options → Interface → Menu style switches to vanilla's screens (Classic, kept inhorizon.txt;HORIZON_MENU_STYLE=horizon|classicoverrides it, and scripted runs default to Classic). Title (webm), worlds, options, pause.
Parity
- Rust rewrite status: completion criteria, how to reproduce the validation, and per-area scope.
- Parity workflow:
tools/parity.py, the gate, other machines, merging. - Area notes: block behaviours and ticking, section meshing.
- Version ports: how a new Minecraft release is detected, diffed against the pinned one and ported, and what stays manual.
- Decompilation and research lab and decompilation status: the local game inspection workspace the harnesses build on.
Architecture: world generation
- World generation: the pipeline from noise to features.
- Noise generation, compiled density functions, structure density, terrain filling.
- Biomes: lookup, temperatures.
- Surfaces: material surfaces, material conditions, rule libraries, vertical anchors, value providers.
- Carving, heightmaps, feature placement.
Architecture: world data and simulation
- World data: chunk storage, palettes, region files.
- Block-state codecs, scheduled ticks.
- Collision geometry: shapes, collision, movement and fluids.
- Face visibility: which model faces the mesher emits.