Problem definition
Pressure involving raid gates, party rebuilding and learning.
View all bottlenecksGAME DECISION MAP
Lost Ark
Design direction
Show gates, party state, open roles, readiness, retry and next actions within the same raid context, preserving roles, difficulty, rewards and access rules.
View all mechanismsRead the recurring-flow summary
Choose a class → fight through quests and daily or weekly activities → collect Gold and honing materials → hone gear and raise item level → enter higher Legion Raids and repeat progression.
REASONING IN THIS GAME
Selected designs and judgment conditions
Goals and residual processing
Initial IFR · goal direction
Realign matching, routing, state exposure and retry timing.
Final IFR · design goal
Connect existing party-finder, gate, vacancy and retry states in one context, supporting same-context rebuilding and retry after a member exits.
Recurring Structures
Detailed Repeating Structures
What repeats and keeps the system moving?
3 analysis items · Read the method
Core classification and definition · External Calendar
External Calendar
Choose a class → fight through quests and daily or weekly activities → collect Gold and honing materials → hone gear and raise item level → enter higher Legion Raids and repeat progression.
Events, operating schedules, and live operations reactivate participation, exchange, and reward states.
View pattern definition →Cooperation Adaptive Fallback · Cooperation
This source-declared cooperation loop connects the game's actual repeat sequence.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Economy Resource Conversion · Economy
This source-declared economy loop connects the game's actual repeat sequence.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Return Periodic Self-Return ·
This source-declared loop connects the game's actual repeat sequence.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Core classification and definition · Allocation and Coordination Failure
Allocation and Coordination Failure
The affected flow runs through gate-to-completion by persona/time; its limiting point is the social operations coordination handoff.
Limited people, exposure, routes, shared assets, or roles are not matched and coordinated with the right targets, opportunities, and actions.
View pattern definition →Core rebuild time
The affected flow runs through gate-to-completion by persona/time; its limiting point is the social operations coordination handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting schedule
The limiting point sits in the routine liveops return handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting access delay and constrained progression
The limiting point sits in the entry handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting recovery cost and build constraint
The limiting point sits in the economy commerce settlement handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting comparison effort and constrained informed choice
The limiting point sits in the economy commerce settlement handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting recovery time and channel constraint
The limiting point sits in the liveops operations synchronization 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 · Challenge and Strategy Depth vs Decision and Experiment Load
Challenge and Strategy Depth vs Decision and Experiment Load
Across formation/rebuild/learning/retry/completion continuity, improve Performance Vs Load while preserving Complexity Vs Convenience.
Cost, outcome, and experimental hypotheses must become decidable while challenge, strategy, and record depth remain protected.
View pattern definition →Core Core Contradiction
Across formation/rebuild/learning/retry/completion continuity, improve Performance Vs Load while preserving Complexity Vs Convenience.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Routine Reset and Task Load Pressure
Across reset/cap/task-load coupling + observability, improve Performance Vs Load while preserving Complexity Vs Convenience.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Growth Transformation and Access Delay Pressure
Across material/failure-to-access-delay transfer, improve Complexity Vs Convenience while preserving Performance Vs Load.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Pheon, Trade and Setup Recovery Pressure
Across transaction-cost/setup-recovery coupling, improve Freedom Vs Control while preserving Revenue Vs Trust.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Multi-Currency Shop Value-Comparison Pressure
Across information completeness + value comparison, improve Complexity Vs Convenience while preserving Revenue Vs Trust.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Event Lifecycle and Reward-Recovery Pressure
Across contribution → claim/use lifecycle continuity, improve Popularity Vs Scarcity while preserving Stability Vs Volatility.
- 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 formation/rebuild/learning/retry/completion 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 formation/rebuild/learning/retry/completion continuity while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Cadence and Rhythm Coordination · Attachment
Apply Cadence and Rhythm Coordination across reset/cap/task-load coupling + observability while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Route and Return Handoff · Attachment
Apply Route and Return Handoff across material/failure-to-access-delay transfer while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Baseline and Resource Stabilization · Attachment
Apply Baseline and Resource Stabilization across transaction-cost/setup-recovery coupling while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Layered and Progressive Disclosure · Attachment
Apply Layered and Progressive Disclosure across information completeness + value comparison 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 contribution → claim/use lifecycle 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 formation/rebuild/learning/retry/completion 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 formation/rebuild/learning/retry/completion continuity as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Cadence and Rhythm Coordination · Attachment Composition
Connect 1 source-declared mechanism across reset/cap/task-load coupling + observability as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Route and Return Handoff · Attachment Composition
Connect 1 source-declared mechanism across material/failure-to-access-delay transfer as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Baseline and Resource Stabilization · Attachment Composition
Connect 1 source-declared mechanism across transaction-cost/setup-recovery coupling as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Layered and Progressive Disclosure · Attachment Composition
Connect 1 source-declared mechanism across information completeness + value comparison 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 contribution → claim/use lifecycle 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 formation/rebuild/learning/retry/completion 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 formation/rebuild/learning/retry/completion continuity as Parallel Local Contracts with Independent Rollback.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence