NOVASMC

GAME DECISION MAP

Wuthering Waves

Action RPG · Cross-platform · 2024

Current analysisBaseline 2026-07-24Open Decision Analysis →

Explore the open world → fight with a three-Resonator team using swaps, dodges, and Echo abilities → spend Waveplate on materials and rewards → level Resonators, weapons, skills, and Echo builds → clear challenges and events → summon or refine the roster and pursue the next target.

Recurring Structures

Detailed Repeating Structures

What repeats and keeps the system moving?

CORE CLASSIFICATION

Compounding Growth

Explore the open world → fight with a three-Resonator team using swaps, dodges, and Echo abilities → spend Waveplate on materials and rewards → level Resonators, weapons, skills, and Echo builds → clear challenges and events → summon or refine the roster and pursue the next target.

Outputs strengthen assets, capabilities, or access and open a stronger next cycle.

View pattern definition →
  1. Acquisition

    Core Experience Loop

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

  2. Acquisition

    Roster Growth Loop

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

  3. Supply

    Mastery Loop

    The actual loop runs through Tower/Whimpering/Endstate/Hologram PvE.

  4. Return

    Version Restart Loop

    The actual loop runs through Echo.

  5. Cooperation

    Social Assistance Loop

    The actual loop runs through Co-op → Echo.

  6. Return

    Catch-Up Loop

    The actual loop runs through Pioneer Experience, Guidebook , Bioprinting.

Bottlenecks

Bottleneck Patterns

Where do decisions and flow break?

CORE CLASSIFICATION

Pressure and Concentration Bottleneck

The limiting point sits in the operations pressure handoff.

Difficulty, randomness, growth, or completion pressure accumulates at one decision point and concentrates the burden of retrying or reinvesting.

View pattern definition →
  1. Core

    Pressure and Concentration Bottleneck · Operations

    The limiting point sits in the operations pressure handoff.

  2. Supporting

    Resource and Value Conversion Failure · Economy Commerce

    The limiting point sits in the economy commerce settlement handoff.

  3. Supporting

    Action Feedback and Failure Attribution Break · Combat Feedback

    The limiting point sits in the combat feedback result handoff.

  4. Supporting

    Outcome and Contribution Attribution Failure · Social

    The limiting point sits in the social result handoff.

  5. Supporting

    Decision and Planning Calculability Breakdown · Growth Economy

    The limiting point sits in the growth economy planning handoff.

  6. Supporting

    Obligation and Volition Erosion · Routine Liveops

    The limiting point sits in the routine liveops return handoff.

Contradictions

Contradiction Patterns

What must improve, and what must remain protected?

CORE CLASSIFICATION

Asset and Economy Grammar Legibility vs Structural Diversity and Control

Across Waveplate → Shell Credit capacity, improve Freedom Vs Control while preserving Performance Vs Load.

The roles, inflows, outflows, states, and uses of assets and currencies must become legible while diversity, reuse value, and economic control remain protected.

View pattern definition →
  1. Core

    Core Contradiction

    Across Waveplate → Shell Credit capacity, improve Freedom Vs Control while preserving Performance Vs Load.

  2. Supporting

    Popularity Vs Scarcity / Complexity Vs Convenience

    Across echo_acquire → sort_filter → enhance → tuner_use → result_validity → equip_or_discard → use_duration, improve Popularity Vs Scarcity while preserving Complexity Vs Convenience.

  3. Supporting

    Speed Vs Integrity / Complexity Vs Convenience

    Across challenge_enter → result → record_delta → comparison_view → edit → retry → share_or_status, improve Speed Vs Integrity while preserving Complexity Vs Convenience.

  4. Supporting

    Freedom Vs Control / Performance Vs Load

    Across coop_enter → host_or_join → help_action → contribution → success → friend_or_reform → repeat_party, improve Freedom Vs Control while preserving Performance Vs Load.

  5. Supporting

    Complexity Vs Convenience / Revenue Vs Trust

    Across goal_select → product_view → price_view → currency_convert → total_cost_estimate → buy_or_hold → goal_progress, improve Complexity Vs Convenience while preserving Revenue Vs Trust.

  6. Supporting

    Performance Vs Load / Stability Vs Volatility

    Across schedule_view → deadline_count → task_start → claim → skip_or_hold → compressed_session → unclaimed, improve Performance Vs Load while preserving Stability Vs Volatility.

Solution Mechanisms

Solution Mechanisms

Which intervention mechanism changes the condition?

CORE CLASSIFICATION

Route and Return Handoff

Apply Route and Return Handoff across Waveplate → Shell Credit capacity 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 Waveplate → Shell Credit capacity while preserving the protected value.

  2. Supporting

    State and Rule Visibility Encoding · Attachment

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

  3. Supporting

    State and Rule Visibility Encoding · Attachment

    Apply State and Rule Visibility Encoding across challenge_enter → result → record_delta → comparison_view → edit → retry → share_or_status while preserving the protected value.

  4. Supporting

    State and Rule Visibility Encoding · Attachment

    Apply State and Rule Visibility Encoding across coop_enter → host_or_join → help_action → contribution → success → friend_or_reform → repeat_party while preserving the protected value.

  5. Supporting

    State and Rule Visibility Encoding · Attachment

    Apply State and Rule Visibility Encoding across goal_select → product_view → price_view → currency_convert → total_cost_estimate → buy_or_hold → goal_progress while preserving the protected value.

  6. Supporting

    State and Rule Visibility Encoding · Attachment

    Apply State and Rule Visibility Encoding across schedule_view → deadline_count → task_start → claim → skip_or_hold → compressed_session → unclaimed while preserving the 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 Waveplate → Shell Credit capacity 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 Waveplate → Shell Credit capacity as Single-Track Localized Bundle.

  2. Supporting

    State and Rule Visibility Encoding · Attachment Composition

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

  3. Supporting

    State and Rule Visibility Encoding · Attachment Composition

    Connect 1 source-declared mechanism across challenge_enter → result → record_delta → comparison_view → edit → retry → share_or_status as Single-Track Localized Bundle.

  4. Supporting

    State and Rule Visibility Encoding · Attachment Composition

    Connect 1 source-declared mechanism across coop_enter → host_or_join → help_action → contribution → success → friend_or_reform → repeat_party as Single-Track Localized Bundle.

  5. Supporting

    State and Rule Visibility Encoding · Attachment Composition

    Connect 1 source-declared mechanism across goal_select → product_view → price_view → currency_convert → total_cost_estimate → buy_or_hold → goal_progress as Single-Track Localized Bundle.

  6. Supporting

    State and Rule Visibility Encoding · Attachment Composition

    Connect 1 source-declared mechanism across schedule_view → deadline_count → task_start → claim → skip_or_hold → compressed_session → unclaimed as Single-Track Localized Bundle.

  7. Supporting

    Parallel Solution-Mechanism Composition

    Connect 6 source-declared mechanisms across Waveplate → Shell Credit capacity as Core-First Branch-Sequential Portfolio.

  8. Supporting

    Parallel Solution-Mechanism Composition

    Connect 6 source-declared mechanisms across Waveplate → Shell Credit capacity as Parallel Local Contracts with Independent Rollback.