01

Importing a build is only the first step

The developer's featured-build instructions say to copy the shared string and open Build Planner from the world map or main menu. Select Import, confirm the setup appears in the editor and save it. Start a ritual, enable Auto-Build Mode and choose the saved build from the dropdown. A build string is configuration data, not a redeem code or a reward claim.

The original 0.20 announcement explains that a shared build can specify character properties, abilities, equipment and Soul Fragment preferences. That makes it more complete than a screenshot of the final character sheet. It also means there are more dependencies to check when importing into a different account or patch. The planner accepting the string does not establish that every required unlock is available.

02

Match the setup to its intended content

Version 0.20.6 adds ritual tags and displays the build's creation version in its tooltip. The same announcement distinguishes official and featured community builds visually. Use those labels to understand where the recommendation comes from and what it was designed to do. An official feature is evidence of publication by the developer, not a fresh benchmark on every later version.

Compare an older demonstration with your intended ritual before changing equipment. A farming setup and a boss-focused setup can answer different player questions even if they use the same class. The supplied sources do not establish one configuration as best for every purpose. Exact performance rankings, universal clear tiers and guaranteed farming rates remain 待确认.

03

Check Auto-Build's limitations

Auto-Build receives the same random choices as a manual player, according to the 0.20 introduction. It tries to follow a plan rather than bypassing the selection system. Version 0.20.7 makes it ignore locked armor-set, stat or passive requirements and choose alternatives instead. This is a documented reason for your finished character to differ from an imported plan.

Class and origin changes can also invalidate parts of a configuration. The same update says options tied to the replaced class or origin are ignored. In 0.21, the default Auto-Build hotkey becomes unbound to prevent accidental activation. Inspect both the actual selected options and your keybindings before interpreting a discrepancy as a damage bug.

04

Translate Instant Attack into its current name

Patch 0.21 renames Instant Attack Chance to Rapid Attack Chance. Primary Attack Abilities retain their previous behavior. For other abilities, the stated cooldown reduction drops from 95% to 50%. An old build centered on repeated non-primary casts therefore needs a more careful review than a simple label replacement.

Those percentages are not a universal damage-loss calculation. Cast animations, other bonuses and the distribution of damage between abilities still matter. The patch itself notes the primary-attack animation distinction. Read the Instant Attack Chance explanation for the confirmed rule without converting it into an unsupported DPS promise.

05

Recheck proficiency and damage dependencies

The 0.21 notes remove separate Sigils and Auras proficiencies. Affected abilities receive other proficiency requirements, while affected origins gain different bonuses. Old instructions that tell you to acquire one of the removed proficiencies are therefore outdated. The exact replacement should be read from the relevant current ability rather than assumed from the category name.

Shadowstrikes, Mark of Shadow and Edge of Darkness change to Umbral damage in this update. Ring of Ruin is also changed to stack from all damage sources, including Burning. These are concrete interactions to compare against an old build's explanation. They do not by themselves prove that a Thief, burning or artifact build is the new universal winner.

06

Inspect equipment names, sets and locked stats

Deathspeaker's Handwraps replaces Deathbringer's Handwraps in 0.21. The Chromatic Unique Set is rebalanced and gains Umbral-related bonuses, but the announcement does not enumerate its complete final tooltip. Some strong armor stats, including dodge and movement charges, can no longer be enhanced. A lock icon identifies non-enhanceable stats, so do not keep rerolling to pursue a now-invalid upgrade assumption.

The history of Chain Mail is another reason to use the latest applicable note. Version 0.20.7 prevented exact required stats from being set in the planner because of the odds of obtaining them. Version 0.21 explicitly allows exact required Chainmail stats again. Preserve that chronological distinction instead of presenting both historical rules as simultaneously current.

07

Check runes before changing unrelated bonuses

Version 0.21 adds Abyss runes, Runewords and a fix for an Auto-Build selection issue involving three identical runes together with Yiln. A copied sequence should be checked slot by slot. An active individual rune effect is not proof of an active Runeword. If a shared Runeword stays inactive, compare its order, unlock state and Runeword Discovery with the reference.

The supplied material does not provide a verified threshold for every recipe. It also does not establish a complete rune compatibility chart for every ability. Those gaps remain 待确认, rather than being filled from an old table. The runes page explains what can be confirmed from the developer's announcements.

08

Keep the result reproducible

For a practical comparison, retain the source patch, class, origin, ritual tag and the important equipment and rune choices. First check whether the imported plan actually selected those dependencies. Then change one incompatibility at a time so a later attempt has a clear comparison point. This is a suggested testing process, not a claim that these pages have measured the build in-game.

The official Lazy Reflector and other featured builds can illustrate how configurations were shared at a particular time. Their older presentation should not be silently converted into a 0.21 performance guarantee. Keep author claims attributed and distinguish them from later developer balance changes. The useful outcome of this guide is a checked setup, not an invented tier-list position.