01

Treat it as permanent progression

The Steam Community guide describes Destiny Inscription as a skill-tree-like system with nodes that unlock in sequence. It also notes that sapphires are earned during dungeon progress and can be used in the Pocket Dimension.

Before spending, decide whether you are unlocking a new route, improving survivability, or adding more run flexibility. The best first node depends on what you are currently failing to do.

02

Keep old numbers labeled

The available long-form community guide was written around the 0.7.x period and contains several explicit uncertainty notes. Use it to locate systems and questions, but re-check every percentage, cost, and unlock condition against the current game.

This page therefore separates stable system explanations from values that require a fresh in-game capture.

03

A useful upgrade order

Write your preferred order as a path, not a tier list: unlock the system that removes your current bottleneck, test it for one run, then revisit the tree. Keep a screenshot or patch note beside the path when the game changes.

04

Spend for the bottleneck

Permanent progression is easiest to plan when it answers a failure you can name. If you are dying before a build comes online, favor consistency and survivability; if you survive but lack damage, favor the node that improves your next upgrade choices.

Write the path as a sequence of decisions, including the reason for each node. That keeps the page useful after balance changes and makes it easier to reverse-engineer a successful save.

05

What to screenshot

Capture the tree before spending, the selected node after spending, and any unlock confirmation. Keep the version beside each capture because old community guides cover the early-access tree rather than the current 1.0 client.

If a value is not visible in the current client, leave it unfilled. A verified blank is more trustworthy than a precise number copied from an older patch.