NOVASMC

GAME DECISION MAP

Puzzle & Dragons

Puzzle RPG · Mobile · 2012

Current analysisBaseline 2026-07-09Open Decision Analysis → · Korean full analysis

Problem definition

Multiple growth layers, required mechanics and monster eligibility interrupt the calculability of valid teams and dungeon performance.

View all bottlenecks

Design direction

Layer readiness, optional causes, dependencies and outcome history before team formation, preserving evidence for materials, modes, acquisition and events, and free, manual core play.

View all mechanisms
Read the recurring-flow summary

Choose a dungeon and team → match drops → defeat enemies → collect, strengthen, and evolve monsters → enter harder dungeons.

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.

Recurring Structures

Detailed Repeating Structures

What repeats and keeps the system moving?

2 analysis items · Read the method

Core classification and definition · Compounding Growth

Compounding Growth

Choose a dungeon and team → match drops → defeat enemies → collect, strengthen, and evolve monsters → enter harder dungeons.

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

View pattern definition →
  1. Supply

    Dungeon Core Loop

    Dungeon entry → puzzle combat → reward → monster growth/evolution → re-team → higher dungeon challenge.

    Evidence
    Source Described
    Outcome basis
    Design Evidence
  2. Economy

    One-touch Parallel Sub-loop

    One-touch Dungeon adds automated exploration with its own rules, time reduction and exchange materials.

    Evidence
    Source Described
    Outcome basis
    Design Evidence

Bottlenecks

Bottleneck Patterns

Where do decisions and flow break?

6 analysis items · Read the method

Core classification and definition · Decision and Planning Calculability Breakdown

Decision and Planning Calculability Breakdown

The affected flow runs through owned_asset → growth_choice → team_edit → eligibility → stage_result → retry/acquire; its limiting point is the growth economy planning handoff.

Multiple goals, resources, states, rules, and paths cannot be compared on one decision surface, forcing repeated reprioritization.

View pattern definition →
  1. Core

    Decision and Planning Calculability Breakdown · Growth Economy

    The affected flow runs through owned_asset → growth_choice → team_edit → eligibility → stage_result → retry/acquire; its limiting point is the growth economy planning handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  2. Supporting

    Decision and Planning Calculability Breakdown · Growth Economy

    The affected flow runs through material_need → route_search → exchange/shop/dungeon → gain → growth; its limiting point is the growth economy planning handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    Access and Qualification Friction ·

    The affected flow runs through mode_view → team_edit → entry/cancel → result → retry; its limiting point is the entry handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  4. Supporting

    Rights and Lifecycle Discontinuity · Asset

    The affected flow runs through channel_compare → detail/probability → pull → duplicate → deploy/exchange; its limiting point is the asset lifecycle handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    Obligation and Volition Erosion · Routine Liveops

    The affected flow runs through return → event_goal → progress → reward/exchange → next_action → next_session; its limiting point is the routine liveops return handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    Resource and Value Conversion Failure · Economy Commerce

    The affected flow runs through offer/view → use → manual_task_delta → core_return → renew; its limiting point is the economy commerce settlement 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

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 →
  1. Core

    Core Contradiction

    Improve Complexity Vs Convenience while preserving Freedom Vs Control.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  2. Supporting

    Complexity Vs Convenience / Freedom Vs Control

    Across source/sink, improve Complexity Vs Convenience while preserving Freedom Vs Control.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    Complexity Vs Convenience / Speed Vs Integrity

    Improve Complexity Vs Convenience while preserving Speed Vs Integrity.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  4. Supporting

    Revenue Vs Trust / Popularity Vs Scarcity

    Improve Revenue Vs Trust while preserving Popularity Vs Scarcity.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    Performance Vs Load / Stability Vs Volatility

    Improve Performance Vs Load while preserving Stability Vs Volatility.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    Revenue Vs Trust / Complexity Vs Convenience

    Across entitlement, improve Revenue Vs Trust while preserving Complexity Vs Convenience.

    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 · Layered and Progressive Disclosure

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 and Progressive Disclosure · Core

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

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  2. Supporting

    State and Rule Visibility Encoding · Attachment

    Apply State and Rule Visibility Encoding across source/sink while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    State and Rule Visibility Encoding · Attachment

    Apply State and Rule Visibility Encoding to the source-declared attachment track while preserving its protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  4. Supporting

    Loss Trust and Entitlement Buffer · Attachment

    Apply Loss Trust and Entitlement Buffer to the source-declared attachment track while preserving its protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    Cadence and Rhythm Coordination · Attachment

    Apply Cadence and Rhythm Coordination to the source-declared attachment track while preserving its protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    State and Rule Visibility Encoding · Attachment

    Apply State and Rule Visibility Encoding across entitlement 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 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 as Single-Track Localized Bundle.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  2. Supporting

    State and Rule Visibility Encoding · Attachment Composition

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

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    State and Rule Visibility Encoding · Attachment Composition

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

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  4. Supporting

    Loss Trust and Entitlement Buffer · Attachment Composition

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

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    Cadence and Rhythm Coordination · Attachment Composition

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

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    State and Rule Visibility Encoding · Attachment Composition

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

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  7. Supporting

    Parallel Solution-Mechanism Composition

    Connect 6 source-declared mechanisms across source/sink as Core-First Branch-Sequential Portfolio.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  8. Supporting

    Parallel Solution-Mechanism Composition

    Connect 6 source-declared mechanisms across source/sink as Parallel Local Contracts with Independent Rollback.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence