PEAK arrived on consoles on 22 October 2026, and the announcement that carried it also carried three numbers now being quoted interchangeably. The build is 3.0.0, whose patch notes are a section of that same post, followed on 23 October by 3.0.1, a hotfix one sentence long. The third, 208, is not a version at all: it is the count of island maps Team PEAK moved into assetBundle files in that build, and the count of maps the studio says will now cycle permanently.
That distinction matters for a group deciding whether to come back this week: the map change and the crossplay change are separate pieces of work with separate consequences, and only one was still being patched a day later. This piece reads the official posts rather than the coverage of them, and states plainly what 3.0 does not contain — because the same posts say the content side of PEAK finished in August.
What this covers: the 3.0.0 and 3.0.1 builds of PEAK line by line, the 208-map rotation they introduced, the platform and price picture as printed on the stores, and the run-up patches that a returning group has missed. Why it matters: crossplay shipped without cross-save and without mod support, on a game whose studio has stated it does not plan further major updates — so this is close to the finished shape of PEAK, and the decision to return is now a decision about a fixed target. Who should care: four-player groups split across PC and console, lapsed players who stopped before the August finale, and anyone who reads “208 maps” as a promise of new content.
Three numbers, three different things
The console launch post opens with the platform news and closes with the patch notes, and the two halves are worth keeping apart.
The platform half: “PEAK is now out on consoles, which means CROSSPLAY is available for PEAK Steam players. The game has launched to PlayStation 5, Xbox Series X|S and Nintendo Switch 2.” The post carries a 15:00 UTC timestamp on 22 October, matching the 8 AM PT slot the studio had named a week earlier.
The patch half sits under its own heading, “3.0.0 Patch Notes”, and contains five bugfixes plus a short modder section. There is no new biome, no new item, no new badge in it. The content update that carried those things was v2.0.a, published 11 August under the title “THE FINAL ASCENT”, and the crossplay post refers back to it: “we also released the final content update to PEAK back in August.”
Then the maps. Under “What’s Next For PEAK?” the post says: “As for the rotation of maps, we’re adding 208 new maps to the game that will cycle through forever. This is so that you can still enjoy the replayability of PEAK even when we’re not patching every two weeks.” The modder notes at the bottom of the same post phrase it differently: “Island maps have now been moved into assetBundle files… There are 208 of them. They are not expected to be modified much, ever, except to fix case-by-case critical issues with procgen.” Both are official and they do not say quite the same thing: one describes 208 additions, the other 208 existing files relocated. The number is agreed; whether it is a net addition or an inventory is not stated.
| Build | Published | What the post says is in it | Who notices |
|---|---|---|---|
| 3.0.0 | 22 Oct 2026, 15:00 UTC | Console launch and crossplay; room-code joins across platforms; five bugfixes; island maps moved into assetBundle files (208 of them) | Everyone, on every platform |
| 3.0.1 | 23 Oct 2026 | “Room codes for joining games in other regions should now be fixed” — the whole note | Groups whose friends sit in another Steam region |
| 2.6.b | 6 Oct 2026 | Late-join cleanup: a fix for a t-posing skeleton on load, late joins for players “with slow computers or bad connections”, and a badge fix for revives in the Gloom or the Citadel | Anyone joining a run in progress |
| 2.6.a | 2 Oct 2026 | Map pool “replaced with islands that are properly randomized”, plus a run of save and reconnect fixes | Groups that continue a run from a campfire save |
What the 3.0.0 notes actually fix
The five bugfixes are short enough to quote, and each maps to something a co-op group will feel:
- “Walking into a crouching scout will once again allow you to climb onto their shoulders” — the boost that lets a two-player stack reach a ledge, restored after a regression.
- “Scouts can no longer climb on invisible trees in the Mesa” — an exploit closed, not a feature added.
- “Dead scouts should no longer find themselves warped into space when revived by the Scout’s Honour” — a revive-path defect; the Scout’s Honour is named in the note but not described.
- “Removed the bookworm badge cheat. You will now need to earn the bookworm badge normal style!!”
- “Hopefully fixed an issue that would sometimes cause the Kiln’s campfire to be deleted when a new game starts” — the campfire is the save point, and the studio’s own wording stops at “hopefully”.
That is the entire functional content of 3.0.0; the rest is platform work and a map file restructure.
The hotfix a day later is narrower still, and it reads like a launch-day lesson: cross-region room codes were broken on arrival. The 3.0.1 post is one line — “HOTFIX PATCH! Room codes for joining games in other regions should now be fixed” — and worth knowing if your group tried crossplay the evening it landed and could not get in. The hedge in “should now be fixed” is the studio’s; this piece keeps it.
The 208 maps, and how the rotation now works
The rotation is a daily one, and the store page states it plainly: “The game’s map rotates out every 24 hours! Try out the new layout each day, or give the same island multiple attempts in a day until you conquer it.” The 208 figure is a stock of island layouts behind that daily swap, bundled so that the rotation keeps working without a patch.
The biome layer sits on top. The August finale added “new variant biomes: GLOOM and THE CITADEL, which will cycle out with CALDERA and THE KILN”, and the notes underneath spell out the mechanism: “Added GLOOM and THE CITADEL, randomly replacing CALDERA and THE KILN on some maps.” That post also set a schedule for the transition — “the next TWO WEEKS will exclusively feature maps containing the GLOOM and THE CITADEL. After that, like other biomes, it will be random whether the CALDERA/KILN or the GLOOM/CITADEL spawns in a daily map.”
So a returning player who last climbed in July meets a coin-flip between two biome pairs, not one fixed set. The 2 October patch also matters here, because the map pool itself was misbehaving immediately after the biome change: that post opens, “You may have noticed this last week’s maps have been weirdly consistent in terms of biome selection, with each day being either all old or all new maps. This patch will replace the current map pool with islands that are properly randomized.”
One caution. A daily rotation over 208 layouts is not 208 routes with new content in them; the modder note calls them island maps and limits future edits to fixes “to fix case-by-case critical issues with procgen”. If “208 new maps” sounded like 208 new things to find, expect variety in layout, not in mechanics.
Crossplay: what is printed on a store page, and what is not
| Platform | Where the price is printed | Price | Notes from the page |
|---|---|---|---|
| PC (Steam) | Steam appdetails, US storefront | US$7.99 | Store page lists Windows only; features include “Online, cross-platform co-op and offline single player” |
| Nintendo Switch 2 | Nintendo Store US | US$9.99 | Release date listed as 22 October 2026; tag “Cross-platform play”; page reads ”© 2026. Landfall Publishing AB and Aggro Crab Games LLC.” |
| PlayStation 5 | Not confirmed on a store page I could load | — | Launch named in the 22 October post; a physical edition with Skybound was announced on 15 October |
| Xbox Series X|S | Not confirmed on a store page I could load | — | Launch named in the 22 October post |
Two things follow. The PC and Nintendo prices differ, so a mixed group is not paying one flat rate; and the PS5/Xbox price is the one figure here this piece will not state, because it appears in neither the launch post nor the pages that rendered for me.
The joining mechanism is the room code. The launch post: “You can join lobbies using the ROOM CODES we introduced a couple of months ago!” That is the cross-platform entry point, and it is also the thing 3.0.1 hotfixed a day later for cross-region groups. The store description still frames multiplayer as private — “Multiplayer in PEAK is friends-only - invite up to three other scouts online to climb together” — and the feature list gives the size and the voice layer: “Climb with a total of 4 friends” and “Communicate through proximity chat.” This site has looked at how a sibling co-op game handles proximity voice in the R.E.P.O. extraction and voice comms guide.
Two limits are stated outright in the launch FAQ. On progress: “There is no save progress transfer for PEAK to other platforms, you’ll just have to get those badges again, or act as a guide for your friends that are new to the game!” On mods: “Short answer is: no” — with the studio adding that client-side mods “may” work but that it “can’t guarantee that they won’t cause any issues with lobbies or games”, and asking players to strip mods before filing a bug report. If your install carries mods, that note decides who hosts; our Garry’s Mod 64-bit guide covers that problem in a different engine.
What a returning group meets in the first evening
Four practical points, in the order a group will hit them.
Update before you plan. 3.0.1 exists, and it addresses only cross-region room codes. Steam clients patch automatically; console players are on their storefront’s schedule, and the launch post describes no version check on the console side.
Decide the mod question before the lobby opens. The FAQ’s answer is a soft no, and the failure mode it describes is “issues with lobbies or games” — the kind of problem that looks like a networking fault and eats an evening.
Expect the badge ledger to restart for console friends. No transfer means a Steam veteran sits next to a friend with an empty case; the studio frames the asymmetry as a feature (“act as a guide”), and it changes the dynamic of a four-player run.
Check where your old save sits. The run from 2.5.a through 2.6.b is almost entirely save-state and reconnection repair, and 2.6.a explains why in unusual detail: “When we started integrating the changes necessary to support PEAK on consoles, we created a lot of bugs having to do with how player and world stateworld state. The shared record of everything that has happened in the game world — who owns what, what's been built or destroyed. are saved.” The same post admits a limit that survives the fixes — players who are not the original host “don’t get complete world state in their game saves like the host does”, so a run continued by a different host “will still see a little weirdness around item spawning”. Groups that rotate hosts should expect that to persist.
For anyone who stopped at the difficulty wall, the August patch changed one thing worth knowing: Ascent 7 no longer forbids reviving. The finale notes replaced “You cannot revive the dead” with “Start cursed and take more curse from revival”, reasoning that the old rule “made this Ascent less fun and was not in the spirit of the game (and its meaningless in a solo run!)”.
What is not in this patch
Three absences matter, because each is the kind of thing a patch-notes headline invites you to assume.
There is no content in 3.0.0. The biomes, the Ascent 8 addition, the ten new badges, Clown Luggage, the Jetpack, Warp Fungus and Glider, the Traditional Chinese localisation and the campfire save change all belong to v2.0.a from 11 August. A player who skipped the summer and reads “3.0” as a big number will be met by five bugfixes and a file restructure.
There is no stated plan for further updates. The launch post says the studio will “keep an eye out for any bug reports that may arise with the recent release, and slowly wrap up any loose ends on the game”, adding: “While we don’t plan any more major updates, this game won’t disappear into the void.” That is a maintenance posture, not a roadmap; any reason to wait now turns on bug-fix cadence, not content.
There is no cross-save, and no documented console parity list. Console players get the same builds per the launch post, but nothing in the sources itemises per-platform differences beyond mods. Treat any claim about feature parity beyond that as unverified.
The short answer for a group
If all four of you are on PC and none has played since the summer, 3.0.1 changes almost nothing: the value is in v2.0.a from August and the map-pool fix from 2 October. Read the finale notes and go.
If part of your group is on console, this is the first week it has been possible at all, and the two-line history — crossplay on the 22nd, cross-region room codes fixed on the 23rd — is the whole risk profile. Settle the mod question before the first climb: the studio’s answer is a no with a disclaimer rather than a hard block, and a half-working lobby costs more time than removing them.
And if you are holding out for a bigger PEAK, the studio has said where it stands: the map rotation is the last thing it added, and its stated purpose is to keep the game playable “even when we’re not patching every two weeks”.
This piece assumes the live build of 29 October 2026: 3.0.1 on Steam, with the 22 October console release on PlayStation 5, Xbox Series X|S and Nintendo Switch 2 as described in the launch post. Everything about v2.0.a is quoted from the 11 August announcement, and every price is the one printed on the store page named beside it.