NOVASMC

GAME DECISION MAP

Dungeon & Fighter Mobile

Action RPG · Mobile · 2022

Current analysisBaseline 2026-07-06Open Decision Analysis →

Enter a side-scrolling dungeon and fight manually → defeat enemies and bosses for equipment and materials → build the character through gear, skills, and Armory progression → raise Equipment Point and meet upper-content gates → enter raids, party, competition, and advanced farming → reinvest rewards into the next build and dungeon.

Recurring Structures

Detailed Repeating Structures

What repeats and keeps the system moving?

CORE CLASSIFICATION

Compounding Growth

Enter a side-scrolling dungeon and fight manually → defeat enemies and bosses for equipment and materials → build the character through gear, skills, and Armory progression → raise Equipment Point and meet upper-content gates → enter raids, party, competition, and advanced farming → reinvest rewards into the next build and dungeon.

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

View pattern definition →
  1. Core

    Core Loop: Quest → Battle → Reward → Growth

    This source-declared core loop connects the game's actual repeat sequence.

  2. Core

    Periodic Self-Return · Core

    This source-declared core loop connects the game's actual repeat sequence.

Bottlenecks

Bottleneck Patterns

Where do decisions and flow break?

CORE CLASSIFICATION

Access and Qualification Friction

The affected flow runs through matched gate sequence; its limiting point is the entry handoff.

Players cannot reliably identify, meet, or sustain the opportunity, qualification, capability, role, or viable path needed to enter.

View pattern definition →
  1. Core

    gate criteria

    The affected flow runs through matched gate sequence; its limiting point is the entry handoff.

  2. Supporting

    path concentration

    The affected flow runs through residual after CT controls; its limiting point is the operations pressure handoff.

  3. Supporting

    match

    The affected flow runs through matched graph/conditions; its limiting point is the combat feedback result handoff.

  4. Supporting

    input

    The affected flow runs through device/control/job/encounter; its limiting point is the combat feedback result handoff.

  5. Supporting

    role

    The affected flow runs through party graph/choke point; its limiting point is the social operations coordination handoff.

  6. Supporting

    probability

    The affected flow runs through lineage + completion cohort; 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 gate/next-step , , entry/failure feedback, improve Complexity Vs Convenience while preserving None.

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 gate/next-step , , entry/failure feedback, improve Complexity Vs Convenience while preserving None.

  2. Supporting

    Freedom Vs Control / Performance Vs Load

    Across time/click cost, improve Freedom Vs Control while preserving Performance Vs Load.

  3. Supporting

    Freedom Vs Control / None

    Across match condition → result → reward re-entry continuity, improve Freedom Vs Control while preserving None.

  4. Supporting

    Complexity Vs Convenience / None

    Across input-feedback continuity, fail/retry/clear , device/control, improve Complexity Vs Convenience while preserving None.

  5. Supporting

    Complexity Vs Convenience / None

    Across phase formation → clear, improve Complexity Vs Convenience while preserving None.

  6. Supporting

    Popularity Vs Scarcity / Revenue Vs Trust

    Across completion → ownership state, improve Popularity Vs Scarcity while preserving Revenue Vs Trust.

Solution Mechanisms

Solution Mechanisms

Which intervention mechanism changes the condition?

CORE CLASSIFICATION

Layered and Progressive Disclosure

Apply Layered and Progressive Disclosure across gate/next-step , , entry/failure feedback 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 gate/next-step , , entry/failure feedback while preserving the protected value.

  2. Supporting

    Route and Return Handoff · Attachment

    Apply Route and Return Handoff across time/click cost while preserving the protected value.

  3. Supporting

    State and Rule Visibility Encoding · Attachment

    Apply State and Rule Visibility Encoding across match condition → result → reward re-entry continuity while preserving the protected value.

  4. Supporting

    State and Rule Visibility Encoding · Attachment

    Apply State and Rule Visibility Encoding across input-feedback continuity, fail/retry/clear , device/control while preserving the protected value.

  5. Supporting

    Context Asset and Authority Isolation · Attachment

    Apply Context Asset and Authority Isolation across phase formation → clear while preserving the protected value.

  6. Supporting

    State and Rule Visibility Encoding · Attachment

    Apply State and Rule Visibility Encoding across completion → ownership state 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 gate/next-step , , entry/failure feedback 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 gate/next-step , , entry/failure feedback as Single-Track Localized Bundle.

  2. Supporting

    Route and Return Handoff · Attachment Composition

    Connect 1 source-declared mechanism across time/click cost as Single-Track Localized Bundle.

  3. Supporting

    State and Rule Visibility Encoding · Attachment Composition

    Connect 1 source-declared mechanism across match condition → result → reward re-entry continuity as Single-Track Localized Bundle.

  4. Supporting

    State and Rule Visibility Encoding · Attachment Composition

    Connect 1 source-declared mechanism across input-feedback continuity, fail/retry/clear , device/control as Single-Track Localized Bundle.

  5. Supporting

    Context Asset and Authority Isolation · Attachment Composition

    Connect 1 source-declared mechanism across phase formation → clear as Single-Track Localized Bundle.

  6. Supporting

    State and Rule Visibility Encoding · Attachment Composition

    Connect 1 source-declared mechanism across completion → ownership state as Single-Track Localized Bundle.

  7. Supporting

    Parallel Solution-Mechanism Composition

    Connect 6 source-declared mechanisms across gate/next-step , , entry/failure feedback as Core-First Branch-Sequential Portfolio.

  8. Supporting

    Parallel Solution-Mechanism Composition

    Connect 6 source-declared mechanisms across gate/next-step , , entry/failure feedback as Parallel Local Contracts with Independent Rollback.