Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Install a local unsigned developer base

developer-install installs a game executable built from a trusted checkout. This is a separate launcher installation command, not a native mod build route. It runs the checkout's packaging code with your rights and requires --trust-unsigned.

Commit tracked changes, build the game and companion programs, generate the wasm standard library beside the game, and prepare compatible exporters from your own Minecraft installation before installing. The packager copies horizon-wasm-std.wasm from the game's folder for every developer base, whether the mods you build are native or wasm; the command names it if it is missing:

cargo run --locked -p cargo-horizon-mod -- wasm-std CHECKOUT/target/debug/horizon-wasm-std.wasm
horizon-launcher developer-install CHECKOUT --program CHECKOUT/target/debug/horizon-client --trust-unsigned

The install needs these files. The checkout's packager (cargo run -p xtask -- package, and package-server for a server folder) checks them all before it writes anything, and names every missing one in one message with the command that makes it. Its list is crates/horizon-mod-package/src/sdk/inputs.json; a test keeps this table equal to it. In the commands, PROFILE is the cargo flag of the profile the game program was built with (--release for target/release, nothing for target/debug), PROGRAM_FOLDER its folder, and on Windows the programs end in .exe:

FileWhereNeeded byHow to make it
horizon-ctlbeside the game programpackagecargo build PROFILE -p horizon-client-lib --bin horizon-ctl
horizon-preparebeside the game programpackage, package-servercargo build PROFILE -p horizon-prepare
horizon-serverbeside the game programpackage, package-servercargo build PROFILE -p horizon-server
horizon-wasm-std.wasmbeside the game programpackage, package-servercargo run --locked -p cargo-horizon-mod -- wasm-std PROGRAM_FOLDER/horizon-wasm-std.wasm
exporters/manifest.jsonin the checkoutpackage, package-serverhorizon-prepare compile-exporters --root CHECKOUT, then copy its server, client and manifest.json into CHECKOUT/exporters/

The command returns a developer-… tag. Select that exact tag, prepare its resources, and pin an instance to it. Automatic updates do not replace a local unsigned base. Remove it with horizon-launcher remove DEVELOPER_TAG when no instance needs it.

A native mod build needs the prebuilt SDK of the base's exact commit. For a commit without a published SDK, build it from the same checkout and name its folder; one folder holds one side:

python3 tools/prebuilt_game.py build SDK_FOLDER            # add --server for a dedicated server
HORIZON_LAUNCHER_DEVELOPER_SDK=SDK_FOLDER horizon-launcher native-build MODS --version DEVELOPER_TAG --trust-native-code

The variable is read for developer bases only, and the folder is used where it is. It must be that commit's build for this computer, side and the launcher's Rust, as a downloaded SDK must; anything else is refused. Without it, the launcher uses the commit's SDK release when one is published, and otherwise says the build has no mod tools. The native mod builder never compiles the checkout itself. For native mixins, the pinned source must also be available for copying the target functions.