NOVASMC

GAME DECISION MAP

Township

City-building Simulation · Cross-platform · 2011

Current analysisBaseline 2026-06-23Open Decision Analysis → · Korean full analysis

Problem definition

A bottleneck in reading combined supply and next actions in the growth flow.

View all bottlenecks

Design direction

Connect prerequisites and next consequences of production, orders, market, waiting and convenience routes through a dismissible comparison layer at the need state, preserving the economy, prices and free routes.

View all mechanisms
Read the recurring-flow summary

Plant and harvest crops → raise animals and process goods in factories → fulfill Helicopter, Train, and Airport orders → earn Coins, XP, building materials, and tools → level up and expand population, land, Barn, and production capacity → join Team, Regatta, Match-3 events, collections, Mine, Zoo, and islands → reinvest and produce again.

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.

Goals and residual processing

Initial IFR · goal direction

Recombine state, routing, queue-result exposure, sequence and comparison rules.

Recurring Structures

Detailed Repeating Structures

What repeats and keeps the system moving?

3 analysis items · Read the method

Core classification and definition · External Calendar

External Calendar

Plant and harvest crops → raise animals and process goods in factories → fulfill Helicopter, Train, and Airport orders → earn Coins, XP, building materials, and tools → level up and expand population, land, Barn, and production capacity → join Team, Regatta, Match-3 events, collections, Mine, Zoo, and islands → reinvest and produce again.

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

View pattern definition →
  1. Supply

    Adaptive Fallback · Supply

    This source-declared supply loop connects the game's actual repeat sequence.

    Evidence
    Source Described
    Outcome basis
    Design Evidence
  2. Return

    Adaptive Fallback ·

    The actual loop runs through Match-3.

    Evidence
    Source Described
    Outcome basis
    Design Evidence
  3. Resilience

    Adaptive Fallback · Resilience

    The actual loop runs through Grand → Thematic.

    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 limiting point sits in the production growth 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 · Production Growth

    The limiting point sits in the production growth planning handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  2. Supporting

    Access and Qualification Friction · Cooperation

    The limiting point sits in the cooperation entry handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    Legibility and Interpretation Break · Market Production

    The limiting point sits in the market production entry handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  4. Supporting

    Resource and Value Conversion Failure · Commerce Growth

    The limiting point sits in the commerce growth settlement handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    Outcome and Contribution Attribution Failure · Event Cooperation

    The limiting point sits in the event cooperation result handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    Rights and Lifecycle Discontinuity · City

    The limiting point sits in the city return 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 · Action and Return Continuity vs System Depth and Throughput

Action and Return Continuity vs System Depth and Throughput

Across need-state route → queue → next-result, improve Complexity Vs Convenience 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

    Core Contradiction

    Across need-state route → queue → next-result, improve Complexity Vs Convenience while preserving Freedom Vs Control.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  2. Supporting

    Complexity Vs Convenience / Stability Vs Volatility

    Across entry → contribution/reward/value → continuation, improve Complexity Vs Convenience while preserving Stability Vs Volatility.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    Complexity Vs Convenience / None

    Across role/currency/reward hierarchy claim/use, improve Complexity Vs Convenience while preserving None.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  4. Supporting

    Revenue Vs Trust / Freedom Vs Control

    Across intent → free alternative → post-use → next-session relief, improve Revenue Vs Trust while preserving Freedom Vs Control.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    Complexity Vs Convenience / Freedom Vs Control

    Across contribution → role → reward → recognition → operation, improve Complexity Vs Convenience while preserving Freedom Vs Control.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    Complexity Vs Convenience / Popularity Vs Scarcity

    Across remaining distance → duplicate correction → ownership → display/use, improve Complexity Vs Convenience while preserving Popularity Vs Scarcity.

    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 · Route and Return Handoff

Route and Return Handoff

Apply Route and Return Handoff across Route & Queue Contract Layer 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

    Route & Queue Contract Layer

    Apply Route and Return Handoff across Route & Queue Contract Layer while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  2. Supporting

    Entry-to-Continuation Contract Layer

    Apply State and Rule Visibility Encoding across Entry-to-Continuation Contract Layer while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    Event Claim-State Disclosure Standard

    Apply State and Rule Visibility Encoding across Event Claim-State Disclosure Standard while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  4. Supporting

    Post-Use Value Contract Layer

    Apply State and Rule Visibility Encoding across Post-Use Value Contract Layer while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    Help-to-Recognition Receipt Standard

    Apply State and Rule Visibility Encoding across Help-to-Recognition Receipt Standard while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    Gap-to-Ownership Receipt Standard

    Apply State and Rule Visibility Encoding across Gap-to-Ownership Receipt Standard 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 across Route & Queue Contract Layer 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

    Route & Queue Contract Layer Composition

    Connect 1 source-declared mechanism across Route & Queue Contract Layer as Single-Track Localized Bundle.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  2. Supporting

    Entry-to-Continuation Contract Layer Composition

    Connect 1 source-declared mechanism across Entry-to-Continuation Contract Layer as Single-Track Localized Bundle.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    Event Claim-State Disclosure Standard Composition

    Connect 1 source-declared mechanism across Event Claim-State Disclosure Standard as Single-Track Localized Bundle.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  4. Supporting

    Post-Use Value Contract Layer Composition

    Connect 1 source-declared mechanism across Post-Use Value Contract Layer as Single-Track Localized Bundle.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    Help-to-Recognition Receipt Standard Composition

    Connect 1 source-declared mechanism across Help-to-Recognition Receipt Standard as Single-Track Localized Bundle.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    Gap-to-Ownership Receipt Standard Composition

    Connect 1 source-declared mechanism across Gap-to-Ownership Receipt Standard 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 Route & Queue Contract Layer 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 Route & Queue Contract Layer as Parallel Local Contracts with Independent Rollback.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence