Project planning / Rocket crash
A planning brief for a custom build · multi-brand operation · handover planning.
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 game launch integration work should be evaluated during handover planning before the scope of the custom build is accepted.
Define documentation, account ownership, secret rotation, support contacts and the acceptance record required for handover.
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
Agree a commissioned production against a specific brief, review milestones and acceptance criteria. Decide which work begins only after the concept is approved.
Map requested changes to the build and record acceptance evidence.
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 / Request a launch for an allowed game | Record the Orbital Run build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 02 / Attempt a launch after licence expiry | Record the Orbital Run build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 03 / Check a hostname outside the agreement | Record the Orbital Run build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 04 / Confirm credential revocation blocks new requests | Record the Orbital Run build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 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 handover planning. |
| 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 handover planning. |
| 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 handover planning. |
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-4300. Requirements must be confirmed against your actual platform and agreement.