NOVASMC

GAME DECISION MAP

DRAGON BALL Z DOKKAN BATTLE

Puzzle RPG · Mobile · 2015

Current analysisBaseline 2026-07-26Open Decision Analysis → · Korean full analysis

Problem definition

Fragmented continuity of actionable states and definitions in live events.

View all bottlenecks

Design direction

Connect active goals, deadlines, claims, exchanges, permanent conversion and renewal through states and definitions, preserving event, reward, exchange, price and timing rules.

View all mechanisms
Read the recurring-flow summary

Build a Dragon Ball character team → select an event or stage → connect Ki Spheres and trigger attacks in turn-based battles → earn characters, medals, currency, and event rights → train, awaken, EZA or SEZA the roster → claim or exchange rewards and enter the next event or challenge.

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 state, sequence, exposure and completion definitions to recover trust, volition and value.

Final IFR · design goal

Connect current state, next action, deadline, collection and completion through progressive information layers and consistent state grammar while retaining event identity, choice and voluntary time.

Recurring Structures

Detailed Repeating Structures

What repeats and keeps the system moving?

1 analysis items · Read the method

Core classification and definition · External Calendar

External Calendar

Build a Dragon Ball character team → select an event or stage → connect Ki Spheres and trigger attacks in turn-based battles → earn characters, medals, currency, and event rights → train, awaken, EZA or SEZA the roster → claim or exchange rewards and enter the next event or challenge.

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

View pattern definition →
  1. Acquisition

    Core Game Loop

    The actual loop runs through Summon/Acquire → Growth → Challenge/Event → Reward → Summon ~.

    Evidence
    Source Described
    Outcome basis
    Design Evidence

Bottlenecks

Bottleneck Patterns

Where do decisions and flow break?

6 analysis items · Read the method

Core classification and definition · Temporal and Operational Synchronization Break

Temporal and Operational Synchronization Break

The affected flow runs through state transition/terminal definitions; its limiting point is the liveops operations synchronization handoff.

Schedules, deadlines, renewals, settlement, return, and pacing do not form one executable order and operating rhythm.

View pattern definition →
  1. Core

    state transition

    The affected flow runs through state transition/terminal definitions; its limiting point is the liveops operations synchronization handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  2. Supporting

    growth steps, materials, search and repetition delay first practical use

    The affected flow runs through acquisition → steps → first/full use; its limiting point is the transition handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    source, eligibility, residual, use, exchange and expiry meanings fragment

    The affected flow runs through rights state → unused/expiry/inquiry; its limiting point is the asset lifecycle handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  4. Supporting

    character

    The affected flow runs through formation reason → first/30d use; its limiting point is the rules handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    authorization

    The affected flow runs through initiation → grant → receipt/use/CS; its limiting point is the rules handoff.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    new supply and EZA

    The affected flow runs through restoration pacing; its limiting point is the asset lifecycle 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

Across actionable-state legibility + terminal settlement continuity, improve Complexity Vs Convenience while preserving Stability Vs Volatility.

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 actionable-state legibility + terminal settlement continuity, improve Complexity Vs Convenience while preserving Stability Vs Volatility.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  2. Supporting

    Performance Vs Load / Complexity Vs Convenience

    Across acquisition → growth steps → first-use continuity, improve Performance Vs Load while preserving Complexity Vs Convenience.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  3. Supporting

    Complexity Vs Convenience / Revenue Vs Trust

    Across source → eligibility → use/exchange → expiry lifecycle legibility, improve Complexity Vs Convenience while preserving Revenue Vs Trust.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  4. Supporting

    Complexity Vs Convenience / Freedom Vs Control

    Across condition/team graph legibility; formation → use link, improve Complexity Vs Convenience while preserving Freedom Vs Control.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    Speed Vs Integrity / Revenue Vs Trust

    Across auth → grant → receipt → use terminal continuity, improve Speed Vs Integrity while preserving Revenue Vs Trust.

    Evidence
    Classification Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    Stability Vs Volatility / Popularity Vs Scarcity

    Across supply/restoration → formation → use continuity, improve Stability Vs Volatility while preserving Popularity Vs Scarcity.

    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 across Progressive Action-State Contract 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

    Progressive Action-State Contract

    Apply Layered and Progressive Disclosure across Progressive Action-State Contract while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  2. Supporting

    State and Rule Visibility Encoding · Attachment

    Apply State and Rule Visibility Encoding across Protected Growth Fast-Path Contract while preserving the 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 Rights Lifecycle Passport & Protected Handoff while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  4. Supporting

    Formation Reason Graph & Safe Preview

    Apply State and Rule Visibility Encoding across Formation Reason Graph & Safe Preview while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    Canonical Transaction State & Exception Contract

    Apply State and Rule Visibility Encoding across Canonical Transaction State & Exception Contract while preserving the protected value.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    Supply–Restoration Cadence Contract

    Apply State and Rule Visibility Encoding across Supply Restoration Cadence Contract 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 Progressive Action-State Contract 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

    Progressive Action-State Contract Composition

    Connect 1 source-declared mechanism across Progressive Action-State Contract 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 across Protected Growth Fast-Path Contract 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 Rights Lifecycle Passport & Protected Handoff as Single-Track Localized Bundle.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  4. Supporting

    Formation Reason Graph & Safe Preview Composition

    Connect 1 source-declared mechanism across Formation Reason Graph & Safe Preview as Single-Track Localized Bundle.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  5. Supporting

    Canonical Transaction State & Exception Contract Composition

    Connect 1 source-declared mechanism across Canonical Transaction State & Exception Contract as Single-Track Localized Bundle.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence
  6. Supporting

    Supply–Restoration Cadence Contract Composition

    Connect 1 source-declared mechanism across Supply Restoration Cadence Contract 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 Progressive Action-State Contract 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 Progressive Action-State Contract as Parallel Local Contracts with Independent Rollback.

    Evidence
    Solution Link Confirmed
    Outcome basis
    Design Evidence