Kingsway

Every few years, a solo developer ships something that makes the rest of the industry look unimaginative. In 2017, that developer was Andrew Morrish — previously of Super Puzzle Platformer — and the game was Kingsway, a roguelike fantasy RPG that runs entirely inside a fake operating system pulled straight from 1995.

To be precise about what that means, because the premise is easy to undersell: Kingsway is not a game with a retro skin. The OS is the game. The quest log is an email client. The inventory is a file directory players drag loot into. An ogre ambush is a popup window — and when three ogres attack at once, that’s three popups, each with its own attack timer, each demanding clicks, drags, and triage while a trap window slides across the screen and the health bar sits buried under the map. The skeuomorphism isn’t decoration; it’s the entire mechanical substrate. Mastering Kingsway means mastering the desktop layout, and that’s a design idea that hasn’t been executed anywhere else.

The market received it accordingly: an 80 on Metacritic. Years later, it occupies a strange and enviable position: a cult classic that nobody has meaningfully imitated. That’s usually a sign the idea was harder to pull off than it looks.

• The Fake OS Interface: Combat, quests, inventory, and navigation all live in draggable, resizable windows on a Windows-95-alike desktop. Popups are enemies. Emails are quests. Files are loot. Window arrangement is, functionally, a character build’s second half.
• Roguelike Structure with Permadeath: Each run generates a fresh kingdom of monsters, bandits, crypts, and fellow travelers. Death wipes the run. Multiple classes with distinct abilities keep restarts from feeling identical.
• Open-Ended Morality: Players can escort strangers, grind quest rewards, spelunk for treasure, or simply rob and murder their way across the map. The game doesn’t editorialize; it just tracks the consequences.
• Time-Pressure Clicking Layered on Turn-Based Combat: Fights are nominally turn-based, but attack timers, dodgeable popups, and multi-window skirmishes inject real-time dexterity into what would otherwise be a menu game.

The Loop

A run in Kingsway follows familiar roguelike contours: pick a class, traverse a procedurally generated overworld node by node, fight what attacks, loot what doesn’t, and grow strong enough to survive the endgame — or, more likely, die to a bad string of encounters somewhere in the mid-game. On paper, it’s unremarkable. Structurally, it borrows from a hundred other permadeath RPGs.

The interface is what transforms it, and the transformation is deeper than novelty. Consider what happens in a difficult fight. An enemy window opens with an attack timer counting down. The player can attack back, use an item — which means opening the inventory window, finding the potion file, and dragging it onto the character — or attempt to physically dodge by clicking away the incoming attack popup before it lands. Add a second enemy. Add a trap window that drifts across the screen and must be caught and closed. The screen becomes a small crisis of overlapping rectangles, and survival depends on decisions made ten minutes earlier about where the health display lives and whether potions are one click away or three.

This is the insight that makes Kingsway’s premise work as design rather than gimmick: interface friction, the thing every other game tries to eliminate, is the difficulty curve. Veterans don’t just build better characters; they build better desktops. They shrink windows, stack them deliberately, keep escape routes clear. The game rewards a kind of spatial literacy that no stat on a character sheet captures. It’s the rare game where “getting good” means something ergonomic.

Where It Frays

The honest critique is that Kingsway’s ideas run deeper than its content. Two problems are baked into the design.

First, RNG variance is punishing in a way that occasionally feels arbitrary rather than tense. Roguelikes live and die on whether a death feels earned. Kingsway’s deaths mostly do, but a run can be quietly doomed by item drought or a brutal early encounter chain, and the interface cleverness can’t disguise that the underlying RPG math is fairly thin. There’s less build depth here than in a Slay the Spire or even a mid-tier traditional roguelike.

Second, repetition sets in. The popup panic that’s electrifying early on becomes routine once the window-management meta is internalized. The game’s central tension partially dissolves — the desktop is solved, and what remains is a competent but modest RPG. The class variety and open-ended playstyles (the thievery route is fun) extend the runway, but they don’t fundamentally reset it.

Neither flaw is disqualifying. But they explain why Kingsway is a medium-length love affair rather than a lifestyle game, and buyers should calibrate accordingly.

The Onboarding Question

One more thing deserves credit: teaching this game should have been a nightmare, and it isn’t. Because the interface mimics conventions anyone over 25 has in their muscle memory — close buttons, drag-and-drop, inboxes — the tutorial burden is nearly zero. Morrish outsourced his onboarding to Microsoft circa 1995. That’s not a joke; it’s shrewd design economics for a solo developer.

The pixel-art-meets-beige-plastic aesthetic is executed with real discipline. Window chrome, system fonts, dithered wallpapers, chunky dialog boxes — the pastiche is loving and specific rather than vague “retro.” The fantasy art inside the windows is serviceable pixel work, not spectacular, but the composition of the whole screen is the actual visual product, and it lands.

Performance should be a non-issue for a game deliberately imitating software that ran on a Pentium; a 2D game of this scope is light on hardware. One legitimate design concern: at very high resolutions the faux-OS can feel small, and readability of tiny window text varies. This is a game built around clicking precise targets under time pressure, so every pixel of legibility matters.

Kingsway is Steam-only, and honestly, it couldn’t be anything else without compromise. The entire design assumes a mouse — precise cursor movement under pressure is the core verb. This is one of the few games where a controller or Steam Deck-style setup seems actively inadvisable; playable, perhaps, but players would be fighting the input layer on top of fighting the ogres, and only one of those fights is intentional. On a desktop with a real mouse, it’s exactly the machine it was built for — there’s a pleasant recursion in running a fake OS inside a real one, alt-tabbing between genuine spreadsheets and fictional goblin popups. At $9.99, the value math is comfortable.

Kingsway is what happens when a developer finds one great idea and has the discipline to build an entire game inside it rather than around it. The fake OS isn’t a frame for the roguelike — it is the roguelike, and the moment the window layout becomes a survival decision, the game clicks into a register almost nothing else occupies. Its RPG bones are thinner than its interface deserves, and the magic fades before the content technically runs out. We recommend it to the right audience: originality this complete is rare, and years on, still uncopied.