Developer setup

Start with a reproducible SDK example

Run the local lobby example, inspect its error cases, then configure the backend your project actually needs.

Looking for a Game ID?

Some SDK guides link here to obtain project settings. This page does not issue credentials or create projects. For an existing deployment, obtain the Game ID, server address and approved client configuration from its administrator. For a new managed project, request setup assistance. Keep administrative keys out of client code.

Explore the SDK or read the configuration reference. The reference describes options; availability depends on your deployment.

Verified local lobby sample

Tested September 10, 2026 with Node 25.6.1. This source-based example needs no account or npm packages. Download these files into one empty directory:

node --experimental-strip-types run.mjs

The checks cover two local slots becoming ready, rejecting a premature start, rejecting a third slot in a full lobby, and ending the local match. Expected results: players: 2 and all three result checks true.

Source commit: f4329a486c98fe5712dbe9ac7f5c30d1b4f1952c. The runner checks the source hash before loading it. The README contains setup and error recovery instructions.

Turn the sample into a reviewable scope

The editable example separates local functionality from proposed UI accessibility checks. Human review is pending, and its validator intentionally reports that the scope is not ready.

Editable scope (JSON) · Structural validator · Review and error-case instructions

node validate.mjs

Download JSON and validator together. Expected: checks passed; ready false, with six unresolved requirements. A structural check cannot verify a reviewer’s identity or approve an accessible implementation.

What this establishes

This is a company-authored, automatically checked local example. It does not establish real participants, online connectivity, reward eligibility, production activation or independent review. The SDK currently reports a zero start timestamp in this local result; do not use it to measure duration.

The public npm lookup for @intelliversex/sdk@5.8.0 returned 404 during verification. Use the pinned source above for this example. A successful local run is a first setup check; genuine activation requires a provisioned project and a verified server operation.