NOVASMC

GAME DECISION MAP

Call of Duty: Mobile

Shooter · Mobile · 2019

Current analysisBaseline 2026-07-04Open Decision Analysis →

Choose a mode and loadout → fight and complete objectives → earn XP and rewards → unlock or equip gear → re-enter matches.

Recurring Structures

Detailed Repeating Structures

What repeats and keeps the system moving?

CORE CLASSIFICATION

Compounding Growth

Choose a mode and loadout → fight and complete objectives → earn XP and rewards → unlock or equip gear → re-enter matches.

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

View pattern definition →
  1. Core

    Shared Combat Hub Loop

    Core structure: common input/weapon/operator pipeline supports Multiplayer, Battle Royale and DMZ: Recon as parallel pillars.

  2. Competition

    Multiplayer Pillar Loop

    MP match → Battle Pass/Challenge progress → ranked/league/WCPS status → seasonal rewards and store/draw exposure.

  3. Competition

    Battle Royale Pillar Loop

    BR session → ranked/event progress → BR class/LTM engagement → season rewards and themed event/store hooks.

  4. Economy

    DMZ Risk Pillar Loop

    Pre-battle loadout → contracts/loot/bosses → exfil/loss → Black Market/talents/reactive camos → account-season value.

  5. Acquisition

    Season Package Loop

    Season launch bundles mode update, event list, Battle Pass, Challenge Pass and Store/Draw update into one operating package.

  6. Acquisition

    Event-to-Store

    Collaboration/event novelty routes attention into Draw, Armory, Web Store and Battle Pass monetization surfaces.

Bottlenecks

Bottleneck Patterns

Where do decisions and flow break?

CORE CLASSIFICATION

Rule and State Fragmentation

The affected flow runs through chain by persona/window; its limiting point is the liveops event entry handoff.

Rules and states vary across channels, platforms, resets, or probabilities and fail to form a consistent action grammar.

View pattern definition →
  1. Core

    Rule and State Fragmentation · Liveops Event

    The affected flow runs through chain by persona/window; its limiting point is the liveops event entry handoff.

  2. Supporting

    Transition and Handoff Break · Growth

    The affected flow runs through Credits/XP/unlock/goal; its limiting point is the growth return handoff.

  3. Supporting

    Rights and Lifecycle Discontinuity · Armory Collection

    The affected flow runs through rule/draw/duplicate/completion; its limiting point is the armory collection handoff.

  4. Supporting

    Fairness and Legitimacy Erosion · Ranked Competition

    The affected flow runs through result/review/edit/retry; its limiting point is the ranked competition result handoff.

  5. Supporting

    Resource and Value Conversion Failure · Dmz Growth

    The affected flow runs through reward/market/Camo/return; its limiting point is the dmz growth reinvestment handoff.

  6. Supporting

    Outcome and Contribution Attribution Failure · Social

    The affected flow runs through graph/social return; its limiting point is the social result handoff.

Contradictions

Contradiction Patterns

What must improve, and what must remain protected?

CORE CLASSIFICATION

Action and Return Continuity vs System Depth and Throughput

Across Pass → Challenge → Event effort → reward → claim/exchange → return, improve Complexity Vs Convenience while preserving Stability Vs Volatility.

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 Pass → Challenge → Event effort → reward → claim/exchange → return, improve Complexity Vs Convenience while preserving Stability Vs Volatility.

  2. Supporting

    Stability Vs Volatility / Complexity Vs Convenience

    Across evergreen claim → Credits/Weapon XP → unlock → next-goal → return, improve Stability Vs Volatility while preserving Complexity Vs Convenience.

  3. Supporting

    Complexity Vs Convenience / Revenue Vs Trust

    Across rule/probability → draw → duplicate → completion → equip/display governance, improve Complexity Vs Convenience while preserving Revenue Vs Trust.

  4. Supporting

    Speed Vs Integrity / Complexity Vs Convenience

    Across result comprehension → review/edit → retry/exit, improve Speed Vs Integrity while preserving Complexity Vs Convenience.

  5. Supporting

    Popularity Vs Scarcity / Freedom Vs Control

    Across DMZ reward → voucher/market → asset completion → return, improve Popularity Vs Scarcity while preserving Freedom Vs Control.

  6. Supporting

    Complexity Vs Convenience / Freedom Vs Control

    Across contribution → recognition/practice → persistent relation capital → return, improve Complexity Vs Convenience 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 Layered Contract Status Spine 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 Contract Status Spine

    Apply Layered and Progressive Disclosure across Layered Contract Status Spine while preserving the protected value.

  2. Supporting

    Persistence- Milestone Spine

    Apply Route and Return Handoff across Persistence- Milestone Spine while preserving the protected value.

  3. Supporting

    Source- Collection Contract Spine

    Apply State and Rule Visibility Encoding across Source- Collection Contract Spine while preserving the protected value.

  4. Supporting

    Integrity- Ranked Decision Spine

    Apply State and Rule Visibility Encoding across Integrity- Ranked Decision Spine while preserving the protected value.

  5. Supporting

    Mode- Reward-to-Asset Spine

    Apply State and Rule Visibility Encoding across Mode- Reward-to-Asset Spine while preserving the protected value.

  6. Supporting

    Layered Voluntary Contribution-to-Recognition Spine

    Apply Layered and Progressive Disclosure across Layered Voluntary Contribution-to-Recognition Spine 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 Layered Contract Status Spine 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 Contract Status Spine Composition

    Connect 1 source-declared mechanism across Layered Contract Status Spine as Single-Track Localized Bundle.

  2. Supporting

    Persistence- Milestone Spine Composition

    Connect 1 source-declared mechanism across Persistence- Milestone Spine as Single-Track Localized Bundle.

  3. Supporting

    Source- Collection Contract Spine Composition

    Connect 1 source-declared mechanism across Source- Collection Contract Spine as Single-Track Localized Bundle.

  4. Supporting

    Integrity- Ranked Decision Spine Composition

    Connect 1 source-declared mechanism across Integrity- Ranked Decision Spine as Single-Track Localized Bundle.

  5. Supporting

    Mode- Reward-to-Asset Spine Composition

    Connect 1 source-declared mechanism across Mode- Reward-to-Asset Spine as Single-Track Localized Bundle.

  6. Supporting

    Layered Voluntary Contribution-to-Recognition Spine Composition

    Connect 1 source-declared mechanism across Layered Voluntary Contribution-to-Recognition Spine as Single-Track Localized Bundle.

  7. Supporting

    Parallel Solution-Mechanism Composition

    Connect 6 source-declared mechanisms across Layered Contract Status Spine as Core-First Branch-Sequential Portfolio.

  8. Supporting

    Parallel Solution-Mechanism Composition

    Connect 6 source-declared mechanisms across Layered Contract Status Spine as Parallel Local Contracts with Independent Rollback.