Goal Builds

Achievement builds should start from the unlock condition, not from a generic tier list.

Achievements change what a build is supposed to do. A run chasing a stat breakpoint, a boss trick, a Bestiary gap, a pacifist condition, or Pressure progression should not always choose the same upgrades. This page gives a cautious planning framework for building toward goals without pretending every route is fully solved.

Quick Facts

Fast read before the full guide

Best Use

Planning a run around one achievement family.

Core Rule

Read the condition first, then choose the build shape.

Good Targets

Stats, combat milestones, boss tricks, challenge runs, Bestiary, and Pressure.

Avoid

Trying to chase every achievement type in one run.

Short Answer

Pick the achievement category first:

  • Stat goals need body-shape steering.
  • Combat goals need total damage, burst, or a specific tool.
  • Boss goals need condition control.
  • Challenge goals need risk suppression.
  • Bestiary goals need tracking and encounter coverage.
  • Pressure goals need consistency.

Then build only for that goal family.

Stat Goals: Shape The Body Early

Stat achievements such as size, speed, or dodge-style goals are usually build steering problems. You need to start reading the run through that stat early enough that random upgrades do not pull you away from the target.

Build priorities:

  • Choose upgrades that move the target stat directly or indirectly.
  • Avoid pieces that fight the target shape.
  • Keep enough survival so the run can actually reach the breakpoint.
  • Stop taking attractive upgrades if they make the target harder.

The mistake is treating stat goals like normal clears. They are more like route discipline tests.

Combat Goals: Know The Damage Type

Combat achievements can ask for very different damage logic. Total damage, one-hit burst, tool-specific kills, and boss finishers are not the same route.

Build priorities:

  • For total damage, build for long-run scaling and survival.
  • For burst, build around one clean spike.
  • For tool-specific goals, protect the required tool from being replaced by easier damage.
  • For boss finishers, avoid over-damaging before the condition is ready.

The mistake is adding “more damage” without knowing what kind of damage the achievement actually wants.

Boss Goals: Control The Final Condition

Boss achievements often care about timing, terrain, final-hit ownership, speed, or a special event. That means the build needs restraint as much as power.

Build priorities:

  • Keep the boss alive long enough to set up the condition.
  • Bring the specific tool or route needed for the finish.
  • Maintain enough movement to survive while waiting for the window.
  • Avoid uncontrolled damage sources if the final hit matters.

The mistake is killing the boss cleanly but missing the achievement condition.

Challenge Goals: Remove Risk First

Pacifist, no-hit, or extreme restriction goals are not normal combat builds. They are route-control builds.

Build priorities:

  • Reduce accidental damage.
  • Improve movement and disengage.
  • Avoid upgrades that break the restriction.
  • Favor tools that let the environment, allies, or indirect systems handle danger when appropriate.
  • Keep the route simple enough to execute under pressure.

The mistake is choosing a fun combat package that invalidates the challenge condition.

Bestiary Goals: Build For Coverage

Bestiary and collection routes reward seeing and documenting the right entries, not necessarily clearing as fast as possible.

Build priorities:

  • Survive long enough to reach varied encounters.
  • Keep movement high enough to search safely.
  • Avoid killing targets too quickly if scanning, observation, or specific interactions are needed.
  • Track variants, summons, and boss-family entries separately.

The mistake is treating Bestiary completion like a damage race.

Pressure Goals: Build For Consistency

Pressure achievements or high-pressure progression reward builds with fewer weak links.

Build priorities:

  • Stable food access.
  • Damage that works in bad spaces.
  • Movement that remains useful under crowding.
  • Sustain that prevents one mistake from ending the run.
  • Defense that buys time without ruining positioning.

The mistake is copying a low-pressure high-roll build into a higher-pressure consistency test.

One-Run Planning Template

Before starting an achievement attempt, write the route in one sentence:

This run is for [achievement family], so my build needs [primary tool], [survival support], and [failure condition to avoid].

Examples:

  • This run is for a stat goal, so my build needs target-stat steering, survival support, and no upgrades that fight the stat.
  • This run is for a boss trick, so my build needs condition control, enough movement, and no uncontrolled final-hit damage.
  • This run is for Pressure, so my build needs stable food, reliable damage, and no early narrow greed.

What Still Needs Verification

  • Some achievement conditions need more reliable in-game confirmation.
  • Exact fastest routes should not be treated as solved.
  • Build recommendations should remain category-based until more repeatable route data exists.