Balatro’s solo dev got real about dropping out — and yes, 1.1 is still being made

Why this anniversary post actually matters

This caught my attention because anniversary posts are usually a thank-you tweet and a coupon code – not a candid life story that doubles as a status update for a major patch. On Balatro’s second birthday, solo developer LocalThunk published a blog post (titled “Bad Grades”) that does both: it humanizes the brain behind one of the last few years’ most talked-about indie roguelikes and quietly reassures players that the long-promised 1.1 update is still actively being built.

• LocalThunk opens up about leaving an engineering degree for computer science and learning by doing.
• Balatro’s free 1.1 “major gameplay” update is still in development, but there’s no release date yet.
• Since launch the dev shipped a mobile port and iterative balance work, and intentionally delayed 1.1 to avoid crunch.
• The post doubles as a transparency move: honesty about the process softens the sting of long waits.

Breaking down the anniversary post

Across reporting from PC Gamer, GamesRadar+ and Steam News, the core of the post is consistent: LocalThunk walks readers through his early programming experiments – command-line projects, a perlin-noise terrain generator, and a multi-year prototype that never shipped – then ties that history to why he made Balatro. He admits he wasn’t a standout student, switched majors, and kept building small, selfish projects outside class. Those exercises, he says, were the template that became Balatro.

It’s the kind of vulnerability indie developers rarely put front and center: the grades, the uncertainty, the long nights when making a thing felt like the only real option. PC Gamer quotes him saying he can’t imagine what advice he’d give his past self to prepare for “the insanity” that followed Balatro’s runaway success — which is refreshingly honest compared with the usual glow of PR-safe origin stories.

What 1.1 looks like (and when?)

If you only care about the patch: it exists and work is ongoing, but there’s no release date. GamesRadar+ and Steam News both relay the same status-check positioned at the end of the blog post — a terse, effective postscript: “Yes, I’m still working on 1.1.” That’s small, but meaningful. The update was pushed from 2025 into 2026 explicitly to avoid returning to the crunch that characterised Balatro’s initial development, and LocalThunk has reiterated a “it’s done when it’s done” approach.

Between launch and this anniversary LocalThunk shipped a mobile port and performed balance patching, which suggests the developer is prioritising accessible, iterative improvements over a rushed feature dump. Steam’s official channels have echoed the same lack of a fixed timetable — transparency without a promise — which is about as responsible as you can get when one person is juggling code, art, and community expectations.

The solo-dev balancing act

Here’s what matters beyond sentimentality: Balatro’s ecosystem is powered by one person. That explains both the long waits and why candor about process matters. LocalThunk’s frankness — about staying up into the early hours drawing pixel art and writing code while sipping decaf — signals commitment, not neglect. It also frames the delay as a conscious trade-off: a polished, expanded roguelike instead of an earlier, half-baked release or a burned-out developer.

There’s also a consumer protection angle gamers should appreciate. GamesRadar+ noted the dev’s refusal to lean on microtransactions; combined with the delay to avoid crunch, those are signs this project is being shepherded with a clear set of priorities. That doesn’t make waiting fun, but it does matter.

What to expect next — and how to treat it

Don’t expect a date. Expect incremental communication and small releases (balance patches, ports, maybe merch) while 1.1 takes shape. The anniversary post reads like a reset: a reminder that the person who made Balatro is still making it, and that making it sustainably is worth more than hurry.

TL;DR

LocalThunk’s anniversary blog is a rare blend of personal origin story and developer status update. It reassures players that the promised 1.1 update is alive, highlights the costs of solo development, and explains why patience — while galling — is the sensible ask here. For now, keep an eye on official channels for progress, but take the post at face value: the dev is working, slowly but deliberately.