Skip to content

Deterministic replays

PixelRifts can capture a bounded replay inside an authoritative room for compatibility testing and debugging. Replay capture is not controlled by creator code or the browser.

Replay format v1 binds a recording to:

  • the immutable Rift project, version, and bundle digest;
  • the seeded random stream;
  • the exact physics adapter and version;
  • player-slot join and release transitions;
  • the validated input consumed for each player entity on each tick; and
  • the resulting deterministic state hash for every tick.

The verifier loads the independently resolved immutable Rift, checks SHA-256 envelope integrity and physics compatibility, then simulates from tick one. If behavior changes, it reports the first tick whose state hash differs. Capture is limited to 36,000 ticks, or ten minutes at the fixed 60 Hz simulation rate.

Replay artifacts intentionally omit account, guest, device, connection, resume-token, and session identifiers. They are diagnostic data, not proof of player identity and not authorization for scores or rewards. PixelRifts does not yet expose persistent replay uploads, public ghosts, sharing, or replay-based anti-cheat decisions.

PixelRifts creator documentation · generated reference · protocol 21