The current roster is Warrior, Witch, Bard, and Paladin
Lootbound's current class roster is Warrior, Witch, Bard, and Paladin. If normal progress leaves one class locked, record the available roster, completed runs, current difficulty, visible ability state, and Barracks state. Keep that snapshot before trying any technical change.
Do not edit, delete, or combine save files to force a class open. A class remaining locked does not provide a confirmed unlock order, threshold, or Seal formula. Preserve the progression state and keep unlock troubleshooting separate from build advice.
Choose a class by the role the current drops can support
Warrior supports direct pressure through a Slash plan or a durable thorns-oriented role. Witch can build around Corruption and use Acid when armor would delay health pressure. Bard can use instruments for buffs, healing, and party support. Paladin can combine hammer pressure with defense. These are demonstrated archetypes, not fixed item lists.
The correct class plan is the one whose anchor, support pieces, and companions form a coherent board. Do not force every drop into a remembered template. Start with the class action pattern, keep equipment that advances it, and assign missing armor pressure, finishing damage, or support to companions.
| Class | Practical archetype | Party need to check |
|---|---|---|
| Warrior | Slash pressure or durable thorns | Armor answer and support |
| Witch | Corruption with focused setup | Opening survival and finishing damage |
| Bard | Instrument support, buffs, and healing | Enough party damage |
| Paladin | Hammer pressure and defense | Companions that use the extra turns |
Use update, restart, and file verification only as technical remediation
Install the current game update when the installation is outdated, restart Lootbound and Steam when the client state is stale, and verify local files when installation damage is suspected. These actions repair technical conditions only. They are not an unlock sequence and they do not satisfy an unstated progression condition.
Before verification or reinstallation, close the game and copy the complete LootBound/Data folder. Launch afterward and compare the roster and Hub state with the snapshot recorded before remediation. Preserve both states until the correct progression is confirmed.
- Record the locked class and current progression state.
- Close Lootbound and back up the complete Data folder.
- Update, restart, or verify files only for the matching technical problem.
- Launch and compare the state with the recorded snapshot.
- Keep the backup and do not promise that remediation changes the lock.
Protect progression while diagnosing the problem
Lootbound stores .data files inside the platform-specific ArtDock/LootBound/Data directory. Close the game before making a backup so the copied files belong to one completed write. Keep that backup outside the live folder. Steam Cloud support is useful, but a manual copy gives you a fixed recovery point before file verification or device changes.
Do not mix files from different attempts while checking a locked class. Change one technical variable, launch the game, record the roster state, and close cleanly. Multiple simultaneous changes make it impossible to identify whether the installation changed while putting progression at unnecessary risk.
- Close the game before copying the Data folder.
- Keep the backup outside the live save directory.
- Verify files only after the backup exists.
- Never delete the original progression to test a guessed unlock method.
Move from unlock troubleshooting to class progression
Once the class is available, choose one demonstrated archetype and play several attempts with the same central plan. The achievement list separately tracks unlocking all abilities for each class companion and completing a run with each class on Difficulty III; verify those two conditions independently.
Keep unlock work separate from build work. A class can be available while its run still fails from poor shapes, weak target focus, empty mana, or unsupported companions. Diagnose those run systems instead of treating technical remediation as progression.