Summon and collect heroes and pets → level, enhance, and awaken the roster → assemble eligible teams → play turn-based PvE, Arena, raids, and guild content → receive battle and activity rewards → reinvest Ruby and materials into heroes and the next formation.
Recurring Structures
Detailed Repeating Structures
What repeats and keeps the system moving?
CORE CLASSIFICATION
External Calendar
Summon and collect heroes and pets → level, enhance, and awaken the roster → assemble eligible teams → play turn-based PvE, Arena, raids, and guild content → receive battle and activity rewards → reinvest Ruby and materials into heroes and the next formation.
Events, operating schedules, and live operations reactivate participation, exchange, and reward states.
The affected flow runs through state-result attribution; its limiting point is the economy commerce settlement handoff.
Supporting
source
The affected flow runs through source/sink → growth stop; its limiting point is the economy commerce settlement handoff.
Supporting
overlap→deadline choice
The affected flow runs through overlap → deadline choice; its limiting point is the routine liveops return handoff.
Supporting
right→use
The affected flow runs through right → use/expiry/CS; its limiting point is the asset lifecycle handoff.
Supporting
detail→formation
The affected flow runs through detail → formation/Codex; its limiting point is the information interpretation handoff.
Supporting
result→replay
The affected flow runs through result → replay/retry; its limiting point is the combat feedback result handoff.
Contradictions
Contradiction Patterns
What must improve, and what must remain protected?
CORE CLASSIFICATION
Input and Reward Value Closure vs Diversity and Invested-Asset Preservation
Across F/C/M, improve Complexity Vs Convenience while preserving Freedom Vs Control.
Time, currency, purchases, rewards, and held assets must close into trustworthy value while route diversity, scarcity, and invested assets remain protected.
Apply State and Rule Visibility Encoding across F/C/M while preserving the protected value.
Supporting
Route and Return Handoff · Attachment
Apply Route and Return Handoff across source → gain → stock → spend → growth-stop → next-play while preserving the protected value.
Supporting
Route and Return Handoff · Attachment
Apply Route and Return Handoff across voluntary/deadline → skip → unused right → post-return while preserving the protected value.
Supporting
Loss Trust and Entitlement Buffer · Attachment
Apply Loss Trust and Entitlement Buffer across offer/right/grant/use/expiry/reset/CS lifecycle → source integrity while preserving the protected value.
Supporting
State and Rule Visibility Encoding · Attachment
Apply State and Rule Visibility Encoding across taxonomy/duplicate → formation/Codex → adoption terminal feedback while preserving the protected value.
Supporting
State and Rule Visibility Encoding · Attachment
Apply State and Rule Visibility Encoding across result → cause → learning/retry while preserving the protected value.
Solution Compositions
Solution Compositions
How should interventions be combined and sequenced?
CORE CLASSIFICATION
Single-Track Localized Bundle
Connect 1 source-declared mechanism across F/C/M as Single-Track Localized Bundle.
Combine a core intervention with stabilizing or accelerating support within one problem track and keep its impact localized.