News from the build
Devlog
Notes from the development of No Kings Left: design decisions, technology and progress, written as the work happens. Also available as an RSS feed.
Building an MMO alone: the plan
An online RPG is the classic project a solo developer should not attempt. The scope, the order of work and the rules that are meant to make this one finishable.
Four classes, no tank, no healer
No Kings Left has no tank, healer or damage roles. Every class deals damage and survives on its own. Why the game drops the trinity.
Gear without rarity colours
No white, green, blue and purple items. No Kings Left has five armour tiers, full-set perks and upgrades that never destroy an item. Here is why.
How a 3D MMO runs in a browser tab
TypeScript, three.js and WebGL 2, a server that decides everything valuable, and a frame-rate budget set by an ordinary laptop. The technology behind No Kings Left.
The combo test: earning a place in the game
Timing combos are in the plan for No Kings Left, but only if they pass a test. How the decision will be made, and what the game does if they fail it.
The games that shaped No Kings Left
Drakensang Online and Cabal Online are behind many of this game's ideas. What No Kings Left takes from each, and what it leaves behind.
What makes a browser game a real MMORPG
Browser MMORPG has meant many things, from text games with timers to full 3D worlds. Here is the checklist No Kings Left is being built against.
Why dungeons are short, with no daily limits
Dungeons in No Kings Left are short, ranked by clear time and open as often as you like. The thinking behind runs that fit into an evening.
Why we are building an MMO for the browser
No download, no launcher, just a browser tab. Why No Kings Left runs where you already are, and where the game stands today.
Join the journey
Be the first to know
Development updates and the first playtest invites, straight to your inbox.

