NOVASMC

GAME DECISION MAP

Goddess of Victory: NIKKE

Action RPG · Cross-platform · 2022

Current analysisBaseline 2026-07-22Open Decision Analysis →

Build a five-Nikke squad → aim, cover, reload, and trigger Burst chains in Campaign and combat modes → gain rewards and raise Outpost Defense → accumulate idle growth resources → level, skill, equip, and synchronize Nikkes → recruit or refine the roster and enter the next battle.

Recurring Structures

Detailed Repeating Structures

What repeats and keeps the system moving?

CORE CLASSIFICATION

External Calendar

Build a five-Nikke squad → aim, cover, reload, and trigger Burst chains in Campaign and combat modes → gain rewards and raise Outpost Defense → accumulate idle growth resources → level, skill, equip, and synchronize Nikkes → recruit or refine the roster and enter the next battle.

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

View pattern definition →
  1. Supply

    Campaign–Idle Loop

    Campaign clear increases Outpost productivity; Outpost resources fuel level growth; level growth enables next campaign clear.

  2. Supply

    Daily Specialized Farming Loop

    Outpost, Dispatch, Simulation Room, Interception and daily missions route recurring resources into growth.

  3. Supply

    Vertical Challenge Loop

    Tribe Tower, Lost Sector, Overclock and Solo Raid Museum validate power and supply specialized growth resources.

  4. Return

    Seasonal Acceleration Loop

    Events, mini-games, login, FULL BURST DAY and raids create short-term resource acceleration and return reasons.

Bottlenecks

Bottleneck Patterns

Where do decisions and flow break?

CORE CLASSIFICATION

Transition and Handoff Break

The affected flow runs through Mileage → CS; its limiting point is the transition 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 ·

    The affected flow runs through Mileage → CS; its limiting point is the transition handoff.

  2. Supporting

    Rights and Lifecycle Discontinuity · Asset

    The limiting point sits in the asset lifecycle handoff.

  3. Supporting

    Obligation and Volition Erosion · Routine Liveops

    The affected flow runs through Event/Core faucet; its limiting point is the routine liveops return handoff.

  4. Supporting

    Rights and Lifecycle Discontinuity · Asset

    The affected flow runs through Mileage → CS; its limiting point is the asset lifecycle handoff.

  5. Supporting

    Allocation and Coordination Failure · Social Operations

    The affected flow runs through Arena 2 +Solo Raid 1; its limiting point is the social operations coordination handoff.

Contradictions

Contradiction Patterns

What must improve, and what must remain protected?

CORE CLASSIFICATION

State and Timing Integrity vs Operational Volatility

Improve Stability Vs Volatility while preserving Complexity Vs Convenience.

State, deadline, channel, and charge consistency must improve while legitimate operating rhythm, variation, and speed remain protected.

View pattern definition →
  1. Core

    Core Contradiction

    Improve Stability Vs Volatility while preserving Complexity Vs Convenience.

  2. Supporting

    Complexity Vs Convenience / Performance Vs Load

    Improve Complexity Vs Convenience while preserving Performance Vs Load.

  3. Supporting

    Stability Vs Volatility / Complexity Vs Convenience

    Improve Stability Vs Volatility while preserving Complexity Vs Convenience.

  4. Supporting

    Revenue Vs Trust / Popularity Vs Scarcity

    Improve Revenue Vs Trust while preserving Popularity Vs Scarcity.

  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 to the source-declared core track while preserving its 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 to the source-declared core track while preserving its protected value.

  2. Supporting

    State and Rule Visibility Encoding · Attachment

    Apply State and Rule Visibility Encoding to the source-declared attachment track while preserving its protected value.

  3. Supporting

    State and Rule Visibility Encoding · Attachment

    Apply State and Rule Visibility Encoding to the source-declared attachment track while preserving its protected value.

  4. Supporting

    State and Rule Visibility Encoding · Attachment

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

  2. Supporting

    State and Rule Visibility Encoding · Attachment Composition

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

  3. Supporting

    State and Rule Visibility Encoding · Attachment Composition

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

  4. Supporting

    State and Rule Visibility Encoding · Attachment Composition

    Connect 1 source-declared mechanism 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 as Core-First Branch-Sequential Portfolio.

  7. Supporting

    Parallel Solution-Mechanism Composition

    Connect 5 source-declared mechanisms as Parallel Local Contracts with Independent Rollback.