Problem definition
Probability, pity, duplicate and fusion conditions weaken confidence in collection completion and subsequent investment decisions.
View all bottlenecksGAME DECISION MAP
Probability, pity, duplicate and fusion conditions weaken confidence in collection completion and subsequent investment decisions.
View all bottlenecksPlace acquisition-promise consistency, voluntary return and contribution entry paths for new and small guilds on their respective control surfaces.
View all mechanismsAccept quests and hunt → collect gear and currency → enhance equipment and collections → enter dungeons, bosses, or PvP → return to higher-level fields.
REASONING IN THIS GAME
Realign rules, exposure, state, feedback and governance to recover trust and value.
Recurring Structures
What repeats and keeps the system moving?
10 analysis items · Read the method
Accept quests and hunt → collect gear and currency → enhance equipment and collections → enter dungeons, bosses, or PvP → return to higher-level fields.
Daily, weekly, or seasonal resets restore eligibility for the same activity.
View pattern definition →Quest/field/dungeon play feeds gold, EXP, materials and then enhancement/skill/collection spending.
Dungeon resets, Valhalla daily schedule, world dungeon biweekly cycle and guild war seasons produce medium-term goals.
Max level, high-grade gear, avatar/mount/rune/codex and guild status form long-term retention goals.
Content rewards become enhancement, crafting, gacha and shop demand; sinks regulate economy and progression.
Early/mid PvE growth routes eventually convert into PvP, guild war and world-level competition participation.
Guild cooperation builds capacity for siege, territory, world boss and server/world competition.
Events fill update gaps, inject rewards, refresh goals and accelerate growth/economic consumption.
Auto/idle systems reduce repetitive fatigue but can weaken manual engagement and combat mastery.
Premium shop and gacha provide power goals, while events/free rewards soften stress.
representatives map into //, currencies into , and event/shop/gacha rewards into growth.
The affected flow runs through offer → probability/pity → draw → duplicate → later action; its limiting point is the asset lifecycle handoff.
Acquisition, ownership, guarantees, resets, expiry, refunds, editing, and reuse do not form one continuous lifecycle.
View pattern definition →The affected flow runs through offer → probability/pity → draw → duplicate → later action; its limiting point is the asset lifecycle handoff.
The affected flow runs through overlap → mission/popup → miss → reward → return; its limiting point is the routine liveops return handoff.
The affected flow runs through join → contribution → reward → bridge/key node → survival; its limiting point is the social operations coordination handoff.
Contradictions
What must improve, and what must remain protected?
3 analysis items · Read the method
Across Trust, improve Revenue Vs Trust while preserving Complexity Vs Convenience.
Time, currency, purchases, rewards, and held assets must close into trustworthy value while route diversity, scarcity, and invested assets remain protected.
View pattern definition →Across Trust, improve Revenue Vs Trust while preserving Complexity Vs Convenience.
Across cycle, improve Performance Vs Load while preserving Stability Vs Volatility.
Across small/new guild network access, improve Freedom Vs Control while preserving None.
Solution Mechanisms
Which intervention mechanism changes the condition?
3 analysis items · Read the method
Apply Loss Trust and Entitlement Buffer across Trust while preserving the protected value.
Buffer loss, regret, probability, completion, and purchase-right risk while preserving existing value and voluntary choice.
View pattern definition →Apply Loss Trust and Entitlement Buffer across Trust while preserving the protected value.
Apply Cadence and Rhythm Coordination across cycle while preserving the protected value.
Apply Context Asset and Authority Isolation across small/new guild network access while preserving the protected value.
Solution Compositions
How should interventions be combined and sequenced?
5 analysis items · Read the method
Connect 1 source-declared mechanism across Trust 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 →Connect 1 source-declared mechanism across Trust as Single-Track Localized Bundle.
Connect 1 source-declared mechanism across cycle as Single-Track Localized Bundle.
Connect 1 source-declared mechanism across small/new guild network access as Single-Track Localized Bundle.
Connect 3 source-declared mechanisms across Trust as Core-First Branch-Sequential Portfolio.
Connect 3 source-declared mechanisms across Trust as Parallel Local Contracts with Independent Rollback.