Well Dweller Bugs and Fixes

For a Well Dweller startup or save crash, match the exact error below and copy your save folder before trying recovery. For missing spirit trinkets on Steam, install the October 2 update and load the affected save. On consoles, check the installed update and missing item first. For Steam Deck map zoom, use the linked bumper and restart checks.

The developer's October 2 patch repairs reward state in affected saves. The September 27 troubleshooting post supplies the display workarounds. The patch history separates these repairs from September 26 changes so you can choose the relevant check.

Startup or save error: match the message first

If the game crashes before a slot opens, copy the full error and protect the save folder before testing recovery. The late-October reports below have different signatures, so record the object and function names as well as the first line.

• ds_map_find_value / o_Persistent_save / Step_0 (line 125): an October 28 startup report describes this error on each launch. On Windows Steam, close the game, copy %LOCALAPPDATA%\WellDweller, then follow the Settings-reset and file-size branches. That recovery comes from the developer's earlier instructions; compare the message after one attempt.
• Attempting to read from outside the buffer / LoadJSONfromFile (line 22) / o_menu_control_Create_0: an October 29 save-error report follows a tent visit and a save indicator that kept running. After closing the game, preserve the folder and inspect the active slot and matching backup sizes. Use the zero-byte backup branch only when the active slot is actually empty; preserve a non-empty file for diagnosis before replacement.

If the error survives the Settings reset, keep the original copies and send the complete message, platform, installed version, affected slot and file sizes to the developer's support thread. Include whether the failure happens at launch, when selecting a slot or after entering a tent. A reply to the buffer-error case says reinstalling left that player's error unchanged.

These reports identify symptoms to compare, rather than a new announced repair. For Steam Deck's map controls, try the bumper-input and restart checks; map scale is separate from the Time Trial camera issue below.

Check your platform before applying a fix

Scroll sideways to compare all columns.

The developer's reply in the missing-trinket thread distinguishes a Steam repair from a console patch. A player's report after that announcement shows a case worth investigating; it does not identify which update was installed on that console.

Match your symptom to the right fix

The following announced fixes and display workarounds are from Steam / Windows developer notes. Use the platform table above for console reports.

Scroll sideways to compare all columns.

“Announced fixed” identifies a developer-listed correction; display workarounds remain tests for matching symptoms. The Dollmaker change is weaker evidence: the developer could not reproduce the reported stuck fight and made preventive changes. Update and retry, then report any remaining case with its room and action.

Missing spirit rewards: load the patched save

First compare the Night Garden nest's returned count with these reward thresholds:

Scroll sideways to compare all columns.

If you freed a spirit but have not returned it, finish that delivery first. If the nest's count is still short, use all 20 spirit locations to find the remaining statue or trial reward. If its threshold is met and the named item is absent, follow the platform table. On Steam, install the October 2 update and load the affected save; the announced repair should add the missing reward. If a different trinket is missing, use its individual location before treating it as this reward bug.

If the trinket remains absent, note the returned-spirit count and the exact missing item. Check that the updated build is installed and load the affected slot, rather than another playthrough. When making a new hand-in, still wait to collect its reward before leaving so you can verify the result immediately.

Keep the affected save if you need to report a remaining case. Restoring an older backup can roll back progress and may retain the same missing-reward state. The patch's inventory repair is therefore the first test for this symptom; reserve file recovery for a save that fails to load.

For completion tracking, compare returned spirits, owned trinkets and trinket slots separately in the achievement checklist. A Full Flock unlock indicates the spirit goal, while Expert Collector checks trinkets. Neither counter, by itself, identifies the exact item missing from your inventory.

Time Trial camera: separate tracking from a missed jump

If a bubble launches Glimmer out of view while the camera stays still, check camera tracking before practicing a different jump. The September 26 Steam announcement lists a wide-zoom tracking fix for certain trials. Install that update or later on Steam and repeat the same transition.

If the symptom remains, compare the same course at a closer camera zoom. A successful retest gives you a setting to continue with; it does not establish that another platform received the Steam patch. On consoles, include the installed version alongside the zoom, course and launch point when reporting a remaining fault.

For the Midnight Drench wall-and-bubble course, use the camera test and route chapter. When tracking works but you miss the next surface, return to the movement route and extra-time options. Those checks address a different obstacle from a camera that loses the player.

PS5 progress loss: identify what the save retained

The October 9 PS5 report describes a freeze while moving from The Docks to The Deep, then roughly two hours of missing progress after closing the game. In the reply, the developer asks about the save notification and cloud saving and distinguishes this rollback from the earlier whole-file corruption issue.

If your symptom matches, note the last tent that showed a save notification, the room that froze, and the area loaded afterward. Include the installed version and whether cloud saving was enabled. These details separate a rollback from a save that cannot load at all. Cloud saving was a diagnostic question in the reply, not a confirmed cause. Keep existing save data; an older backup can replace progress rather than recover the missing session.

Save crashes: protect files before testing

For the Windows Steam edition, the developer names the local WellDweller folder and a numbered active save such as WellDweller1. A matching backup uses the BACKUP_ prefix. Begin with a copy of the complete folder somewhere outside that location; this protects the original and the backup during diagnosis.

The save location guide gives the exact path and the developer's Settings-file reset sequence. It then branches according to file size: a non-empty active save should be tried after the reset, while a zero-byte active file requires a healthy matching backup. Use the branch that matches your files instead of deleting every slot.

After recovery, load once and inspect your area and recent progress. Keep the untouched recovery copy until you know the restored file saves and loads properly. Update before continuing the run so the original save-and-pause timing trigger is addressed.

Stutter and FPS: change one display setting at a time

Start with V-sync in the options. Replay the same short section after changing it, so you can compare the result without mixing in a different room or combat effect. If the movement is still uneven, reduce resolution and test that section again. The developer identifies resolution reduction as a useful first step because the game places more load on the GPU than the CPU.

Write down the original settings before changing them. A resolution test is easier to interpret when the difficulty, room and other options stay the same. If the result improves, you have a usable setting for continuing the run and a clearer description of the original symptom.

A report that V-sync feels ineffective is not automatically the same as the documented crash below. For a settings problem, describe the resolution, display mode, refresh rate and visible behavior. For a crash, include the complete error text instead of only saying the frame rate dropped.

GPU crash: try windowed mode for the matching error

The developer specifically mentions 0x887a0005, including cases associated with switching away from the game. Try running windowed and repeat the action that preceded the crash. Save normally before the test, and keep the recovery copy if your run has already shown loading problems.

If a different code appears, report that complete code. Similar-looking Windows messages can describe different failures, so the workaround is best treated as a test for this particular symptom. Include whether you changed focus with Alt+Tab, whether audio kept playing, and whether the error occurred during loading or active play.

Chase difficulty versus a game fault

If the Innkeeper catches you during the Webdrench Inn chase, update and try Easy: the October 2 patch adds checkpoints, while Kyle Thompson's earlier reply confirms that chase speed also changes with difficulty. Bells, barriers and grapple direction still need the correct actions.

For a persistent problem, report your platform, installed version, save slot, room, last action and result after updating through the developer's Steam support discussion. For rewards, attach the nest counter and inventory name; for progress loss, include the last retained area.

Sources and review date

October 31, 2026: added the original October 28 startup and October 29 save-error signatures, plus the Deck map-input route. The community replies do not establish the cause of those errors. Windows recovery remains the earlier developer procedure, used as a diagnostic branch after preserving the files.

Camera symptom and Steam fix reviewed October 19, 2026 against the September 26 announcement. The closer-zoom comparison is our diagnostic inference from that announcement, not a verified console repair. The platform reports below retain their original review dates.

Platform reports and developer replies were reviewed October 14, 2026. Reward thresholds follow the item records linked from Trinkets. Confirmed Steam repairs use the October 2 announcement; the existing Windows troubleshooting and chase reply were reviewed October 3. Community cases above retain their platform and report date; none establishes a universal console fix or a confirmed cause for PS5 progress loss.