Colonize

Most colony sims lean on threat — raiders, monsters, harsh weather events engineered to test a player's crisis management. Colonize, from Slovak developer Rembrosoft, deliberately strips that out. "There are no armies, no enemies, and no warfare," the game's own description states plainly. "Your challenge is the colony itself." It's a genuinely appealing pitch, guiding a small 17th-century settlement across historically-inspired locations — Roanoke, Plymouth, Bermuda — purely through the quieter tensions of food, shelter, trade and worker wellbeing. Since exiting Early Access into a full 1.0 release on 4 February 2026, the game has settled into a Mixed 40.5% rating across 168 Steam reviews, and the story behind that score is unusually well-documented and unusually resolvable: a genuinely rough launch, a real gap in development the studio has since publicly owned, and early signs of a recovery already visible in the most recent reviews.

A distinctive premise, genuinely appreciated

Reviewers who engage with Colonize on its own terms consistently praise the specific thing it's trying to do differently. "It turned out to be a nice RTS strategy game. I like that there's no combat, it's better to focus on city-building experience," one recent review states. Another, written just days before this review, captures the appeal precisely: "A relaxing and enjoyable colony builder with a satisfying resource and settlement management loop. I especially like the peaceful focus without unnecessary combat." The production-chain and trade systems — gathering raw materials, refining them, shipping goods back to England for resources the colony lacks — draw specific praise for feeling genuinely rewarding once a player understands how the pieces connect. "Managing the settlement and setting up the supply lines feels really rewarding once you get the hang of it," one review notes, while flagging that the surrounding interface can feel clunky along the way.

A launch undermined by severe, specific bugs

What kept Colonize from building on that promise at 1.0 wasn't a design disagreement — it was a concrete, repeatedly documented set of technical failures serious enough to end playthroughs outright. Save-game corruption is the single most repeated complaint in the sample: "saved games wont load, and it looks like it been a problem for months," one review states; another, more bluntly: "The game is fun until you can't load your save." A separate, equally serious bug involving colonist behaviour draws its own detailed complaint: "Population mechanics are just insane... citizens frozen in place which causes them death," one reviewer describes, reporting that reassigning frozen colonists and even restarting the game failed to resolve it. These aren't vague performance grumbles — they're specific, reproducible failure states that several reviewers describe as ending long, invested playthroughs entirely, the kind of bug that does lasting damage to a genre built around exactly the sunk-cost investment a broken save file destroys.

A real, developer-acknowledged gap — and a documented return

What makes Colonize worth examining more carefully than a typical buggy launch is what happened next, because it's unusually well-documented on both sides. Multiple independent reviewers describe an extended period with no meaningful updates or developer response. "Dev seemed to have abandoned this game," one review states. "ABANDONED game. Incomplete and POS developers moved on. Never buying again from this group," reads another, considerably more heated. A third, more measured: "There has been no additional content since June so I won't hold my breath." Checking the developer's own Steam news feed independently confirms the shape of that gap: a Save & Load patch shipped 11 March 2026, and then genuinely nothing followed for over three months — a silence that lines up precisely with when the sharpest "abandoned" complaints were written.

To Rembrosoft's real credit, that silence has a documented end rather than simply persisting. A 17 June 2026 post, titled plainly "We Are Returning to Colonize," addresses the gap directly rather than pretending it didn't happen: "Over the past months, we have been reading your reviews, comments, and feedback. We know that some parts of the game did not work as well as they should, and we want to improve the overall experience." The post commits to specific work — simplified design elements, a new church building, a new Boston map, and "general polish and quality-of-life improvements" — and the studio has followed through with four numbered patches (1.1.0 through 1.1.3) between 19 June and 23 July 2026. That's a genuine, verifiable pattern of a small team publicly owning a real lapse and then demonstrably following through on a stated recovery plan, which is worth crediting distinctly from simply excusing the original gap.

What the most recent reviews suggest

The clearest evidence that the return is landing with at least some of the community comes from the review timestamps themselves. Reviews written in the days immediately following this review's research — in the final week of July 2026 — read measurably calmer and more constructively critical than the March-to-June cluster, focused on specific remaining rough edges like camera zoom controls rather than the game-ending bugs and abandonment complaints that dominated the gap period. "Has some bugs but still very entertaining to play," one very recent review states, describing a genuine learning curve rather than a broken experience. That's not proof the game is now fully sound, but it's a meaningfully different tone than the reviews written mid-crisis, and worth weighing alongside the older, more severe complaints rather than instead of them.

Where this leaves a buyer

At NZ$14.75, Colonize offers a genuinely distinctive premise in a genre that rarely tries a fully peaceful approach, and the developer's public, followed-through recovery from a real and well-documented rough patch is a meaningfully positive signal about where the game is headed. The honest caution belongs to buyers weighing a purchase today: the severe save-corruption and colonist-freezing bugs that defined the game's worst period are serious enough, and recent enough, that treating them as fully resolved without further evidence would be premature. Players drawn specifically to the no-combat historical setting, and comfortable buying into a small studio's demonstrated-but-recent recovery rather than a fully settled, trouble-free product, have real reason for cautious optimism. Anyone burned before by early-access-style instability should probably wait for a few more patch cycles to confirm the recovery holds before committing.