Overworld

Overworld is a weird thing — something between a simulator and an RPG that casts you as a tool supposedly capable of nearly anything, and then quietly watches you struggle to figure it out. Released in 2010, but it feels more like an experimental project from an academic workshop that someone unleashed on the world without much hope of being understood.

You play as something between a god and a world manager. You're supposed to influence the course of things — creatures, environment, events. There's no classic story or linear path. Instead, you get a space that changes based on your interventions, or rather, your interventions are supposed to have some meaning. The game assumes you know what you want to do, and I'm just some tool without a guide.

That's where the problem lies. The controls are stiff, the interface is clunky, and what exactly I'm doing with things remains genuinely unclear. Creation is sound as a concept — that's probably the most interesting part here — but playing itself feels more like fumbling with code than playing a game. If transparency and intuition were supposed to save it, well, they're not here.

Overworld didn't turn out particularly well, but it's not a failure. It's more of a quiet warning — not every interesting idea can be wrapped into something you'd actually want to play. The game maintains a certain existential appeal precisely because it's unlike anything else, but that didn't save it from being fun.

Today you'll pick it up when tinkering with incomplete tools and scraps of information the game keeps hidden isn't boring enough for you. Or when you want to remember what indie development looked like at the start of the decade, when creators still thought that overdone originality was enough on its own.