Submission / Guide
Verify a published release
Check the actual immutable release, gameplay reports and player-facing experience.
Before review
- Metadata and claims match the build: title, description, controls, inputs and supported devices.
- Cover decodes and displays correctly; version is higher than the active release.
- ZIP has root index.html and all local assets; no private credentials or native project source.
- Event definitions are agreed with staff, including required fields and release scopes.
- Package preview loads and controls fit the viewport; native engine limitations are documented.
After publication
- Open /games/your-slug, then /play/your-slug in a fresh browser session.
- Read configuration and check the release-associated context. Watch the actual game's acknowledgement log.
- Start a run, make real progress, pause/resume if implemented and finish. Verify accepted:true, not just visual completion.
- Replay and verify a fresh session with a reset sequence. Refresh and check that assets load from the active immutable release.
- Test guest and authorized signed-in journeys separately. Test server receipts only where rules are configured; never infer a missing reward is a transport failure.
- Test desktop, keyboard and the mobile/touch layouts you declared. Check mute, reduced motion, orientation changes and error presentation.
Recovery
Stop testing if events are rejected, then use the error guide. Staff can deliberately roll back an active package; providers should request changes through the existing review process. A metadata rollback alone does not restore an earlier executable release.