Problem definition
A bottleneck in translating rewards into the next growth goal.
View all bottlenecksGAME DECISION MAP
Archero
Design direction
Connect reward outcomes to chapter goals, required growth, investment routes and another attempt, preserving existing values and combat rules.
View all mechanismsRead the recurring-flow summary
Enter a Main Chapter room → move to evade or stop to auto-attack → choose one of three Run Abilities and clear rooms and bosses → collect Gold, equipment, and growth resources → invest in heroes, equipment, talents, and layered account systems → retry the current chapter or enter the next mode and event.
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.
Goal-Linked Reward Route Card
Goal-Context Contribution Lens
Layered Combat Cause Grammar
Protected Core-Time Budget Envelope
Layered Result-Factor Attribution Contract
Layered Entitlement Lifecycle Contract
Goals and residual processing
Initial IFR · goal direction
Realign sequence, information exposure and economic boundaries where rewards connect to a target.
Final IFR · design goal
Read the current-goal context from existing reward results and offer manual route choices for direct use, verified conversion, no current use or unknown status.
Recurring Structures
Detailed Repeating Structures
What repeats and keeps the system moving?
8 analysis items · Read the method
Core classification and definition · Compounding Growth
Compounding Growth
Enter a Main Chapter room → move to evade or stop to auto-attack → choose one of three Run Abilities and clear rooms and bosses → collect Gold, equipment, and growth resources → invest in heroes, equipment, talents, and layered account systems → retry the current chapter or enter the next mode and event.
Outputs strengthen assets, capabilities, or access and open a stronger next cycle.
View pattern definition →Core Core Loop
Precision roguelite run → permanent growth → higher challenge; main chapter remains the hub.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Supply Primary Progress Loop
Main chapter attempt, failure/clear, resource settlement, permanent growth, next chapter, system unlock.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Resilience Recovery Loop
Hard wall leads to daily farming, Quick Raid and Hero Patrol to gather missing resources before core retry.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Return Mastery Validation Loop
Growth investment is tested in Expedition, Inferno and high-difficulty events, then build/skill is adjusted.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Competition Competition Loop
Core/meta growth feeds Hero Duel, Monster Arena and seasonal rankings; rewards return to growth and status.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Cooperation Cooperation Loop
Solo growth feeds Hero Duo, Clan, Monster Treasure and Squad; joint rewards and relationships return to growth.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Return Seasonal Overlay Loop
Event notice, limited actions, event currency, exchange/ranking, core-growth reflection and season end.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Resilience Compression Loop
First manual clear unlocks Quick Raid, 2x speed, auto-enhance and batch/claim convenience for repeated value recovery.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Core classification and definition · Resource and Value Conversion Failure
Resource and Value Conversion Failure
The affected flow runs through source/goal/hour/payer-free → use/retry; its limiting point is the economy commerce settlement handoff.
Currencies, assets, products, or inputs do not convert reliably into utility or residual value.
View pattern definition →Core held reward fails at receipt→conversion→target-use→retry
The affected flow runs through source/goal/hour/payer-free → use/retry; its limiting point is the economy commerce settlement handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting upgrade contribution
The affected flow runs through build/hour → upgrade → performance/use; its limiting point is the growth economy planning handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting VFX
The affected flow runs through device/FPS/VFX/loadout/mode → result; its limiting point is the device runtime handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting low-decision routines occupy voluntary Core time
The affected flow runs through content time → Core time → return; its limiting point is the routine liveops return handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting skill
The affected flow runs through controlled factors → review/retry; cash/Gems separate; its limiting point is the combat feedback result handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Pricing interpretation + voluntary choice
The affected flow runs through right type/tenure → use → renew/cancel; 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 receipt → conversion → target use → Core retry , , mapping, improve Popularity Vs Scarcity while preserving Complexity Vs Convenience.
Continuity to the next action, return, or reinvestment must improve while route diversity, strategic depth, and throughput remain protected.
View pattern definition →Core Core Contradiction
Across receipt → conversion → target use → Core retry , , mapping, improve Popularity Vs Scarcity while preserving Complexity Vs Convenience.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Complexity Vs Convenience / Freedom Vs Control
Across upgrade contribution → priority investment → performance/use, improve Complexity Vs Convenience while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Complexity Vs Convenience / Speed Vs Integrity
Across VFX/FPS/input → pain/readability → result combat feedback legibility failure attribution, improve Complexity Vs Convenience while preserving Speed Vs Integrity.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Performance Vs Load / Stability Vs Volatility
Across voluntary Core-time availability routine/event time-budget, improve Performance Vs Load while preserving Stability Vs Volatility.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Speed Vs Integrity / Revenue Vs Trust
Across skill → power → stakes → network → loadout result attribution, rule transparency, review/retry, improve Speed Vs Integrity while preserving Revenue Vs Trust.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Revenue Vs Trust / Complexity Vs Convenience
Across receipt → use → duration → overlap → renewal time-value, improve Revenue Vs Trust while preserving Complexity Vs Convenience.
- 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 Goal-Linked Reward Route Card 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 Goal-Linked Reward Route Card
Apply Route and Return Handoff across Goal-Linked Reward Route Card while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Goal-Context Contribution Lens
Apply State and Rule Visibility Encoding across Goal-Context Contribution Lens while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Layered Combat Cause Grammar
Apply Layered and Progressive Disclosure across Layered Combat Cause Grammar 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 Protected Core-Time Budget Envelope while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Layered Result-Factor Attribution Contract
Apply State and Rule Visibility Encoding across Layered Result-Factor Attribution Contract while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Layered Entitlement Lifecycle Contract
Apply Layered and Progressive Disclosure across Layered Entitlement Lifecycle 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 Goal-Linked Reward Route Card 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 Goal-Linked Reward Route Card Composition
Connect 1 source-declared mechanism across Goal-Linked Reward Route Card as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Goal-Context Contribution Lens Composition
Connect 1 source-declared mechanism across Goal-Context Contribution Lens as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Layered Combat Cause Grammar Composition
Connect 1 source-declared mechanism across Layered Combat Cause Grammar 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 Protected Core-Time Budget Envelope as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Layered Result-Factor Attribution Contract Composition
Connect 1 source-declared mechanism across Layered Result-Factor Attribution Contract as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Layered Entitlement Lifecycle Contract Composition
Connect 1 source-declared mechanism across Layered Entitlement Lifecycle Contract as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Parallel Solution-Mechanism Composition
Connect 6 source-declared mechanisms across Goal-Linked Reward Route Card 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 Goal-Linked Reward Route Card as Parallel Local Contracts with Independent Rollback.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence