Developer documentation
Integrate the SDK, handle player data and prepare compatible releases.
Build your first SDK game
Create and run a complete SDK example entirely in the Studio.
Check which SDK features are available
Distinguish a declared API from an enabled product feature.
Configure llvls.json
Declare build inputs, controls and SDK features in your project manifest.
Design within the game sandbox
Know which browser capabilities belong to the host.
Handle input, resize and accessible presentation
Match controls and rendering to the manifest and host context.
Handle SDK errors and negative outcomes
Separate expected refusals from exceptions and preserve recoverable game state.
How a game runs on llvls
Understand the project, SDK, host and release boundaries.
Implement lifecycle and pause handling
Initialise correctly and distinguish game breaks from host pauses.
Integrate optional ad requests without depending on fill
Handle the ad SDK safely while distinguishing simulation from live demand.
Load project images, sounds and level data
Use local asset helpers and static imports instead of network access.
Persist progress and migrate save data
Use host storage and handle unavailable or incompatible saves.
Prepare compatible releases and debug failures
Keep source history, live releases and save formats aligned.
Respect pause, mute and audio activation
Keep sound under the host's lifecycle controls.
SDK reference map
Find SDK methods, return values and the relevant integration guides.
Submit scores and record numeric events
Declare ids in the manifest and handle the platform's outcomes.
Test a game before release
Use Code editor diagnostics, Run and a repeatable Studio test matrix.
Understand builds, checks and release identity
Follow the files from source project to a reviewed release.
Use sign-in and result sharing
Let the host handle identity and sharing without exposing player details.
Use the supported engine and library registry
Pin dependencies and adapt engine features to the sandbox.