Dungeonbound ran a closed playtest before the demo, and the playtest build is still installed on some machines even though the test itself has ended. The supported way to play today is the free demo, which sits on the Steam store page and runs a couple of updates ahead of the playtest build.

Dungeonbound playtest: the closed test before the demo

  • The playtest build ran with roughly 10 playable heroes, against about 4 in the demo and 39 in the shipped game — the character roster grew at every stage.
  • The playtest was where a lot of the mechanical knowledge in circulation came from: the combat footage cited for the Monk and Rogue builds, the workshop screenshots, the enemy-scaling reports and the day-one bug reports all date from the playtest and demo era.

Where the demo is and what it covers is in the demo and release guide.

Progress carried from test to demo to release

The chain is playtest → demo → release, with no loss. Players kept their fully tested characters, with only one glitched character left locked; demo saves then carried forward into the full release.

That is worth knowing if you are returning: an old playtest account can continue in the demo and then in the release, and a fresh demo save still becomes a full-game save.

The bugs the test exposed

The playtest produced the early bugs that the patch log later fixed:

  • The launch crash when dropping one item onto another — fixed in v0.1.22.
  • The daily-run crash on death or abandon — fixed in v0.1.40.
  • Status stacks not resetting between rooms in incremental mode, which the developer confirmed as unintended and hotfixed.
  • The gray band and thin line flashing across the battle view — fixed in v0.1.46.
  • Co-op hangs and stuck lobbies, addressed across v0.1.50 and v0.1.51.

Which patch fixed which of these is in the patch notes guide.

The leftover playtest install

After the playtest ended, the executable remained on disk, and players could still launch it directly from C:\Program Files (x86)\Steam\steamapps\common\Dungeonbound Playtest. The playtest build sits alongside the Dungeonbound Demo and Dungeonbound folders on disk, which is also why a full progress wipe has to cover all three save folders.