The short answer
The short answer
The 2.6 series is mainly a reliability pass around the map pool, campfire saves, reconnects, room codes, and late joins. Patch 2.6.a randomized the island pool and fixed several save and reconnect cases; Patch 2.6.b followed with late-join and Gloom/Citadel revival fixes. The official posts do not promise that every network, inventory, or achievement report is gone, so this page labels each item as Fixed, Still possible, or Player report pending.
PEAK version timeline: 2.0.a through 2.6.b
The table keeps the official announcement date separate from the practical effect on a player. A blank content field means the post was a fix-focused patch, not that the build contained no code changes. The status column describes what the announcement supports today; it does not claim that a local installation cannot have a different bug.
Use the related-page links in the impact column when you need a procedure. The version number is the primary keyword for patch searches, while the issue labels match the questions players report after a save, reconnect, or achievement attempt.
| Version and date | New maps, biomes, items, or systems | Fixes and player impact | Official status | Related guide |
|---|---|---|---|---|
| Patch 2.6.b - 2026-10-06 | No new map or item announced. Late-join handling was tightened. | Reviving in Gloom or Citadel should award Medieval History when eligible; mid-game joins should no longer load a t-posing skeleton; assorted slow-computer and slow-connection late-join cases were tidied. | Fixed in the announcement; a new or repeat late-join report is still possible and should be reported. | multiplayer troubleshooting and achievement checks |
| Patch 2.6.a - 2026-10-02 | The map pool was replaced with properly randomized islands. | Citadel campfire saves track luggage and nearby objects better; non-host saves are more consistent; host run-based achievement progress saves at a campfire; reconnecting after Continue from a save should not spawn an alive player dead; bad room codes should no longer trap the menu in loading. | Fixed or mitigated; the official post still warns that non-host saves can show item-spawn weirdness. | save and reconnect and room codes |
| Patch 2.5.a - 2026-09-28 | No new map announced. Final-biome meshes and Kiln lava visuals were optimized. | Reconnecting alive players should stay alive; Citadel save loading should allow Medieval History; cross-region joins should leave the Loading screen; nonexistent room codes should not break menu buttons; skeleton reconnect or save loading should not instantly kill the player. | Fixed in the announcement; regional and local network reports remain possible. | multiplayer troubleshooting and save and reconnect |
| Patch 2.4.c - 2026-09-14 | No new map announced. Cooking changed because Amulets can no longer be cooked. | Bookworm progress no longer resets; Guidebook Scrolls should remain after opening; long runs should stop suddenly lagging; nonexistent rooms should not hang Loading; Aeronautics should not unlock for the wrong lobby player; Daredevil should trigger correctly. | Officially fixed; player reports need a fresh version, run, and reproduction before calling the issue open. | achievement checks and multiplayer troubleshooting |
| HOTFIX 2.4.b - 2026-09-02 | No new map, biome, item, or system announced. | Render Scales below Native and Steam Avatars positioning in the pause menu were fixed. | Fixed in the official hotfix; this is a presentation/UI fix and does not establish a map or save change. | full update timeline and game tips |
| Patch 2.04.a - 2026-09-02 | Caldera and The Kiln returned to rotation. Condors were added around Caldera; Petrifying Rocks and hot-rock bridges were added to The Kiln; room codes and richer campfire object saves arrived. | Solo Fanny Pack behavior changed; dropped host items, laggy drop-pickup deletion, voice mute feedback, and several cooking and map-generation cases were fixed. | New systems are confirmed. Cross-platform use is planned around room codes, while reports about connection or save state remain version-sensitive. | map rotation, room codes, and save and reconnect |
| Patch 2.03.a - 2026-08-27 | A new batch of maps containing Gloom and Citadel entered the daily rotation. | The pool context changed while Caldera and The Kiln were being prepared; older daily-map screenshots may describe a different pool. | Pool change confirmed; no permanent daily order is established by the post. | map rotation, Gloom guide, and Citadel guide |
| Patch 2.02.a - 2026-08-18 | No new map announced. Rope grab stamina behavior and the Jester achievement luggage count were adjusted. | The distance-based stamina cost for starting a grab was reverted, and the Clown Luggage requirement for Jester dropped from three to two. | Balance and achievement-condition changes confirmed; check the current build before using an older run record. | game tips and achievement checks |
| Patch 2.01.a - 2026-08-13 | No new map announced. Frog cooldown and related gameplay bugs were addressed; Citadel generation received a floating-obstacle fix. | Use the official post for the exact fix list and treat route, hazard, and generation behavior as version-sensitive. | Fixes confirmed; adjacent reports remain player-report pending. | Citadel guide and full update timeline |
| Patch 2.0.a - 2026-08-11 | The Final Ascent introduced Gloom, Citadel, Ascent 8, new badges, Clown Luggage, Jetpack, Warp Fungus, and Glider systems. | This content update created the route, badge, and item context later patches refined. It is the anchor version for Gloom and Citadel guides. | Content is established; exact route rotation and badge behavior still depend on later patches. | Gloom guide, Citadel guide, and map rotation |
What the updates changed for map rotation
Patch 2.03.a temporarily added a new batch of Gloom and Citadel maps while Caldera and The Kiln were being prepared. Patch 2.04.a then put Caldera and The Kiln back into the rotation with new hazards. Patch 2.6.a changed the pool again by replacing the unusually consistent old-or-new daily selection with properly randomized islands. These statements come from the official posts; they do not establish a fixed daily seed or a permanent five-biome calendar.
The map page therefore shows a dated community estimate and a clear source state. Treat the sequence as planning context, confirm the active route in the game, and use the version timeline when an old screenshot or guide conflicts with the current session. The current data card can be pending when its date is stale; that is preferable to inventing a route.
- Current route Confirm the route shown by the game after a reset or update.
- Pool change Read Patch 2.6.a when a daily sequence looks different from older records.
- Return of Caldera and The Kiln Read Patch 2.04.a before using an old Gloom-only route plan.
- Source boundary The official posts prove the pool change, not the exact route in every lobby.
How to use the status labels
Fixed means the linked official post says the named case was corrected. Still possible means the post fixed a known path but leaves a documented caveat, a different network path, or a version-sensitive state. Player report pending means a community report exists or a player sees a symptom, but the official material checked here does not confirm the same cause or a new regression.
When reporting an issue, include the exact version, host or joining role, room-code or invite path, region, save state, and what happened after one retry. A short dated reproduction is more useful than a claim that the whole service is broken. Keep private room codes, account data, and tokens out of public reports.
| Label | Meaning | What to do next |
|---|---|---|
| Fixed | The official patch explicitly names the case as fixed. | Retest on the current build and record a new report if it still reproduces. |
| Still possible | A patch reduced the known case but leaves a caveat or adjacent path. | Follow the save, reconnect, room-code, or achievement guide and keep the exact context. |
| Player report pending | Players describe the symptom, but the official source does not confirm a cause or regression. | Treat it as a report, not a diagnosis, and wait for a source-backed update. |
A five-step check after a PEAK update
A patch can be technically correct while a player still has an old save, a different host, or a different network path. Use one controlled run after updating: start from a fresh lobby when possible, note who is host, and change one condition at a time. This makes the result useful to the group and to a later support report.
Do not delete saves or disable security software as a first response. Verify the game files through Steam, remove unsupported mods before comparing, and preserve the original error text. If the issue affects a badge, use a normal run rather than a Custom Run because the badge reference says Custom Runs disable badges.
- 1. Record the build Write down the patch title, date, and whether the run was new or loaded.
- 2. Identify the role Note host, non-host, reconnecting player, and the room-code or Steam-invite path.
- 3. Check the route Open the current map page and confirm the route in-game after a reset.
- 4. Test one change Do not combine a new VPN, firewall change, mod removal, and save migration in one test.
- 5. Report precisely Keep screenshots free of account names, room codes, private chat, and credentials.
Quick answers
PEAK update timeline FAQ
What is the latest PEAK update?
Patch 2.6.b, published October 6, 2026, is the latest confirmed entry checked for this page. It addresses Gloom and Citadel revival badges, t-pose skeletons on mid-game joins, and late joins on slow computers or connections.
Did Patch 2.6.a add a new map?
It changed the map pool to use properly randomized islands. The official post describes a pool change, not a new named biome or a fixed daily sequence.
Are PEAK reconnect deaths fixed?
Patches 2.5.a and 2.6.a explicitly fix several cases where a player returned dead after reconnecting or loading a save. A different or new case can still be player-report pending.
Did Patch 2.4.c fix achievements?
It fixes Bookworm progress reset, Aeronautics attribution, and the Daredevil unlock requirement. Patch 2.6.a also fixes host run-based progress at campfires, and 2.6.b addresses a Gloom or Citadel Medieval History case.
Where should I go for a room-code or Loading problem?
Use the multiplayer troubleshooting page for symptoms, then the room-code guide for the join flow and the save and reconnect page when a save is involved.
Are player reviews official bug reports?
No. Recent Steam reviews are useful evidence of player experience and demand, but they do not prove a cause. Official Steam announcements and a reproducible report are needed to call a behavior fixed or confirmed.
Sources and limits
How to read this page
Version numbers, dates, content, and fixes on this timeline are transcribed from the linked official Steam announcements. The map estimate and player-feedback context are secondary evidence. A status label describes the evidence checked on 2026-10-07 and can change after a new patch.