Project planning / Premium cinematic slot

Solar Vault
Brand customisation

A planning brief for a monthly licence · platform planning · discovery.

Your project scenario

A cinematic five-reel slot with winning cascades, reactor wilds, vault free spins and original action sounds. Customise your edition in Game Studio.

Solar Vault combines cascades and reactor wilds with a premium cinematic slot concept. For platform planning, the brand customisation work should be evaluated during discovery before the scope of the monthly licence is accepted.

Produce a written requirements list and identify missing information before quoting implementation work.

Solar Vault concept artworkPlayable concept

Explore Solar Vault ↗

Premium cinematic slot · 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

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

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

Cascades and reactor wilds

Three winning cascades charge the reactor; initial vault keys trigger free spins. Customer presentation settings do not change the mathematical model.

Acceptance checklist

CheckEvidence to collect
01 / Record font and artwork usage rightsRecord the Solar Vault build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery.
02 / Review long labels and localisation expansionRecord the Solar Vault build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery.
03 / Check contrast and control visibilityRecord the Solar Vault 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 buildRecord the Solar Vault build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery.
05 / Check autoplay stop and loss limitsRecord the Solar Vault build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery.
06 / Verify event-synchronised action soundsRecord the Solar Vault build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery.
07 / Verify customer edition isolationRecord the Solar Vault build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery.

Agreement review

  • Monthly term
  • Approved domains
  • Cancellation handling

For this Solar Vault 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 Solar Vault evaluation. Start with the checklist above, then add partner-specific cases.

21 planned test executions.

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