NOVASMC

GAME DECISION MAP

Mabinogi Mobile

MMORPG · Cross-platform · 2025

Current analysisBaseline 2026-03-18Open Decision Analysis →

Explore Erinn → switch combat classes and complete quests or dungeons → gather and craft through life skills → upgrade equipment, runes, and combat or life power → join cooperative raids, guild, and social activities.

Recurring Structures

Detailed Repeating Structures

What repeats and keeps the system moving?

CORE CLASSIFICATION

External Calendar

Explore Erinn → switch combat classes and complete quests or dungeons → gather and craft through life skills → upgrade equipment, runes, and combat or life power → join cooperative raids, guild, and social activities.

Events, operating schedules, and live operations reactivate participation, exchange, and reward states.

View pattern definition →
  1. Core

    Story → Dungeon → Life Content Loop

    Early-to-mid progression alternates main story, combat missions, dungeons, and life-content beats to vary tempo.

  2. Core

    Challenge Endgame Loop

    Unlimited Tower, hard PvE, and world boss content extend late-game challenge after core progression.

  3. Supply

    Daily Farming Loop

    Adventure / field / dungeon repeats feed EXP, gear, gold, and steady power growth.

  4. Return

    World

    World events and community activities are inserted into repeat loops to reduce farming fatigue.

Bottlenecks

Bottleneck Patterns

Where do decisions and flow break?

CORE CLASSIFICATION

Resource and Value Conversion Failure

The affected flow runs through causal order after controls; its limiting point is the growth planning handoff.

Currencies, assets, products, or inputs do not convert reliably into utility or residual value.

View pattern definition →
  1. Core

    Resource and Value Conversion Failure · Growth

    The affected flow runs through causal order after controls; its limiting point is the growth planning handoff.

  2. Supporting

    Transition and Handoff Break · Content Growth

    The affected flow runs through residual after CT/event/competition; its limiting point is the content growth return handoff.

  3. Supporting

    Obligation and Volition Erosion · Routine Liveops

    The affected flow runs through dose/threshold after controls; its limiting point is the routine liveops return handoff.

  4. Supporting

    Pressure and Concentration Bottleneck · Commerce Liveops

    The affected flow runs through residual after CT exposure control; its limiting point is the commerce liveops entry handoff.

  5. Supporting

    Fairness and Legitimacy Erosion · Competition Commerce

    The affected flow runs through reproducible segmented response; its limiting point is the competition commerce result handoff.

  6. Supporting

    Outcome and Contribution Attribution Failure · Cooperation Social

    The affected flow runs through graph/return relation after access controls; its limiting point is the cooperation social result handoff.

Contradictions

Contradiction Patterns

What must improve, and what must remain protected?

CORE CLASSIFICATION

Probabilistic Safety vs Scarcity Revenue and Autonomy

Improve Complexity Vs Convenience while preserving Freedom Vs Control.

Probability, guarantee, duplication, and completion safeguards must become decidable while scarcity, revenue structure, autonomy, and higher-order value remain protected.

View pattern definition →
  1. Core

    Core Contradiction

    Improve Complexity Vs Convenience while preserving Freedom Vs Control.

  2. Supporting

    Complexity Vs Convenience / Stability Vs Volatility

    Across completion next-goal progress meaning, improve Complexity Vs Convenience while preserving Stability Vs Volatility.

  3. Supporting

    Performance Vs Load / Stability Vs Volatility

    Across voluntary cadence, improve Performance Vs Load while preserving Stability Vs Volatility.

  4. Supporting

    Revenue Vs Trust / Freedom Vs Control

    Across offer, improve Revenue Vs Trust while preserving Freedom Vs Control.

  5. Supporting

    Freedom Vs Control / Revenue Vs Trust

    Across segment rule → public payoff, improve Freedom Vs Control while preserving Revenue Vs Trust.

  6. Supporting

    Complexity Vs Convenience / Freedom Vs Control

    Across role → reciprocity → rematch relationship accumulation, 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 growth attempt/result contract 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 and Progressive Disclosure · Core

    Apply Layered and Progressive Disclosure across growth attempt/result contract while preserving the protected value.

  2. Supporting

    Route and Return Handoff · Attachment

    Apply Route and Return Handoff across permanent purpose compass while preserving the protected value.

  3. Supporting

    Cadence and Rhythm Coordination · Attachment

    Apply Cadence and Rhythm Coordination across current-window voluntary cadence while preserving the protected value.

  4. Supporting

    State and Rule Visibility Encoding · Attachment

    Apply State and Rule Visibility Encoding across source-bound voluntary offer record while preserving the protected value.

  5. Supporting

    State and Rule Visibility Encoding · Attachment

    Apply State and Rule Visibility Encoding across responsibility-separated competition ledger while preserving the protected value.

  6. Supporting

    Route and Return Handoff · Attachment

    Apply Route and Return Handoff across source-bound reciprocity continuity 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 growth attempt/result contract 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 and Progressive Disclosure · Core Composition

    Connect 1 source-declared mechanism across growth attempt/result contract as Single-Track Localized Bundle.

  2. Supporting

    Route and Return Handoff · Attachment Composition

    Connect 1 source-declared mechanism across permanent purpose compass as Single-Track Localized Bundle.

  3. Supporting

    Cadence and Rhythm Coordination · Attachment Composition

    Connect 1 source-declared mechanism across current-window voluntary cadence as Single-Track Localized Bundle.

  4. Supporting

    State and Rule Visibility Encoding · Attachment Composition

    Connect 1 source-declared mechanism across source-bound voluntary offer record as Single-Track Localized Bundle.

  5. Supporting

    State and Rule Visibility Encoding · Attachment Composition

    Connect 1 source-declared mechanism across responsibility-separated competition ledger as Single-Track Localized Bundle.

  6. Supporting

    Route and Return Handoff · Attachment Composition

    Connect 1 source-declared mechanism across source-bound reciprocity continuity as Single-Track Localized Bundle.

  7. Supporting

    Parallel Solution-Mechanism Composition

    Connect 6 source-declared mechanisms across growth attempt/result contract as Core-First Branch-Sequential Portfolio.

  8. Supporting

    Parallel Solution-Mechanism Composition

    Connect 6 source-declared mechanisms across growth attempt/result contract as Parallel Local Contracts with Independent Rollback.