Story Towers extend progress from completed Story content into specialized clears and crafting. Community documentation describes unlocking a Story Tower by clearing its related Story across required difficulties, then earning crystals used for cards or accessories. Confirm the current requirement and recipe in your server.
Confirm the unlock
Open the Story Tower interface and read the related map, difficulty requirement, and current lock message. Return to Story Mode and complete only the missing prerequisite. Do not grind an archived number of maps when the live panel names a different condition.
Reopen the tower after the clear and verify that access recorded.
Prepare for the tower
Use a reliable deck that handled the related Story but account for tower scaling or waves. Verify support activation and equip items that improve the actual failure point. Save this as a separate loadout if the normal Story farm uses faster but less durable cards.
Choose the first clear or checkpoint shown by the interface as the target.
Track crystals and rewards
Record the exact crystal or material name and quantity from the result panel. Check nearby crafting options before repeating. Separate guaranteed first-clear rewards from random or replay observations.
Community references mention pity-related systems, but exact counters and rates are update-sensitive. Use only the counter displayed by the current game.
Compare cards and accessories
Read every current recipe. For a card, identify its role and compare it with the active party. For an accessory, match its effect to a card you actually use. Do not craft solely because the recipe is the first affordable option.
Preserve enough currency for a higher-priority result if it is within reach. Verify the crafted asset in Card Index, Deck, or inventory.
Improve a failed clear
Note whether the team lacks early damage, sustained output, activation, or survival. Change one card or item and repeat the same floor. Use permanent upgrades or another mode when the tower requires an improvement you cannot create inside it.
Avoid consuming rare timed buffs unless the next clear unlocks a meaningful checkpoint or recipe.
Maintain the route
After updates, recheck Story prerequisites, tower floors, crystals, recipes, and pity displays. Date personal notes. Use Crafting before spending materials, Artifacts for accessory testing, and Card List to verify crafted cards.
The useful Story Tower loop is clear Story requirement, verify tower access, earn confirmed crystals, compare recipes, and test the result. Every step should be visible in the current server.
Plan a crystal target
Choose one current card or accessory recipe and record its exact crystal requirement. Note your existing balance, first-clear rewards, and any repeat source shown. Farm only until the planned amount is reached, then compare the recipe again before crafting.
If the same crystal buys several results, rank them by current deck need. A broadly useful accessory may be stronger account value than a card that duplicates an established role; a missing key support may reverse that decision.
Use pity information carefully
If the current interface exposes a pity counter, record its starting value, eligible action, guarantee, and whether it survives leaving or changing towers. Do not import an older published rate. Perform a small test and confirm the counter changes exactly as described before committing a full currency reserve.
If no counter is visible, do not claim one exists. Treat community records as historical orientation.
Benchmark a crafted card
Read the card’s current effect and restrictions, then add it to one saved-deck copy. Use the related Story stage or a known benchmark and compare activation, clear time, and reliability. Delay rare traits until the new card proves a role.
For an accessory, equip it on the intended attacker or support and keep every other item stable. Record whether it improves Story, the tower, or only one specialized fight.
Resolve access problems
When the tower remains locked after the named Story clears, reopen Story and verify every required difficulty recorded. Rejoin a fresh server and inspect the entrance again. Capture the lock text before repeating content, because one missing branch is easier to solve than replaying the entire map set.