Matches

Prepare the same project

1. Choose the same project in the dashboard as in your game configuration.

   Matches →

2. No additional definition is needed for the first request. An empty result is valid until matching game data exists.

   Use two separate player sessions: create a lobby, join, start in an explicit order, submit alternating byte-state turns, then report the same final result independently.

   This first example reads data. It creates no group, match or object. An empty list is a valid first response.

Two players, one original turn

Use two separate player sessions: create a lobby, join, start in an explicit order, submit alternating byte-state turns, then report the same final result independently.

Persist the exact request before sending. After a timeout, read current state and reconcile. Never replace its revision or create another intent silently.

Reports use the immutable final state revision. Agreement is not a trusted victory proof; disagreement and missing reports never imply a winner.

Ranked runs require a confirmed ranked match and the existing Validated Actions pipeline. Ordinary match reports do not grant rewards.

PHP supports ordinary match REST routes. Ranked validation and realtime are unavailable and return FEATURE_NOT_SUPPORTED where required.

Test your new feature.

Coordinate a lobby, alternating turns and independent final reports with two player sessions.

Choose the same project in the dashboard as in your game configuration.