Deskrawl Gems and Runes: Build a Set Without Waste

Separate gems from rune-set direction

A gem is a slot-level choice: use it to reinforce damage, sustain, or another stat the build already needs. A rune can be more structural because set effects may change skill coverage, automate casts, or reward a specific attack pattern.

“Runebound” unlocks when the first rune is equipped. Treat that first placement as a tutorial, not a commitment to force every later item into the same set.

Choose a set only after naming the engine

Use a no-regret socket workflow

Active discussions describe gem destruction as punishing. Until every removal rule is documented officially, assume an irreversible action may consume value and verify the UI confirmation before continuing.

1. Lock or store every rare gem and rune you are not actively testing.
2. Write down the destination item, replacement cost, and expected interaction.
3. Confirm the item will remain in the build long enough to justify the resource.
4. Test the equipped result on a stable map and one boss checkpoint.
5. Only dismantle duplicates after the new setup has survived a full idle session.

Measure effect uptime, not tooltip excitement

A set that triggers Lightning Storm is valuable only if the build produces the required lightning events and keeps enemies in range. A dodge engine is valuable only if incoming attacks, dodge chance, and mana use create a stable cycle.

Record clear time, death count, resource stalls, and boss performance. If the set wins only in a short manual burst but fails unattended, it is not yet an idle build.

Keep a compact rune inventory

• One working set for the current build.
• One alternate set for the next difficulty or boss problem.
• Rare pieces with unclear effects, stored until the wording is verified.
• Duplicates kept only when they protect an upgrade or trade plan.
• Screenshots or notes for every irreversible socket or dismantle decision.