Lootbound Witch

What Witch wants from loot

Witch thrives when items reinforce magic pressure, bypass tools, and Chaos. If you feed the kit random off-identity trophies, companions look broken and the hero feels underpowered. Start every biome by naming the identity you are feeding, then only break that identity when a full pivot is available.

District plan

Seat keystone pieces first and grow neighbors with Grid and Rotation discipline. Keep utility from cracking the center of the board. Rehearse with Aura Planner and theory from Auras Explained.

Best lane partners

Lean into Damage Types and Damage Cheat Sheet. Use Build Path Advisor if a loot spike tempts you into a muddy hybrid.

Companion and hero roles

If Witch is your hero, build the climax pattern on that board. If Witch is a companion, script automatic behavior with equipment that makes default actions useful—break, sustain, enable, or payoff. Review Classes for swap ideas with Warrior, Paladin, Witch, and Jester.

Map shopping list

Chase nodes that complete your identity before novelty rooms. Route Choice and Risk Reward Dice should read like errands for the kit, not entertainment.

Combat notes

Translate the kit into target order and mana timing via Combat Priority. Witch still loses to the wrong armor pattern if you ignored Damage Types.

Guardian readiness

Before finales, confirm the kit’s damage language still matches assembled parts (Guardian Parts, How to Beat Guardians.

Practice goal

Finish one demo expedition where at least seventy percent of equipped items visibly serve magic pressure, bypass tools, and Chaos. If you cannot explain an item’s job, it is probably tourist loot.

Field notes from failed expeditions

Most players do not fail because they lack mechanical talent. They fail because they change plans every room. Write a one-line plan at the start of a biome—“crit district on hero, break tools on companion, safe route until keystone drops”—and obey it unless the loot pool makes obedience impossible. When obedience becomes impossible, pivot with a full rebuild, not with five disconnected upgrades.

How this page connects to the rest of the wiki

Return to How to Play if the overall loop still feels fuzzy. Use Beginner Tips as a habit checklist after messy runs. Open Tools when you need an interactive rehearsal instead of another paragraph. Confirm store timing on Demo and Release during launch week so patch notes and wishlist messaging stay aligned with reality.

Pre-release and post-release use

Before August 14, 2026, treat every section as demo-validated systems literacy. After release, treat the same sections as a troubleshooting index: inventory pages for board failures, map pages for pacing failures, boss pages for finale failures, and build pages for identity failures. The wiki is unofficial and should lose to the Steam page whenever dates or features conflict.

Extended practical checklist — Witch

For “Witch”, use this checklist at every biome gate and after every elite that nearly wiped you. First, name the lane in one sentence so you cannot hide behind vague ambition. Second, point at the keystone aura on each board and confirm it still activates after the latest pickup. Third, name the armor answer in the party—break, shred, bypass, or a documented mix—and identify which character seats it. Fourth, count remaining mana and health debt before you accept another high-risk branch. Fifth, decide which companion is carrying enable, which is carrying payoff, and which is carrying durability so loot stops being sprinkled by panic.

When a drop arrives, force a four-question filter before it touches the grid: what footprint remains after rotation, which district wants it, which item loses its seat, and whether the swap still serves the finale you are assembling. If you cannot answer those questions quickly, leave the item on the floor. Lootbound rewards decisive refusal more often than heroic packing. Rehearse refusals in the demo until they feel boring; boring discipline is how expeditions become repeatable.

Common failure stories and repairs

On “Witch” pages, failure story A is the museum board: every rarity represented, no district alive. Repair by deleting tourist items until two neighborhoods are obvious. Failure story B is the empty-pool fighter: flashy ability use on trash, silence on bosses. Repair by assigning autoattacks to easy rooms and saving spend for elites. Failure story C is the authored hard counter: boss parts chosen for spectacle while damage coverage was incomplete. Repair by treating part choice as matchmaking against your own seats. Failure story D is companion neglect: hero jewelry polished while allies wear junk. Repair by scripting at least one automatic action pattern that matters every fight.

Cross-link your repair to the right hub instead of rereading everything. Inventory confusion belongs with grid and aura pages. Pacing confusion belongs with route and dice pages. Finale confusion belongs with Guardian pages. Identity confusion belongs with builds and the advisor tool. The fastest improvement loop is narrow: one failure story, one hub, one tool rehearsal, one more run.

Launch-week and long-term maintenance

When revisiting “Witch” in the days around August 14, 2026, expect patches, balance notes, and community shorthand to move faster than any static guide. Use this wiki as a systems framework, then verify contested numbers and date-sensitive claims on Steam. Keep your personal notes short: lane, keystone, coverage, next purchase. Those four fields survive meta shifts better than a screenshot folder of random inventories. After each meaningful clear or wipe, update only the field that actually broke. That is how a fan wiki stays useful without pretending to be a patch blog.

Focus keyword for this page: Witch. Keep repairs tied to this topic instead of rereading the entire wiki after every wipe.