NOVASMC

GAME DECISION MAP

Love and Deepspace

Action RPG · Cross-platform · 2024

Current analysisBaseline 2026-06-21Open Decision Analysis →

Follow Main Story and companion combat → farm Bounty Hunt, Core Hunt, Trials, and daily tasks → strengthen Memories and Protocores and prepare Stellactrum formations → unlock Affinity, Date, Voice, Home, and Photo relationship content → acquire limited Memories through Wish, shops, exchanges, and events → return to story, combat, and relationship progression.

Recurring Structures

Detailed Repeating Structures

What repeats and keeps the system moving?

CORE CLASSIFICATION

External Calendar

Follow Main Story and companion combat → farm Bounty Hunt, Core Hunt, Trials, and daily tasks → strengthen Memories and Protocores and prepare Stellactrum formations → unlock Affinity, Date, Voice, Home, and Photo relationship content → acquire limited Memories through Wish, shops, exchanges, and events → return to story, combat, and relationship progression.

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

View pattern definition →
  1. Core

    Home

    Home, study/workout/work, mini-games and photo features maintain non-combat retention between major banners.

  2. Core

    Low-toxicity Challenge Loop

    Hunter Contest and Trials keep mastery pressure asynchronous and subordinate to relationship immersion.

  3. Return

    Core Relationship Growth Loop

    Story/battle/farming feed Memory growth; Memory and Affinity unlock dates, voice, Myths, home/photo interaction; events and Wish Pools restart the loop.

  4. Supply

    Combat Growth Farm Loop

    Bounty Hunt and Core Hunt supply materials and Protocores; Deepspace Trials and Hunter Contest validate the resulting builds.

  5. Return

    Limited Event Monetization Loop

    Version/event trigger creates desire for limited Memory/outfit/home/photo value; Wish and shop conversion then feed relationship assets.

  6. Cooperation

    Partner Cooperation Loop

    Player-partner pair combat and daily shared activities substitute for guild-style social cooperation.

Bottlenecks

Bottleneck Patterns

Where do decisions and flow break?

CORE CLASSIFICATION

Decision and Planning Calculability Breakdown

The limiting point sits in the growth collection 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 Collection

    The limiting point sits in the growth collection planning handoff.

  2. Supporting

    Rights and Lifecycle Discontinuity · Commerce

    The limiting point sits in the commerce result handoff.

  3. Supporting

    Temporal and Operational Synchronization Break · Liveops Event

    The limiting point sits in the liveops event return handoff.

  4. Supporting

    Pressure and Concentration Bottleneck · Roster Growth

    The affected flow runs through requirement → allocation → retry; its limiting point is the roster growth planning handoff.

  5. Supporting

    Action Feedback and Failure Attribution Break · Combat Mastery

    The limiting point sits in the combat mastery result handoff.

Contradictions

Contradiction Patterns

What must improve, and what must remain protected?

CORE CLASSIFICATION

Action and Return Continuity vs System Depth and Throughput

Across Home → Event, 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 Home → Event, improve Complexity Vs Convenience while preserving Freedom Vs Control.

  2. Supporting

    Limited Wish Decision Contract

    Across Limited/Precise Wish, improve Revenue Vs Trust while preserving Freedom Vs Control.

  3. Supporting

    Event Concurrency and Post-Event Residence

    Across event core, improve Stability Vs Volatility while preserving Performance Vs Load.

  4. Supporting

    Late Multi-Formation

    Across setup → roster/resource → retry, improve Complexity Vs Convenience while preserving Freedom Vs Control.

  5. Supporting

    Combat Result–Rule–Correction–Retry Continuity

    Improve Complexity Vs Convenience while preserving None.

Solution Mechanisms

Solution Mechanisms

Which intervention mechanism changes the condition?

CORE CLASSIFICATION

Layered and Progressive Disclosure

Apply Layered and Progressive Disclosure across Home → Event 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 Home → Event while preserving the protected value.

  2. Supporting

    State and Rule Visibility Encoding · Attachment

    Apply State and Rule Visibility Encoding across Wish while preserving the protected value.

  3. Supporting

    State and Rule Visibility Encoding · Attachment

    Apply State and Rule Visibility Encoding across Event while preserving the protected value.

  4. Supporting

    State and Rule Visibility Encoding · Attachment

    Apply State and Rule Visibility Encoding across setup → roster/resource → retry while preserving the protected value.

  5. Supporting

    State and Rule Visibility Encoding · Attachment

    Apply State and Rule Visibility Encoding to the source-declared attachment track while preserving its 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 Home → Event 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 Home → Event as Single-Track Localized Bundle.

  2. Supporting

    State and Rule Visibility Encoding · Attachment Composition

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

  3. Supporting

    State and Rule Visibility Encoding · Attachment Composition

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

  4. Supporting

    State and Rule Visibility Encoding · Attachment Composition

    Connect 1 source-declared mechanism across setup → roster/resource → retry as Single-Track Localized Bundle.

  5. Supporting

    State and Rule Visibility Encoding · Attachment Composition

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

  6. Supporting

    Parallel Solution-Mechanism Composition

    Connect 5 source-declared mechanisms across Home → Event as Core-First Branch-Sequential Portfolio.

  7. Supporting

    Parallel Solution-Mechanism Composition

    Connect 5 source-declared mechanisms across Home → Event as Parallel Local Contracts with Independent Rollback.