Files
horizon-airdef/launcher

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, and Java 25), then starts the client, or a server (--dedicated --nogui) in a folder you choose, with a live console. Preparing is horizon-prepare: linked into the launcher, used in-process when a version ships the same preparer sources, else that version's own horizon-prepare; versions released before it still prepare with their Python script and need Python 3.10+.
  • Patch notes: each release's notes, newest first, with a link to GitHub Sponsors. Quiet "Join Discord" and "Website" links sit in the sidebar footer.

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 (on unless you turn it off; the selected version only moves to the new one if you were on the newest), the opening animation, the game's menu style, and the launcher's own version and update state.
  • Menu style: Horizon's own menus or Classic (vanilla's screens). Classic has no way back inside the game, so the launcher is where you return to Horizon's. It is the menuStyle: line of horizon.txt in the game's home folder (HORIZON_HOME, else horizon in the data directory), which the game reads when it starts.
  • Links: the Discord invite, the Sponsors page and the website come from launcher/links.json on main ({"discord": "...", "sponsor": "...", "website": "..."}), so they change without a launcher release. Offline, the launcher uses the same values built in; an empty address hides its button.

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 links                          the Discord, sponsor and website links
horizon-launcher menu-style [horizon|classic]   show or set the game's menu style
horizon-launcher update [--check]               Horizon and the launcher

--json prints JSON where there is something to report (versions, install, notes, next, links, menu-style, 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, links, menu_style 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 (or a launcher-* one), then installs the latest Horizon into a temporary folder and checks that the client starts (--help) and that the binaries import only system libraries (Windows).

cargo test --lib    # tag separation, version order, update selection, notes as text,
                    # the auto-install default, the links fallback, the menu style file

Geist, Geist Mono and Instrument Serif (SIL Open Font License, crates/horizon-theme/fonts/OFL-*.txt, shared with the game's menus) 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