Developer guides
Build with the Game Kits
How to use GripForge's libraries in your own project. Every guide is also read offline with grip-forge docs <topic> and by an AI agent through the MCP tool gripforge_docs. Looking for the REST endpoints? See the API reference; to connect an agent, the MCP documentation.
Use the Game Kits from
Run a game made with the Game Kits where you need it. Each guide: what it is for, install, a first example, the API, the errors, the limits.
Web
Putting an exported game in a web page
Usage guide: what gripforge game-export writes, serving the folder from your own site (MIME types, relative paths), the options of the page (?logic, ?renderer), updating an export, the messages of the CLI and of the page when the game cannot start, limits, versions.
grip-forge docs web-exportGodot
Using the Game Kits from Godot (GfGameHost, GfGameView)
Usage guide of the Godot addon: getting started in five steps without Rust, export a game as a Godot project (gripforge game-export --target godot: the prebuilt addon is fetched for Windows, macOS and Linux, checked and cached; --platforms, --addon offline, --with-web), supported Godot versions and platforms, what GfGameView draws of the kits (models, clips, camera, lights, module commands) and what it does not, the provisional HUD and hud_data(), every method and signal of GfGameHost (load_game, start, step, inputs, hooks, saves, present_*), errors, limits.
grip-forge docs godotDesktop
Using the Game Kits on the desktop (the native player)
Usage guide of the desktop export: gripforge game-export --target desktop makes a folder with the prebuilt native player (the Bevy player with the Rust logic of the kits and their presentation modules linked as native code) and the game as data; where the player comes from (release, catalogue, cache, --runtime, error codes), platforms, what the native window shows, the browser engine of the interface (--bundle-web-engine), checking an export without a screen (--replay), publishing the player, limits.
grip-forge docs desktopUnity
Using the Game Kits from Unity (GfGameHost, GfGameView)
Usage guide of the Unity package ai.gripforge.kits: getting started without Rust, export a game as a Unity project (gripforge game-export --target unity: the prebuilt libraries libgfkits and libgfpresent are fetched for Windows, macOS and Linux, checked and cached; --platforms, --capi and --package offline), the project and its first opening, building a player from the command line, what GfGameView draws of the kits and what it does not, the HUD of ui.webui, every method and event of GfGameHost (LoadGame, StartGame, Step, inputs, hooks, saves, Present*), errors, limits.
grip-forge docs unityNative (C)
The C API of the kit host (gfkits.h)
Usage guide of libgfkits from C: build and link, a first program, every function with its signature (create from { project, lock }, step, inputs, the zone and its entity rows, events, hooks by C callback, services, registries, saves), the statuses, limits, versions.
grip-forge docs c-api
Extend
Add rules of your own to a game, or change the ones it has.
Write a kit
Writing a third-party kit (step by step)
A kit of game logic of your own, in Rust: kit.json and its source, the common build tool (gripforge kit build on the build base: pinned toolchain, locked crates, structures checked), the two ways a game loads it — isolated in a memory of its own, or trusted in the common memory (trust, kit by kit) —, declaring it (gripforge kit add|verify|list|remove, gripforge_third_party_kit_*: source, sha256, trust, lock), try-kit, web export, what the page says, versions, limits.
grip-forge docs kit-third-partyMod a game
Mod a game — in the Third-party developer guide
Change the rules, numbers and content of a game with a mod (gripforge.mod/1): config, content, hooks that change or cancel a decision, scripts; what a game allows; installing and validating.
Reference
What the guides rely on.
Third-party developer guide
Third-party developer guide
Modules, mods, UI and games made outside GripForge: SDK, needs, commands, WGSL, caps, assets, fonts, ui.webui, publishing, ABI compatibility.
grip-forge docs third-partyKit API reference
Kit API reference
How to read the API reference of a kit (grip-forge kit api <id>, gripforge_gamekit_api) and what it holds.
grip-forge docs kit-apiGlossary
Glossary
The words of the docs: KitHost, module, ABI, slot, view, hook, passport…
grip-forge docs glossary