Classic Fruits 3×3 — SEVENS Jackpot Presentation
Game-specific unique-mechanic module for
classic-fruits-3x3-gdd.md, based on the sharedslot-presentation-flow-template.md.Status:
DRAFT · VISUAL REFS ARE PLACEHOLDERS · NOT READY FOR FRONTEND IMPLEMENTATION
1. Scope
This module defines the presentation of the SEVEN count-anywhere jackpot. It does not add a bonus
round or durable feature state. The jackpot settles inside the same paid round as the five fixed
paylines.
Standard reel spin, no-win, ordinary line-win and total-win behavior use the shared presentation
flow. The unique behavior begins when six revealed SEVEN symbols make a seventh still possible.
2. Authoritative inputs
The frontend must receive or derive from explicit server receipts, never monetary inference:
The client may count the visible symbols only as a presentation consistency check. It must not select a tier or calculate money.
3. Presentation flow
4. Required phase order
5. Anticipation rules
- Anticipation starts only after six
SEVENsymbols are actually visible. - At least one unresolved position/reel must still be capable of revealing the seventh.
- Already resolved cells do not spin, blur, move or change.
- Anticipation may change timing, light and audio only; it cannot delay settlement indefinitely or alter the outcome.
- A miss is deliberately shorter and quieter than a Major reveal.
- Skip snaps to the final authoritative grid and continues at the correct result branch.
6. Jackpot and line-win ordering
- Jackpot presentation must not cover the grid until contributing line evidence has been readable.
- A jackpot award is not a second wallet credit or another round.
- Tier awards are mutually exclusive, not cumulative.
- For nine
SEVEN,1300×remains a design target until backend math and evidence prove it. The UI always displays the payout in the response.
7. Skip, reconnect and failure
- Skip finalizes the current visual phase and continues forward; it never omits settlement evidence.
- Reconnect restores the final grid, line receipts, jackpot receipt and combined total without replaying or duplicating money.
- A stale animation completion cannot enable Spin during a newer round.
- Missing or contradictory jackpot evidence is a required presentation failure: keep Spin disabled and reconcile instead of counting locally.
- Closing a tier popup finalizes presentation only; it does not acknowledge or create an award.
8. Visual reference registry
9. Deterministic DEV scenarios
- Six visible
SEVEN, final unresolved cell misses; no jackpot. - Six visible
SEVEN, seventh lands; Major 50× receipt. - Eight final
SEVEN; Grand 250× receipt. - Nine final
SEVEN; five SEVEN lines, Super 1000× and exact combined total. - Ordinary multi-line win with fewer than seven
SEVEN. - Skip during anticipation, count resolve, line sequence, tier reveal and combined total.
- Reconnect after settlement during each required presentation phase.
- Contradictory/missing jackpot receipt fails closed without a second wager.
10. Gate status
The unique-mechanic module and state flow exist. The Unique Mechanic Presentation Gate remains open until:
- backend wire fields and deterministic scenarios are implemented;
- every placeholder in the visual-reference registry is replaced by an approved moving reference;
- frontend tests prove ordering, skip/finalize and reconnect behavior.