Project planning / Premium cinematic slot

Solar Vault
Technical evaluation

A planning brief for a one-time 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 technical evaluation work should be evaluated during discovery before the scope of the one-time 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

Technical evaluation

Evaluate the current concept against the requirements of your platform. Separate demonstrated features from changes that still require production work.

Record reproducible steps, expected outcomes and device details for each issue; retest the specific affected behaviour after a fix.

Commercial scope

One-time licence

Define a right to use the agreed build, with the brands, domains and delivery scope written down. A one-time payment does not automatically transfer ownership.

Specify whether maintenance is included or separately renewed.

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 / List requirements absent from the conceptRecord the Solar Vault build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery.
02 / Check initial loading and asset failuresRecord the Solar Vault build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery.
03 / Exercise a complete demo roundRecord the Solar Vault build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery.
04 / Record recovery after navigation or refreshRecord 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

  • Permitted usage
  • Delivered version
  • Maintenance responsibility

For this Solar Vault proposal, connect each agreed right to an identifiable deliverable. Keep technical evaluation 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-0016. Requirements must be confirmed against your actual platform and agreement.