These entries come from the publisher’s own Steam announcements for app 4705510, read through Valve’s news API. They are paraphrased for length, and every entry below is an official change rather than a player report.

1.99.2 — 26 September 2026

  • Changed the “At What Cost?” achievement to be more forgiving.
  • Fixed duplicate/ghost windows appearing on Windows 11.
  • Fixed the Steam overlay on Linux.
  • Fixed other minor Steam overlay issues.
  • Added a subforum for sharing levels, where players can post their creations.

1.99.1 — 23 September 2026

  • Replaced the “Publish your first level” achievement with “Complete 10 Editor Playtests”, explicitly to curb the flood of achievement-farming levels.
  • Escape now pauses the game in addition to Tab. F11 toggles fullscreen.
  • Reduced input latency.
  • Fixed the game being unable to exit correctly sometimes.
  • Fixed the game reading non-standard controllers as input devices.
  • Fixed the Autopilot achievement.
  • Fixed a startup crash on Linux when using Wayland.
  • Fixed a memory leak.
  • Minor UI fixes.

One item is worth calling out because the announcement itself admitted the mistake: a speculative Windows 11 duplicate-window fix was attempted in this patch, introduced a worse bug, and was then reverted. The developer said a proper fix would follow. It arrived in 1.99.2.

1.99 — 21 September 2026

  • Initial Steam release.

Why this matters for guides

Two of these patches changed achievement requirements, which means any achievement list written on 21 September is already partly wrong:

Achievement change Patch Effect
“Publish your first level” removed 1.99.1 Replaced by “Complete 10 Editor Playtests”
“At What Cost?” relaxed 1.99.2 Bleed-out window after finishing was previously much tighter

If a guide still tells you to publish a level to unlock the editor achievement, it was written before 23 September 2026.

Reading future patch notes

When new patches land, the reliable sequence is:

  1. Check the official Steam announcements for the game. That is where these entries come from.
  2. Check whether the patch touches achievements, because that is the change most likely to invalidate existing guides.
  3. Check whether it touches input or frame timing, because those change how specific levels feel.
  4. Re-check any page here that references the changed system — every page on this site shows the date it was last checked.

A note on the browser version

The browser version has its own separate history of changes, and it is not patched alongside the Steam build. A change listed above does not necessarily apply to the web version.