Project planning / Coin pusher
A planning brief for a annual licence · mobile web · discovery.
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 mobile web, the wallet integration work should be evaluated during discovery before the scope of the annual licence is accepted.
Produce a written requirements list and identify missing information before quoting implementation work.
Playable conceptCoin pusher · Virtual-credit demo
Integration priority
Map player identifiers, currency units, transaction identifiers and response codes before connecting a casino wallet.
Run balance, debit, credit, refund, insufficient-funds and retry cases. Keep every test account separate from production.
Commercial scope
Define a recurring annual access period and what happens at renewal or expiry. Separate the software right from hosting and operational services.
Set the agreed end date and test access after it passes.
Channel requirements
Prioritise narrow screens, touch controls, interrupted connections and browser navigation. Test portrait and landscape where the design supports them.
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 / Compare balances before and after each transaction | Record the Coral Treasury build, mobile web environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 02 / Retry a transaction with the same identifier | Record the Coral Treasury build, mobile web environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 03 / Reject a reused identifier carrying a different amount | Record the Coral Treasury build, mobile web environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 04 / Confirm that a refund cannot exceed or repeat its original debit | Record the Coral Treasury build, mobile web environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 05 / Observe overlapping coin motion | Record the Coral Treasury build, mobile web environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 06 / Check the push action and visual response | Record the Coral Treasury build, mobile web environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 07 / Review the end-of-round state | Record the Coral Treasury build, mobile web environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
For this Coral Treasury proposal, connect each agreed right to an identifiable deliverable. Keep wallet 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-0632. Requirements must be confirmed against your actual platform and agreement.