There is no permanent best Core build supported by the evidence: make a build-stamped plan for the current weapon and combat problem, then strengthen one synergy or cover one weakness.
Reject a permanent tier list
Official sources confirm that Weapon Cores and Combination Cores can create expedition synergies, but they do not publish an official tier list or a single universal best build. Early Access patches change damage, range, drops, slots, and named Core behavior, so an older ranking can become wrong even when it once described a real test.
Treat “best” as a narrow claim: best among the options seen in a named build, for a named weapon, squad, difficulty, and encounter goal. Without those conditions, a ranking hides more than it explains.
Choose one combat goal first
Organize a candidate build by the problem it must solve:
- crowd pressure: prioritize an effect whose current description reaches or controls several targets;
- single durable target: prioritize reliable focused damage that fits the current weapon;
- survival: address the reason the Leader or squad is failing rather than adding unrelated damage;
- squad support: use effects whose visible wording actually applies to soldiers; or
- movement and control: create safer positioning when the encounter demands it.
These are functional groups, not promises that a particular named Core always fills them. Read the active cards. The research does not contain a permanent effect table that would justify assigning every Core to a fixed box.
Use a three-step selection method
First, identify the weapon and immediate failure. Second, choose a Core that visibly addresses that failure now. Third, use later choices either to reinforce the same trigger or to cover the most dangerous remaining gap.
For example, an area effect is only useful as a crowd answer if its current card, weapon interaction, and encounter make it repeatable. A squad effect is only a squad build if the current wording applies to the soldiers being used. The method prevents an attractive rarity or remembered old ranking from replacing the actual expedition state.
The Weapon Cores guide explains the difference between weapon, Combination, and squad-oriented effects.
Learn from the AG-14 example
AG-14 increased Vortex Shell damage and increased Thunderbolt Arrow damage range. Those are real official examples of a patch shifting two named choices. They are not proof that either became globally best or that their present values match an older recording.
When a patch touches a candidate Core, start a new comparison row. Do not silently combine pre-patch and post-patch observations.
Keep a build-stamped test record
Record the build or patch date, difficulty, weapon, Core set, squad context, encounter type, and result. A useful note explains what failed or improved. It does not need an invented score.
Community discussions in the canonical research report that strong Core combinations can define an expedition and that long-run combat balance changes with progression. Those reports motivate comparison; they do not control for every variable and cannot become an official ranking.
Adapt the plan to missions and capture
A decisive battle may reward a different answer from a normal expedition route. The Elysia Oasis guide separates official turret, weak-point, and spawn changes from general preparation. If capture is the goal, preserve the ability to weaken a target and use Capture Rounds instead of judging the run only by defeat speed.
Retire a recommendation when its build stamp, current card wording, or encounter no longer matches. A reproducible conditional result is more useful than a permanent list the evidence cannot support.