# 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](https://www.gpui.rs), Zed's UI framework; it has its own Cargo workspace and is not part of the game's builds. ![Play](docs/play.png) The opening, then Play ([clip](docs/opening.webm)): ![Opening](docs/opening-1.png) ## 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) and copies its sounds from your launcher's asset store (`horizon-prepare sounds`; a launcher install without them only leaves the game silent), then starts the client. 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+. Before importing, preparation reuses checksum-verified game jars and libraries from the current or another installed Horizon version, so the original Minecraft install is only required when no valid imported copy exists. - **Mods**: search Modrinth (CurseForge support is coming soon) for resource packs and modpacks, each marked Works, Partly or Doesn't run in Horizon; Java mod jars are never offered. Install puts a pack and what it needs in `resourcepacks/` only after its SHA-512 matches, and a modpack goes to the Modpacks page; installed packs show their source and checksum, with Update and Remove ([docs/mod-browser.md](../docs/mod-browser.md)). - **Modpacks**: import a Java modpack (a Modrinth `.mrpack`, a CurseForge zip, or a Prism, MultiMC or CurseForge instance folder) and see its coverage report: per mod, ported, partial, not yet or not needed, with the reason ([docs/modpacks.md](../docs/modpacks.md)). **Port** gets the jars of what this computer can port today (content mods with data and assets only) the player's own way: copied from a folder they have, or downloaded from the pack's own links or the same file on Modrinth's CDN, hash checked; files only CurseForge has come from your installed instance (CurseForge downloads are coming soon). It carries them over for the selected version, and **Play** starts the game as the pack's own profile (`ports//home/` in the game's home: its own saves and options) with those mods. Nothing is uploaded or shared: mod jars and ports stay on this computer. - **Servers**: host a world for friends with buttons. **Create a server** asks for a name, a world (a new one, with an optional seed, or a copy of one of your single-player worlds), the game mode, difficulty, most players, who can join (friends only, the default, or anyone with the address) and your agreement to the Minecraft EULA; with the defaults (tick the EULA, press Create) you get a friends-only survival world with you as its operator. Each server then has **Start**, **Stop** and **Restart**, its state (also when it crashed and was restarted), players online with their heads, TPS, MSPT and RAM, the address friends on your network type with **Copy**, a console that takes commands, **Open the web panel**, and four tabs: **Overview**; **Players** (online players with Make operator, Kick and Ban; who may join, with Friends only, Let in and Remove; Unban); **Settings** (the message in the server list, game mode, difficulty, PvP, most players, view and simulation distance, port, account checks, **Run in the background and at login**); **Backups** (Back up now, the list with dates and sizes, Restore with a confirmation, Back up automatically, and **Updates**: Check for updates, Update now with its automatic rollback, and how many older versions to keep). Changes the running game can take apply at once, the others say "Restart to apply". Everything goes through `horizon-server` itself ([docs/hosting.md](../docs/hosting.md)): the launcher copies a prepared version's programs and game files into `server-runtime/` laid out as `install.sh` does, runs `horizon-server init`, `config`, `start`, `backup`, `restore`, `update` and `service` there, and talks to a running server through its control API. Problems are said in plain words, with a button when there's a fix (another port, the game files, the EULA). **Friends over the internet** (on Overview) uses Tailscale: it says whether Tailscale is installed and signed in (with Install, Sign in and Check again; signing in is always yours, in Tailscale's own app or page), shows this computer's Tailscale name and address with **Copy**, and invites a friend to this one computer: in the admin console, or here with an access token you make there (kept in the system keychain), which also lists invitations with Withdraw / Stop sharing and offers **Limit them to Minecraft**: when your tailnet has Tailscale's default access controls, one click changes them so friends you share with reach only the server's port (Remove the limit undoes it); custom access controls are never rewritten, the page gives the rule to add instead. Horizon never turns on Funnel. - **Instances**: separate game folders, each with its own worlds, options and packs. The game's folder stays the first one, "Horizon", exactly where it was; imported and registry modpacks are instances too, in their own folders as before; new ones go to `instances//` in the game's folder, empty but for the player's options and name, or a copy of another instance (never its sign-in sessions, logs or data collection state). Names, icons (a block or item texture from the player's prepared files, or a colour) and groups are kept in `instances.json` in the launcher's data folder, so renaming moves nothing. Every instance follows the launcher's data collection answer and No AI. In the window, **+** beside Instances makes one, the sidebar lists them by group (click one to play it), and Home's Instance row has Edit (name, group, icon), Copy and Open folder. The Instance row shows its play time and when it was last played: every run started from the window or `horizon-launcher play` adds to it (`instance list` shows it too). Each instance plays the launcher's version, which follows updates, unless the Play page's version picker keeps it on another installed one (to keep an old world on the version it was made with); picking the version marked "follows updates" lets it follow again. - **Worlds**: Home lists the selected instance's worlds (picture, mode, version, last played, size). **Back up** zips one into the instance's `backups/` as the game's Make Backup does (`_