Make current Potion, Task, District and ledger states, progress attribution, next actions and recovery or alternative routes identifiable.
FIVE FIELDS
Key judgments across five fields
Read from the recurring flow to problem definition and improvements with protected conditions.
- 01
Loops and breaks
Level wins feed Potion, Task and District progress, then return to the next level.
External Calendar - 02
Bottlenecks
After a level result or stop, multiple progress states and the next action are difficult to read.
Transition and Handoff Break - 03
Contradictions
Clarify the next action while preserving match-three simplicity, free progression and reward density.
Action and Return Continuity vs System Depth and Throughput - 04
Solution mechanisms
A three-layer design makes results, progress attribution and next actions readable.
Layered and Progressive Disclosure - 05
Game-local composition
Combine the core result capsule with five attachments for recovery, events, battle, competition and collection.
Single-Track Localized Bundle
Loops and breaks
What repeats, and where does it break?
Judgment methodLevel wins carry progress into the next District
- 1Match-three level
- 2Clear the move-limited objective
- 3Level win
- 4Potion and event progress
- 5Task and District progress
- 6Chest and next District
The interrupted handoff
The core bottleneck is the handoff from result or stop screens to Potion, Task, District and multiple progress ledgers. The difficulty centers on distinguishing the next action and recovery or alternative routes.
Core classification · External Calendar
Events, operating schedules, and live operations reactivate participation, exchange, and reward states.
Read the type definitionAll analysis items
1 itemsCoreCore recurring flowExternal Calendar
Enter a match-three level, clear the objective within the move limit, and carry Potion and event progress from the win into Tasks, Districts, chests and the next District.
Core Loop
Type definition · External CalendarBottlenecks
What obstructs the next action?
Judgment methodA broken handoff at the shared progress result screen
The core bottleneck is the handoff from result or stop screens to Potion, Task, District and multiple progress ledgers. The difficulty centers on distinguishing the next action and recovery or alternative routes.
Core classification · Transition and Handoff Break
The result of one step does not connect to the next action, return, or reinvestment decision.
Read the type definitionAll analysis items
7 itemsCoreFrom level results to the next actionTransition and Handoff Break
The core bottleneck is the handoff from result or stop screens to Potion, Task, District and multiple progress ledgers. The difficulty centers on distinguishing the next action and recovery or alternative routes.
Level result
Type definition · Transition and Handoff BreakSupportingLoss and recovery choices after failureTransition and Handoff Break
Difficulty comparing combined state loss, recovery cost and effects, and another failure affects retry, exit and trust.
compound state loss→recovery comparison
Type definition · Transition and Handoff BreakSupportingReading battle targets and rulesRule and State Fragmentation
Ambiguous battle targets and rules lead to misread actions, wasted resources and phase failures, obstructing competence expression and value judgment.
Battle target
Type definition · Rule and State FragmentationSupportingCompetition score contribution and attributionFairness and Legitimacy Erosion
Mixed score contributions make fairness and status attribution difficult to read, affecting retry and return decisions.
mixed Score contribution→fairness
Type definition · Fairness and Legitimacy ErosionSupportingHelp, contribution and partner coordinationAllocation and Coordination Failure
Help, contribution and partner lock-in can create concentration or inactivity that obstructs completion and relationships.
help
Type definition · Allocation and Coordination FailureSupportingOverlapping event ledgers and deadlinesObligation and Volition Erosion
Overlapping ledgers, deadlines and multipliers create obligation and expiry problems, complicating claim, ignore and return choices.
ledger
Type definition · Obligation and Volition ErosionSupportingCollection completion and expiryRights and Lifecycle Discontinuity
Rare missing items, duplicates and social acquisition routes make target distance difficult to read and disrupt completion and expiry decisions.
rare tail
Type definition · Rights and Lifecycle DiscontinuityContradictions
What should improve, and what must be preserved?
Judgment methodImprove clarity while protecting progression and choice
Preserve match-three simplicity, non-payment Potion progression, Task and District continuity, reward density, and fair and free routes.
Core classification · Action and Return Continuity vs System Depth and Throughput
Continuity to the next action, return, or reinvestment must improve while route diversity, strategic depth, and throughput remain protected.
Read the type definitionAll analysis items
6 itemsCoreNext-action clarity and progression valueAction and Return Continuity vs System Depth and Throughput
Make current Potion, Task, District and ledger states, progress attribution, next actions and recovery or alternative routes identifiable. Preserve match-three simplicity, non-payment Potion progression, Task and District continuity, reward density, and fair and free routes.
Core Contradiction
Type definition · Action and Return Continuity vs System Depth and ThroughputSupportingRecovery comparison and voluntary retryOutcome and Failure Attribution vs System Depth and Rule Integrity
Make loss, recovery cost and effects, refailure, retry and exit comparable while preserving fair retry, free recovery, agency and voluntary continuation.
Compound Failure
Type definition · Outcome and Failure Attribution vs System Depth and Rule IntegritySupportingBattle-result legibility and competenceOutcome and Failure Attribution vs System Depth and Rule Integrity
Make battle targets, rules, resources, phases, actions, waste and outcomes readable while preserving battle expression, polish, PvE differentiation and competence.
Battle Information
Type definition · Outcome and Failure Attribution vs System Depth and Rule IntegritySupportingCompetition attribution and rule integrityOutcome and Failure Attribution vs System Depth and Rule Integrity
Make skill, time, attempt and resource contributions, brackets, ranks and status attributable in time while preserving skill expression, fairness boundaries and competition integrity.
Competition Attribution
Type definition · Outcome and Failure Attribution vs System Depth and Rule IntegritySupportingEvent clarity and optional participationParticipation and Routine Burden Relief vs Operational Vitality and Reward Value
Make event exposure, entry, ledger overlap, deadlines, claims, ignore and return readable while preserving event variety, free tracks, earned rewards and optional participation.
Event Ledger
Type definition · Participation and Routine Burden Relief vs Operational Vitality and Reward ValueSupportingCompletion-path legibility, ownership and rarityInput and Reward Value Closure vs Diversity and Invested-Asset Preservation
Make acquisition, duplicates, Star conversion, requests, sending, season end and target distance readable while preserving collection ownership, rarity, earned progress and safeguards.
Collection Convergence
Type definition · Input and Reward Value Closure vs Diversity and Invested-Asset PreservationSolution mechanisms
Which principles change the conditions?
Judgment methodThree-Layer Result Capsule
On existing result or stop screens, show the next action first, then let players inspect progress attribution and settlement reasons at the depth they need.
- 01
Next action and headline
Read the immediate result and next action first.
- 02
Progress attribution
Inspect how the result is attributed to Potion, Task and District progress.
- 03
Source-backed settlement reasons
Choose a deeper explanation of reasons grounded in actual states and rules.
Applied NTRIZ principles
Use these principles to layer facts, encode actual states and keep meanings consistent across progress ledgers.
Core classification · Layered and Progressive Disclosure
Separate complex meaning, rules, and strategy into layers and reveal only the depth needed at each moment.
Read the type definitionAll analysis items
6 itemsCoreThree-Layer Result CapsuleLayered and Progressive Disclosure
On existing result or stop screens, show the next action first, then let players inspect progress attribution and settlement reasons at the depth they need.
Type definition · Layered and Progressive DisclosureSupportingRecovery State–Choice MatrixState and Rule Visibility Encoding
Compare retained and lost states with the costs and effects of retry, free recovery and exit in the current failure context.
Type definition · State and Rule Visibility EncodingSupportingBattle Signal–Outcome TraceState and Rule Visibility Encoding
Connect targets, rules and resources before battle, phase and action signals during battle, and source-backed results afterward.
Type definition · State and Rule Visibility EncodingSupportingContribution–Settlement–Status ReceiptState and Rule Visibility Encoding
Read contribution, settlement and status attribution together with the source version and effective time.
Type definition · State and Rule Visibility EncodingSupportingVoluntary Event Lifecycle LedgerState and Rule Visibility Encoding
Separate available, chosen, claimable and ending states, displaying valid entry, ignore, defer and return paths.
Type definition · State and Rule Visibility EncodingSupportingCollection Convergence ReceiptState and Rule Visibility Encoding
Connect the target and distance, canonical acquisition paths, completion and expiry. Behavior Instrumentation is used for validation.
Type definition · State and Rule Visibility EncodingGame-local composition
How are the solutions grouped and sequenced?
Judgment methodCore result capsule + five attachments
Connect five attachments around the core result capsule. Recovery, events, battle, competition and collection retain their own states, rules and responsibilities, with validation and rollback handled per component.
Selected game-local designs
Three-Layer Result Capsule
On existing result or stop screens, show the next action first, then let players inspect progress attribution and settlement reasons at the depth they need.
Recovery State–Choice Matrix
Compare retained and lost states with the costs and effects of retry, free recovery and exit in the current failure context.
Voluntary Event Lifecycle Ledger
Separate available, chosen, claimable and ending states, displaying valid entry, ignore, defer and return paths.
Battle Signal–Outcome Trace
Connect targets, rules and resources before battle, phase and action signals during battle, and source-backed results afterward.
Contribution–Settlement–Status Receipt
Read contribution, settlement and status attribution together with the source version and effective time.
Collection Convergence Receipt
Connect the target and distance, canonical acquisition paths, completion and expiry. Behavior Instrumentation is used for validation.
Initial and final design goals
- Initial IFR · goal direction
- Realign information exposure, sequence and rule conditions at the hub connecting level wins, Potion, Tasks and Districts.
- Final IFR · design goal
- Within existing result or stop screens, connect next actions and headlines, Potion, Task and District attribution, and source-backed settlement reasons in layers.
Zero issues are classified as naturally resolved. Attachment processing is recorded as design work; actual resolution is assessed through observations and validation after application.
- Observation coordinates
- Observation coordinates include Potion earning and spending, Task backlog, District steps, stopped progress states and continuation in the next session.
- Validation decisions
- Use observations to assess route comprehension and next-action changes. Information overload, conflicting or stale states, concealed free routes and misrouting trigger reassessment and rollback decisions.
Core classification · Single-Track Localized Bundle
Combine a core intervention with stabilizing or accelerating support within one problem track and keep its impact localized.
Read the type definitionAll analysis items
8 itemsCoreThree-Layer Result Capsule CompositionSingle-Track Localized Bundle
A localized composition addressing Three-Layer Result Capsule within one problem track.
Type definition · Single-Track Localized BundleSupportingRecovery State–Choice Matrix CompositionSingle-Track Localized Bundle
A localized composition addressing Recovery State–Choice Matrix within one problem track.
Type definition · Single-Track Localized BundleSupportingBattle Signal–Outcome Trace CompositionSingle-Track Localized Bundle
A localized composition addressing Battle Signal–Outcome Trace within one problem track.
Type definition · Single-Track Localized BundleSupportingContribution–Settlement–Status Receipt CompositionSingle-Track Localized Bundle
A localized composition addressing Contribution–Settlement–Status Receipt within one problem track.
Type definition · Single-Track Localized BundleSupportingVoluntary Event Lifecycle Ledger CompositionSingle-Track Localized Bundle
A localized composition addressing Voluntary Event Lifecycle Ledger within one problem track.
Type definition · Single-Track Localized BundleSupportingCollection Convergence Receipt CompositionSingle-Track Localized Bundle
A localized composition addressing Collection Convergence Receipt within one problem track.
Type definition · Single-Track Localized BundleSupportingCore-first branch-sequential compositionCore-First Branch-Sequential Portfolio
Place the core result capsule first, then connect recovery, battle, competition, event and collection mechanisms branch by branch.
Parallel Solution-Mechanism Composition
Type definition · Core-First Branch-Sequential PortfolioSupportingParallel composition with independent validation and rollbackParallel Local Contracts with Independent Rollback
Address six mechanisms across parallel problem tracks while keeping responsibility, validation and rollback independent for each track.
Parallel Solution-Mechanism Composition
Type definition · Parallel Local Contracts with Independent Rollback