NOVASMC

GAME DECISION MAP

Warcraft Rumble

Mobile Action Strategy · Mobile / PC Beta · 2023

Current analysisBaseline 2026-06-08Open Decision Analysis → · Korean full analysis

Design direction

Connect rewards and offers before delivery to valid uses within the same supply budget and one lifecycle carryover, preserving prices, supply, ownership and free routes.

View all mechanisms
Read the recurring-flow summary

Build an Army with one Leader and six configurable slots → enter Campaign, Heroic, Quest, Dungeon, PvP, Siege, Raid, or an Event rule set → gain Gold and control lanes, towers, stones, mines, chests, and objectives by deploying Minis → defeat the Boss or opposing Base → receive Sigils, XP, Tomes, Coins, Arc Energy, Cores, Stars, Valor, Slots, or Event rewards → invest through Level, Rarity, Talent, Army Slots, G.R.I.D., collection, and the Shop → revise the Army, target, mode, partner, or next objective and return.

REASONING IN THIS GAME

Selected designs and judgment conditions

Selected principles and the game-local design6 design records

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.

Goals and residual processing

Initial IFR · goal direction

Realign rewards, goals, exposure and operating lifecycle conditions by account stage to recover value, volition and trust.

Final IFR · design goal

Relay pre-grant reward or offer outcomes to valid uses suited to account stage, ownership and existing next goals within the same supply budget, providing one carryover.

Recurring Structures

Detailed Repeating Structures

What repeats and keeps the system moving?

3 analysis items · Read the method

Core classification and definition · External Calendar

External Calendar

Build an Army with one Leader and six configurable slots → enter Campaign, Heroic, Quest, Dungeon, PvP, Siege, Raid, or an Event rule set → gain Gold and control lanes, towers, stones, mines, chests, and objectives by deploying Minis → defeat the Boss or opposing Base → receive Sigils, XP, Tomes, Coins, Arc Energy, Cores, Stars, Valor, Slots, or Event rewards → invest through Level, Rarity, Talent, Army Slots, G.R.I.D., collection, and the Shop → revise the Army, target, mode, partner, or next objective and return.

Events, operating schedules, and live operations reactivate participation, exchange, and reward states.

View pattern definition →
  1. Supply

    Repeat Farming Loop

    Quest, Arclight Surge, Dungeon and Event repeat growth resources back into Mini/Army power.

    Evidence
    Source Described
    Outcome basis
    Design Evidence
  2. Competition

    Competition Loop

    Army composition enters Ranked PvP, produces Honor/VP/Status and returns rewards to growth.

    Evidence
    Source Described
    Outcome basis
    Design Evidence
  3. Cooperation

    Cooperation Loop

    Partnered Siege/Raid converts co-op boss clears into Valor, slot and growth rewards.

    Evidence
    Source Described
    Outcome basis
    Design Evidence

Bottlenecks

Bottleneck Patterns

Where do decisions and flow break?

8 analysis items · Read the method

Core classification and definition · Rights and Lifecycle Discontinuity

Rights and Lifecycle Discontinuity

The limiting point sits in the asset lifecycle handoff.

Acquisition, ownership, guarantees, resets, expiry, refunds, editing, and reuse do not form one continuous lifecycle.

View pattern definition →
  1. Core

    completion, resource age, receipt→7-day use, valid goal, carryover

    The limiting point sits in the asset lifecycle handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  2. Supporting

    attribution

    The limiting point sits in the combat feedback result handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    next-action path

    The limiting point sits in the transition handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  4. Supporting

    target wait

    The limiting point sits in the liveops operations synchronization handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    access liquidity

    The limiting point sits in the entry handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    social-edge persistence

    The limiting point sits in the social result handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  7. Supporting

    post-clear purpose

    The limiting point sits in the transition handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  8. Supporting

    fail→edit learning

    The affected flow runs through fail → edit break beyond difficulty; its limiting point is the combat feedback result handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence

Contradictions

Contradiction Patterns

What must improve, and what must remain protected?

6 analysis items · Read the method

Core classification and definition · Input and Reward Value Closure vs Diversity and Invested-Asset Preservation

Input and Reward Value Closure vs Diversity and Invested-Asset Preservation

Across account-stage Reward → Offer , valid next-goal density, Event carryover, improve Popularity Vs Scarcity while preserving Stability Vs Volatility.

Time, currency, purchases, rewards, and held assets must close into trustworthy value while route diversity, scarcity, and invested assets remain protected.

View pattern definition →
  1. Core

    Core Contradiction

    Across account-stage Reward → Offer , valid next-goal density, Event carryover, improve Popularity Vs Scarcity while preserving Stability Vs Volatility.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  2. Supporting

    Competitive Skill–Power Attribution

    Across Skill → Power → rule attribution legibility, rematch confidence, improve Complexity Vs Convenience while preserving Speed Vs Integrity.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    Next-Action Priority Legibility

    Across next-action recognition, path depth, entry → claim → re-entry legibility, improve Complexity Vs Convenience while preserving Freedom Vs Control.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  4. Supporting

    G.R.I.D. Target Access Predictability

    Across target exposure predictability, target pursuit continuity, action latency legibility, improve Popularity Vs Scarcity while preserving Freedom Vs Control.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    Real-Time Access Liquidity

    Across time-band access liquidity, completion → reuse, improve Performance Vs Load while preserving Freedom Vs Control.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    Post-First-Clear PvE Purpose Renewal

    Across post-clear next purpose, replay path, reward-use continuity, authored-asset life, improve Stability Vs Volatility while preserving Performance Vs Load.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence

Solution Mechanisms

Solution Mechanisms

Which intervention mechanism changes the condition?

6 analysis items · Read the method

Core classification and definition · Route and Return Handoff

Route and Return Handoff

Apply Route and Return Handoff across Account-Stage Utility Relay while preserving the protected value.

Connect the current state to valid next actions, routes, retries, and returns while preserving choice and existing paths.

View pattern definition →
  1. Core

    Account-Stage Utility Relay

    Apply Route and Return Handoff across Account-Stage Utility Relay while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  2. Supporting

    Observed Outcome Attribution Ledger

    Apply State and Rule Visibility Encoding across Observed Outcome Attribution Ledger while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    Selected-Objective Route Ledger

    Apply State and Rule Visibility Encoding across Selected-Objective Route Ledger while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  4. Supporting

    Target Window and Coin-Readiness Ledger

    Apply State and Rule Visibility Encoding across Target Window and Coin-Readiness Ledger while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    Mode-Preserving Liquidity Router

    Apply State and Rule Visibility Encoding across Mode-Preserving Liquidity Router while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    Post-Clear Purpose Relay

    Apply State and Rule Visibility Encoding across Post-Clear Purpose Relay while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence

Solution Compositions

Solution Compositions

How should interventions be combined and sequenced?

8 analysis items · Read the method

Core classification and definition · Single-Track Localized Bundle

Single-Track Localized Bundle

Connect 1 source-declared mechanism across Account-Stage Utility Relay 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

    Account-Stage Utility Relay Composition

    Connect 1 source-declared mechanism across Account-Stage Utility Relay as Single-Track Localized Bundle.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  2. Supporting

    Observed Outcome Attribution Ledger Composition

    Connect 1 source-declared mechanism across Observed Outcome Attribution Ledger as Single-Track Localized Bundle.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    Selected-Objective Route Ledger Composition

    Connect 1 source-declared mechanism across Selected-Objective Route Ledger as Single-Track Localized Bundle.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  4. Supporting

    Target Window and Coin-Readiness Ledger Composition

    Connect 1 source-declared mechanism across Target Window and Coin-Readiness Ledger as Single-Track Localized Bundle.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    Mode-Preserving Liquidity Router Composition

    Connect 1 source-declared mechanism across Mode-Preserving Liquidity Router as Single-Track Localized Bundle.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    Post-Clear Purpose Relay Composition

    Connect 1 source-declared mechanism across Post-Clear Purpose Relay as Single-Track Localized Bundle.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  7. Supporting

    Parallel Solution-Mechanism Composition

    Connect 6 source-declared mechanisms across Account-Stage Utility Relay as Core-First Branch-Sequential Portfolio.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  8. Supporting

    Parallel Solution-Mechanism Composition

    Connect 6 source-declared mechanisms across Account-Stage Utility Relay as Parallel Local Contracts with Independent Rollback.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence