Pizza House Simulator Patch 1.007
Official 23 August 2026 notes: save data safety, multiplayer improvements, and reduced restaurant lag on Windows.
Patch v1.007 is a real Steam news post dated 23 August 2026, four days after the 19 August Windows launch. Broken Lyre called it a stability and multiplayer pass. This page is a teaching summary of that post. It is not a leak. Confirm wording on Steam if a later hotfix supersedes it. The parent index is the Updates Hub. Launch week narrative is on launch notes. The prior patch lives at patch 1.005.
What 1.007 changes for every owner
The headline fix is save data safety. Players had reported that reloading a save could reset money, progress, or station states. That bug was marked as under investigation in 1.005. Version 1.007 addresses it directly: save files are now handled with stricter integrity checks on write and read. If you lost money or unlocks from a prior reload, that data is not automatically recovered—but going forward, saves should hold. Before this fix, owners were advised to avoid mid-service reloads; that caution is reduced but not gone if you are on an older pre-1.007 build.
A general performance improvement was shipped for Windows, targeting frame drops during busy dinner service. A packed dining room plus overlays had been the scenario most likely to trigger hitching. The improvement is described as reduced lag, not a frame-rate overhaul; if your rig is below the minimum specs, dinner will still stutter. Confirm your build is 24887476 or later in the Steam beta tab if needed.
Multiplayer pain points addressed
Co-op lobbies received targeted fixes:
- Lobby stability was improved for sessions with six players. Join-drop cycles that had been causing rubber-banding or ghost sessions should be less frequent.
- Motto synchronization received another pass. Patch 1.005 had already fixed motto text for joiners; 1.007 continues that work and widens the fix to include active session transitions.
- Item placement for joining players was revisited. Items that appeared inside shelves or stacked in the center for late joiners should now sit in their correct slots.
- Host migration resilience was improved for sessions that need to recover after a brief host disconnect.
Bug fixes with kitchen consequences
- A rare case where station upgrades could revert after a reload was patched.
- Camera controls occasionally broke when the restaurant grew very large; that is now stable.
- The order tablet should no longer clip through the counter in tight kitchen layouts.
- Night-mode lighting no longer flickers during certain calendar weather events.
Known issues still in progress
These were listed as known at the time of the 23 August post:
- Quest-reward freeze (a few-second UI pause when claiming certain quest rewards) is still being worked.
- Transparent outdoor ground persists on some configurations; Windows and Deck/Linux reports both exist.
- Unusually slow customer flow for some owners continues to be investigated.
If you are on a pre-1.007 build and lost data to a save bug, verify files and update first. Then check whether the specific unlocks or cash were affected. If the save integrity fix did not fully resolve a regression you experienced, use the in-game feedback form with the version and date attached.
How to play after 1.007
Verify files in Steam, confirm you see build 24887476 or later, and run a normal dinner. The save fix alone is worth a restart if you had been avoiding reloads. After dinner, apply one upgrade from kitchen upgrades and check the first-shift checklist. Hardware doubts: system requirements. Streamers: Twitch and Kick. Store and studio: Links Hub. Review context: Review Hub.
This wiki will not invent a 1.008 until Steam does. When the next numbered post lands, it gets a sibling page or a dated subsection here. Until then, treat 1.007 as the second post-launch verb change: saves, multiplayer, and dinner lag.
Frequently Asked Questions
Quick answers drawn from the kitchen loop, co-op lobbies, and economy systems.
When did patch 1.007 ship?
Steam news dated it 23 August 2026, four days after the 19 August Windows launch. Confirm the live build in your Steam library details.
Did 1.007 fix the save reset bug?
It addressed save data integrity with stricter write and read checks. Future saves should be more stable. Prior corrupted saves are not automatically recovered, but going forward reloads should hold correctly.
Should I verify files after 1.007?
Yes, especially if you experienced money resets or lost upgrades after reloading. Update, verify files, then run one dinner to confirm stability.