NOVASMC

GAME DECISION MAP

Free Fire

Battle Royale · Mobile · 2017

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

Problem definition

A bottleneck in attributing competitive results and reading readiness.

View all bottlenecks

Design direction

Layer causal and readiness information on the existing result screen and connect it to loadout, requeue and exit through common decision wording.

View all mechanisms
Read the recurring-flow summary

Enter a Battle Royale or Clash Squad match → scavenge weapons and equipment or buy a round loadout → fight, reposition, and survive → earn Booyah or be eliminated → advance rank, currency, Pass, character, pet, and collection goals → adjust skills, Preset, and Loadout → re-enter.

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 rule language, information exposure and attribution sequence at the result-attribution junction.

Final IFR · design goal

Rearrange verified cause and readiness information in progressive layers using consistent cause criteria, linking to existing Loadout, requeue and exit.

Recurring Structures

Detailed Repeating Structures

What repeats and keeps the system moving?

3 analysis items · Read the method

Core classification and definition · External Calendar

External Calendar

Enter a Battle Royale or Clash Squad match → scavenge weapons and equipment or buy a round loadout → fight, reposition, and survive → earn Booyah or be eliminated → advance rank, currency, Pass, character, pet, and collection goals → adjust skills, Preset, and Loadout → re-enter.

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

View pattern definition →
  1. Core

    Battle Royale and Clash Squad Re-entry Loop

    Access the rules, enter Battle Royale or Clash Squad, convert competitive and cooperative results into progression and economic assets, then let LiveOps reopen the next match.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  2. Return

    Event Token Return Loop

    Enter an event, complete missions and logins, collect tokens and free rewards, exchange them for the next target, then re-enter Battle Royale or Clash Squad.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  3. Cooperation

    Guild Contribution and Exchange Loop

    Join guild missions, turn individual and collective contribution into Guild Tokens and cooperative rewards, exchange them in the store, then return to shared guild and match play.

    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 · Action Feedback and Failure Attribution Break

Action Feedback and Failure Attribution Break

The affected flow runs through Result → prep action → requeue/exit event sequence; its limiting point is the combat feedback result handoff.

Outcomes, causes, rules, rewards, and retry information do not close the feedback loop needed for correction.

View pattern definition →
  1. Core

    Action Feedback and Failure Attribution Break · Combat Feedback

    The affected flow runs through Result → prep action → requeue/exit event sequence; its limiting point is the combat feedback result handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  2. Supporting

    Transition and Handoff Break ·

    The affected flow runs through Result → prep action → requeue/exit event sequence; its limiting point is the transition handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    Virtual Economy & Progression Curves(.Commerce.VirtualEconomy.)

    The affected flow runs through sequence; its limiting point is the economy commerce settlement handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  4. Supporting

    Obligation and Volition Erosion · Routine Liveops

    The affected flow runs through Event/non-event period return interval + goal path + claim load; its limiting point is the routine liveops return handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    Fairness and Legitimacy Erosion · Competition

    The affected flow runs through sequence; its limiting point is the competition result handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    Octalysis(.Design.Octalysis.)

    The affected flow runs through sequence; its limiting point is the social result 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 Speed Vs Integrity.

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 Speed Vs Integrity.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  2. Supporting

    Performance Vs Load / Complexity Vs Convenience

    Improve Performance Vs Load while preserving Complexity Vs Convenience.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    Complexity Vs Convenience / Freedom Vs Control

    Across source/sink, improve Complexity Vs Convenience while preserving Freedom Vs Control.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  4. Supporting

    Stability Vs Volatility / Performance Vs Load

    Improve Stability Vs Volatility while preserving Performance Vs Load.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    Revenue Vs Trust / Popularity Vs Scarcity

    Improve Revenue Vs Trust while preserving Popularity Vs Scarcity.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    Popularity Vs Scarcity / Revenue Vs Trust

    Improve Popularity Vs Scarcity while preserving Revenue Vs Trust.

    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 · Layered and Progressive Disclosure

Layered and Progressive Disclosure

Apply Layered and Progressive Disclosure to the source-declared core track while preserving its 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 and Progressive Disclosure · Core

    Apply Layered and Progressive Disclosure to the source-declared core track while preserving its protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  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.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    State and Rule Visibility Encoding · Attachment

    Apply State and Rule Visibility Encoding across source/sink while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  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.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  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.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    State and Rule Visibility Encoding · Attachment

    Apply State and Rule Visibility Encoding to the source-declared attachment track while preserving its 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 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 and Progressive Disclosure · Core Composition

    Connect 1 source-declared mechanism 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 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 source/sink as Single-Track Localized Bundle.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  4. Supporting

    State and Rule Visibility Encoding · Attachment Composition

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

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    State and Rule Visibility Encoding · Attachment Composition

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

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    State and Rule Visibility Encoding · Attachment Composition

    Connect 1 source-declared mechanism 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 source/sink 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 source/sink as Parallel Local Contracts with Independent Rollback.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence