Project planning / Rocket crash
A planning brief for a one-time licence · multi-brand operation · commercial scoping.
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 multi-brand operation, the technical evaluation work should be evaluated during commercial scoping before the scope of the one-time licence is accepted.
Turn the evaluation into deliverables, ownership terms, acceptance evidence and a responsibility matrix.
Playable conceptRocket crash · Virtual-credit demo
Integration priority
Evaluate the current concept against the requirements of your platform. Separate demonstrated features from changes that still require production work.
Record reproducible steps, expected outcomes and device details for each issue; retest the specific affected behaviour after a fix.
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
Separate each brand’s approved hostnames, catalogue access and operational contacts. Test that one customer or brand cannot obtain another customer’s credentials or sessions.
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 / List requirements absent from the concept | Record the Orbital Run build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping. |
| 02 / Check initial loading and asset failures | Record the Orbital Run build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping. |
| 03 / Exercise a complete demo round | Record the Orbital Run build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping. |
| 04 / Record recovery after navigation or refresh | Record the Orbital Run build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping. |
| 05 / Use manual cash-out during ascent | Record the Orbital Run build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping. |
| 06 / Check the state after flight end | Record the Orbital Run build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping. |
| 07 / Review multiplier readability | Record the Orbital Run build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping. |
For this Orbital Run proposal, connect each agreed right to an identifiable deliverable. Keep technical evaluation 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-4205. Requirements must be confirmed against your actual platform and agreement.