Problem definition
A break between input, frame, network and build conditions and result attribution.
View all bottlenecksGAME DECISION MAP
Dead by Daylight Mobile
Design direction
Build a verified match-context card while safeguarding official results, mastery, fairness, one-versus-four tension and build diversity.
View all mechanismsRead the recurring-flow summary
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.
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.
Verified Match Context Card
Canonical Contribution Evidence Protocol
Pool-Aware Queue Condition Protocol
Calculable Growth Path Protocol
Offer-to-Rights Calculability Protocol
Voluntary Event Value Carryover Protocol
Goals and residual processing
Initial IFR · goal direction
Realign exposure, sequence and rules for state, cause and result at the established junction, recovering trust with volition and value.
Recurring Structures
Detailed Repeating Structures
What repeats and keeps the system moving?
9 analysis items · Read the method
Core classification and definition · Compounding Growth
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 →Core Mastery Loop
Trial success/failure → learn cause → adjust character/perk/loadout → next Trial → mastery gain.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Core Continuity Loop
Investment should become account-level continuity; actual mobile-only loop failed at EOS.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Supply Core Match Loop
Queue → Trial → Result → Immediate Reward → Rematch; Standard 1v4 Trial is the ecosystem hub.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Economy Progression Loop
Trial → XP/Bloodpoints → Character Level/Bloodmarket → option breadth → Trial.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Competition Competition Loop
Ranked Trial → Rank/Leaderboard/Season status → next objective → additional Trial.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Supply Season Loop
Trial/Mission → Rift progress → tier reward/collection → next season expectation.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Economy Collection Loop
Play/Purchase → Cosmetic/Treasure/Rift → Collection/Platinum/Profile exposure → further collection.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Cooperation Social Loop
Random Trial → positive interaction → Friend/Party/Squad → repeat Trial → relationship reinforcement.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Return LiveOps Loop
New Character/Map/Collaboration/Mode → return/learning → match volume → event/Rift consumption.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Core classification and definition · Action Feedback and Failure Attribution Break
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 →Core Action Feedback and Failure Attribution Break · Combat Competition Runtime
The limiting point sits in the combat competition runtime result handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Queue & Population Fragmentation
The limiting point sits in the matchmaking population entry handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Growth Access & Procurement
The limiting point sits in the growth entry handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Commerce Grammar & Purchase Explainability
The limiting point sits in the commerce collection entry handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Match-Impact Asset Fairness
The limiting point sits in the competition result handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting LiveOps & Late-Value Sustainability
The limiting point sits in the liveops content return 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 · Outcome and Failure Attribution vs System Depth and Rule Integrity
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 →Core Core Contradiction
Across component-addressable, improve Complexity Vs Convenience while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
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.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
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.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
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.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Freedom Vs Control / Revenue Vs Trust
Across acquisition path → asset/build → runtime → skill contribution, improve Freedom Vs Control while preserving Revenue Vs Trust.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
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.
- 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 · Context Asset and Authority Isolation
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 →Core Verified Match Context Card
Apply Context Asset and Authority Isolation across Verified Match Context Card while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Canonical Contribution Evidence Protocol
Apply Context Asset and Authority Isolation across Canonical Contribution Evidence Protocol while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Pool-Aware Queue Condition Protocol
Apply Context Asset and Authority Isolation across Pool-Aware Queue Condition Protocol while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Calculable Growth Path Protocol
Apply Baseline and Resource Stabilization across Calculable Growth Path Protocol while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Offer-to-Rights Calculability Protocol
Apply Loss Trust and Entitlement Buffer across Offer-to-Rights Calculability Protocol while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Voluntary Event Value Carryover Protocol
Apply Cadence and Rhythm Coordination across Voluntary Event Value Carryover Protocol 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 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 →Core Verified Match Context Card Composition
Connect 1 source-declared mechanism across Verified Match Context Card as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Canonical Contribution Evidence Protocol Composition
Connect 1 source-declared mechanism across Canonical Contribution Evidence Protocol as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Pool-Aware Queue Condition Protocol Composition
Connect 1 source-declared mechanism across Pool-Aware Queue Condition Protocol as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Calculable Growth Path Protocol Composition
Connect 1 source-declared mechanism across Calculable Growth Path Protocol as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Offer-to-Rights Calculability Protocol Composition
Connect 1 source-declared mechanism across Offer-to-Rights Calculability Protocol as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Voluntary Event Value Carryover Protocol Composition
Connect 1 source-declared mechanism across Voluntary Event Value Carryover Protocol as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Parallel Solution-Mechanism Composition
Connect 6 source-declared mechanisms across Verified Match Context Card as Core-First Branch-Sequential Portfolio.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Parallel Solution-Mechanism Composition
Connect 6 source-declared mechanisms across Verified Match Context Card as Parallel Local Contracts with Independent Rollback.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence