: I'm curious how much manual effort or prep work went into building the real
: website for this? My goal is to just point a script at a directory full of
: maps and have it generate the whole page. I looked at your stuff very
: briefly and it looked like it might not be that easy to work with
: arbitrary map files, but I could definitely be missing something. Here's
: the page if you're curious what I'm doing. I plan to add more scenarios at
: some point.
Cool. I like what you've done. I've thought about doing other scenarios, but figured I'd start with the original trilogy first.
There are basically two files per scenario that I had to hand create. The first is the chapter list. (I'm now wondering if that data is in the map data somewhere… I'll have to look.) The second is each "overlays.json" This connects the checkboxes and SVG classes. Some of this is actually generated/extracted from the maps and I want to extend this to be fully automated. That would solve the friendly/hostile categorization for different levels. Some is manually copied from the AlephOne source files. Both _should_ be able to be automated, or at least the common stuff hard coded and then just the per-map dynamic stuff could be extracted for each scenario. It's on the list.
I'm using Woodpecker as a continuous build tool and you should be able to read those files to see how the site is built from the source code. I should probably document it a bit better for someone running it by hand.
I should definitely take a look at adding some additional scenarios as a next task. Where'd my additional time power-up go?
Thanks for your site link, I specifically like the level graph. How did you generate those?
