Problem definition
Constrained retry choices after failure on hard levels.
View all bottlenecksGAME DECISION MAP
Constrained retry choices after failure on hard levels.
View all bottlenecksReorder the failure screen around results, equal retry and map choices, and optional recovery, preserving difficulty, rewards, the economy and free recovery routes.
View all mechanismsSpend a life to enter a move-limited match-3 level → swap candies and create special candies to clear the board objective → complete the level and advance on the Saga Map → route the win into races, teams, passes, collections, and events → use earned lives and boosters to attempt the next level.
REASONING IN THIS GAME
Realign choice, exposure, sequence and rule conditions to recover volition, value and trust.
Show the result first on the failure surface, offer Retry and Return to Saga Map as equal immediate choices, and open recovery or offer details after explicit action with synchronized state cues.
Recurring Structures
What repeats and keeps the system moving?
2 analysis items · Read the method
Spend a life to enter a move-limited match-3 level → swap candies and create special candies to clear the board objective → complete the level and advance on the Saga Map → route the win into races, teams, passes, collections, and events → use earned lives and boosters to attempt the next level.
Outputs strengthen assets, capabilities, or access and open a stronger next cycle.
View pattern definition →Select level → limited-move match-3 board → objective clear/fail → next map node or retry.
Star Tournament/endcap spaces mitigate latest-level cap while preserving core puzzle input.
The limiting point sits in the retry result handoff.
Difficulty, randomness, growth, or completion pressure accumulates at one decision point and concentrates the burden of retrying or reinvesting.
View pattern definition →The limiting point sits in the retry result handoff.
The limiting point sits in the entry handoff.
The limiting point sits in the booster handoff.
The limiting point sits in the liveops event return handoff.
The limiting point sits in the economy planning handoff.
Contradictions
What must improve, and what must remain protected?
5 analysis items · Read the method
Across retry/stop ; ; seed, improve Complexity Vs Convenience while preserving Performance Vs Load.
Continuity to the next action, return, or reinvestment must improve while route diversity, strategic depth, and throughput remain protected.
View pattern definition →Across retry/stop ; ; seed, improve Complexity Vs Convenience while preserving Performance Vs Load.
Across access continuity → route/receipt, improve Freedom Vs Control while preserving Popularity Vs Scarcity.
Across capacity → use → result attribution, improve Freedom Vs Control while preserving Popularity Vs Scarcity.
Across voluntary/legible completion path, improve Performance Vs Load while preserving Stability Vs Volatility.
Across choice control → alternative legibility, improve Freedom Vs Control while preserving Revenue Vs Trust.
Solution Mechanisms
Which intervention mechanism changes the condition?
5 analysis items · Read the method
Apply Route and Return Handoff across retry/stop ; ; seed while preserving the protected value.
Connect the current state to valid next actions, routes, retries, and returns while preserving choice and existing paths.
View pattern definition →Apply Route and Return Handoff across retry/stop ; ; seed while preserving the protected value.
Apply Loss Trust and Entitlement Buffer across access continuity → route/receipt while preserving the protected value.
Apply State and Rule Visibility Encoding across capacity → use → result attribution while preserving the protected value.
Apply Cadence and Rhythm Coordination across voluntary/legible completion path while preserving the protected value.
Apply Loss Trust and Entitlement Buffer across choice control → alternative legibility while preserving the protected value.
Solution Compositions
How should interventions be combined and sequenced?
7 analysis items · Read the method
Connect 1 source-declared mechanism across retry/stop ; ; seed as Single-Track Localized Bundle.
Combine a core intervention with stabilizing or accelerating support within one problem track and keep its impact localized.
View pattern definition →Connect 1 source-declared mechanism across retry/stop ; ; seed as Single-Track Localized Bundle.
Connect 1 source-declared mechanism across access continuity → route/receipt as Single-Track Localized Bundle.
Connect 1 source-declared mechanism across capacity → use → result attribution as Single-Track Localized Bundle.
Connect 1 source-declared mechanism across voluntary/legible completion path as Single-Track Localized Bundle.
Connect 1 source-declared mechanism across choice control → alternative legibility as Single-Track Localized Bundle.
Connect 5 source-declared mechanisms across retry/stop ; ; seed as Core-First Branch-Sequential Portfolio.
Connect 5 source-declared mechanisms across retry/stop ; ; seed as Parallel Local Contracts with Independent Rollback.