Connect a Unit to the right Trait and Equipment job
Choose the Unit first, then choose Carry damage, Support / control, Farm income, or Status damage. The finder joins the supported Unit, Trait, and Equipment records in two selections and refuses unsupported combinations instead of inventing a universal best build.
27Supported Units
10Linked Traits
15Linked Equipment
2Selections to answer
Use Shadow as the damage anchor only after its attack cycle solves a repeated stage problem. Keep the trait and gear roll that improve that job; do not chase a perfect roll on a temporary slot.
Place the intended Magical carry inside Shadow’s coverage, then confirm the lane survives longer than it does with a second standalone DPS.
Unbound+350% Damage, -5% SPA, +10% Range
Hexed Blade+1% to +5% Range · +1% to +10% Damage
Magic Book+5% to +20% Magical Damage DealtUse the linked gear when its stat family matches the live Unit job.
Build decision layer
The finder is intentionally narrower than a DPS simulator. It joins a Unit’s recorded role with the Trait and Equipment relationships that can change the next repeatable task.
Use the carry result when the Unit is responsible for repeated damage. Compare Damage first, then check SPA and Range against the stage before spending a rare Lock. A large panel number is not useful if the Unit cannot keep its attack cycle on the target.
Test: same stage → same placement → one changed rollSupport and control rolls earn their slot by extending coverage, grouping enemies, or preserving the carry’s safe window. Read the linked effect and Equipment family together; do not replace a reliable control window with a higher personal DPS number.
Test: same wave → same support position → coverage or control resultFarm Units should be judged by the income route they unlock, not by whether combat gear makes their card look stronger. Leave premium damage equipment on a combat slot unless the live task genuinely needs the farm Unit to attack.
Test: same farm route → same time window → income resultStatus damage is a repeated-effect question. Use the linked trait direction, then verify that the stage and target behavior allow the effect to apply often enough to matter. Do not lock a status roll from a single short wave.
Test: same target type → longer wave → visible status contributionLock and reroll route
When the Unit, stage, and job stay stable, the result tells you whether a Trait or Equipment change solved the blocker. If the test changes several variables at once, return to the Unit record and establish a smaller baseline.
Choose carry, support/control, farm income, or status damage before reading a recommendation.
Open the linked Unit, Trait, and Equipment records and confirm the relation is supported rather than inferred from rarity.
Keep placement, stage, and team context stable while testing one Trait or Equipment result.
Preserve a roll when it improves the same task more than once; otherwise keep the baseline and test again later.
Use the Unit database for panel identity, the Trait database for effect scope, and Equipment for the exact stat family before opening Evolution Planner.
Share this guide
Share the current Anime Expeditions route, or copy the link for Discord and group chat.
Player questions
Use the current game panel before spending rare resources on a value that can change.
It connects a supported Unit to recorded Traits and Equipment for a chosen job, then explains what to lock and what to test in the live panel.
No. It does not simulate passives, buffs, summons, status damage, or hidden attack timing. Use the Unit database for known panel values and the finder for the relationship decision.
The current public data does not support a safe recommendation for that Unit and job combination. Choose one of its recorded jobs rather than filling the gap with a generic build.
Choose Farm income. Investor is the recorded trait direction, and premium combat Equipment should stay on a different slot because Ramen Guy’s job is Yen generation.
No. Treat the list as a comparison set. Confirm the live Unit job and attack cycle, then lock only a result that improves that repeated task.
