This is a game made for the gamejam over at http://2016.js13kgames.com. Compressed in the zip file, the whole thing comes in at just under 13 kilobytes of data! The game is also hosted here at Github.
It was built primarily in CoffeeScript, using WebGL and WebAudio in the browser and node.js for development.
There is a minimal node server in the package whose job is to build the project. When run, you can navigate to the root of localhost:8081, where you'll find the game running in a debuggable state, while the packed and minified html and zip files have been refreshed on disk. You'll also see a report in the terminal listing the current HTML and ZIP sizes. My process was to have Atom open, with auto saved enabled. I'd make edits, switch to the browser and refresh, grin smugly, then worry about the inexorably upwards ticking package size number in the corner of the screen. #jamLyfe
Number one surprising dev thing? 13k is a LOT of room. Most the code was written imperatively with the assumption that I'd quickly run out of space. Hundreds of lines of code later, I have global state variables called just... 't'. Welcome to a special edition of what-have-I-done-hell.
WebGL is basically a dream to work with: pretty much everything worked as I'd imagine it would right out of the box. Performance is still variable, but given the stability of the ES2 standard, the browser meisters can work behind the scenes to keep improving that while us devs get to work making content. Graphics for this game were largely generated in pixel shaders, using what amounts to layers of plotting functions.
WebAudio, on the other hand, is still an unpredictable, nightmarish mess. Case in point? Back here in September of 2016, In Firefox you can't fade gain to 0... because 0 isn't a positive number. Uh huh. Sigh It's doubly sad because there's so much potential here: the standard even as it stands can already be used to build super interesting audio experiments and synths. It's just completely unreliable.
If you're lucky, Chrome will still playback the sound in this game the way I authored it back in Chrome v52. Whether it'll continue to work in the future is seriously anybody's guess. If it sounds like a cat being strangled by a tardis, then hit M in digust to disable sound all together. I'll see about making a soundless build with all audio code entirely disabled, to futureproof the project.
Otherwise though, this was a TON of fun, and I'd recommend the jam to anyone who's into game development. Here's to JS13k 2017!
Hilarious irony note: the promo gif above is 7 Mb , over 500 times the size of the game! ¯\_(ツ)_/¯