Project planning / Rocket crash
A planning brief for a exclusive project · platform planning · discovery.
A rocket climbs towards orbit as its multiplier rises. Choose when to cash out before the flight ends.
Orbital Run combines cash-out timing and flight end with a rocket crash concept. For platform planning, the brand customisation work should be evaluated during discovery before the scope of the exclusive project is accepted.
Produce a written requirements list and identify missing information before quoting implementation work.
Playable conceptRocket crash · Virtual-credit demo
Integration priority
Document the brand assets, interface language, animation style and sound requirements before asking for a reskin.
Review visual assets at real display sizes and check that text and controls remain readable during play.
Commercial scope
Define the exact scope of exclusivity: game, artwork, brand, territory or channel. Exclusivity has value only when its boundaries are explicit.
Confirm ownership of third-party assets and define what may be reused.
Channel requirements
Start with the operator’s actual browser, wallet and player journey requirements. This brief is a planning scenario, not a claim of compatibility with an unnamed casino.
Game-specific decision
A live crash game needs an authoritative cash-out acceptance rule and settlement timing. Network delay must not let the browser decide whether a real bet won.
| Check | Evidence to collect |
|---|---|
| 01 / Record font and artwork usage rights | Record the Orbital Run build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 02 / Review long labels and localisation expansion | Record the Orbital Run build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 03 / Check contrast and control visibility | Record the Orbital Run build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 04 / Agree sign-off on the first playable build | Record the Orbital Run build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 05 / Use manual cash-out during ascent | Record the Orbital Run build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 06 / Check the state after flight end | Record the Orbital Run build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 07 / Review multiplier readability | Record the Orbital Run build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
For this Orbital Run proposal, connect each agreed right to an identifiable deliverable. Keep brand customisation changes explicit in the statement of work.
The current game is a playable concept. Test wallet behaviour is available separately in the developer sandbox. Real-money wagering is disabled in that sandbox.
A live build requires server-authoritative gameplay, validated payout maths, partner-specific wallet integration and applicable testing. This brief is a planning aid, not evidence of certification or an existing platform connector.
Adjust the environments and test cases for this Orbital Run evaluation. Start with the checklist above, then add partner-specific cases.
Planning reference GQX-0084. Requirements must be confirmed against your actual platform and agreement.