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.
No Kings Left has no client to download. Everything the game needs arrives in a browser tab. This post explains what is in that tab, what is not, and the budget the whole thing is built around.
What draws the world
The 3D world is drawn with three.js, a JavaScript 3D library, on top of WebGL 2. WebGL is the browser’s interface to your graphics card, and version 2 is supported by every current desktop browser: Chrome, Edge, Firefox and Safari.
There is a newer interface, WebGPU. The game does not use it for its first version. WebGL 2 is the path that runs everywhere today and the one the game’s test code was written for. That choice can be revisited once the game is in players’ hands.
The game itself is written in TypeScript, and the interface that sits over the 3D view, the skill bar and the inventory, is ordinary web technology.
The budget: an ordinary laptop
The frame-rate target is 60 frames per second on a mid-range laptop with built-in graphics, at 1080p, and never under 30 with fifty characters on screen.
That one line decides more about the game than any design document:
- The art style. Characters and props are built from smooth, simple, hand-painted shapes and shown in daylight. That is a look, and it is also a budget. Simple shapes and painted textures are cheap to draw.
- The shape of the world. Towns and short instanced dungeons load fast and keep the number of things on screen under control.
- The camera. A camera that looks down on your character shows a known, limited piece of the world at a time.
A gaming PC will run the game well. But the gaming PC is not the baseline. The laptop is.
Who decides what
In an online game the most important technical question is who you trust. In No Kings Left the answer is: the server, for everything valuable. Damage, loot, experience, upgrades and trades are decided on the server. The browser shows the world and sends what the player wants to do.
Movement is the one thing that has to feel instant, and click-to-move helps here. When you click the ground, the browser sends the destination and starts walking at once. The server runs the same path-finding code and checks the result. Because the client and the server share that code, written in the same language, they agree on where you can walk.
A server that starts inside the tab
Multiplayer is one of the later steps on the roadmap, but the game is not being built as a single-player game that will be converted later. That conversion is how online games get rewritten.
Instead the game is a client and a server from the first day, and until the multiplayer phase the server runs inside the browser tab. Combat, dungeons and loot can be built and tested without running any machines. When multiplayer arrives, the same server code moves out of the tab and onto a real server, with accounts and a database behind it.
What can go wrong in a browser
A browser is a less controlled place than an installed game, and the plan accounts for it:
- No WebGL 2, or a graphics chip that is too weak. The game says so clearly before it loads anything large.
- The graphics context is lost, which happens when a driver resets or a laptop wakes from sleep. The game rebuilds its renderer from what it has already loaded. It does not leave you with a blank page.
- Slow connections. The plan is to develop with artificial network delay switched on, so the game is tuned for a real connection and not for the developer’s own machine.
What this means for you
You need a desktop or laptop, a current browser, a mouse and a keyboard. You do not need a download, a launcher or a plug-in, and when the game is updated you get the new version the next time you open the tab.
The page on playing in the browser has the short version, and What makes a browser game a real MMORPG covers what the game is and is not.

