Project planning / Coin pusher
A planning brief for a custom build · 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 technical evaluation 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 conceptCoin pusher · 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
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
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 / List requirements absent from the concept | Record the Coral Treasury build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 02 / Check initial loading and asset failures | Record the Coral Treasury build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 03 / Exercise a complete demo round | Record the Coral Treasury build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 04 / Record recovery after navigation or refresh | 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 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 Coral Treasury evaluation. Start with the checklist above, then add partner-specific cases.
Planning reference GQX-0597. Requirements must be confirmed against your actual platform and agreement.