Files
horizon-airdef/docs/api/mods.md
T
Ludovic Marie 0a1d3a7534 Horizon APIs: the docs portal and the stability and versioning policy
docs/api/ gets one page per surface other programs build on (mods,
shaders, agent control, servers, the launcher, data formats), each with an
overview measured from the source, the guide, the generated reference, examples,
its stability, what is not there yet and a changelog, plus the policy every
API follows (docs/api/stability.md): a version per API, semver lines,
experimental / preview / stable, deprecation windows, compatibility tests and
the level of every part today.

The website gets a "Build on Horizon" page (website/docs/apis.md) that
summarises them and links the repository's pages.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-24 20:50:20 +02:00

4.4 KiB

Mod API

Mods are Rust crates compiled to sandboxed WebAssembly components. They run in the player's game and, once server mods land, wherever a world is simulated. Design and the runtime: mods.md.

Overview

A mod today can read the local player and the world clock, show chat lines only that player sees, draw a text panel on the HUD, keep small files of its own, register chat commands, and run on every tick, frame or chat line it asks for. A content mod adds blocks and items from JSON in its .hmod, copying vanilla templates, plus tags, recipes, loot, models, textures and structures in its own namespaces. Every capability is declared in the manifest, shown to the player before the mod is turned on, and checked against the component's real imports.

Count
Interfaces the game offers 5: log, game, chat, hud, storage
Functions in them 9
Hooks a mod exports 5: init, tick, frame, command, chat
Capabilities 5: game-read, chat, hud, storage, registries
Manifest api lines served 2: 0.1 (code), 0.2 (content)
SDK the Mod trait (5 methods), Registration (4 builders), export_mod!, log helpers
cargo horizon-mod new, build, run
Example mods coords-hud (code), ruby-content (content)

Guide

  1. rustup target add wasm32-unknown-unknown, cargo install --git https://github.com/ludovic111/horizon cargo-horizon-mod, then cargo horizon-mod new my-mod (Making a mod).
  2. Implement Mod for your type, list the capabilities you import in horizon-mod.toml (The manifest).
  3. cargo horizon-mod run builds the .hmod and starts the game with it as a dev mod; after an edit, cargo horizon-mod build and the running game reloads it.
  4. Content mods: Content mods (API 0.2).

Reference

mods-reference.md, generated from crates/horizon-mod-sdk/wit/horizon.wit: every capability, interface, type, function and hook, with the limits the guide lists (16 HUD lines of 256 characters, 8 chat lines per call, 4 MiB of storage, fuel per call).

Examples

  • crates/horizon-mod-sdk/examples/coords-hud: coordinates, facing and time on the HUD; /where, /coords; storage.
  • crates/horizon-mod-sdk/examples/ruby-content: no code; a gem and a block of ruby from vanilla templates, with their recipes, loot, tags, models, textures and names.
  • crates/horizon-mods/tests/guest: a mod that misbehaves on command (spins, panics, grows its memory), for the sandbox tests.

Stability

Preview (stability.md): API 0.1 and content 0.2 are served together; a mod built for 0.1.0 keeps loading on every 0.1.x game. Block entities (draft #1189, api = "0.4") are experimental.

Not there yet

What real mods need next, in the order modpacks and servers need it:

  • Server mods: the same component running on the server thread and the dedicated server, with world events (block broken or placed, entity spawned or killed, player joined or left), game rules and server commands with typed arguments.
  • World and blocks: read blocks, block states and biomes in loaded chunks; change them through the server's block log, so clients and the parity harnesses see vanilla's updates.
  • Items and inventories: the player's inventory, held item and open container; item stacks with components.
  • Entities: query and change entities near a position; spawn from a mod's own entity types (data first).
  • Block entities and menus: ticking machines with slots and their screens (draft #1189 is the first step).
  • Screens and UI: widgets built from vanilla's, a screen the mod owns, a settings page under Options > Mods.
  • Networking: a channel between a mod's two halves, client and server, typed by the mod's own WIT.
  • Config: typed settings the game shows and stores for the mod, on the server too.
  • Keys and the crosshair target: keybinds in Controls; what the player is looking at.
  • SDK: a headless test runner (load a mod, feed it ticks and events, assert on its output, no window), templates per kind of mod, typed wrappers in the SDK for every interface. Dev mods already reload when rebuilt.

Changelog

  • API 0.2 (content): data-driven blocks and items, tags, horizon:add_to, terrain adaptation.
  • API 0.1.0: log, game, chat, hud, storage; init, tick, frame, command, chat.