Concepts
These pages explain how Labrador sees a game: what it calls, what it owns, what it leaves to you, and in what order things happen. Each page quotes the sample code it discusses, so they read without a build, on any machine. To see a game on the engine run without building anything, play LineSweeper in a desktop browser, the one sample hosted today. Building the minimal sample by Get Started is optional, though having its code open beside these pages helps.
Each idea here also appears in the design documents, which give the reasons in full. The pages below give enough of the reasons to use the engine well, and link to the rest.
What a game is to the engineThree interfaces you implement, the machinery you drive, and what the engine has no type for.
States and the stackScreens and modes as states; push, pop and typed results; what a covered state is told.
The tickThe fixed step, input, update, collision, the end of the tick, and then drawing.
Drawing, views and camerasWhy draw() is const, what a view is, and how a frame is recorded.
Names, handles and resourcesContent named in a manifest, resolved once at load, read by handle every frame.
Documentation for Labrador v0.3.0. Built from Labrador 0f4f503 of 2026-11-03.