Okay, now I am taking liberties. NEHZ’s MountainStruggle AoS is, as the name suggests, an “Aeon of Strife” type map, where two teams of up to five heroes assist waves of spawned units as they battle down lanes to destroy the opposing base. Ever since I first played it with NEHZ and the rest of the Clan WCM crowd, this take on the AoS genre captured my heart more than any other with its tight, multi-layered landscape and Soulstone system.
Most importantly, however, it has bots — so while everyone else moved on with their lives, I could keep playing alone. And the AoS genre is about controlling a single hero against the world, as they gain experience and use abilities, so technically it’s still an RPG…
Today: the inimitable MountainStruggle AoS by NEHZ
This one is going to be controversial, because this map is not a dedicated singleplayer map: it’s co-op, for up to 7 players (odd number, but who am I to complain?). However, it can be played quite happily alone, and I do, with potentially shocking regularity. Why? Because it’s procedurally generated, that’s why! Every play-through is different!
So while this does not strictly qualify for the SPRPG Diaries by being a dedicated singleplayer map, it is a map that’s stayed with me and that occupies much more of my brain than it should. I think, therefore, it deserves some attention and discussion.
Today: the endlessly varied Warcraft Rogue by Polaris0082.
It’s amazing what you can do with only global state and one-dimensional arrays, when you really put your mind to it. What was supposed to be a quick fart in the general direction of a Warcraft project has grown into something quite incredible.
Well, incredible on the technical side. The game itself is no more or no less than a streamlined version of my standard WC3 RPG formula. You may or may not want this.
When it comes to modding, I have to admit to a masochistic streak. I could use the 3rd party pre-processor to get structs and pseudo-object-orientated syntax that would make this a whole heap easier, but no, I’ve got to use the bare metal to feel alive.
So, that procedurally generated Warcraft III side project I’ve been fiddling with during lunch hour is a whole barrel of laughs. This episode’s consternation surrounds creature spawning.
We’ve been through the cellular automata algorithm before. I said some things back then that were mostly theory — things I’ve now been able to test in the wild.
So how does one take a grid of noise and turn it into a functional RPG? Well, lucky for you, I’m getting close…
I think it is perhaps poetic justice that, on replaying all my own maps years after closing the lid on each one, I experienced all the very prominent bugs other people had discovered since that I had never managed to reproduce.
Maybe I could sit on a few of them, like the one where Fallen Stones V chases you down and ruins the gauntlet sequence of This Wreckage, because that doesn’t actually break the game.
Others, like Project Y4‘s infamous bomb drop crash bug that stops people barely ten minutes into the game, definitely needed some care and attention.
Considering I’m now making a real game for real, maybe now is a good time to go back to my roots and examine what went right… and what went wrong… with my previous development efforts: my Warcraft III maps.
Today: my swansong, RDZ Industries: Project Y4
Wow, I managed to do this one without spoilers, too. Check me out.