sickcodes / doom-wasm

Chocolate Doom WebAssembly port with WebSockets support

Wasm Doom

This is a Chocolate Doom WebAssembly port with WebSockets support.

Requirements

You need to install Emscripten and a few other tools first:

brew install emscripten
brew install automake
brew install sdl2 sdl2_mixer sdl2_net

Linux users will need to install emscripten and then add emscripten to your PATH export PATH=$PATH:/usr/lib/emscripten

Compiling

There are two scripts to facilitate compiling Wasm Doom:

./scripts/clean.sh
./scripts/build.sh

Running

Copy the shareware version of doom1.wad to ./src (make sure it has the name doom1.wad)

Then start a web server in src directory using python:

cd src
python -m SimpleHTTPServer

or using PHP

cd src
php -e -S "localhost:8000"

Then open your browser and point it to http://0.0.0.0:8000/

Doom should start (local mode, no network). Check doom-workers if you want to run multiplayer locally.

Inspect src/index.html for startup details.

Check our live multiplayer demo and blog post.

stdout procotol

To show important messages coming from the game while it's running we send the following formatted stdout messages, which can be parsed in the web page running the wasm:

doom: 1, failed to connect to websockets server
doom: 2, connected to %s
doom: 3, we're out of client addresses
doom: 4, ws error(eventType=%d, userData=%d)
doom: 5, ws close(eventType=%d, wasClean=%d, code=%d, reason=%s, userData=%d)
doom: 6, failed to send ws packet, reconnecting
doom: 7, failed to connect to %s
doom: 8, uid is %d
doom: 9, disconnected from server
doom: 10, game started
doom: 11, entering fullscreen
doom: 12, client '%s' timed out and disconnected

License

Chocolate Doom and this port are distributed under the GNU GPL. See the COPYING file for more information.