Check the branch before troubleshooting

v0.111 is an optional beta build. A fix listed in its patch notes may not exist on main v0.107.1 yet.

Before changing a setting or touching a save:

  1. Read the version on the title screen.
  2. Confirm the selected Steam branch.
  3. Confirm the in-game profile.
  4. Note whether mods were enabled or declined.
  5. Preserve the relevant save directories before manual repair.

This prevents a branch mismatch from looking like data loss.

What changed for modded saves

v0.111 fixes two specific save-copy cases:

  • unmodded saves should no longer copy into the modded save directory when a player declines mod loading but leaves mods installed; and
  • players who had previously declined mod loading should now receive the intended unmodded-save copy when appropriate.

This does not combine progress. Modded and unmodded saves remain deliberately separate. A run completed with mods enabled may not appear when the game is launched without mods, and the reverse can also be true.

The Steam Workshop and save guide explains that separation in more detail.

Safe save diagnosis

If progress looks missing, do not immediately delete or rename folders.

Use a reversible sequence:

  1. Close the game.
  2. Confirm whether Steam is set to main or public beta.
  3. Record which mods are installed and enabled.
  4. Relaunch with the same branch and mod state used for the missing run.
  5. Check the correct in-game profile.
  6. Back up both modded and unmodded save locations before any manual change.

If the expected progress appears only with mods enabled, that is evidence of save separation, not proof of corruption.

Controller and keyboard fixes

The patch restores E as a confirmation key during card selection. It also fixes controller focus failing to return to cards after a reward reroll.

If input still fails on v0.111:

  • verify the game window has focus;
  • check the binding shown in settings;
  • note whether Steam Input is active;
  • reproduce the issue without remapping several controls at once; and
  • use the in-game feedback flow with the exact version and input device.

The keyboard-only controls guide covers full keyboard navigation. This page covers the narrower v0.111 fixes.

Map drawing, badges, and crashes

v0.111 also fixes input being blocked after clearing map drawings and map lines breaking when cleared mid-stroke. If a drawing problem continues, test whether it occurs only in multiplayer, only during an active stroke, or after clearing the board.

The patch addresses badges that could be lost when leaving the game-over screen early or after earning every unlock. It also lists fixes for crashes involving treasure-room relic selection in multiplayer, reopening single-card inspection, cards moving after combat, and combat ending while cards are still shuffling.

These are scoped fixes, not a guarantee that every crash has the same cause. Record the action immediately before the error.

What to include in a useful bug report

Provide:

  • exact game version and branch;
  • operating system and input device;
  • whether mods were installed, enabled, or declined;
  • single-player or multiplayer;
  • the last action before the problem; and
  • whether the issue repeats after a clean relaunch.

Do not attach private files publicly unless the official support flow requests them and you have checked their contents.

The practical boundary

Use v0.111 when one of these listed fixes blocks beta play and you are comfortable testing. Keep a serious main-branch run on its original version unless you have a clear reason to switch.

Most importantly, preserve the evidence before trying a repair. The fastest way to turn a branch or profile mismatch into real loss is to overwrite the copy you had not yet identified.