Project planning / Coin pusher

Coral Treasury
Brand customisation

A planning brief for a exclusive project · platform planning · prototype review.

Your project scenario

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 brand customisation work should be evaluated during prototype review before the scope of the exclusive project is accepted.

Play the concept with representative users from your team and record the difference between preference changes and defects.

Coral Treasury concept artworkPlayable concept

Explore Coral Treasury ↗

Coin pusher · Virtual-credit demo

Integration priority

Brand customisation

Document the brand assets, interface language, animation style and sound requirements before asking for a reskin.

Review visual assets at real display sizes and check that text and controls remain readable during play.

Commercial scope

Exclusive project

Define the exact scope of exclusivity: game, artwork, brand, territory or channel. Exclusivity has value only when its boundaries are explicit.

Confirm ownership of third-party assets and define what may be reused.

Channel requirements

Platform planning

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

Coin movement and pushing

Define how simulated coin movement relates to any future monetary result. Do not derive real payouts from an untrusted browser simulation.

Acceptance checklist

CheckEvidence to collect
01 / Record font and artwork usage rightsRecord the Coral Treasury build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing prototype review.
02 / Review long labels and localisation expansionRecord the Coral Treasury build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing prototype review.
03 / Check contrast and control visibilityRecord the Coral Treasury build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing prototype review.
04 / Agree sign-off on the first playable buildRecord the Coral Treasury build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing prototype review.
05 / Observe overlapping coin motionRecord the Coral Treasury build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing prototype review.
06 / Check the push action and visual responseRecord the Coral Treasury build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing prototype review.
07 / Review the end-of-round stateRecord the Coral Treasury build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing prototype review.

Agreement review

  • Scope of exclusivity
  • Asset ownership
  • Reuse restrictions

For this Coral Treasury proposal, connect each agreed right to an identifiable deliverable. Keep brand customisation changes explicit in the statement of work.

Scope boundary

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.

Plan the test workload

Adjust the environments and test cases for this Coral Treasury evaluation. Start with the checklist above, then add partner-specific cases.

21 planned test executions.

Planning reference GQX-0192. Requirements must be confirmed against your actual platform and agreement.