PEAK is one of the most played games on Steam right now. It has sold close to 10 million copies since launching in June 2025. It costs eight dollars. And the feature that defines its daily experience, the rotating mountain players assume is algorithmically generated, has never used procedural generation at all.

Here is how it actually works, where the game came from, and why it matters that you know both things.

The Mountain You Climb Today Was Designed

The premise of PEAK is simple. You and up to three friends try to reach the summit of a mountain. If you fall, you reset from the last checkpoint. The mountain changes daily.

That last part is what players almost universally assume means procedural generation. A new mountain every day sounds like a live service roguelike with a seed refresh. That is not what is happening.

Aggro Crab's Nick Kaman explained the actual process at GDC 2026. The developers cannot generate maps at runtime the way a traditional roguelike would. The engine constraints do not allow it. So instead, the team hand-builds maps in Unity Editor, 14 at a time, and ships them to players as a game patch every two weeks. The "daily rotation" is a content patch delivered on a predictable schedule.

This is worth sitting with for a moment. Every mountain you have climbed in PEAK was designed by a person. The layout of the rocks, the placement of the hazards, the angle of the final ridge before the summit, these were decisions someone made. The experience feels generative and fresh because the maps are genuinely new, but the freshness comes from craft, not code.

Kaman mentioned that early attempts to build smart procedural generation produced mountains that felt wrong, lacking the kind of difficulty curve and visual clarity that comes from intentional design. The naive approach of just building maps by hand and shipping them as patches ended up being more fun and more reliable. So they kept doing it.