Problem definition
Problems involving core rules, late-stage power and progression continuity.
View all bottlenecksGAME DECISION MAP
Brawl Stars
Design direction
Connect current state, causal context and result traces to existing rules, retry and return, preserving combat, power, direct control and mode distinctions.
View all mechanismsRead the recurring-flow summary
Choose a Brawler and enter a short real-time match → aim, move, and use attacks, Super, and gadgets to complete the mode objective → earn Trophies, XP, rewards, and quest progress → unlock and upgrade Brawlers and customize loadouts and skins → re-enter Trophy, Ranked, club, and rotating event play.
REASONING IN THIS GAME
Selected designs and judgment conditions
Goals and residual processing
Initial IFR · goal direction
Retain layered rule and power depth and event variation while making state, cause, result and retry or return consistently readable.
Final IFR · design goal
Connect state, cause-context and trace layers with consistent result keys across existing Rule Profiles and result, retry and return junctions.
Recurring Structures
Detailed Repeating Structures
What repeats and keeps the system moving?
1 analysis items · Read the method
Core classification and definition · Compounding Growth
Compounding Growth
Choose a Brawler and enter a short real-time match → aim, move, and use attacks, Super, and gadgets to complete the mode objective → earn Trophies, XP, rewards, and quest progress → unlock and upgrade Brawlers and customize loadouts and skins → re-enter Trophy, Ranked, club, and rotating event play.
Outputs strengthen assets, capabilities, or access and open a stronger next cycle.
View pattern definition →Core Core Loop
Brawler selection → short real-time match → outcome/objective → conditional progress/rewards → unlock/upgrade/cosmetic/prestige → re-entry.
- Evidence
- Source Described
- 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 rule transition/result/retry/return; its limiting point is the competition power result handoff.
Outcomes, causes, rules, rewards, and retry information do not close the feedback loop needed for correction.
View pattern definition →Core Action Feedback and Failure Attribution Break · Competition Power
The affected flow runs through rule transition/result/retry/return; its limiting point is the competition power result handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Decision and Planning Calculability Breakdown · Growth Collection
The limiting point sits in the growth collection planning handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Decision and Planning Calculability Breakdown · Roster Competition
The affected flow runs through source/sink/upgrade/readiness; its limiting point is the roster competition planning handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Legibility and Interpretation Break · Combat Ui
The affected flow runs through information hierarchy at input/hit/death/result; its limiting point is the combat ui handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Resource and Value Conversion Failure · Commerce Collection
The affected flow runs through offer view/comparison/expiry; its limiting point is the commerce collection entry handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Outcome and Contribution Attribution Failure · Social Cooperation
The affected flow runs through contribution/reparty/relation state; its limiting point is the social cooperation 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 · Outcome and Failure Attribution vs System Depth and Rule Integrity
Outcome and Failure Attribution vs System Depth and Rule Integrity
Across rule/power condition legal action → consequence ; feedback/result/retry/return continuity, improve Complexity Vs Convenience while preserving Stability Vs Volatility.
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 rule/power condition legal action → consequence ; feedback/result/retry/return continuity, improve Complexity Vs Convenience while preserving Stability Vs Volatility.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Complexity Vs Convenience / Freedom Vs Control
Across next-goal choice, route retrieval, earned-progress continuity, improve Complexity Vs Convenience while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Complexity Vs Convenience / Freedom Vs Control
Across resource roles, upgrade timing, roster-readiness path, improve Complexity Vs Convenience while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Complexity Vs Convenience / None
Across combat-critical signal input/state/result, improve Complexity Vs Convenience while preserving None.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Complexity Vs Convenience / Revenue Vs Trust
Across deliberate access, comparison, price/currency predictability, autonomous choice, improve Complexity Vs Convenience while preserving Revenue Vs Trust.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Performance Vs Load / Freedom Vs Control
Across contribution recognition, relationship recall, re-formation continuity, improve Performance Vs Load 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 rule/power condition legal action → consequence ; feedback/result/retry/return continuity 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 →Core Route and Return Handoff · Core
Apply Route and Return Handoff across rule/power condition legal action → consequence ; feedback/result/retry/return continuity while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting multi-track breadth·early orientation
Apply Multifunction and Multitrack Coordination across next-goal choice, route retrieval, earned-progress continuity while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting resource role·upgrade timing·readiness
Apply Baseline and Resource Stabilization across resource roles, upgrade timing, roster-readiness path while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting cosmetic expression·accessibility·direct control
Apply State and Rule Visibility Encoding across combat-critical signal input/state/result while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State and Rule Visibility Encoding · Attachment
Apply State and Rule Visibility Encoding across deliberate access, comparison, price/currency predictability, autonomous choice while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Context Asset and Authority Isolation · Attachment
Apply Context Asset and Authority Isolation across contribution recognition, relationship recall, re-formation continuity 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 rule/power condition legal action → consequence ; feedback/result/retry/return continuity 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 Route and Return Handoff · Core Composition
Connect 1 source-declared mechanism across rule/power condition legal action → consequence ; feedback/result/retry/return continuity as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting multi-track breadth·early orientation Composition
Connect 1 source-declared mechanism across next-goal choice, route retrieval, earned-progress continuity as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting resource role·upgrade timing·readiness Composition
Connect 1 source-declared mechanism across resource roles, upgrade timing, roster-readiness path as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting cosmetic expression·accessibility·direct control Composition
Connect 1 source-declared mechanism across combat-critical signal input/state/result as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State and Rule Visibility Encoding · Attachment Composition
Connect 1 source-declared mechanism across deliberate access, comparison, price/currency predictability, autonomous choice as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Context Asset and Authority Isolation · Attachment Composition
Connect 1 source-declared mechanism across contribution recognition, relationship recall, re-formation continuity as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Parallel Solution-Mechanism Composition
Connect 6 source-declared mechanisms across rule/power condition legal action → consequence ; feedback/result/retry/return continuity as Core-First Branch-Sequential Portfolio.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Parallel Solution-Mechanism Composition
Connect 6 source-declared mechanisms across rule/power condition legal action → consequence ; feedback/result/retry/return continuity as Parallel Local Contracts with Independent Rollback.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence