Project planning / Rocket crash
A planning brief for a one-time licence · 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 game launch integration work should be evaluated during discovery before the scope of the one-time licence is accepted.
Produce a written requirements list and identify missing information before quoting implementation work.
Playable conceptRocket crash · Virtual-credit demo
Integration priority
Define who requests the launch, how the player reaches the game and which exact hostnames may embed it. API secrets stay on the operator server.
Test valid and expired launches, suspended licences, unauthorised games and unapproved subdomains.
Commercial scope
Define a right to use the agreed build, with the brands, domains and delivery scope written down. A one-time payment does not automatically transfer ownership.
Specify whether maintenance is included or separately renewed.
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 / Request a launch for an allowed game | Record the Orbital Run build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 02 / Attempt a launch after licence expiry | Record the Orbital Run build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 03 / Check a hostname outside the agreement | Record the Orbital Run build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 04 / Confirm credential revocation blocks new requests | 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 game launch integration 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-0036. Requirements must be confirmed against your actual platform and agreement.