Project planning / Prize wheel

Jade Fortune
Game launch integration

A planning brief for a monthly licence · multi-brand operation · commercial scoping.

Your project scenario

A gold-and-jade prize wheel combines twelve sectors with classic and bold play modes in a polished visual setting.

Jade Fortune combines wheel sectors and risk mode with a prize wheel concept. For multi-brand operation, the game launch integration work should be evaluated during commercial scoping before the scope of the monthly licence is accepted.

Turn the evaluation into deliverables, ownership terms, acceptance evidence and a responsibility matrix.

Jade Fortune concept artworkPlayable concept

Explore Jade Fortune ↗

Prize wheel · Virtual-credit demo

Integration priority

Game launch integration

Define who requests the launch, how the player reaches the game and which exact hostnames may embed it. API secrets stay on the operator server.

Test valid and expired launches, suspended licences, unauthorised games and unapproved subdomains.

Commercial scope

Monthly licence

Define a monthly access agreement with clear game coverage and an agreed notice process. Avoid assuming unlimited brands or domains.

Confirm the current period and the action required when access ends.

Channel requirements

Multi-brand operation

Separate each brand’s approved hostnames, catalogue access and operational contacts. Test that one customer or brand cannot obtain another customer’s credentials or sessions.

Game-specific decision

Wheel sectors and risk mode

Agree sector weights and mode-specific probabilities before describing an RTP or maximum win. The twelve visible sectors alone do not establish payout maths.

Acceptance checklist

CheckEvidence to collect
01 / Request a launch for an allowed gameRecord the Jade Fortune build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping.
02 / Attempt a launch after licence expiryRecord the Jade Fortune build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping.
03 / Check a hostname outside the agreementRecord the Jade Fortune build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping.
04 / Confirm credential revocation blocks new requestsRecord the Jade Fortune build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping.
05 / Review all twelve visible sectorsRecord the Jade Fortune build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping.
06 / Switch classic and bold modesRecord the Jade Fortune build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping.
07 / Check wheel-stop and result alignmentRecord the Jade Fortune build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing commercial scoping.

Agreement review

  • Monthly term
  • Approved domains
  • Cancellation handling

For this Jade Fortune proposal, connect each agreed right to an identifiable deliverable. Keep game launch integration 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 Jade Fortune evaluation. Start with the checklist above, then add partner-specific cases.

42 planned test executions.

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