Project planning / Physics drop
A planning brief for a annual licence · 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 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 conceptPhysics drop · 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
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 / Compare balances before and after each transaction | Record the Boss Drop build, platform planning 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 Boss Drop build, platform planning 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 Boss Drop build, platform planning 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 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 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 Boss Drop evaluation. Start with the checklist above, then add partner-specific cases.
Planning reference GQX-0007. Requirements must be confirmed against your actual platform and agreement.