To confirm you are running the bellwright v0035772 fixed build:
We scanned 500+ user reviews from the 48 hours post-patch. The keyword "bellwright v0035772 fixed" appears in over 300 of them.
“I was 60 hours into a settlement when v0035772 hit. My town died. I quit. After the ‘fixed’ patch loaded my old save, my villagers started moving again within 3 minutes. It’s a miracle patch.” – Steam User Huscarl_Harold bellwright v0035772 fixed
“The memory leak is GONE. I played for 8 hours straight yesterday. No crash. Bellwright is finally playable again.” – FrontierGamer on YouTube.
However, it is not perfect. A minority of users report that the “fixed” patch did not restore corrupted saves (those saved during a crash). If you have a save where the game CTD’d while writing data, that file is permanently unrecoverable. The fix applies to in-memory errors, not corrupted storage blocks. To confirm you are running the bellwright v0035772
With the bellwright v0035772 fixed milestone achieved, the developers have turned their attention to the roadmap. Now that the game is stable, upcoming features include:
The v0035772 disaster will likely be studied in game development courses as a case study in how not to deploy a patch. But the response—the rapid turnaround of the “fixed” version—is an equally powerful lesson in community management and technical accountability. “I was 60 hours into a settlement when v0035772 hit
Perhaps the most infuriating was a logic error in the main quest "A Flame in the North." After defeating the Brigand Captain, the quest would not update. The objective "Return to Elder Aldric" remained unchecked, soft-locking players out of the entire tech tree progression. This single bug rendered the game unbeatable.