TL;DR I embedded a RESTful API into the classic 1993 game DOOM, allowing the game to be queried and controlled using HTTP and JSON.
1993 was an exciting year - Sleepless in Seattle opened in theatres, Microsoft shipped Windows NT 3.1, and Whitney Houston’s ‘I Will Always Love You’ was the best selling song for 2 straight months. Oh, and a game called Doom was released!
Doom was created by a small team at ID Software. Wikipedia describes it as one of the most significant and influential titles in video game history, and growing up I loved playing it. As an adult I couldn’t put down a book called Masters of DOOM, which describes the back story of ID Software.
ID Software has a super cool practice of releasing source code for their games. For the kind of hackers who lurk on /r/gamedev, an ID Software engine is an amazing resource to learn from. And lo, in 1997, the Doom engine source code was released, causing much happiness!
I was having trouble finding a fun API to use in a talk I had to do. I had spent the normal amount of time procrastinating and stressing about having to give the talk, and wasn’t making any progress on building a compelling demo.
Late one night, out of the blue, I had the idea to create an API for Doom, now 24 years old(!), and obviously never designed to have an API. I could have some fun digging around the Doom source code and solve my API problem at the same time!
My random idea became RESTful-DOOM - a version of Doom which really does host a RESTful API! The API allows you to query and manipulate various game objects with standard HTTP requests as the game runs.
There were a few challenges:
I choose chocolate-doom as the base Doom code to build on top of. I like this project because it aims to stick as close to the original experience as possible, while making it easy to compile and run on modern systems.
chocolate-doom already uses SDL, so I added an
-apiport <port> command line arg and used
SDLNet_TCP_Open to open a TCP listen socket on startup. Servicing client connections while the game is running is a bit trickier, because the game must continue to update and render the world many times a second, without delay. We must not make any blocking network calls.
The first change I made was to edit
D_ProcessEvents (the Doom main loop), to add a call to our new API servicing method
API_RunIO. This calls
SDLNet_TCP_Accept which accepts a new client, or immediately returns NULL if there are no clients.
If we have a new client, we add its socket to a SocketSet by calling
SDLNet_TCP_AddSocket. Being part of a SocketSet allows us to use the non-blocking
SDLNet_CheckSockets every tic to determine if there is data available.
If we do have data,
API_ParseRequest attempts to parse the data as an HTTP request, using basic C string functions. I used cJSON and yuarel libraries to parse JSON and URI strings respectively.
Routing an HTTP request involves looking at the method and path, then calling the right implementation for the requested action. Below is a snippet from the
Each action implementation (for example
API_PatchPlayer) returns an
api_response_t containing a status code and JSON response body.
Putting it all together, this is what the call graph looks like when handling a request for
Building an API into a game not designed for it is actually quite easy when the game is written in straight C. There are no private fields or class hierarchies to deal with. And the extern keyword makes it easy to reference global Doom variables in our API handling code, even if it feels a bit dirty ;)
cJSON library is used to generate the JSON formatted response data from API calls.
We want the API to provide access to the current map, map objects (scenery, powerups, monsters), doors, and the player. To do these things, we must understand how the Doom engine handles them.
The current episode and map are stored as global int variables. By updating these values, then calling the existing
G_DeferedInitNew, we can trigger Doom to switch smoothly to any map and episode we like.
Map objects (mobj_t) implement both scenery items and monsters. I added an
id field which gets initialized to a unique value for each new object. This is the id used in the API for routes like
To create a new map object, we call the existing
P_SpawnMobj with a position and type. This returns us an
mobj_t* that we can update with other properties from the API request.
The local player (player_t) is stored in the first index of a global array of players. By updating fields of the player, we can control things like health and weapon used. Behind the scenes, a player is also an
A door in Doom is a line_t with a special door flag. To find all doors, we iterate through all
line_t in the map, returning all lines which are marked as a door. To open or close the door, we call the existing
EV_VerticalDoor to toggle the door state.
An API spec describes the HTTP methods, routes, and data types that the API supports. For example, it will tell you the type of data to send in a POST call to
/api/world/objects, and the type of data you should expect in response.
I wrote the API spec in RAML 1.0. It is also hosted in a public API Portal for easier reading.
So now we have an HTTP+JSON server inside Doom, interfacing with Doom objects in memory, and have written a public API specification for it. Phew!
We can now query and manipulate this 24 year old game from any REST API client - heres a video proving exactly that! Enjoy ;)