Lootbound Damage Types

Why damage types exist

Lootbound wants you to build identity, not generic attack. Different damage approaches interact differently with armor and health. Steam’s framing highlights directions such as armor penetration, exhaustion, armor destruction, and direct damage. Community write-ups also discuss readable labels like base, slash, crush, and acid-style bypass. Use whichever labels your build UI shows—but keep the coverage idea identical: raw damage alone is not a plan.

Coverage checklist for every party

• A reliable generalist damage option
• A way to break or shred armor
• A way to ignore or bypass armor
• A plan for long fights if the Guardian stalls you

Validate quickly with the Damage Cheat Sheet.

Building coverage on the grid

Damage types are not abstract—they live on items seated in districts. If your only bypass piece is unplaced, you do not have bypass. Seat these tools with the same care as crit or vamp keystones (Grid and Rotation, Auras Explained.

Class tendencies

Warrior leans physical payoff (Warrior. Paladin leans durable pressure (Paladin. Witch often brings bypass/debuff identities (Witch. Jester enables others rather than solo-carrying type coverage (Jester.

Map shopping for missing languages

If biome two already shows heavy armor packs and you lack break tools, your next high-risk room should chase that answer (Route Choice, Biomes.

Combat conversion

When a foe is spongy, swap focus to the character holding the correct type instead of dumping mana into the wrong language (Combat Priority.

Boss assembly warnings

Boss parts can create finales that demand a type you ignored. Track that on Guardian Parts before it is too late.

Lane interactions

Crit wants types that actually connect (Crit Build. Lifesteal needs connecting hits to refund health (Lifesteal Build. Tank needs types so longer fights end (Tank Build.

Extended practical checklist — Damage Types

For “Damage Types”, 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 “Damage Types” 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 “Damage Types” 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: Damage Types. Keep repairs tied to this topic instead of rereading the entire wiki after every wipe.