01

Build around a repeatable action

A build becomes understandable when you can describe the action it wants you to repeat: keep distance, stay aggressive, block into a counter, or convert a defensive window into damage. Start there, then choose weapons and artifacts that make that action more reliable.

The official game description calls out the inventory system and tablet-powered artifacts, so build notes should always record the weapon path and the inventory arrangement together.

02

Separate the build from the patch

A community build video can demonstrate timing and movement, but its numbers may belong to an earlier patch. Keep the game version, source date, and the exact upgrade names beside every recommendation.

When a build depends on a specific artifact or tablet, link to that item page rather than hiding the dependency inside a paragraph.

03

Use a simple test

Test a build in three situations: clearing normal rooms, surviving a crowded room, and dealing with a boss window. If it only works in a perfect setup, label it as a specialist build instead of a universal recommendation.

04

Three build directions to test

A close-range build asks for entry and exit timing; a ranged build asks for a clean firing lane; a spell or companion route asks for resource control. Start with the action you enjoy repeating, then let artifacts and tablets support it.

This makes a build understandable even when the exact drop is random. You are looking for a family of replacements, not one irreplaceable item.

05

Fallbacks when the run misses

Keep one fallback for damage, one for survival, and one for room control. If the ideal artifact does not appear, switch to the fallback that preserves your route instead of forcing a different build halfway through a chapter.

Record the missing piece and the replacement you used. Those notes are the beginning of a real tier list because they explain why a build works, not just what it contains.