NOVASMC

GAME DECISION MAP

PUBG Mobile

Battle Royale · Mobile · 2018

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

Problem definition

A bottleneck in translating outcomes from multiple loops into account value.

View all bottlenecks

Design direction

Connect mode-native outcomes to non-power account attribution and optional existing goals, preserving mode economies, combat power and fairness.

View all mechanisms
Read the recurring-flow summary

Enter Classic or Ranked → loot weapons, equipment, and supplies → fight and survive the shrinking play zone → advance rank, missions, and season progress → build account honor, Pass, and collection value → review events, offers, and the next goal → re-enter Classic or Ranked.

REASONING IN THIS GAME

Selected designs and judgment conditions

Selected principles and the game-local design6 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.

Goals and residual processing

Initial IFR · goal direction

Realign attribution rules, exposure, sequence and governance at the common junction toward the established recovery goals.

Final IFR · design goal

Retain mode-native results while expressing them as non-power attribution records, connecting account history and existing next goals in one selectable context.

Recurring Structures

Detailed Repeating Structures

What repeats and keeps the system moving?

4 analysis items · Read the method

Core classification and definition · External Calendar

External Calendar

Enter Classic or Ranked → loot weapons, equipment, and supplies → fight and survive the shrinking play zone → advance rank, missions, and season progress → build account honor, Pass, and collection value → review events, offers, and the next goal → re-enter Classic or Ranked.

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

View pattern definition →
  1. Core

    Classic and Ranked Return Loop

    Enter Classic or Ranked, loot, fight, and survive, convert the result into rank, mission, and seasonal progress, then use events and the next target to re-enter the mode.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  2. Sub-Core

    Metro Asset Reinvestment Loop

    Prepare equipment, enter Metro, loot, fight, and extract, accept secured assets or losses, convert the result into Metro Cash, Fame, and chapter progress, then reinvest.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  3. Cooperation

    Creator and Social Return Loop

    Enter World of Wonder, P.D.P., HOME, or the Hub, create, play, visit, and exhibit, convert participation into relationships and social visibility, then return through visits and events.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  4. Competition

    Competitive Trust Loop

    Protect the equal-start promise through network, input, matchmaking, and anti-cheat controls, make competitive results credible, and convert that trust into long-term ranked participation.

    Evidence
    Classification Confirmed
    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 affected flow runs through mechanism; 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 mechanism; its limiting point is the transition handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  2. Supporting

    Action Feedback and Failure Attribution Break · Combat Feedback

    This bottleneck concerns alignment between combat results and technical feedback, and trust when retrying, across result states, technical signals, cause explanations, settings changes, and retries.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    Outcome and Contribution Attribution Failure · Social

    The affected flow runs through Premade → Clan/Crew → HOME/Hub → mechanism; its limiting point is the social result handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  4. Supporting

    Rights and Lifecycle Discontinuity · Asset

    This bottleneck concerns continuity across the purchase path, entitlement, and renewal, joining exposure, product details, transaction results, entitlement, first use, and renewal states.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    Obligation and Volition Erosion · Routine Liveops

    The affected flow runs through lifecycle → mechanism; its limiting point is the routine liveops return handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    Transition and Handoff Break ·

    The affected flow runs through E Metro → S Classic/Metro → Chapter/Fame → mechanism; its limiting point is the transition 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

    Speed Vs Integrity / Complexity Vs Convenience

    Improve Speed Vs Integrity while preserving Complexity Vs Convenience.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    Complexity Vs Convenience / Freedom Vs Control

    Improve Complexity Vs Convenience while preserving Freedom Vs Control.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  4. Supporting

    Revenue Vs Trust / Complexity Vs Convenience

    Across transaction → entitlement, improve Revenue Vs Trust while preserving Complexity Vs Convenience.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    Performance Vs Load / Stability Vs Volatility

    Across Core, improve Performance Vs Load while preserving Stability Vs Volatility.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    Stability Vs Volatility / Freedom Vs Control

    Across Metro, improve Stability Vs Volatility while preserving Freedom Vs Control.

    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 Mode-Value Translation Bridge 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

    Mode-Value Translation Bridge

    Apply Route and Return Handoff across Mode-Value Translation Bridge while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  2. Supporting

    Result–Technical Context–Retry Spine

    Apply State and Rule Visibility Encoding across Result Technical Context Retry Spine while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    Layered Contribution Receipt

    Apply Layered and Progressive Disclosure across Layered Contribution Receipt while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  4. Supporting

    Transaction–Entitlement Rights Spine

    Apply Loss Trust and Entitlement Buffer across Transaction Entitlement Rights Spine while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    Core-Preserving Event Trim

    Apply State and Rule Visibility Encoding across Core-Preserving Event Trim while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    Layered Metro Recovery & Re-entry Map

    Apply Layered and Progressive Disclosure across Layered Metro Recovery & Re-entry Map 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 Mode-Value Translation Bridge 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

    Mode-Value Translation Bridge Composition

    Connect 1 source-declared mechanism across Mode-Value Translation Bridge as Single-Track Localized Bundle.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  2. Supporting

    Result–Technical Context–Retry Spine Composition

    Connect 1 source-declared mechanism across Result Technical Context Retry Spine as Single-Track Localized Bundle.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    Layered Contribution Receipt Composition

    Connect 1 source-declared mechanism across Layered Contribution Receipt as Single-Track Localized Bundle.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  4. Supporting

    Transaction–Entitlement Rights Spine Composition

    Connect 1 source-declared mechanism across Transaction Entitlement Rights Spine as Single-Track Localized Bundle.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    Core-Preserving Event Trim Composition

    Connect 1 source-declared mechanism across Core-Preserving Event Trim as Single-Track Localized Bundle.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    Layered Metro Recovery & Re-entry Map Composition

    Connect 1 source-declared mechanism across Layered Metro Recovery & Re-entry Map 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 Mode-Value Translation Bridge 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 Mode-Value Translation Bridge as Parallel Local Contracts with Independent Rollback.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence