NOVASMC

GAME DECISION MAP

Merge Mansion

Merge-2 Puzzle · Mobile · 2020

Current analysisBaseline 2026-06-05Open Decision Analysis →

Read the current Task and persistent 7×9 Main Board → tap Producers using Yellow Energy → merge two matching items into the next chain state → manage Board space, Regular Inventory, Producer cooldown, and alternate routes → submit required items to restore the mansion and reveal story → receive Coins, Gems, XP, parts, chests, Pass or event progress → return to the next Task, Producer decision, Daily, Pass, collection, or optional competition cycle.

Recurring Structures

Detailed Repeating Structures

What repeats and keeps the system moving?

CORE CLASSIFICATION

Compounding Growth

Read the current Task and persistent 7×9 Main Board → tap Producers using Yellow Energy → merge two matching items into the next chain state → manage Board space, Regular Inventory, Producer cooldown, and alternate routes → submit required items to restore the mansion and reveal story → receive Coins, Gems, XP, parts, chests, Pass or event progress → return to the next Task, Producer decision, Daily, Pass, collection, or optional competition cycle.

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

View pattern definition →
  1. Core

    Mainline Restoration Loop

    The actual loop runs through Energy → Producer → Item Chain → Task → Story Beat → Task/Area.

  2. Acquisition

    Daily Support Loop

    The actual loop runs through Mainline /Trade → Key → Point → Chest.

  3. Supply

    Season Pass Loop

    The actual loop runs through Pass Item → Milestone.

  4. Return

    Separate Board Event Loop

    The actual loop runs through Board/Energy/Producer → Chain → Point/Milestone/Rank → Pouch → Mainline.

  5. Return

    Core-Integrated Event Loop

    The actual loop runs through Task → Trade → Bubble → Merge → Event Point → Race/League/Milestone.

  6. Acquisition

    Collection Loop

    The actual loop runs through Event/Offer Collection Unit → Set → Collection.

Bottlenecks

Bottleneck Patterns

Where do decisions and flow break?

CORE CLASSIFICATION

Access and Qualification Friction

The affected flow runs through state → action → return/transaction; its limiting point is the resource progression handoff.

Players cannot reliably identify, meet, or sustain the opportunity, qualification, capability, role, or viable path needed to enter.

View pattern definition →
  1. Core

    Access and Qualification Friction · Resource Progression

    The affected flow runs through state → action → return/transaction; its limiting point is the resource progression handoff.

  2. Supporting

    Transition and Handoff Break · Progression Commerce

    The affected flow runs through post-use completion/regret/repeat; its limiting point is the progression commerce return handoff.

  3. Supporting

    Temporal and Operational Synchronization Break · Operations

    The affected flow runs through cycle burden → return; its limiting point is the operations return handoff.

  4. Supporting

    Temporal and Operational Synchronization Break · Liveops Commerce

    The affected flow runs through three cycles; its limiting point is the liveops commerce settlement handoff.

  5. Supporting

    Resource and Value Conversion Failure · Progression Economy

    The affected flow runs through item use → next delta; its limiting point is the progression economy result handoff.

Contradictions

Contradiction Patterns

What must improve, and what must remain protected?

CORE CLASSIFICATION

Action and Return Continuity vs System Depth and Throughput

Improve Performance Vs Load while preserving Freedom Vs Control.

Continuity to the next action, return, or reinvestment must improve while route diversity, strategic depth, and throughput remain protected.

View pattern definition →
  1. Core

    Performance Vs Load / Freedom Vs Control

    Improve Performance Vs Load while preserving Freedom Vs Control.

  2. Supporting

    Revenue Vs Trust / Freedom Vs Control

    Improve Revenue Vs Trust while preserving Freedom Vs Control.

  3. Supporting

    Performance Vs Load / Stability Vs Volatility

    Improve Performance Vs Load while preserving Stability Vs Volatility.

  4. Supporting

    Revenue Vs Trust / Speed Vs Integrity

    Improve Revenue Vs Trust while preserving Speed Vs Integrity.

  5. Supporting

    Complexity Vs Convenience / Freedom Vs Control

    Improve Complexity Vs Convenience while preserving Freedom Vs Control.

Solution Mechanisms

Solution Mechanisms

Which intervention mechanism changes the condition?

CORE CLASSIFICATION

Route and Return Handoff

Apply Route and Return Handoff across Constraint-Sliced Next-Action Bridge 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

    Constraint-Sliced Next-Action Bridge

    Apply Route and Return Handoff across Constraint-Sliced Next-Action Bridge while preserving the protected value.

  2. Supporting

    State-Verified Relief-to-Completion Bridge

    Apply Route and Return Handoff across State-Verified Relief-to-Completion Bridge while preserving the protected value.

  3. Supporting

    State-Verified Item–Task Fit & Use Bridge

    Apply Context Asset and Authority Isolation across State-Verified Item Task Fit & Use Bridge while preserving the protected value.

  4. Supporting

    Canonical Routine Schedule & Skip Disclosure

    Apply Cadence and Rhythm Coordination across Canonical Routine Schedule & Skip Disclosure while preserving the protected value.

  5. Supporting

    Canonical Pass End-State Disclosure & Value Lock

    Apply Loss Trust and Entitlement Buffer across Canonical Pass End-State Disclosure & Value Lock 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 Constraint-Sliced Next-Action Bridge 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

    Constraint-Sliced Next-Action Bridge Composition

    Connect 1 source-declared mechanism across Constraint-Sliced Next-Action Bridge as Single-Track Localized Bundle.

  2. Supporting

    State-Verified Relief-to-Completion Bridge Composition

    Connect 1 source-declared mechanism across State-Verified Relief-to-Completion Bridge as Single-Track Localized Bundle.

  3. Supporting

    State-Verified Item–Task Fit & Use Bridge Composition

    Connect 1 source-declared mechanism across State-Verified Item Task Fit & Use Bridge as Single-Track Localized Bundle.

  4. Supporting

    Canonical Routine Schedule & Skip Disclosure Composition

    Connect 1 source-declared mechanism across Canonical Routine Schedule & Skip Disclosure as Single-Track Localized Bundle.

  5. Supporting

    Canonical Pass End-State Disclosure & Value Lock Composition

    Connect 1 source-declared mechanism across Canonical Pass End-State Disclosure & Value Lock as Single-Track Localized Bundle.

  6. Supporting

    Parallel Solution-Mechanism Composition

    Connect 5 source-declared mechanisms across Constraint-Sliced Next-Action Bridge as Parallel Local Contracts with Independent Rollback.

  7. Supporting

    Parallel Solution-Mechanism Composition

    Connect 2 source-declared mechanisms across Canonical Routine Schedule & Skip Disclosure as Core-First Branch-Sequential Portfolio.