Problem definition
A break in the decisions linking offline rewards, growth, formation and another campaign attempt.
View all bottlenecksGAME DECISION MAP
A break in the decisions linking offline rewards, growth, formation and another campaign attempt.
View all bottlenecksProgressively connect the current state to required growth, formation changes and the choice to try again.
View all mechanismsClaim AFK and Fast Rewards → summon and collect heroes → level, ascend, equip, and build a faction-aware formation → auto-battle Campaign, Arena, towers, and Labyrinth → claim battle and activity rewards → reinvest into heroes and formation and retry the next challenge.
REASONING IN THIS GAME
These entries describe the selected design. Design selection is distinct from actual application and effect validation. The classified objects below retain their own roles and connections.
Read current value, further investment, completion and the next action continuously at existing touchpoints while retaining protected value.
Use state, reasons or alternatives, and detail layers with consistent state grammar to connect reward collection, growth, formation and retry.
Recurring Structures
What repeats and keeps the system moving?
6 analysis items · Read the method
Claim AFK and Fast Rewards → summon and collect heroes → level, ascend, equip, and build a faction-aware formation → auto-battle Campaign, Arena, towers, and Labyrinth → claim battle and activity rewards → reinvest into heroes and formation and retry the next challenge.
Events, operating schedules, and live operations reactivate participation, exchange, and reward states.
View pattern definition →Campaign Stage → AFK output rate → offline accumulation → reward claim → growth investment → next Campaign Stage.
Hero acquisition → ascension/common level sharing → broader formation capacity → multi-team content → specialized resources.
Growth investment → Tower/Boss/Rift challenge → records/floors/bands → scarce resources → growth reinvestment.
Account capital → PvP/PvE record competition → rank/reward/status → expanded growth capital.
Owned heroes/combat power → lending/shared/guild contribution → group rewards/status → social retention.
New hero/growth layer/season → trials/events/rule changes → roster reevaluation → target resources and spending.
The affected flow runs through return/login → reward claim → upgrade → power delta → Formation apply → Campaign retry → next-day return; its limiting point is the transition handoff.
The result of one step does not connect to the next action, return, or reinvestment decision.
View pattern definition →The affected flow runs through return/login → reward claim → upgrade → power delta → Formation apply → Campaign retry → next-day return; its limiting point is the transition handoff.
The affected flow runs through pool/pity view → pull → first copy → duplicate → SI/Furniture/Engraving/Gear → viable threshold → roster use; its limiting point is the asset lifecycle handoff.
The affected flow runs through battle → result → cause view → formation change → retry → next result; its limiting point is the combat feedback result handoff.
The affected flow runs through currency ledger → balance age → pool/shop view → compare → spend/exchange → expiry → residual balance; its limiting point is the growth economy planning handoff.
The affected flow runs through enter → opponent/rules → attempt/result → rank/reward → reinvest → next-season mobility; its limiting point is the competition result handoff.
The affected flow runs through 2 overlap → event start/completion → switch → claim/unclaimed → residual currency → session length → Event-to-Core Return; its limiting point is the liveops operations synchronization handoff.
The affected flow runs through 90 legacy asset/content/currency use → swap/exchange → archive state → inventory balance → returnee action → QA/CS cost; its limiting point is the asset lifecycle handoff.
Contradictions
What must improve, and what must remain protected?
6 analysis items · Read the method
Across claim → need → upgrade → power delta → Formation → Campaign retry → next target, improve Complexity Vs Convenience while preserving Freedom Vs Control.
Continuity to the next action, return, or reinvestment must improve while route diversity, strategic depth, and throughput remain protected.
View pattern definition →Across claim → need → upgrade → power delta → Formation → Campaign retry → next target, improve Complexity Vs Convenience while preserving Freedom Vs Control.
Across pity/ completion stack → viable use, improve Popularity Vs Scarcity while preserving Revenue Vs Trust.
Across pool/shop, improve Freedom Vs Control while preserving Revenue Vs Trust.
Across result → cause → Formation change → retry → next result → route, improve Complexity Vs Convenience while preserving Freedom Vs Control.
Across start/switch/completion/claim/end → Campaign AFK, improve Stability Vs Volatility while preserving Performance Vs Load.
Across cohort, improve Popularity Vs Scarcity while preserving Freedom Vs Control.
Solution Mechanisms
Which intervention mechanism changes the condition?
6 analysis items · Read the method
Apply Layered and Progressive Disclosure across claim → need → upgrade → power delta → Formation → Campaign retry → next target while preserving the protected value.
Separate complex meaning, rules, and strategy into layers and reveal only the depth needed at each moment.
View pattern definition →Apply Layered and Progressive Disclosure across claim → need → upgrade → power delta → Formation → Campaign retry → next target while preserving the protected value.
Apply Loss Trust and Entitlement Buffer across pity/ completion stack → viable use while preserving the protected value.
Apply State and Rule Visibility Encoding across result → cause → Formation change → retry → next result → route while preserving the protected value.
Apply State and Rule Visibility Encoding across Wallet Atlas while preserving the protected value.
Apply State and Rule Visibility Encoding across cohort while preserving the protected value.
Apply Cadence and Rhythm Coordination across Core-Return while preserving the protected value.
Solution Compositions
How should interventions be combined and sequenced?
8 analysis items · Read the method
Connect 1 source-declared mechanism across claim → need → upgrade → power delta → Formation → Campaign retry → next target 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 claim → need → upgrade → power delta → Formation → Campaign retry → next target as Single-Track Localized Bundle.
Connect 1 source-declared mechanism across pity/ completion stack → viable use as Single-Track Localized Bundle.
Connect 1 source-declared mechanism across result → cause → Formation change → retry → next result → route as Single-Track Localized Bundle.
Connect 1 source-declared mechanism across Wallet Atlas as Single-Track Localized Bundle.
Connect 1 source-declared mechanism across cohort as Single-Track Localized Bundle.
Connect 1 source-declared mechanism across Core-Return as Single-Track Localized Bundle.
Connect 6 source-declared mechanisms across claim → need → upgrade → power delta → Formation → Campaign retry → next target as Core-First Branch-Sequential Portfolio.
Connect 6 source-declared mechanisms across claim → need → upgrade → power delta → Formation → Campaign retry → next target as Parallel Local Contracts with Independent Rollback.