NOVASMC

GAME DECISION MAP

Honkai: Star Rail

Turn-based RPG · Cross-platform · 2023

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

Problem definition

A bottleneck in cumulative growth continuity between farming outcomes, correction, build changes and deployment.

View all bottlenecks

Design direction

Read the improvement configuration in the detailed record of the mechanism classified as layered and progressive disclosure.

View all mechanisms
Read the recurring-flow summary

Explore and complete quests → enter turn-based battles → farm materials → upgrade characters, Light Cones, and Relics → assemble teams and clear challenges.

REASONING IN THIS GAME

Selected designs and judgment conditions

Goals and residual processing

Initial IFR · goal direction

Create observable continuity from farming outcomes to deployment while preserving depth.

Final IFR · design goal

Apply information layers, consistent state grammar and display continuity across existing farming, relic or ornament, correction, equipment and deployment touchpoints, preserving economic values and research depth.

Recurring Structures

Detailed Repeating Structures

What repeats and keeps the system moving?

1 analysis items · Read the method

Core classification and definition · Resource Conversion

Resource Conversion

Explore and complete quests → enter turn-based battles → farm materials → upgrade characters, Light Cones, and Relics → assemble teams and clear challenges.

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

View pattern definition →
  1. Economy

    Core Combat-Build Loop

    Primary loop is acquire character/Light Cone → grow via / → verify in → reinvest into farming, warp and shop.

    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 · Action Feedback and Failure Attribution Break

Action Feedback and Failure Attribution Break

The limiting point sits in the combat feedback result handoff.

Outcomes, causes, rules, rewards, and retry information do not close the feedback loop needed for correction.

View pattern definition →
  1. Core

    observable accumulation

    The limiting point sits in the combat feedback result handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  2. Supporting

    Fairness and Legitimacy Erosion · Competition

    The limiting point sits in the competition result handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    Obligation and Volition Erosion · Routine Liveops

    The limiting point sits in the routine liveops return handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  4. Supporting

    Rights and Lifecycle Discontinuity · Asset

    The limiting point sits in the asset lifecycle handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    Rights and Lifecycle Discontinuity · Asset

    The limiting point sits in the asset lifecycle handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    Temporal and Operational Synchronization Break · Liveops Operations

    The limiting point sits in the liveops operations synchronization 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

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

    Improve Complexity Vs Convenience while preserving Freedom Vs Control.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  2. Supporting

    Complexity Vs Convenience / Speed Vs Integrity

    Across face, improve Complexity Vs Convenience while preserving Speed Vs Integrity.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    Performance Vs Load / Stability Vs Volatility

    Across clean exit, improve Performance Vs Load while preserving Stability Vs Volatility.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  4. Supporting

    Revenue Vs Trust / Speed Vs Integrity

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

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    Freedom Vs Control / Popularity Vs Scarcity

    Improve Freedom Vs Control while preserving Popularity Vs Scarcity.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    Performance Vs Load / Stability Vs Volatility

    Improve Performance Vs Load while preserving Stability Vs Volatility.

    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

    operator triple

    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 face while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    Cadence and Rhythm Coordination · Attachment

    Apply Cadence and Rhythm Coordination across clean exit while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  4. Supporting

    Loss Trust and Entitlement Buffer · Attachment

    Apply Loss Trust and Entitlement Buffer across use while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    Route and Return Handoff · Attachment

    Apply Route and Return Handoff 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 to the source-declared attachment track while preserving its 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

    operator triple 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 face as Single-Track Localized Bundle.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    Cadence and Rhythm Coordination · Attachment Composition

    Connect 1 source-declared mechanism across clean exit 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 across use as Single-Track Localized Bundle.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    Route and Return Handoff · 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 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 face 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 face as Parallel Local Contracts with Independent Rollback.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence