Documentation
Some documentation requires an account. Public guides are below.
Playing
User manual
Every page of the player site, every button on it, and what each one does — with pictures.
EveryoneHow fair play is enforced
Why a game cannot decide who wins, and what stops someone cheating you.
Building a game
Getting started
Build a game for the platform. Start here.
EveryoneTutorial: build Tic-Tac-Toe
A complete walkthrough, start to published. Nothing skipped.
EveryoneTrust model
What your game can and cannot do, and why.
EveryoneWriting the server rules
The half that decides outcomes. Seven functions, and what they may touch.
EveryoneWriting deterministic rules
The rules that decide winners must be reproducible. How, and how it is proven.
EveryoneMaking a game feel good
Movement, feedback and sound — render-only, and why it must stay that way.
EveryonePublishing lifecycle
From your machine to players: staging, review, approval, updates.
EveryoneBuilding a client
For a front end talking to the platform directly.
EveryoneServer API reference
Every RPC the platform exposes, and who may call it.
Engine guides
Building with Excalibur.js
Code-first, and the most direct fit for the platform.
EveryoneBuilding with Defold
The smallest builds, and how to make Lua deterministic.
EveryoneBuilding with Phaser
Plain JavaScript on a canvas, and what to ship inside the bundle.
Everything about building a game is on this page. The other 8 documents are operations runbooks — deploying, backups, restoring from one, the payment egress address — and they are kept for platform operators because they describe how to run the infrastructure, not how to build for it.