Manifold modding docs

Manifold is a reusable voxel engine. Its flagship game is built as WASM mods and registered content, through the same contract available to yours. These pages document that contract and how to build on it: what the engine can do today, how a mod reaches each capability, and step-by-step guides that end with something to try in game.

Where to start

1. Capability map. What the engine can do today, whether it has shipped, and how a mod reaches it: data files, assets, declarations or a WIT interface. Each row links to the page with the rules.
2. Guides. Build something end to end: make a creature from data alone, or add a held item. Each guide is backed by a compiled example mod, so its examples are checked against the engine.
3. References. Look things up as you build:
   • the mod contract explains packages, versions and linking, and the contract reference lists every WIT package, interface, function, type and payload;
   • the data registry reference lists every data/<dir> registry a mod can author, with its fields, types, defaults and an example;
   • the contract pages in the sidebar cover each system: the data stage, the gameplay framework, archetypes, creature brains, terrain recipes, text and localization and more.

Use the search box to find a registry, field, interface or function by name. For tools and language models, llms.txt indexes the reference pages.

Status and limits

The engine is under active development. No contract track is released yet: every 0.2 WIT interface is on the open, unreleased track and may change before the first release. The capability map marks each capability as shipped, preview or design, and says what is missing. Read the limits on a page before relying on it; written design does not mean a feature ships today.

How this site is made

This site is generated from the Markdown sources in the engine repository, at the revision it was published from. Reference pages are generated from the engine’s own definitions and checked by tests, so they change with the code. A mention of a repository path, such as crates/manifold-wasm-abi/wit/, names a file in the engine source tree.