NOVASMC

GAME DECISION MAP

Odin: Valhalla Rising

MMORPG · Cross-platform · 2021

Current analysisBaseline 2026-05-22Open Decision Analysis → · Korean full analysis

Problem definition

Probability, pity, duplicate and fusion conditions weaken confidence in collection completion and subsequent investment decisions.

View all bottlenecks

Design direction

Place acquisition-promise consistency, voluntary return and contribution entry paths for new and small guilds on their respective control surfaces.

View all mechanisms
Read the recurring-flow summary

Accept quests and hunt → collect gear and currency → enhance equipment and collections → enter dungeons, bosses, or PvP → return to higher-level fields.

REASONING IN THIS GAME

Selected designs and judgment conditions

Goals and residual processing

Initial IFR · goal direction

Realign rules, exposure, state, feedback and governance to recover trust and value.

Recurring Structures

Detailed Repeating Structures

What repeats and keeps the system moving?

10 analysis items · Read the method

Core classification and definition · Periodic Self-Return

Periodic Self-Return

Accept quests and hunt → collect gear and currency → enhance equipment and collections → enter dungeons, bosses, or PvP → return to higher-level fields.

Daily, weekly, or seasonal resets restore eligibility for the same activity.

View pattern definition →
  1. Core

    Daily Growth Loop

    Quest/field/dungeon play feeds gold, EXP, materials and then enhancement/skill/collection spending.

    Evidence
    Source Described
    Outcome basis
    Design Evidence
  2. Competition

    Weekly

    Dungeon resets, Valhalla daily schedule, world dungeon biweekly cycle and guild war seasons produce medium-term goals.

    Evidence
    Source Described
    Outcome basis
    Design Evidence
  3. Cooperation

    Long-term Meta Growth Loop

    Max level, high-grade gear, avatar/mount/rune/codex and guild status form long-term retention goals.

    Evidence
    Source Described
    Outcome basis
    Design Evidence
  4. Economy

    Growth-Economy Loop

    Content rewards become enhancement, crafting, gacha and shop demand; sinks regulate economy and progression.

    Evidence
    Source Described
    Outcome basis
    Design Evidence
  5. Competition

    PvE-to-PvP Transition Loop

    Early/mid PvE growth routes eventually convert into PvP, guild war and world-level competition participation.

    Evidence
    Source Described
    Outcome basis
    Design Evidence
  6. Cooperation

    Cooperation-to-Competition Loop

    Guild cooperation builds capacity for siege, territory, world boss and server/world competition.

    Evidence
    Source Described
    Outcome basis
    Design Evidence
  7. Return

    Event-LiveOps Loop

    Events fill update gaps, inject rewards, refresh goals and accelerate growth/economic consumption.

    Evidence
    Source Described
    Outcome basis
    Design Evidence
  8. Supply

    Automation-Fatigue Loop

    Auto/idle systems reduce repetitive fatigue but can weaken manual engagement and combat mastery.

    Evidence
    Source Described
    Outcome basis
    Design Evidence
  9. Acquisition

    Gacha-Shop-Monetization Loop

    Premium shop and gacha provide power goals, while events/free rewards soften stress.

    Evidence
    Source Described
    Outcome basis
    Design Evidence
  10. Acquisition

    Cross-System Consistency Loop

    representatives map into //, currencies into , and event/shop/gacha rewards into growth.

    Evidence
    Source Described
    Outcome basis
    Design Evidence

Bottlenecks

Bottleneck Patterns

Where do decisions and flow break?

3 analysis items · Read the method

Core classification and definition · Rights and Lifecycle Discontinuity

Rights and Lifecycle Discontinuity

The affected flow runs through offer → probability/pity → draw → duplicate → later action; its limiting point is the asset lifecycle handoff.

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

View pattern definition →
  1. Core

    Rights and Lifecycle Discontinuity · Asset

    The affected flow runs through offer → probability/pity → draw → duplicate → later action; its limiting point is the asset lifecycle handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  2. Supporting

    obligation

    The affected flow runs through overlap → mission/popup → miss → reward → return; its limiting point is the routine liveops return handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    contribution legitimacy·concentration·key-node dependency·survival

    The affected flow runs through join → contribution → reward → bridge/key node → survival; its limiting point is the social operations coordination handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence

Contradictions

Contradiction Patterns

What must improve, and what must remain protected?

3 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 Trust, improve Revenue Vs Trust while preserving Complexity Vs Convenience.

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 Trust, improve Revenue Vs Trust while preserving Complexity Vs Convenience.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  2. Supporting

    Performance Vs Load / Stability Vs Volatility

    Across cycle, improve Performance Vs Load while preserving Stability Vs Volatility.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    Freedom Vs Control / None

    Across small/new guild network access, improve Freedom Vs Control while preserving None.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence

Solution Mechanisms

Solution Mechanisms

Which intervention mechanism changes the condition?

3 analysis items · Read the method

Core classification and definition · Loss Trust and Entitlement Buffer

Loss Trust and Entitlement Buffer

Apply Loss Trust and Entitlement Buffer across Trust while preserving the protected value.

Buffer loss, regret, probability, completion, and purchase-right risk while preserving existing value and voluntary choice.

View pattern definition →
  1. Core

    RECOMMENDED

    Apply Loss Trust and Entitlement Buffer across Trust while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  2. Supporting

    Cadence and Rhythm Coordination · Attachment

    Apply Cadence and Rhythm Coordination across cycle while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    Context Asset and Authority Isolation · Attachment

    Apply Context Asset and Authority Isolation across small/new guild network access while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence

Solution Compositions

Solution Compositions

How should interventions be combined and sequenced?

5 analysis items · Read the method

Core classification and definition · Single-Track Localized Bundle

Single-Track Localized Bundle

Connect 1 source-declared mechanism across Trust 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

    RECOMMENDED Composition

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

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  2. Supporting

    Cadence and Rhythm Coordination · Attachment Composition

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

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    Context Asset and Authority Isolation · Attachment Composition

    Connect 1 source-declared mechanism across small/new guild network access as Single-Track Localized Bundle.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  4. Supporting

    Parallel Solution-Mechanism Composition

    Connect 3 source-declared mechanisms across Trust as Core-First Branch-Sequential Portfolio.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    Parallel Solution-Mechanism Composition

    Connect 3 source-declared mechanisms across Trust as Parallel Local Contracts with Independent Rollback.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence