1,575
edits
Changes
no edit summary
I found myself in a situation where I was going to be on a [https://en.wikipedia.org/wiki/Local_area_network LAN] without internet access for an extended period of time along with multiple people and multiple computers. I wanted a fun, fast paced, multiplayer game for us. The catch? I didn't want anyone to have to install anything since these computers didn't belong to us. That's a pretty tall order. What I found was [http://www.quakejs.com/ QuakeJS]. [https://en.wikipedia.org/wiki/Quake_III_Arena Quake 3] was [https://github.com/id-Software/Quake-III-Arena open sourced] at the beginning of 2012 and some awesome dudes based [https://github.com/ioquake/ioq3 ioquake3] off of it. Another [https://github.com/inolen awesome dude] created QuakeJS around 2013/2014. QuakeJS allows you to play Quake 3 entirely in a browser.
The [https://github.com/inolen/quakejs source code] has instructions for creating a dedicated server as well as building from source & generating assets for a content server. Unfortunately the [https://emscripten.org/ Emscripten] tool used to build the project has changed the way it operates in since 2014 and the current version of the QuakeJS source [https://github.com/inolen/quakejs/issues/44 doesn't build] with modern versions of Emscripten. I've found Luckily Inolen provided the precompile .js files for those of us just wanting to run a server. Between those .js files, the QuakeJS README, some work-arounds[https://github. Some com/inolen/quakejs/issues/19 helpful discussion ] on how to setup a local webpage to connect to the server (as well as providing the content necessary to play) can be found [https://github.com/inolen/quakejs/issues/19 here]and a bit of tinkering, I've been successful in creating a server environment that I'm happy with.
The theory is pretty simple
#Download everything we might need from the content server http://content.quakejs.com and rehost it locally
#Download the source code (and referenced CSS & JS files) from http://www.quakejs.com/play, modify them for local use, and rehost them locally
#Setup Debian to launch our server on boot
#Frag