NOVASMC

GAME DECISION MAP

Monster Strike

Action RPG · Mobile · 2013

Current analysisBaseline 2026-06-21Open Decision Analysis →

Select a quest and team → slingshot monsters through turn-based battles → collect rewards and monsters → strengthen or evolve the roster → enter harder or co-op quests.

Recurring Structures

Detailed Repeating Structures

What repeats and keeps the system moving?

CORE CLASSIFICATION

Compounding Growth

Select a quest and team → slingshot monsters through turn-based battles → collect rewards and monsters → strengthen or evolve the roster → enter harder or co-op quests.

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

View pattern definition →
  1. Core

    Core quest-growth loop

    The actual loop runs through Quest clear → monsters/materials/gold → higher difficulty access.

  2. Supply

    Co-op efficiency loop

    Host stamina and reward sharing make multiplayer a cost/reward amplifier for growth and farming.

  3. Acquisition

    Gacha-growth loop

    Orbs feed premium/collab gacha; acquired characters widen the box and enable dungeon/gimmick fit.

  4. Return

    Event-collab loop

    Periodic collab/event quests refresh content, trigger limited gacha demand, and supply missions/login rewards.

  5. Competition

    Competition efficiency loop

    絶級トーナメント / 覇者の塔 / 禁忌·深淵 convert high-end clears into next-cycle skips, marks, and access rights.

  6. Economy

    Economy circulation loop

    Free/purchased Orbs, gold, medals, points, and event currencies connect quests, growth, gacha, shop, and events.

  7. Cooperation

    Social reward loop

    初顔合わせボーナス, キズナメーター, multiplayer lottery, and guest-credit events convert cooperation into rewards.

  8. Return

    LiveOps cadence loop

    Monthly/period events sequence challenge, collaboration, and economy activation; fatigue risk requires cadence control.

Bottlenecks

Bottleneck Patterns

Where do decisions and flow break?

CORE CLASSIFICATION

Decision and Planning Calculability Breakdown

The affected flow runs through state → goal → source → attempt → return; its limiting point is the growth collection planning handoff.

Multiple goals, resources, states, rules, and paths cannot be compared on one decision surface, forcing repeated reprioritization.

View pattern definition →
  1. Core

    Decision and Planning Calculability Breakdown · Growth Collection

    The affected flow runs through state → goal → source → attempt → return; its limiting point is the growth collection planning handoff.

  2. Supporting

    Fairness and Legitimacy Erosion · Difficulty Competition

    The affected flow runs through entry → fairness → mid-goal legitimacy; its limiting point is the difficulty competition entry handoff.

  3. Supporting

    Rights and Lifecycle Discontinuity · Collection

    The affected flow runs through pull → outcome → return; its limiting point is the collection result handoff.

  4. Supporting

    Legibility and Interpretation Break · Commerce Subscription

    The affected flow runs through view → compare → purchase; its limiting point is the commerce subscription entry handoff.

  5. Supporting

    Action Feedback and Failure Attribution Break · Combat Mastery

    The affected flow runs through battle → fail → prep/retry; its limiting point is the combat mastery result handoff.

  6. Supporting

    Allocation and Coordination Failure · Cooperation Matching

    The affected flow runs through room → reward → reparty/exit; its limiting point is the cooperation matching entry handoff.

Contradictions

Contradiction Patterns

What must improve, and what must remain protected?

CORE CLASSIFICATION

Asset and Economy Grammar Legibility vs Structural Diversity and Control

Across source/sink, improve Complexity Vs Convenience while preserving Freedom Vs Control.

The roles, inflows, outflows, states, and uses of assets and currencies must become legible while diversity, reuse value, and economic control remain protected.

View pattern definition →
  1. Core

    Core Contradiction

    Across source/sink, improve Complexity Vs Convenience while preserving Freedom Vs Control.

  2. Supporting

    Complexity Vs Convenience / Freedom Vs Control

    Across entry → fairness → retry, improve Complexity Vs Convenience while preserving Freedom Vs Control.

  3. Supporting

    Revenue Vs Trust / Popularity Vs Scarcity

    Across target → duplicate → handoff, improve Revenue Vs Trust while preserving Popularity Vs Scarcity.

  4. Supporting

    Web

    Across benefit → price → channel → informed action, improve Revenue Vs Trust while preserving Complexity Vs Convenience.

  5. Supporting

    Speed Vs Integrity / Complexity Vs Convenience

    Across failure reason → fit → prep → retry, improve Speed Vs Integrity while preserving Complexity Vs Convenience.

  6. Supporting

    Performance Vs Load / Freedom Vs Control

    Across room → role → cost → reward → reparty, improve Performance Vs Load 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 source/sink 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

    operator triple

    Apply Layered and Progressive Disclosure across source/sink while preserving the protected value.

  2. Supporting

    T-

    Apply State and Rule Visibility Encoding across entry → fairness → retry while preserving the protected value.

  3. Supporting

    State and Rule Visibility Encoding · Attachment

    Apply State and Rule Visibility Encoding across target → duplicate → handoff while preserving the protected value.

  4. Supporting

    State and Rule Visibility Encoding · Attachment

    Apply State and Rule Visibility Encoding across benefit → price → channel → informed action while preserving the protected value.

  5. Supporting

    State and Rule Visibility Encoding · Attachment

    Apply State and Rule Visibility Encoding across failure reason → fit → prep → retry while preserving the protected value.

  6. Supporting

    T-

    Apply Context Asset and Authority Isolation across room → role → cost → reward → reparty 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 source/sink 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

    operator triple Composition

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

  2. Supporting

    T- Composition

    Connect 1 source-declared mechanism across entry → fairness → retry as Single-Track Localized Bundle.

  3. Supporting

    State and Rule Visibility Encoding · Attachment Composition

    Connect 1 source-declared mechanism across target → duplicate → handoff as Single-Track Localized Bundle.

  4. Supporting

    State and Rule Visibility Encoding · Attachment Composition

    Connect 1 source-declared mechanism across benefit → price → channel → informed action as Single-Track Localized Bundle.

  5. Supporting

    State and Rule Visibility Encoding · Attachment Composition

    Connect 1 source-declared mechanism across failure reason → fit → prep → retry as Single-Track Localized Bundle.

  6. Supporting

    T- Composition

    Connect 1 source-declared mechanism across room → role → cost → reward → reparty as Single-Track Localized Bundle.

  7. Supporting

    Parallel Solution-Mechanism Composition

    Connect 6 source-declared mechanisms across source/sink as Core-First Branch-Sequential Portfolio.

  8. Supporting

    Parallel Solution-Mechanism Composition

    Connect 6 source-declared mechanisms across source/sink as Parallel Local Contracts with Independent Rollback.