Once a Pawn a King

Introduction

The pitch for Once a Pawn a King is simple enough to say in one line: chess is broken, so gather the Black Army and build a party of chess pieces to fight your way through fractured boards. In practice, developer Clover Bite spent roughly a year in Early Access — starting August 2025 — turning that idea into something reviewers repeatedly compare to Into the Breach's tight tactical puzzles and Hades' character-driven roguelike structure. It left Early Access for a 1.0 release on 25 June 2026. This review reads the complete English sample — 46 reviews — and finds two overlapping stories: genuine, detailed praise for a design that earned real fans over its development, and a specific, consistent account of that design shipping its "finished" version in worse shape than the build that came before it.

A genuinely inventive idea, well executed

The praise from Once a Pawn a King's Early Access period is worth taking seriously on its own terms, because it's specific rather than the generic enthusiasm any well-marketed roguelike attracts. "I think its important for people to understand that more then this game is a chess rogue-like, its a chess themed rogue-like," wrote one reviewer, precisely distinguishing it from a literal chess simulator: "on a macro level it plays similar to games like Into The Breach." Another described the narrative layer directly: "Love the combination between roguelite and plain-old chess, and the Hades-style narrative just makes it all the better." Difficulty draws a specific kind of praise too — reviewers consistently describe losses as their own fault for misreading a position rather than the game cheating them, the mark of a well-tuned puzzle-tactics system: "not paying attention is costly and can and will get [you]," and "because the enemies are so predictable, every loss was 100% my own fault for not seeing the big picture." Art direction and music draw consistent credit throughout the sample, including from reviewers who are otherwise sharply critical of the 1.0 release's technical state.

What changed, and what this review can verify

Here's where the story gets more serious, and where this review wants to be precise about what's confirmed and what isn't. Steam's own news history for the game is a matter of public record: a post titled "Once a Pawn a King Joins Indie.io!" went up on 26 March 2026, confirming a change in the game's publishing arrangement roughly three months before the 1.0 launch. Separately, the single most-upvoted review in this review's entire sample — 132 votes — reproduces what it presents as a verbatim announcement from the developers' own Discord, dated 6 May 2026, reading in part: "Last month, the company under which we developed Once a Pawn a King (and which still owns the IP) let go of its workers - ourselves included." This review could not independently confirm that specific claim through press coverage, and is reporting it exactly as what it is — a quote embedded inside a player review, not a fact this review is asserting on its own authority.

What doesn't require taking anyone's word for it is the state of the 1.0 release itself, because dozens of reviewers, writing independently across several weeks after the June launch, describe the same specific problems. "Since full release too buggy to play, it was actually better in early access somehow?" asked one. Another, more detailed: "It was released in an incomplete state, thus why only two floors and an assortment of bugs." A third catalogued specific regressions: "Health/Damage overlays stay and block visuals after a piece has been captured. Paths don't show when they should, and are sometimes shown permanently after a capture... Only 2 floors. Definitely only half finished. Consistent crashes." One reviewer summarised the trajectory bluntly, comparing the launch build directly against memory of the earlier one: "It felt far more user friendly and playable before 1.0." That degree of independent, specific, and consistent agreement — about missing content and new bugs, not merely "it's still Early Access rough" — is the part of this story that doesn't depend on any single unverified claim to be taken seriously.

Technical specifics worth flagging directly

Beyond the general "buggy 1.0" complaint, several reports are specific enough to be worth naming. Ultrawide monitor support is reported as broken badly enough to block play entirely: "If you have an ultra widescreen monitor you are cooked. The game is unplayable... I can't even get past the start menu." Tutorial softlocks appear in more than one independent review. And a recurring feature request — an undo function for individual moves — reflects a real design tension in a game this punishing: losing a piece to a misread mechanic, with no way to take the move back, reads very differently in a roguelike where a single mistake can end a run.

Final Verdict

Once a Pawn a King is a hard game to score fairly, because the thing being scored has genuinely changed shape between the version that earned its warm Early Access reputation and the version currently for sale. The underlying design — chess pieces reimagined as roguelike characters, a tight tactical puzzle layer, real narrative ambition — is good enough that dozens of reviewers went out of their way to say so in detail, across nearly a year of testing. The 1.0 release that followed a publisher change, whatever exactly happened behind the scenes to produce it, is described independently and specifically by a large share of this review's sample as a step backward rather than the finish line Early Access is supposed to lead to. This review can't in good conscience score the current state of the game on the strength of what it used to be. If Once a Pawn a King gets the support its concept deserves, it could still become the game its Early Access testers believed it was becoming. On the evidence of what's actually shipping today, that's a hope rather than a recommendation.