Lootbound Classes

Classes are loot filters

In Lootbound, a class is less a rigid skill tree and more a filter for which items feel natural. You still win on districts and damage coverage, but Warrior, Paladin, Witch, and Jester pull different levers.

• Warrior �?physical payoff, crit, vampirism lanes
• Paladin �?armor, health, Order sustain
• Witch �?magic pressure, bypass, Chaos tools
• Jester �?enable, buffs, party instruments

Unlock patterns in previews often start with Warrior and reveal others after a win. During a run you may recruit kits before they are permanently unlocked—use that to test identities early.

How to assign loot among kits

Ask which board can activate the item’s aura and damage type. A break tool on a Witch may outperform the same tool jammed into a full Warrior crit district that has no free cell. See Inventory Mastery and Aura Districts.

Party composition tips

You control the hero; companions act automatically. That means class choice is also AI scripting. Pair a durable kit with a bypass kit when biomes show mixed armor. Pair burst with enable when elites must die fast. Deepen combat conversion in Combat Priority.

Lane pairings

Crit loves Warrior (Crit Build. Lifesteal can live on Warrior or hybrid boards (Lifesteal Build. Tank loves Paladin (Tank Build. Witch often carries the type coverage the physical kits forget (Damage Types.

Pre-release learning path

In the demo, force one run per kit focus even if the roster is limited. Take notes on which loot made the kit feel complete. Then use Build Path Advisor to lock a lane for launch week.

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 — Classes Hub

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