It seems like revision 35 of Clockwork Empires, Enola Brimble’s Fine Day In Which Everything Isn’t Going To Explode has been a very well-received! We’ve gotten a lot of positive feedback about it, and we appreciate it; players are appreciating fewer slowdowns, script errors, glitches, stutters, or save errors. So, clearly, we’re making progress.
Some folks are still having save game trouble, and we’re continuing to work on that as our #1 debugging priority (including the folks who don’t seem to be able to load save games at all?) – there are also some OS X speed and crash issues that we are currently debugging. However, we’re glad that people seem to be doing very much better with this latest build.
As the time until the next patch is roughly three weeks away, it looks like we will be primarily focusing the next patch on quality of life improvements – again! We’re rebalancing certain parts of the AI to try and clean up some odd behaviours with combat, social behaviours, and things not working correctly. We’re also just fixing a bunch of AI related bugs. One major quality-of-life improvement that is a new system, however, is fog-of-war, which is getting a rewrite.
Also, fog-of-war is not technically a quality-of-life system. More specifically, it improves our lives, but it makes your life moody and depressing.
Under the Influence (of Euclidean Distance Mapping)
First off, an announcement: customarily, we release new builds of CE (major ones) at the fifteenth of the month, or as close as we can get to that. This month’s build will be pushed back until next week, owing to the fact that we lost a week and a bit of development time in December due to the Fishmas Holidays; experimental builds will, of course, continue.
That said: Technical Talk Day.
Loosely speaking, this month’s patch is focused on doing spit and polish, maintenance on existing issues, and busting some bugs rather than new gameplay features (although we’ve done a bit of that). In terms of character behavior, you may have noticed that characters occasionally do things that are counter-intuitive; we are narrowing this down as development continues (Daniel has a huge and terrifying spreadsheet). We have received a number of bug reports of the following varieties:
“people wander off into the woods and die”
And, well, that’s about it, really.
Tangentially, here’s a tantalizing sneak peak at the promo illustration for this month’s update.
The solution to this is that people should calculate when they are, or are not, in the user’s colony. We previously did this with a notion of “civilization”, which computed (for each tile) the closest distance between the tile and any civilization in range. The problem is that the way this calculation was done was a) buggy (if a building was not within some radius of the square being tested, which was quite a small radius, we wouldn’t pick it up), and b) slow (using more than one square root per grid tile, which adds up on a 512×512 map.) I finally got sick and tired of this this week, and decided to look up the right way to compute distances.
{ read this article }
15 Comments