NOVASMC

GAME DECISION MAP

Last War: Survival

Strategy · Mobile · 2023

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

Problem definition

Pressure in connecting routine reward claims to the next action.

View all bottlenecks

Design direction

Connect existing tasks, mail, schedules, scores, receipts, formation and alliance notices through common state wording, keeping screen authority and free routes separate.

View all mechanisms
Read the recurring-flow summary

Run lane-shooter stages → collect resources and heroes → build and upgrade the base and squads → join alliance and world battles → claim rewards and continue growth.

REASONING IN THIS GAME

Selected designs and judgment conditions

Selected principles and the game-local design12 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?

1 analysis items · Read the method

Core classification and definition · External Calendar

External Calendar

Run lane-shooter stages → collect resources and heroes → build and upgrade the base and squads → join alliance and world battles → claim rewards and continue growth.

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

View pattern definition →
  1. Core

    Main Core Loop

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

    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 · Transition and Handoff Break

Transition and Handoff Break

The limiting point sits in the growth liveops result handoff.

The result of one step does not connect to the next action, return, or reinvestment decision.

View pattern definition →
  1. Core

    Transition and Handoff Break · Growth Liveops

    The limiting point sits in the growth liveops result handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  2. Supporting

    Obligation and Volition Erosion · Liveops Alliance

    The limiting point sits in the liveops alliance return handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    Fairness and Legitimacy Erosion · Alliance Competition

    The limiting point sits in the alliance competition result 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

    Decision and Planning Calculability Breakdown · Combat Growth

    The limiting point sits in the combat growth planning handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    Obligation and Volition Erosion · Alliance Operations

    The limiting point sits in the alliance operations 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 reward_claim, improve Performance Vs Load while preserving None.

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 / None

    Across reward_claim, improve Performance Vs Load while preserving None.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  2. Supporting

    Stability Vs Volatility / None

    Across peak habit loop, improve Stability Vs Volatility while preserving None.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    Freedom Vs Control / None

    Across event score window speedup timing reward_claim next action node, improve Freedom Vs Control while preserving None.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  4. Supporting

    Revenue Vs Trust / None

    Across routine friction , post_purchase_progress_action, improve Revenue Vs Trust while preserving None.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    Complexity Vs Convenience / None

    Across formation asset, improve Complexity Vs Convenience while preserving None.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    Performance Vs Load / None

    Across alliance value pressure proof, improve Performance Vs Load while preserving None.

    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 handoff spine 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 and Return Handoff · Core

    Apply Route and Return Handoff across handoff spine while preserving the 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 missed reward recovery window 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 across timing rule view 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 fallback guardrail while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    branch collection map

    Apply Route and Return Handoff across mixed formation continuity cue while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    Lucky Gift social signal split

    Apply State and Rule Visibility Encoding across Lucky Gift social signal split 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 handoff spine 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 and Return Handoff · Core Composition

    Connect 1 source-declared mechanism across handoff spine 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 missed reward recovery window 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 across timing rule view 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 fallback guardrail as Single-Track Localized Bundle.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    branch collection map Composition

    Connect 1 source-declared mechanism across mixed formation continuity cue as Single-Track Localized Bundle.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    Lucky Gift social signal split Composition

    Connect 1 source-declared mechanism across Lucky Gift social signal split 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 handoff spine 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 handoff spine as Parallel Local Contracts with Independent Rollback.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence