sometimestesting
use the local simulator and game-specific tests to check multiplayer behavior, private data and supported layouts before submitting a build.
local simulator
npm run dev starts a loopback server with two players, narrow and wide views, disconnects, latency, host changes and time advances. it runs your own source. do not run packages from strangers locally; uploaded packages use the managed sandbox.
test the full match
test invalid and repeated actions, late joins, departures, reconnects, deadlines, ties, errors, narrow screens, keyboard input, dark themes and reduced motion. inspect each projection for secret leaks. package verification does not replace game-specific tests.
limits
a package can contain up to 5MB, including up to 32 assets of 2MiB each. private state is limited to 128KB, actions to 8KB, signals to 1KB and saves to 16KB. rooms support up to 32 active players and retain up to 128 participants. each rules invocation has a 50ms CPU budget and a five-second request timeout, with network access disabled.