Hello and welcome to Unity of Command 2 Development Diaries!
We’ll be posting a brand new Development Diary #19 shortly, here on Steam’s announcement section, but here’s a short recap in case you missed any of the previous entries.
While it’s true that Unity of Command 2 hasn’t been properly announced it’s no secret that we’ve been working on the game and, in fact, have been at it for quite some time.
The sequel is on its way, we confirmed that much in this Anniversary post in the Blogs section on Unity of Command web quite some time ago.
The very first Development Diary (‘No More Wipeouts!') was published just a couple of months later and can give you an idea of what to expect from the upgraded mechanics, while the second diary entry (Objectives) weights the pros and cons of timed objectives in the game (spoiler alert: it looks like we’re keeping those).
Excellent reads, both of those, but Tom, our Project Lead on UoC2, has set a high standard for himself and decided to start from scratch. “I’m restarting the dev diary series” announced Tom and then proceeded to explain the envisioned changes to the losses management system in both a scenario and a campaign. The third diary entry (Are You Experienced?) also hints at tweaks to the familiar veterancy levels and mentions upgrades between scenarios for the very first time!
A brand new feature, headquarters, was announced and explained in Report to HQ, ASAP!, while The Supply Network and Move it, Soldier! shed some light on the refining process of the defining mechanics in Unity of Command; planned changes to supply logistics, fighting and maneuvering are detailed in Dev Diaries 5 to 7.
Campaign drops the bomb with the first ever Art Preview, but the excitement doesn’t stop there as Tom announces the switch to a brand new in-house 3D engine built on Python while staying recognizably Unity of Command. Developer Diary 9 (Map Making) takes the next logical step and explains the process of map building, apparently a tedious task with a very limited room for automation. We use the word ‘shader’ for the very first time, marking a new chapter in the development of Development Diaries.
Performance diary answers the age-old question - will this game run on my age-old PC? - with a resounding ‘probably yes!’ but please don’t tell that to anyone just yet as we’re still tweaking things in hopes of making the game look even better and running on lower spec hardware. Oh, and if you read the comments section in Dev Diary 10, there’s also a brief mention of planned additional content for the game which is a politically correct way of saying yes, there will be DLCs!
A rather novel game development technique was introduced last year in the Summer of Systems: the team decided to ditch any low-level system that wasn’t implemented by the end of August. Good news: team crunched and ended up implementing most of the planned systems. Steam release is casually confirmed.
An open invitation to modders was sent out in So over with Under-The-Hood, a Dev Diary 13 that also publishes a new screenshot, describing an interesting problem: the units were drowning in the terrain, which is kind of a point of military uniforms, but apparently not really good for gameplay. The solution? You’ll have to read to blog, unfortunately.
Alternatively, you could start browsing through Dev Diaries 14 -17 that namely discuss new features like The Fog of War, Intel system or the weather modifiers, but truth be told are just excuses for the team to show off a bunch of new visuals: while the subtleties of screen space ambient occlusion are hard to notice, the Unity of Command 2 is starting to look just plain gorgeous! Case in point - this Trick or Treat screenshot.
TL; DR
Not bad for a game that hasn’t even been properly announced, eh? If you read between the lines, we’ve spilled the beans on pretty much all major improvements to gameplay, explained the reasoning behind new features and even gave a hint to the release date - check out the brand new Dev Diary #19.
The work continues!