Problem definition
A bottleneck linking ranked setup, results, contribution and fairness interpretation, and retry.
View all bottlenecksGAME DECISION MAP
Honor of Kings
Design direction
Layer results, verified context, evidence and review routes, retaining retry, hold, report and exit as neutral choices.
View all mechanismsRead the recurring-flow summary
Choose a hero and role → lane, jungle, and team-fight → take towers and objectives and destroy the Crystal → receive rank and rewards → queue again.
REASONING IN THIS GAME
Selected designs and judgment conditions
Goals and residual processing
Initial IFR · goal direction
Connect comprehensible result interpretation to healthy retry or exit while preserving integrity.
Final IFR · design goal
Retain team-result and rank integrity while revealing results, context and evidence in layers and supporting voluntary retry, deferral, reporting or exit.
Recurring Structures
Detailed Repeating Structures
What repeats and keeps the system moving?
2 analysis items · Read the method
Core classification and definition · External Calendar
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 →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.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
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.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Core classification and definition · Action Feedback and Failure Attribution Break
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 →Core ranked queue–result–contribution
The affected flow runs through LP-Q; its limiting point is the competition result handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting role
The affected flow runs through readiness/entry; its limiting point is the role competition growth entry handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting source–threshold
The affected flow runs through currency route; its limiting point is the economy growth settlement handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
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.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting draw rules–outcome–duplicate
The affected flow runs through draw/outcome/-exit; its limiting point is the collection result handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting party formation–social benefit–continuation coordination
The affected flow runs through party/social/async; its limiting point is the social entry 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 · Outcome and Failure Attribution vs System Depth and Rule Integrity
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 →Core Core Contradiction
Across queue/result/contribution/fairness → retry, improve Speed Vs Integrity while preserving Complexity Vs Convenience.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Role
Across role/lane → readiness → first-ranked continuity, improve Complexity Vs Convenience while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
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.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
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.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
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.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Party Absence, Social Utility and Asynchronous Cushion
Across party absence/social touch → cooperation/continuation, improve Complexity Vs Convenience while preserving Performance Vs Load.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Solution Mechanisms
Solution Mechanisms
Which intervention mechanism changes the condition?
1 analysis items · Read the method
Core classification and definition · Layered and Progressive Disclosure
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 →Core Layered and Progressive Disclosure · Core
Apply Layered and Progressive Disclosure across queue/result/contribution/fairness → retry while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Solution Compositions
Solution Compositions
How should interventions be combined and sequenced?
2 analysis items · Read the method
Core classification and definition · Single-Track Localized Bundle
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 →Core Layered and Progressive Disclosure · Core Composition
Connect 1 source-declared mechanism across queue/result/contribution/fairness → retry as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Layered and Progressive Disclosure · Core Composition
Connect 1 source-declared mechanism across queue/result/contribution/fairness → retry as Core-First Branch-Sequential Portfolio.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence