Project planning / Coin pusher
A planning brief for a one-time licence · platform planning · handover planning.
An underwater treasury gives the familiar coin-pusher mechanic an atmospheric ocean world and a fresh visual identity.
Coral Treasury combines coin movement and pushing with a coin pusher concept. For platform planning, the game launch integration work should be evaluated during handover planning before the scope of the one-time licence is accepted.
Define documentation, account ownership, secret rotation, support contacts and the acceptance record required for handover.
Playable conceptCoin pusher · 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
Define how simulated coin movement relates to any future monetary result. Do not derive real payouts from an untrusted browser simulation.
| Check | Evidence to collect |
|---|---|
| 01 / Request a launch for an allowed game | Record the Coral Treasury build, platform planning 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 Coral Treasury build, platform planning 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 Coral Treasury build, platform planning 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 Coral Treasury build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 05 / Observe overlapping coin motion | Record the Coral Treasury build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 06 / Check the push action and visual response | Record the Coral Treasury build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 07 / Review the end-of-round state | Record the Coral Treasury build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
For this Coral Treasury 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 Coral Treasury evaluation. Start with the checklist above, then add partner-specific cases.
Planning reference GQX-0527. Requirements must be confirmed against your actual platform and agreement.