NOVASMC

GAME DECISION MAP

AFK Arena

Idle RPG · Mobile · 2019

Current analysisBaseline 2026-07-21Open Decision Analysis →

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.

Recurring Structures

Detailed Repeating Structures

What repeats and keeps the system moving?

CORE CLASSIFICATION

External Calendar

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 →
  1. Supply

    Idle Production Loop

    Campaign Stage → AFK output rate → offline accumulation → reward claim → growth investment → next Campaign Stage.

  2. Acquisition

    Roster Expansion Loop

    Hero acquisition → ascension/common level sharing → broader formation capacity → multi-team content → specialized resources.

  3. Supply

    Challenge Loop

    Growth investment → Tower/Boss/Rift challenge → records/floors/bands → scarce resources → growth reinvestment.

  4. Competition

    Competition Loop

    Account capital → PvP/PvE record competition → rank/reward/status → expanded growth capital.

  5. Cooperation

    Cooperation Loop

    Owned heroes/combat power → lending/shared/guild contribution → group rewards/status → social retention.

  6. Return

    LiveOps Re-activation Loop

    New hero/growth layer/season → trials/events/rule changes → roster reevaluation → target resources and spending.

Bottlenecks

Bottleneck Patterns

Where do decisions and flow break?

CORE CLASSIFICATION

Transition and Handoff Break

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 →
  1. Core

    Transition and Handoff Break ·

    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.

  2. Supporting

    Rights and Lifecycle Discontinuity · Asset

    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.

  3. Supporting

    Action Feedback and Failure Attribution Break · Combat Feedback

    The affected flow runs through battle → result → cause view → formation change → retry → next result; its limiting point is the combat feedback result handoff.

  4. Supporting

    Decision and Planning Calculability Breakdown · Growth Economy

    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.

  5. Supporting

    Fairness and Legitimacy Erosion · Competition

    The affected flow runs through enter → opponent/rules → attempt/result → rank/reward → reinvest → next-season mobility; its limiting point is the competition result handoff.

  6. Supporting

    Temporal and Operational Synchronization Break · Liveops Operations

    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.

  7. Supporting

    Rights and Lifecycle Discontinuity · Asset

    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

Contradiction Patterns

What must improve, and what must remain protected?

CORE CLASSIFICATION

Action and Return Continuity vs System Depth and Throughput

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 →
  1. Core

    Core Contradiction

    Across claim → need → upgrade → power delta → Formation → Campaign retry → next target, improve Complexity Vs Convenience while preserving Freedom Vs Control.

  2. Supporting

    Acquisition Completion-to-Use

    Across pity/ completion stack → viable use, improve Popularity Vs Scarcity while preserving Revenue Vs Trust.

  3. Supporting

    Multi-Wallet Value Planning

    Across pool/shop, improve Freedom Vs Control while preserving Revenue Vs Trust.

  4. Supporting

    Combat Attribution and Retry Learning

    Across result → cause → Formation change → retry → next result → route, improve Complexity Vs Convenience while preserving Freedom Vs Control.

  5. Supporting

    Event Lifecycle Closure and Core Return

    Across start/switch/completion/claim/end → Campaign AFK, improve Stability Vs Volatility while preserving Performance Vs Load.

  6. Supporting

    Competition Capital Mobility

    Across cohort, improve Popularity Vs Scarcity while preserving Freedom Vs Control.

Solution Mechanisms

Solution Mechanisms

Which intervention mechanism changes the condition?

CORE CLASSIFICATION

Layered and Progressive Disclosure

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 →
  1. Core

    Layered and Progressive Disclosure · Core

    Apply Layered and Progressive Disclosure across claim → need → upgrade → power delta → Formation → Campaign retry → next target while preserving the protected value.

  2. Supporting

    Loss Trust and Entitlement Buffer · Attachment

    Apply Loss Trust and Entitlement Buffer across pity/ completion stack → viable use while preserving the protected value.

  3. Supporting

    State and Rule Visibility Encoding · Attachment

    Apply State and Rule Visibility Encoding across result → cause → Formation change → retry → next result → route while preserving the protected value.

  4. Supporting

    State and Rule Visibility Encoding · Attachment

    Apply State and Rule Visibility Encoding across Wallet Atlas while preserving the protected value.

  5. Supporting

    State and Rule Visibility Encoding · Attachment

    Apply State and Rule Visibility Encoding across cohort while preserving the protected value.

  6. Supporting

    Cadence and Rhythm Coordination · Attachment

    Apply Cadence and Rhythm Coordination across Core-Return while preserving the protected value.

Solution Compositions

Solution Compositions

How should interventions be combined and sequenced?

CORE CLASSIFICATION

Single-Track Localized Bundle

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 →
  1. Core

    Layered and Progressive Disclosure · Core Composition

    Connect 1 source-declared mechanism across claim → need → upgrade → power delta → Formation → Campaign retry → next target as Single-Track Localized Bundle.

  2. Supporting

    Loss Trust and Entitlement Buffer · Attachment Composition

    Connect 1 source-declared mechanism across pity/ completion stack → viable use as Single-Track Localized Bundle.

  3. Supporting

    State and Rule Visibility Encoding · Attachment Composition

    Connect 1 source-declared mechanism across result → cause → Formation change → retry → next result → route as Single-Track Localized Bundle.

  4. Supporting

    State and Rule Visibility Encoding · Attachment Composition

    Connect 1 source-declared mechanism across Wallet Atlas as Single-Track Localized Bundle.

  5. Supporting

    State and Rule Visibility Encoding · Attachment Composition

    Connect 1 source-declared mechanism across cohort as Single-Track Localized Bundle.

  6. Supporting

    Cadence and Rhythm Coordination · Attachment Composition

    Connect 1 source-declared mechanism across Core-Return as Single-Track Localized Bundle.

  7. Supporting

    Parallel Solution-Mechanism Composition

    Connect 6 source-declared mechanisms across claim → need → upgrade → power delta → Formation → Campaign retry → next target as Core-First Branch-Sequential Portfolio.

  8. Supporting

    Parallel Solution-Mechanism Composition

    Connect 6 source-declared mechanisms across claim → need → upgrade → power delta → Formation → Campaign retry → next target as Parallel Local Contracts with Independent Rollback.