Quick Answer: Bills Must Be Paid launched (July 29, 2026) unusually clean — no widespread crashes, no save wipes, no performance meltdowns in the first two days. The launch window's real entries: a blur bug on the bill/collection screens when playing on Low graphics (player-verified fix: switch to Medium; developer investigating), a single report of Windows Defender blocking the game (developer looking into it), and one unanswered launch crash report — for which a developer-endorsed fix from the demo era (launch option -force-d3d11) is the best current lead. Also covered below: why demo saves don't transfer (by design) and two single-report gameplay observations we're tracking. The two-person dev team answers nearly every thread within hours, so expect fast movement on anything real; last checked July 30, 2026.
Blurry Bill / Collection Screens on Low Graphics — Player-Verified Fix
Symptom: UI screens — the bill page and collection views — render noticeably blurry. Two players reported it independently on launch day; one noted it hadn't happened in the demo.
Fix (player-found, second player verified): open settings and switch the graphics preset from Low to Medium — the blur clears immediately. The original reporter discovered it, a second player confirmed, and the affected player's own follow-up closed the loop: "the blurriness was due to low graphics."
Status: the developer replied in the thread — "we're looking into this rn" — so a proper Low-preset fix is likely; until then the Medium workaround costs little in a game this light.
Antivirus / Windows Defender Blocking the Game
One launch-day report: Windows Defender blocked the game from running. The developer's reply: "Sorry to hear that — we'll look into this. We haven't had this issue previously." This has the classic shape of a false positive on a freshly signed indie binary. If it hits you: allow the game through your antivirus, then verify game files through Steam. Single report so far — if it were widespread, the launch-day forum would show it.
Crash on Launch (Unity Splash) — One Report, One Historical Lead
One launch-day player reports the game crashing right after the Unity loading screen, with no developer reply yet. Worth trying while you wait: during the demo period (April 2026), the developer's own fix for an identical-looking crash was to force DirectX 11 — right-click the game in Steam → Properties → Launch Options → add -force-d3d11. That fix was player-verified at the time. It's a demo-era solution to a possibly different crash, so treat it as a lead, not a guarantee — and report your specs in the forum thread either way; this developer actually reads them.
Demo Save Doesn't Transfer (By Design)
Developer-confirmed on launch day, twice: "The save from the demo will NOT transfer to the full game." The reason is scope, not oversight — per the developers' pre-release changelog post, the full version rebalanced piggy HP against the new prestige layer, reworked the RNG and piggy spawner, added legacy points to the bill system, changed upgrade nodes, and added the shop. A demo save simply doesn't describe a compatible game state. (The demo's famous integer-overflow bug — money capped at 2^63-1, then flipping negative — was also confirmed fixed for the full version.)
Single Reports We're Tracking (Not Yet Entries)
- Bomb piggy damage sometimes not registering — one launch review reports hits on the bomb-styled piggy occasionally producing no damage number, across different hammers; possibly an intended cooldown, possibly a bug. No forum thread yet.
- Ignite visual oddity — one review mentions the ignite skill's hammer flame not always behaving as expected. Vague and single-source.
Either of these gets a proper section if a second report or a developer reply lands.
Reporting Bugs That Aren't Here
The Steam discussions are the channel — the two-person team's launch-window response rate is hours, not days, and they've already confirmed fixes from player threads. Include your graphics preset (given the blur bug) and platform.
Sources: launch-window Steam forum threads (blur bug with player-verified workaround and developer reply, antivirus report with developer reply, launch-crash report, demo-save and demo-overflow developer confirmations, the developers' pre-release changelog post) and launch-week reviews for the two tracked observations. Single reports are labeled as such. Compiled July 30, 2026, at the launch version — we re-check daily during the launch window.