NOVASMC

GAME DECISION MAP

MapleStory: Idle RPG

Idle RPG · Cross-platform · 2025

Current analysisBaseline 2026-04-30Open Decision Analysis →

Auto-hunt through chapter stages → collect EXP, currency, and materials → summon or enhance weapons, companions, and growth systems → raise combat power → clear harder bosses, stages, or ranking activities.

Recurring Structures

Detailed Repeating Structures

What repeats and keeps the system moving?

CORE CLASSIFICATION

Resource Conversion

Auto-hunt through chapter stages → collect EXP, currency, and materials → summon or enhance weapons, companions, and growth systems → raise combat power → clear harder bosses, stages, or ranking activities.

Currencies, duplicate assets, rights, or exchange outputs become inputs or qualifications for the next cycle.

View pattern definition →
  1. Core

    Core Loop

    Chapter idle hunt → core currency/EXP → growth sinks → power → next gate.

Bottlenecks

Bottleneck Patterns

Where do decisions and flow break?

CORE CLASSIFICATION

Resource and Value Conversion Failure

The limiting point sits in the economy commerce settlement 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 · Economy Commerce

    The limiting point sits in the economy commerce settlement handoff.

  2. Supporting

    PC Login

    The limiting point sits in the liveops operations synchronization handoff.

  3. Supporting

    Resource and Value Conversion Failure · Economy Commerce

    The limiting point sits in the economy commerce settlement handoff.

  4. Supporting

    Pressure and Concentration Bottleneck · Operations

    The limiting point sits in the operations pressure handoff.

  5. Supporting

    Rights and Lifecycle Discontinuity · Asset

    The limiting point sits in the asset lifecycle handoff.

  6. Supporting

    Daily Battle Pass

    The limiting point sits in the rules handoff.

Contradictions

Contradiction Patterns

What must improve, and what must remain protected?

CORE CLASSIFICATION

Participation and Routine Burden Relief vs Operational Vitality and Reward Value

Improve Performance Vs Load while preserving Freedom Vs Control.

The burden and compulsion of participation, schedules, and processing routines must decrease while competitive, event, and progression vitality and reward meaning remain protected.

View pattern definition →
  1. Core

    Core Contradiction

    Improve Performance Vs Load while preserving Freedom Vs Control.

  2. Supporting

    Daily Battle Pass

    Across entitlement, improve Revenue Vs Trust while preserving Speed Vs Integrity.

  3. Supporting

    PC Login

    Across missed-window, improve Performance Vs Load while preserving Stability Vs Volatility.

  4. Supporting

    Popularity Vs Scarcity / Freedom Vs Control

    Across Event Exchange, improve Popularity Vs Scarcity while preserving Freedom Vs Control.

  5. Supporting

    Freedom Vs Control / Revenue Vs Trust

    Across progression affordability, improve Freedom Vs Control while preserving Revenue Vs Trust.

  6. Supporting

    Revenue Vs Trust / Popularity Vs Scarcity

    Improve Revenue Vs Trust while preserving Popularity Vs Scarcity.

Solution Mechanisms

Solution Mechanisms

Which intervention mechanism changes the condition?

CORE CLASSIFICATION

Route and Return Handoff

Apply Route and Return Handoff across Soft Cap Boundary & Overflow Buffer while preserving the protected value.

Connect the current state to valid next actions, routes, retries, and returns while preserving choice and existing paths.

View pattern definition →
  1. Core

    Return Claim Queue

    Apply Route and Return Handoff across Soft Cap Boundary & Overflow Buffer while preserving the protected value.

  2. Supporting

    Cadence Split Calendar

    Apply Cadence and Rhythm Coordination across Missed-Window Recovery Buffer while preserving the protected value.

  3. Supporting

    Exchange Scarcity Clarity Floor

    Apply State and Rule Visibility Encoding across Exchange Scarcity Clarity Floor while preserving the protected value.

  4. Supporting

    Progression Recovery Credit

    Apply Route and Return Handoff across Next Milestone Route Mediator while preserving the protected value.

  5. Supporting

    Safety-Net Rate Card

    Apply Loss Trust and Entitlement Buffer across Duplicate-to-Mileage Ledger while preserving the protected value.

  6. Supporting

    Pre-Purchase Scope Table

    Apply Loss Trust and Entitlement Buffer across Pre-Purchase Scope Table 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 Soft Cap Boundary & Overflow Buffer 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

    Return Claim Queue Composition

    Connect 1 source-declared mechanism across Soft Cap Boundary & Overflow Buffer as Single-Track Localized Bundle.

  2. Supporting

    Cadence Split Calendar Composition

    Connect 1 source-declared mechanism across Missed-Window Recovery Buffer as Single-Track Localized Bundle.

  3. Supporting

    Exchange Scarcity Clarity Floor Composition

    Connect 1 source-declared mechanism across Exchange Scarcity Clarity Floor as Single-Track Localized Bundle.

  4. Supporting

    Progression Recovery Credit Composition

    Connect 1 source-declared mechanism across Next Milestone Route Mediator as Single-Track Localized Bundle.

  5. Supporting

    Safety-Net Rate Card Composition

    Connect 1 source-declared mechanism across Duplicate-to-Mileage Ledger as Single-Track Localized Bundle.

  6. Supporting

    Pre-Purchase Scope Table Composition

    Connect 1 source-declared mechanism across Pre-Purchase Scope Table as Single-Track Localized Bundle.

  7. Supporting

    Parallel Solution-Mechanism Composition

    Connect 6 source-declared mechanisms across Soft Cap Boundary & Overflow Buffer as Core-First Branch-Sequential Portfolio.

  8. Supporting

    Parallel Solution-Mechanism Composition

    Connect 6 source-declared mechanisms across Soft Cap Boundary & Overflow Buffer as Parallel Local Contracts with Independent Rollback.