POTATO PLEASETHE UNOFFICIAL WIKIBuy on Steam ↗

POTATO PLEASE / FIX A PROBLEM

Potato Please patch notes: 1.0.4 and earlier fixes

What patches 1.0.4, 1.0.3 and 1.0.2 change for saves, machines and continuing after the ending.

By Potato Please Wiki · Checked · 1.0.2–1.0.4

On this page1.0.4: finished saves and recovery1.0.3: power, weather and archived shifts1.0.2: channel jams and retained potatoesWhich advice applies to my run?Sources & versionYour next reference

The latest official announcement found in our 11 November check is patch 1.0.4, posted 8 November. It adds Continue Playing after the credits and safer save recovery. Saves written by 1.0.4 cannot be opened in older versions.

1.0.4: finished saves and recovery

The developer added a way back to the hangar after the credits. Once most of the old pile is gone, the State telephone can request another. Finished saves no longer force floor cleanup.

Automatic backups can recover a damaged save. This is recovery support, not a guarantee that every lost run can be restored. Avoid downgrading a run saved in 1.0.4.

The patch also corrects Spoon Catapult switch feedback and several loading problems. Continue after the ending → · Check save compatibility →

1.0.3: power, weather and archived shifts

The 7 November update adds a machine power panel and a separate Spoon Catapult switch. Storms interrupt main power; hand tools remain usable without electricity. Completed shifts get a separate save slot that New Game preserves.

Other fixes cover crane boundaries, Sack Gantry jams, low-frame-rate bucket physics and achievement syncing. Follow the machine checklist →

1.0.2: channel jams and retained potatoes

The 4 November hotfix addresses late-game water-channel slowdowns and changes what survives a reload: machine hoppers and the vacuum retain their potatoes, while bucket and wheelbarrow contents return to the pile.

It also retains the key potato until collection and keeps Repile in the pause menu after removing the red hold-R badge. For a remaining bug, use the game’s Troubleshooting report option.

Which advice applies to my run?

  1. Check your installed version. These notes describe changes, not proof that your installation already includes them.
  2. Match the symptom to the patch. Start with power for stopped machines and version compatibility for reload problems.
  3. Keep the report specific. Include your build, when the problem began and what you did before it happened.

Sources & version

S03 — Patch 1.0.4 · 8 Nov · S04 — Hotfix 1.0.3 · 7 Nov · S05 — Hotfix 1.0.2 · 4 Nov.

Checked 11 November 2026 against developer documentation, not hands-on game testing. Advice describes the cited version. Editorial policy →

Your next reference