It’s the most productive time of the year! That means it’s time to tackle those big problems that put the fear into you at in any other season. But with a couple weeks of holiday? Oh yes.
Over the weeks leading up to crimbo, I was dancing around, adding little new features and refining systems. I put decorations into the bunkers, added vending machines and guard posts, deleted the crap code that was failing to do these things before — the level generator is, dare I say it, looking pretty damn good.
The next step, then, is to take this mishmash of content and make it… into a campaign.
Yep, that’s four years since I started work on this game — it still has no name (that’s a lie, it almost has a name), but it is still blisteringly consistent with the original vision. So assuming that my constant ramblings haven’t been too coherent over the years, here’s a video so you can acquaint yourself with what it’s actually like. Also includes audio commentary if you just want to hear my dulcet tones for a bit!
Like, comment and subscribe?
Oh yes, it’s the most productive time of the year!
Well, maybe last year I got ahead of myself. The 36-feature plan I gave myself three weeks of holiday to complete in the end took more than six months (bar one remaining feature, the Towers of Hanoi puzzle, for which I have some lovely ideas). Plans, it seems, are not really my strength.
What, then, shall this festive period hold for my still-unnamed magnum opus?
Oh, that thing where you just get out of the way of writing regularly, and then it gets harder to go back to it the longer the hiatus lasts.
I might have decided to replay Dragon Age: Origins and its expansion pack and then moved on to Divinity: Original Sin: Enhanced Edition, which amounted to… well, rather a lot of time not spent working on my own game, I’ll tell you that. I didn’t have much of note to say about either, so I just didn’t say anything.
Now, though, after that holiday, it’s finally time to tackle a problem that’s been lurking at the heart of my engine for a long time now: its use of animations.
This might be the sixth time I’ve reworked my level generator. It’s incredibly complex and every time I think I’ve got it right… Well, after each rework, everything goes smoothly until I start to layer on another system — then suddenly the architecture can’t hold anymore and it’s causing more pain than gain.
Other times, yes, I’ve just been too clever for my own good and tripped over my own shoelaces. Is this one of those times? Erm, possibly…
The player Neutral Passive in Warcraft III is a special bonus player. As the name suggests, units owned by Neutral Passive are neither allies nor enemies to any other player; they offer their services equally to whomever happens to be nearby. As befits my tendancy to reimplement Warcraft III (to eventually allow for similarly structured RPG scenarios), I am now working on adding my own Neutral Passive characters.
Needless to say, due to many holes I’ve dug myself over the last three years of developing this game, this is not so easy. The key stumper at the moment is that clicking a neutral unit should not trigger the player to attack them. Instead, it should trigger a friendly reaction. When is an attack not an attack? When it’s a frob.
Oh, it’s been a while, hasn’t it? I set myself 36 features to build in 3 weeks at the end of last year/start of this one and I have completely failed. Ah well, no plan of battle survives contact with the enemy after all. What’s important is that there has been progress at all… right?
Recently, I’ve been focusing on non-unit level hazards: laser tripwires, spike pits…
I took a week off work to (surprise!) work on my game. Things did not go entirely to plan, as some time during some “routine” fiddling on Sunday or Monday it started crashing. Not crashing as in throwing exceptions from my own code, I mean crashing as in the entire Unity editor bombing out.
I unwound all the potential causes and dug around the internet for answers but basically came up with nothing. It’s something to do with turning colliders on and off and this getting PhysX into a tizzy underneath it all, but I’ve been turning colliders on and off for years (literally years) without a single complaint, let alone an engine-melting complaint.
I found a bug report to Unity which seems to cover it, but that fix won’t be released until June in the next major version. And what if this doesn’t fix my issue, and only affects one with a similar error message? Erk.