NOVASMC

GAME DECISION MAP

Honor of Kings

MOBA · Mobile · 2015

Current analysisBaseline 2026-06-18Open Decision Analysis →

Choose a hero and role → lane, jungle, and team-fight → take towers and objectives and destroy the Crystal → receive rank and rewards → queue again.

Recurring Structures

Detailed Repeating Structures

What repeats and keeps the system moving?

CORE CLASSIFICATION

External Calendar

Choose a hero and role → lane, jungle, and team-fight → take towers and objectives and destroy the Crystal → receive rank and rewards → queue again.

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

View pattern definition →
  1. Core

    5v5 Hub Re-entry Loop

    Enter the fair 5v5 competition contract, turn match performance into account, rank, and seasonal standing, connect it to cosmetics and LiveOps, then re-enter the 5v5 hub.

  2. Competition

    5v5 Match Competition Loop

    Enter a 5v5 match, perform a team role, convert the result into mastery and rank progress, then carry that standing into the next match.

Bottlenecks

Bottleneck Patterns

Where do decisions and flow break?

CORE CLASSIFICATION

Action Feedback and Failure Attribution Break

The affected flow runs through LP-Q; its limiting point is the competition result handoff.

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

View pattern definition →
  1. Core

    ranked queue–result–contribution

    The affected flow runs through LP-Q; its limiting point is the competition result handoff.

  2. Supporting

    role

    The affected flow runs through readiness/entry; its limiting point is the role competition growth entry handoff.

  3. Supporting

    source–threshold

    The affected flow runs through currency route; its limiting point is the economy growth settlement handoff.

  4. Supporting

    claim–voluntary core return–post-peak continuation

    The affected flow runs through claim/core-return/post-peak; its limiting point is the liveops competition return handoff.

  5. Supporting

    draw rules–outcome–duplicate

    The affected flow runs through draw/outcome/-exit; its limiting point is the collection result handoff.

  6. Supporting

    party formation–social benefit–continuation coordination

    The affected flow runs through party/social/async; its limiting point is the social entry handoff.

Contradictions

Contradiction Patterns

What must improve, and what must remain protected?

CORE CLASSIFICATION

Outcome and Failure Attribution vs System Depth and Rule Integrity

Across queue/result/contribution/fairness → retry, improve Speed Vs Integrity while preserving Complexity Vs Convenience.

Causes and retry conditions for outcomes, failures, and fairness must become attributable while strategic, combat, and competitive depth and rule integrity remain protected.

View pattern definition →
  1. Core

    Core Contradiction

    Across queue/result/contribution/fairness → retry, improve Speed Vs Integrity while preserving Complexity Vs Convenience.

  2. Supporting

    Role

    Across role/lane → readiness → first-ranked continuity, improve Complexity Vs Convenience while preserving Freedom Vs Control.

  3. Supporting

    Currency Source, Free Threshold, Exchange and Next Action

    Across source/free threshold/exchange → next action, improve Revenue Vs Trust while preserving Complexity Vs Convenience.

  4. Supporting

    Event Claim, Voluntary Core Return and Post-Peak Continuity

    Across claim → voluntary core return → post-peak continuity, improve Performance Vs Load while preserving Stability Vs Volatility.

  5. Supporting

    Point Draw Price, Probability, Pity, Duplicate and Exchange Trust

    Across price/odds/pity → outcome → duplicate/exchange closure, improve Revenue Vs Trust while preserving Speed Vs Integrity.

  6. Supporting

    Party Absence, Social Utility and Asynchronous Cushion

    Across party absence/social touch → cooperation/continuation, improve Complexity Vs Convenience 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 queue/result/contribution/fairness → retry 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 and Progressive Disclosure · Core

    Apply Layered and Progressive Disclosure across queue/result/contribution/fairness → retry 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 queue/result/contribution/fairness → retry 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 across queue/result/contribution/fairness → retry as Single-Track Localized Bundle.

  2. Supporting

    Layered and Progressive Disclosure · Core Composition

    Connect 1 source-declared mechanism across queue/result/contribution/fairness → retry as Core-First Branch-Sequential Portfolio.