NOVASMC

GAME DECISION MAP

Capybara Go!

Idle RPG · Mobile · 2024

Current analysisBaseline 2026-06-12Open Decision Analysis →

Advance Story Adventure with low-input Auto Turn Combat → resolve battle feedback and collect stage, AFK, Energy, sweep, event, Arena, Guild, and rewarded-access outcomes → acquire equipment, talents, inheritance materials, currencies, and collection assets → enhance, merge, inherit, and compose a build → validate progress in Adventure, competition, cooperation, and rotating events → compare free, saved, exchange, and optional paid routes → return to the next chapter, growth target, or activity.

Recurring Structures

Detailed Repeating Structures

What repeats and keeps the system moving?

CORE CLASSIFICATION

External Calendar

Advance Story Adventure with low-input Auto Turn Combat → resolve battle feedback and collect stage, AFK, Energy, sweep, event, Arena, Guild, and rewarded-access outcomes → acquire equipment, talents, inheritance materials, currencies, and collection assets → enhance, merge, inherit, and compose a build → validate progress in Adventure, competition, cooperation, and rotating events → compare free, saved, exchange, and optional paid routes → return to the next chapter, growth target, or activity.

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

View pattern definition →
  1. Supply

    Story Progression Loop

    Energy → Story/Travel → basic rewards/equipment → Equipment/Talent growth → upper chapter unlock.

  2. Supply

    Specialized Growth Loop

    Ticket/Voucher/Key → Challenge/Dungeon → dedicated materials → Pet/Mount/Artifact/Adventurer/Specialization/Gem growth → higher difficulty.

  3. Competition

    Competition Validation Loop

    Growth build → Arena/Seal/Tournament → rank/division/reward → growth reinvestment → next season competition.

  4. Cooperation

    Cooperation Reinforcement Loop

    Guild/partner content → shared progress, Guild Coin, Aid Token and rewards → shop/growth → stronger future contribution.

  5. Return

    LiveOps Acceleration Loop

    Daily/limited missions specify growth actions and resource use, then return event currencies, gacha tokens and growth materials.

  6. Return

    Return Loop

    Offline time → AFK rewards → immediate reinforcement → frontier retry → daily/weekly routine re-entry.

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

    accretion→legacy

    The limiting point sits in the operations pressure handoff.

  2. Supporting

    schedule→fragmentation

    The limiting point sits in the liveops operations synchronization handoff.

  3. Supporting

    attribution→learning

    The limiting point sits in the combat feedback result handoff.

  4. Supporting

    free opportunity→re-entry

    The limiting point sits in the entry handoff.

  5. Supporting

    acquisition→usable completion

    The limiting point sits in the asset lifecycle handoff.

  6. Supporting

    paid velocity→performance

    The limiting point sits in the competition result handoff.

  7. Supporting

    reward→next advantage

    The limiting point sits in the transition handoff.

  8. Supporting

    participation→completion

    The limiting point sits in the transition handoff.

  9. Supporting

    partner

    The limiting point sits in the social operations coordination handoff.

Contradictions

Contradiction Patterns

What must improve, and what must remain protected?

CORE CLASSIFICATION

Action and Return Continuity vs System Depth and Throughput

Across Layer → Currency → SKU → Event → legacy → QA/CS/ TAT, improve Complexity Vs Convenience 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

    Core Contradiction

    Across Layer → Currency → SKU → Event → legacy → QA/CS/ TAT, improve Complexity Vs Convenience while preserving None.

  2. Supporting

    Complexity Vs Convenience / Speed Vs Integrity

    Across CP → RNG → skill → choice feedback → build edit → retry, improve Complexity Vs Convenience while preserving Speed Vs Integrity.

  3. Supporting

    Revenue Vs Trust / Complexity Vs Convenience

    Across target → rotation → completion cost/time → acquisition usable build completion, improve Revenue Vs Trust while preserving Complexity Vs Convenience.

  4. Supporting

    Performance Vs Load / Freedom Vs Control

    Across participation → completion → reward use → next action ordered closure, improve Performance Vs Load while preserving Freedom Vs Control.

  5. Supporting

    Performance Vs Load / Freedom Vs Control

    Across free supply/opportunity → upgrade → re-entry continuity progression step predictability, improve Performance Vs Load while preserving Freedom Vs Control.

  6. Supporting

    Freedom Vs Control / Performance Vs Load

    Across Co-op access, helper supply, contribution → settlement legibility and sustainable operator value, improve Freedom Vs Control while preserving Performance Vs Load.

Solution Mechanisms

Solution Mechanisms

Which intervention mechanism changes the condition?

CORE CLASSIFICATION

Layered and Progressive Disclosure

Apply Layered and Progressive Disclosure across Layered Continuity Map 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 Continuity Map

    Apply Layered and Progressive Disclosure across Layered Continuity Map while preserving the protected value.

  2. Supporting

    Attribution-to-Edit Ladder

    Apply State and Rule Visibility Encoding across Attribution-to-Edit Ladder while preserving the protected value.

  3. Supporting

    Free-Path Readiness Relay

    Apply Route and Return Handoff across Free-Path Readiness Relay while preserving the protected value.

  4. Supporting

    Acquisition-to-Readiness Contract Ladder

    Apply State and Rule Visibility Encoding across Acquisition-to-Readiness Contract Ladder while preserving the protected value.

  5. Supporting

    Completion-to-Choice Relay

    Apply State and Rule Visibility Encoding across Completion-to-Choice Relay while preserving the protected value.

  6. Supporting

    Voluntary Contribution Lane & Async Mediation Contract

    Apply Context Asset and Authority Isolation across Voluntary Contribution Lane & Async Mediation Contract 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 Layered Continuity Map 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 Continuity Map Composition

    Connect 1 source-declared mechanism across Layered Continuity Map as Single-Track Localized Bundle.

  2. Supporting

    Attribution-to-Edit Ladder Composition

    Connect 1 source-declared mechanism across Attribution-to-Edit Ladder as Single-Track Localized Bundle.

  3. Supporting

    Free-Path Readiness Relay Composition

    Connect 1 source-declared mechanism across Free-Path Readiness Relay as Single-Track Localized Bundle.

  4. Supporting

    Acquisition-to-Readiness Contract Ladder Composition

    Connect 1 source-declared mechanism across Acquisition-to-Readiness Contract Ladder as Single-Track Localized Bundle.

  5. Supporting

    Completion-to-Choice Relay Composition

    Connect 1 source-declared mechanism across Completion-to-Choice Relay as Single-Track Localized Bundle.

  6. Supporting

    Voluntary Contribution Lane & Async Mediation Contract Composition

    Connect 1 source-declared mechanism across Voluntary Contribution Lane & Async Mediation Contract as Single-Track Localized Bundle.

  7. Supporting

    Parallel Solution-Mechanism Composition

    Connect 6 source-declared mechanisms across Layered Continuity Map as Core-First Branch-Sequential Portfolio.

  8. Supporting

    Parallel Solution-Mechanism Composition

    Connect 6 source-declared mechanisms across Layered Continuity Map as Parallel Local Contracts with Independent Rollback.