NOVASMC

GAME DECISION MAP

Crimson Desert

Action Adventure · Cross-platform · 2026

Current analysisBaseline 2026-04-22Open Decision Analysis →

Follow Kliff's campaign and explore Pywel → fight enemies and bosses in real-time action combat → collect gear, skills, and resources → improve the build and Greymane Camp → enter new regions and encounters.

Recurring Structures

Detailed Repeating Structures

What repeats and keeps the system moving?

CORE CLASSIFICATION

Compounding Growth

Follow Kliff's campaign and explore Pywel → fight enemies and bosses in real-time action combat → collect gear, skills, and resources → improve the build and Greymane Camp → enter new regions and encounters.

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

View pattern definition →
  1. Core

    Growth-Centric Core Loop

    Story, exploration and combat feed progression, which reopens the world and the next challenge tier.

  2. Core

    Abyss Cross-System Loop

    Abyss Artifact, Abyss Nexus and Abyss Cresset link exploration, mobility, puzzles and growth into one cross-system loop.

  3. Resilience

    Camp Reconstruction Loop

    Recruit recovery, provisions, commissions, expansion and reconstruction convert world progress into infrastructure.

  4. Supply

    Dispatch Passive Growth Loop

    Active play pauses while recruit dispatch continues to accumulate money, materials, trade goods and crafted output.

  5. Economy

    Life & Trade Support Loop

    Crafting, cooking, fishing, hunting, mining, logging and trade wagon play reinforce self-sufficiency and world depth.

Bottlenecks

Bottleneck Patterns

Where do decisions and flow break?

CORE CLASSIFICATION

Transition and Handoff Break

The affected flow runs through input → feedback → result; role translation; its limiting point is the combat exploration growth result handoff.

The result of one step does not connect to the next action, return, or reinvestment decision.

View pattern definition →
  1. Core

    Transition and Handoff Break · Combat Exploration Growth

    The affected flow runs through input → feedback → result; role translation; its limiting point is the combat exploration growth result handoff.

  2. Supporting

    Transition and Handoff Break · Content Exploration

    The affected flow runs through completion → next-session purpose; its limiting point is the content exploration return handoff.

  3. Supporting

    Rule and State Fragmentation · Economy

    The affected flow runs through rule/error → use/avoidance; its limiting point is the economy settlement handoff.

  4. Supporting

    Decision and Planning Calculability Breakdown · Growth Combat

    The affected flow runs through exposure → investment/build; its limiting point is the growth combat planning handoff.

  5. Supporting

    Rights and Lifecycle Discontinuity · Commerce

    The affected flow runs through claim → delivery → recovery; its limiting point is the commerce settlement handoff.

  6. Supporting

    Rule and State Fragmentation · Commerce Platform

    The affected flow runs through label → price → ownership; its limiting point is the commerce platform entry handoff.

Contradictions

Contradiction Patterns

What must improve, and what must remain protected?

CORE CLASSIFICATION

Action and Return Continuity vs System Depth and Throughput

Improve Complexity Vs Convenience while preserving Speed Vs Integrity.

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

    Improve Complexity Vs Convenience while preserving Speed Vs Integrity.

  2. Supporting

    +

    Across completion purpose next-session reason → revisit, improve Performance Vs Load while preserving Stability Vs Volatility.

  3. Supporting

    +

    Across economy feature use, improve Speed Vs Integrity while preserving Freedom Vs Control.

  4. Supporting

    +

    Across investment → build experimentation, improve Freedom Vs Control while preserving Complexity Vs Convenience.

  5. Supporting

    +

    Across entitlement → claim → delivery → recovery deterministic ownership, improve Speed Vs Integrity while preserving Revenue Vs Trust.

  6. Supporting

    +

    Across product boundary → platform metadata → price → ownership informed purchase, improve Revenue Vs Trust while preserving Speed Vs Integrity.

Solution Mechanisms

Solution Mechanisms

Which intervention mechanism changes the condition?

CORE CLASSIFICATION

Layered and Progressive Disclosure

Apply Layered and Progressive Disclosure to the source-declared core track while preserving its 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 Read→Choose→Recover Grammar

    Apply Layered and Progressive Disclosure to the source-declared core track while preserving its protected value.

  2. Supporting

    Pull-Based Completion Purpose Relay

    Apply Route and Return Handoff across completion purpose next-session reason → revisit while preserving the protected value.

  3. Supporting

    Layered Settlement Contract

    Apply Layered and Progressive Disclosure across economy feature use while preserving the protected value.

  4. Supporting

    Bounded Consequence & Recovery Cue

    Apply Loss Trust and Entitlement Buffer across investment → build experimentation while preserving the protected value.

  5. Supporting

    Existing Add-ons Entitlement Closure

    Apply Loss Trust and Entitlement Buffer across entitlement → claim → delivery → recovery deterministic ownership while preserving the protected value.

  6. Supporting

    Existing Product Information Closure

    Apply State and Rule Visibility Encoding across product boundary → platform metadata → price → ownership informed purchase 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 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 Read→Choose→Recover Grammar Composition

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

  2. Supporting

    Pull-Based Completion Purpose Relay Composition

    Connect 1 source-declared mechanism across completion purpose next-session reason → revisit as Single-Track Localized Bundle.

  3. Supporting

    Layered Settlement Contract Composition

    Connect 1 source-declared mechanism across economy feature use as Single-Track Localized Bundle.

  4. Supporting

    Bounded Consequence & Recovery Cue Composition

    Connect 1 source-declared mechanism across investment → build experimentation as Single-Track Localized Bundle.

  5. Supporting

    Existing Add-ons Entitlement Closure Composition

    Connect 1 source-declared mechanism across entitlement → claim → delivery → recovery deterministic ownership as Single-Track Localized Bundle.

  6. Supporting

    Existing Product Information Closure Composition

    Connect 1 source-declared mechanism across product boundary → platform metadata → price → ownership informed purchase as Single-Track Localized Bundle.

  7. Supporting

    Parallel Solution-Mechanism Composition

    Connect 6 source-declared mechanisms across completion purpose next-session reason → revisit as Core-First Branch-Sequential Portfolio.

  8. Supporting

    Parallel Solution-Mechanism Composition

    Connect 6 source-declared mechanisms across completion purpose next-session reason → revisit as Parallel Local Contracts with Independent Rollback.