NOVASMC

GAME DECISION MAP

Survivor.io

Action Roguelike · Mobile · 2022

Current analysisBaseline 2026-06-09Open Decision Analysis →

Enter a Main Chapter with a Survivor and loadout → move with one hand while attacks fire automatically → collect experience and draft random Skills and Passives into a 6+6 build with EVO → survive timed waves and bosses or stop at the failure point → claim Gold, Gems, materials, Keys, equipment, and Patrol or event rewards → invest across Survivor, Equipment, Tech Parts, Pets, Collectibles, and other permanent layers → return to the next Chapter, Challenge, Event, competition, or Clan objective.

Recurring Structures

Detailed Repeating Structures

What repeats and keeps the system moving?

CORE CLASSIFICATION

Compounding Growth

Enter a Main Chapter with a Survivor and loadout → move with one hand while attacks fire automatically → collect experience and draft random Skills and Passives into a 6+6 build with EVO → survive timed waves and bosses or stop at the failure point → claim Gold, Gems, materials, Keys, equipment, and Patrol or event rewards → invest across Survivor, Equipment, Tech Parts, Pets, Collectibles, and other permanent layers → return to the next Chapter, Challenge, Event, competition, or Clan objective.

Outputs strengthen assets, capabilities, or access and open a stronger next cycle.

View pattern definition →
  1. Core

    Core Structural Loop

    Survivor selection → chapter/combat entry → movement/evasion → auto attack/kill → XP/level → skill/passive selection → slots/EVO → waves/elite/boss → success/failure → meta growth screen → strengthen and retry.

Bottlenecks

Bottleneck Patterns

Where do decisions and flow break?

CORE CLASSIFICATION

Action Feedback and Failure Attribution Break

The limiting point sits in the combat feedback result handoff.

Outcomes, causes, rules, rewards, and retry information do not close the feedback loop needed for correction.

View pattern definition →
  1. Core

    mixed contribution

    The limiting point sits in the combat feedback result handoff.

  2. Supporting

    wall

    The limiting point sits in the transition handoff.

  3. Supporting

    layer accretion→goal

    The limiting point sits in the operations pressure handoff.

  4. Supporting

    duplicate

    The limiting point sits in the asset lifecycle handoff.

  5. Supporting

    schedule

    The limiting point sits in the routine liveops return handoff.

  6. Supporting

    power

    The limiting point sits in the competition result handoff.

  7. Supporting

    offer overlap

    The limiting point sits in the economy commerce settlement handoff.

Contradictions

Contradiction Patterns

What must improve, and what must remain protected?

CORE CLASSIFICATION

Outcome and Failure Attribution vs System Depth and Rule Integrity

Improve Complexity Vs Convenience while preserving Freedom Vs Control.

Causes and retry conditions for outcomes, failures, and fairness must become attributable while strategic, combat, and competitive depth and rule integrity remain protected.

View pattern definition →
  1. Core

    Core Contradiction

    Improve Complexity Vs Convenience while preserving Freedom Vs Control.

  2. Supporting

    Performance Vs Load / Freedom Vs Control

    Across Chapter wall → Patrol/Special Ops → next clear/return, improve Performance Vs Load while preserving Freedom Vs Control.

  3. Supporting

    Complexity Vs Convenience / Popularity Vs Scarcity

    Across Duplicate → pity → key → pool, improve Complexity Vs Convenience while preserving Popularity Vs Scarcity.

  4. Supporting

    Complexity Vs Convenience / Stability Vs Volatility

    Across claim → expiry, improve Complexity Vs Convenience while preserving Stability Vs Volatility.

  5. Supporting

    Complexity Vs Convenience / Freedom Vs Control

    Across status return cohort, improve Complexity Vs Convenience while preserving Freedom Vs Control.

  6. Supporting

    Revenue Vs Trust / Complexity Vs Convenience

    Across anchor → post-use, improve Revenue Vs Trust while preserving Complexity Vs Convenience.

Solution Mechanisms

Solution Mechanisms

Which intervention mechanism changes the condition?

CORE CLASSIFICATION

Layered and Progressive Disclosure

Apply Layered and Progressive Disclosure across 3-Layer Result-to-Build-to-Retry Trace 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

    3-Layer Result-to-Build-to-Retry Trace

    Apply Layered and Progressive Disclosure across 3-Layer Result-to-Build-to-Retry Trace while preserving the protected value.

  2. Supporting

    Context-First Recovery and Next-Progress Bridge

    Apply Route and Return Handoff across Context-First Recovery and Next-Progress Bridge while preserving the protected value.

  3. Supporting

    3-Layer Target-Completion Path Ledger

    Apply State and Rule Visibility Encoding across 3-Layer Target-Completion Path Ledger while preserving the protected value.

  4. Supporting

    Layered Event Lifecycle Contract

    Apply Layered and Progressive Disclosure across Layered Event Lifecycle Contract while preserving the protected value.

  5. Supporting

    Cohort-Bounded Result-and-Status Explanation Overlay

    Apply State and Rule Visibility Encoding across Cohort-Bounded Result-and-Status Explanation Overlay while preserving the protected value.

  6. Supporting

    Layered Offer Choice Contract

    Apply Layered and Progressive Disclosure across Layered Offer Choice Contract 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 3-Layer Result-to-Build-to-Retry Trace 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

    3-Layer Result-to-Build-to-Retry Trace Composition

    Connect 1 source-declared mechanism across 3-Layer Result-to-Build-to-Retry Trace as Single-Track Localized Bundle.

  2. Supporting

    Context-First Recovery and Next-Progress Bridge Composition

    Connect 1 source-declared mechanism across Context-First Recovery and Next-Progress Bridge as Single-Track Localized Bundle.

  3. Supporting

    3-Layer Target-Completion Path Ledger Composition

    Connect 1 source-declared mechanism across 3-Layer Target-Completion Path Ledger as Single-Track Localized Bundle.

  4. Supporting

    Layered Event Lifecycle Contract Composition

    Connect 1 source-declared mechanism across Layered Event Lifecycle Contract as Single-Track Localized Bundle.

  5. Supporting

    Cohort-Bounded Result-and-Status Explanation Overlay Composition

    Connect 1 source-declared mechanism across Cohort-Bounded Result-and-Status Explanation Overlay as Single-Track Localized Bundle.

  6. Supporting

    Layered Offer Choice Contract Composition

    Connect 1 source-declared mechanism across Layered Offer Choice Contract as Single-Track Localized Bundle.

  7. Supporting

    Parallel Solution-Mechanism Composition

    Connect 6 source-declared mechanisms across 3-Layer Result-to-Build-to-Retry Trace as Core-First Branch-Sequential Portfolio.

  8. Supporting

    Parallel Solution-Mechanism Composition

    Connect 6 source-declared mechanisms across 3-Layer Result-to-Build-to-Retry Trace as Parallel Local Contracts with Independent Rollback.