NOVASMC

GAME DECISION MAP

Dead by Daylight Mobile

Asymmetrical Survival Horror · Mobile · 2020

Current analysisBaseline 2026-06-07Open Decision Analysis →

Choose Killer or Survivor and a Character / Loadout → queue for Quick, Ranked, Custom, or a variant → play an asymmetric Trial of chase, Generator repair, rescue, healing, hooks, sacrifice, and escape → receive EXP, Bloodpoints, Rank, Rift, ritual, and event progress → invest through Level, Perk, Prestige, Bloodmarket, Character, Outfit, collection, and social goals → revise the role, build, target, or group and return to the next Trial; at the 2026-06-07 baseline the service and loop are inactive after EOS.

Recurring Structures

Detailed Repeating Structures

What repeats and keeps the system moving?

CORE CLASSIFICATION

Compounding Growth

Choose Killer or Survivor and a Character / Loadout → queue for Quick, Ranked, Custom, or a variant → play an asymmetric Trial of chase, Generator repair, rescue, healing, hooks, sacrifice, and escape → receive EXP, Bloodpoints, Rank, Rift, ritual, and event progress → invest through Level, Perk, Prestige, Bloodmarket, Character, Outfit, collection, and social goals → revise the role, build, target, or group and return to the next Trial; at the 2026-06-07 baseline the service and loop are inactive after EOS.

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

View pattern definition →
  1. Core

    Mastery Loop

    Trial success/failure → learn cause → adjust character/perk/loadout → next Trial → mastery gain.

  2. Core

    Continuity Loop

    Investment should become account-level continuity; actual mobile-only loop failed at EOS.

  3. Supply

    Core Match Loop

    Queue → Trial → Result → Immediate Reward → Rematch; Standard 1v4 Trial is the ecosystem hub.

  4. Economy

    Progression Loop

    Trial → XP/Bloodpoints → Character Level/Bloodmarket → option breadth → Trial.

  5. Competition

    Competition Loop

    Ranked Trial → Rank/Leaderboard/Season status → next objective → additional Trial.

  6. Supply

    Season Loop

    Trial/Mission → Rift progress → tier reward/collection → next season expectation.

  7. Economy

    Collection Loop

    Play/Purchase → Cosmetic/Treasure/Rift → Collection/Platinum/Profile exposure → further collection.

  8. Cooperation

    Social Loop

    Random Trial → positive interaction → Friend/Party/Squad → repeat Trial → relationship reinforcement.

  9. Return

    LiveOps Loop

    New Character/Map/Collaboration/Mode → return/learning → match volume → event/Rift consumption.

Bottlenecks

Bottleneck Patterns

Where do decisions and flow break?

CORE CLASSIFICATION

Action Feedback and Failure Attribution Break

The limiting point sits in the combat competition runtime result handoff.

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

View pattern definition →
  1. Core

    Action Feedback and Failure Attribution Break · Combat Competition Runtime

    The limiting point sits in the combat competition runtime result handoff.

  2. Supporting

    Queue & Population Fragmentation

    The limiting point sits in the matchmaking population entry handoff.

  3. Supporting

    Growth Access & Procurement

    The limiting point sits in the growth entry handoff.

  4. Supporting

    Commerce Grammar & Purchase Explainability

    The limiting point sits in the commerce collection entry handoff.

  5. Supporting

    Match-Impact Asset Fairness

    The limiting point sits in the competition result handoff.

  6. Supporting

    LiveOps & Late-Value Sustainability

    The limiting point sits in the liveops content return handoff.

Contradictions

Contradiction Patterns

What must improve, and what must remain protected?

CORE CLASSIFICATION

Outcome and Failure Attribution vs System Depth and Rule Integrity

Across component-addressable, 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

    Across component-addressable, improve Complexity Vs Convenience while preserving Freedom Vs Control.

  2. Supporting

    Performance Vs Load / Freedom Vs Control

    Across mode → role → time pool queue result repeat continuity, improve Performance Vs Load while preserving Freedom Vs Control.

  3. Supporting

    Complexity Vs Convenience / Freedom Vs Control

    Across growth target → resource/access → first valid build next path, improve Complexity Vs Convenience while preserving Freedom Vs Control.

  4. Supporting

    Revenue Vs Trust / Complexity Vs Convenience

    Across price → probability → guarantee → duplicate → residual value → ownership/lifecycle, improve Revenue Vs Trust while preserving Complexity Vs Convenience.

  5. Supporting

    Freedom Vs Control / Revenue Vs Trust

    Across acquisition path → asset/build → runtime → skill contribution, improve Freedom Vs Control while preserving Revenue Vs Trust.

  6. Supporting

    Stability Vs Volatility / Performance Vs Load

    Across event goal/time/completion core return → durable reuse, improve Stability Vs Volatility while preserving Performance Vs Load.

Solution Mechanisms

Solution Mechanisms

Which intervention mechanism changes the condition?

CORE CLASSIFICATION

Context Asset and Authority Isolation

Apply Context Asset and Authority Isolation across Verified Match Context Card while preserving the protected value.

Isolate truth and responsibility by surface, asset, currency, role, and authority so rules do not bleed across contexts.

View pattern definition →
  1. Core

    Verified Match Context Card

    Apply Context Asset and Authority Isolation across Verified Match Context Card while preserving the protected value.

  2. Supporting

    Canonical Contribution Evidence Protocol

    Apply Context Asset and Authority Isolation across Canonical Contribution Evidence Protocol while preserving the protected value.

  3. Supporting

    Pool-Aware Queue Condition Protocol

    Apply Context Asset and Authority Isolation across Pool-Aware Queue Condition Protocol while preserving the protected value.

  4. Supporting

    Calculable Growth Path Protocol

    Apply Baseline and Resource Stabilization across Calculable Growth Path Protocol while preserving the protected value.

  5. Supporting

    Offer-to-Rights Calculability Protocol

    Apply Loss Trust and Entitlement Buffer across Offer-to-Rights Calculability Protocol while preserving the protected value.

  6. Supporting

    Voluntary Event Value Carryover Protocol

    Apply Cadence and Rhythm Coordination across Voluntary Event Value Carryover Protocol 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 Verified Match Context Card 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

    Verified Match Context Card Composition

    Connect 1 source-declared mechanism across Verified Match Context Card as Single-Track Localized Bundle.

  2. Supporting

    Canonical Contribution Evidence Protocol Composition

    Connect 1 source-declared mechanism across Canonical Contribution Evidence Protocol as Single-Track Localized Bundle.

  3. Supporting

    Pool-Aware Queue Condition Protocol Composition

    Connect 1 source-declared mechanism across Pool-Aware Queue Condition Protocol as Single-Track Localized Bundle.

  4. Supporting

    Calculable Growth Path Protocol Composition

    Connect 1 source-declared mechanism across Calculable Growth Path Protocol as Single-Track Localized Bundle.

  5. Supporting

    Offer-to-Rights Calculability Protocol Composition

    Connect 1 source-declared mechanism across Offer-to-Rights Calculability Protocol as Single-Track Localized Bundle.

  6. Supporting

    Voluntary Event Value Carryover Protocol Composition

    Connect 1 source-declared mechanism across Voluntary Event Value Carryover Protocol as Single-Track Localized Bundle.

  7. Supporting

    Parallel Solution-Mechanism Composition

    Connect 6 source-declared mechanisms across Verified Match Context Card as Core-First Branch-Sequential Portfolio.

  8. Supporting

    Parallel Solution-Mechanism Composition

    Connect 6 source-declared mechanisms across Verified Match Context Card as Parallel Local Contracts with Independent Rollback.