Files
horizon-airdef/launcher
Ludovic Marie 8cdec2c8d9 Tidy the repository now that parity is reached: launcher-first README, docs index, research leftovers removed
Removed (each unreferenced by code, workflows, tests or living docs; no harness
dependency record names any of them, and parity.py --list still finds all 281):
- 22 one-off write-ups of the Java-pack experiments in docs/: adaptive-terrain,
  client-graphics-smoke, compact-headers, core-performance, culling-empty,
  culling-rays, debounce-queue, dispatch-retry, foreground-first,
  graphics-api-comparison, heap-budget, mac-first-test, optimization-plan,
  playable-validation, quad-reuse, server-graphics-context, shader-world-smoke,
  terrain-measurements, terrain-position, terrain-read-wait, tick-membership,
  worker-pacing. Their findings are folded into one paragraph of java-packs.md.
- 24 benchmarks/ observation dumps only those write-ups linked (client graphics,
  culling, queues, heap, Mac Vulkan, shader worlds, software identity, and the
  unlinked rust-core, rust-worldgen-2026-10-05, rust-native-client and
  rust-cuboid-model-decoding runs), plus 12 unlinked files inside kept
  report folders. The scoped-parity reports the living docs cite stay.
- debug/: one server log from a chunk investigation.
- The manual macos-shader-research and macos-vulkan-research workflows.
- tools/logs/latest.log, an empty log committed by accident (now ignored).

Kept: research-lock.json (parity.py, packaging, the launcher and datafix read
it), the Java-pack how-tos (vulkan, collectors, profiling, process-memory,
tick-state) and tools/test_client_graphics.py (ci.yml runs it).

README: leads with what Horizon is and "Download the launcher" (the
launcher-v* releases; the launcher updates itself), then build from source
for developers. Direct game downloads and PLAY.txt steps for players are gone;
the launcher has its own section with two screenshots. The roadmap merges the
known differences, the final checks and the plans after parity, under the
"Roadmap" heading the launcher's What's next page reads. The parity table and
its 100%-of-what-the-harnesses-compare note are unchanged.

docs/README.md indexes what remains: build and run, parity (status and
workflow), world generation, world data and simulation, the old Java track.
Links to the removed pages and README anchors are fixed.

packaging/PLAY.txt now speaks to players who came through the launcher and
points anyone with a bare archive to it, keeping the manual steps short.

The launcher's README link points at main instead of the launcher branch.
.gitignore: tools/logs/ and .DS_Store. No code behaviour changes; the compiler
and clippy flag no unused code and the tree has no stale TODOs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 14:16:55 +02:00
..

Horizon launcher

A small desktop app that installs Horizon builds, prepares them from your own copy of Minecraft, and starts the client or a dedicated server. Built with GPUI, Zed's UI framework; it has its own Cargo workspace and is not part of the game's builds.

Play

The opening, then Play (clip):

Opening

What it does

  • Versions: lists the published releases of ludovic111/horizon, installs the build for this platform into its own folder, and removes it again.
  • Play: prepares resources as PLAY.txt describes (your launcher's 26.3 install, the 26.3 server jar from that version's own json, Python 3.10+ and Java 25), then starts the client, or a server (--dedicated --nogui) in a folder you choose, with a live console.
  • Patch notes: each release's notes, newest first, with a link to GitHub Sponsors.
  • What's next: the README's roadmap, from main.

Data lives in the platform's data directory (~/.local/share/horizon-launcher on Linux, ~/Library/Application Support/horizon-launcher on macOS, %APPDATA%\horizon-launcher on Windows): versions/<tag>/, server-jars/, server/ and settings.json.

  • Settings: install new Horizon versions automatically (off by default; the selected version only moves to the new one if you were on the newest), the opening animation, and the launcher's own version and update state.

Updates

The launcher looks for a newer Horizon release when it starts and every four hours while it is open, and shows a small "available, Install" line on Play.

It also updates itself from GitHub releases tagged launcher-vX.Y.Z (Horizon's own are vYYYY.MM.DD; neither is ever taken for the other). It downloads the new build, replaces its own binary, and offers "Restart to update" in the sidebar. Development builds and HORIZON_LAUNCHER_NO_SELF_UPDATE=1 never replace themselves.

To release the launcher: set version in Cargo.toml, then push a tag launcher-vX.Y.Z. The launcher workflow builds Linux, macOS and Windows and attaches horizon-launcher-linux-x86_64.tar.gz, horizon-launcher-macos-arm64.zip and horizon-launcher-windows-x64.zip to a draft release of that tag, never marked latest. Publish it by hand.

Command line

The same binary is a command-line tool; without a subcommand it opens the window.

horizon-launcher versions [--installed]       releases on GitHub, or what is installed (* = selected)
horizon-launcher install <tag|latest>
horizon-launcher remove <tag>
horizon-launcher prepare [--minecraft <dir>] [--version <tag>]
horizon-launcher play [--version <tag>]
horizon-launcher server [--dir <dir>] [--version <tag>] [--accept-eula]
horizon-launcher notes [<tag>]                  patch notes as plain text
horizon-launcher next                           the roadmap
horizon-launcher update [--check]               Horizon and the launcher

--json prints JSON where there is something to report (versions, install, notes, next, update --check). Errors go to stderr with exit code 1. server runs in the terminal, so lines you type reach its console. HORIZON_LAUNCHER_HOME replaces the data folder (for scripts and tests).

AI agents (MCP)

horizon-launcher mcp is a Model Context Protocol server over stdio. To use it from Claude Code:

claude mcp add horizon -- horizon-launcher mcp

(with the full path to the binary if it is not on your PATH). Its tools: list_versions, install_version, remove_version, prepare_resources, launch_client, start_server, server_command, server_log, stop_server, patch_notes, roadmap and check_updates. A server started through MCP stops (cleanly, with stop) when the session ends. Starting one needs accept_eula, which an agent should only pass with the player's consent.

The window, the command line and the MCP server all call the same core, src/backend.rs.

Building

cargo build --release

On NixOS, nix-shell in this folder provides the libraries GPUI links to (Wayland, X11, xkbcommon, Vulkan, fontconfig). macOS needs Xcode's command line tools. The launcher workflow builds all three platforms on every push to the launcher branch.

cargo test --lib    # tag separation, version order, update selection, notes as text

Geist, Geist Mono and Instrument Serif (SIL Open Font License, assets/fonts/OFL-*.txt) are bundled so the type is the same on every platform.

Background image (assets/background.jpg): backgrounds.supply (free preview), licence to confirm before release.

Screenshots

Server Versions Patch notes Settings