Project planning / Physics drop
A planning brief for a custom build · platform planning · discovery.
A suited boss tumbles through a cinematic city, colliding with obstacles, collecting coins and landing in payout lanes.
Boss Drop combines object collisions and landing behaviour with a physics drop concept. For platform planning, the brand customisation work should be evaluated during discovery before the scope of the custom build is accepted.
Produce a written requirements list and identify missing information before quoting implementation work.
Playable conceptPhysics drop · Virtual-credit demo
Integration priority
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
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
Agree whether the physics is visual presentation or part of the outcome model. A commercial game must prevent client-side manipulation from deciding real payouts.
| Check | Evidence to collect |
|---|---|
| 01 / Record font and artwork usage rights | Record the Boss Drop build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 02 / Review long labels and localisation expansion | Record the Boss Drop build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 03 / Check contrast and control visibility | Record the Boss Drop build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 04 / Agree sign-off on the first playable build | Record the Boss Drop build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 05 / Observe collisions with obstacles | Record the Boss Drop build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 06 / Review landing-lane presentation | Record the Boss Drop build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 07 / Check coin feedback during a fall | Record the Boss Drop build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
For this Boss Drop proposal, connect each agreed right to an identifiable deliverable. Keep brand customisation 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 Boss Drop evaluation. Start with the checklist above, then add partner-specific cases.
Planning reference GQX-0085. Requirements must be confirmed against your actual platform and agreement.