Skip to main content

Compatibility and parity

Server compatibility​

CrowdyCPP targets the current platform APIs and degrades gracefully on older deployments:

  • Game-model invoke denials. Current servers report invoke-policy denials as FORBIDDEN GraphQL errors; newer builds resolve them as success: false invoke results (with a failure event). The kit's kitInvoke maps both onto the same KitInvokeResult{success: false, errorMessage}, so Game Kit code behaves identically on either server generation.
  • userAppState round-trip. Older Game API builds stored the base64 state input verbatim and re-encoded on read, so reads returned base64(base64(bytes)); newer builds round-trip symmetrically. Decode defensively if you must read rows written through an old server.

CrowdyJS parity​

CrowdyCPP mirrors CrowdyJS — same domains, same two-token model, same error codes — and the SDK repository verifies that claim mechanically with a generated parity matrix. The guarantees:

  • Full GraphQL root-field coverage. Every non-deprecated Management API and Game API root field is covered by a typed method. The only waived family is the udp-proxy surface (connectUdpProxy, the proxy send* mutations, the udpNotifications subscription): that is the browser proxy path, and CrowdyCPP replicates natively over UDP instead — each proxy send has a native wire-message counterpart.
  • CrowdyJS method parity. Every CrowdyJS class/method maps to a C++ counterpart, with a handful of documented waivers where the platform differs (browser storage helpers, subscription-style on() registration — the C++ session is tick-driven with handlers on the connection).
  • Blueprint equivalence. The Game Kit blueprint builders emit definitions equivalent to CrowdyJS's, verified by a blueprint-diff tool — worlds deployed from either SDK are playable from both.

The matrix is regenerated after any surface change; missing methods: 0, missing root fields: 0 is the maintained invariant.

Testing your integration​

CrowdyCPP ships an extensive black-box end-to-end suite you can point at any deployment (including your own dev tier) to validate an integration end to end. It provisions like a real integrator through the public Management API — sign in, ensure an access tier, grant access — with no privileged or database access, and it drives replication over the native UDP path, so it exercises the exact shipping client. Coverage spans the replication surface (fan-out, distance/decay, negative auth, cross-app isolation, cross-server, soak), the world-data and management surfaces, the WorldSession data structures, and all 15 Game Kit layers. See tests/e2e/ (configure with CROWDY_E2E_* environment variables) and the coverage matrix, which accounts for every scenario in the platform's other e2e suites. The suites double as runnable, real-world usage examples for each surface.

Versioning​

The current release is v0.2.1 (tagged in the repository). The CMake package config enforces SameMajorVersion compatibility for find_package(CrowdyCPP) consumers. Consumer-facing platform changes land in the changelog; the committed schema snapshot ties each SDK release to a known Management + Game API surface.