Clockwork Empires: Development Progress

Last update: 2015 January 21

Welcome to our progress report!
The purpose of this document is to inform you about the current status and ongoing progress of the Clockwork Empires project as a whole. This involves all the work, from start to finish, that goes into completing the game. Spoiler alert: There's a lot of work involved, so this is necessarily a very high-level perspective. If you would like to follow the weekly development blog updates which discuss more specific details, check out the Gaslamp Games weblog or sign up for the mailing list.

This document itself will evolve as work on Clockwork Empires proceeds, we receive feedback, and find better ways to communicate with players. We are committed to updating the project's status on this page for each major public release, once per month, without exception.

A note on progress numbers:
It is difficult to represent how finished aspects of Clockwork Empires are with just one number for percent complete because a great deal of the work done over the course of developing a game is not visible to the player through the then-current playable version of the product. Development is front-loaded in terms of cost while payoff is back-loaded. In other words, the most progress visible to the player necessarily takes place in the final months of a project in almost all cases. As Sheng-ji Yang put it, "Technological advance is an inherently iterative process. One does not simply take sand from the beach and produce a Dataprobe." Just so with game development: a character cannot walk across the screen until there is a 3D renderer, a 3D asset importer, an animation pipeline, a game aesthetic to build assets to, a scripting engine and database structure to instantiate entities from, and so on. Only after the infrastructure is in place can anything resembling a game begin to form.

Much of the initial time of this project was spent on technological infrastructure. We're now progressing through the phase of development where we see payoff of this investment as we rapidly implement player-facing content and game mechanics. This is the exciting part!


Total Progress

Project Progress: 86%

Project Progress: 86%

Playable Progress: 56%

Playable Progress: 56%

January 2015 update notes:
This month our development goals were more about stability, usability, and cleaning up a lot of smaller features that will build toward a sense of gameplay progression for the player who runs a successful colony from early to mid-game. The December holiday season is necessarily a somewhat short work-month punctuated by all varieties of festivity and plague, so it lends itself better to completing smaller tasks than doing one big feature.

Lots of little things got done: tech fixes and optimization, new UI pieces, more control over small systems, lots of small gameplay bugs squashed, problems with jobs hashed out, re-balancing here and there, graphical polish on things we've been putting off for a while, and even some more work building up to the multiplayer back-end. So rather than continuing to list small things we improved, let's shuffle you along to the sub-sections to learn more about the details of what we got done - the UI/UX section is particularly beefy.

As ever, adventurous players should opt-in to the "experimental" build of the game using the properties>betas option in Steam. You can see the new content we're working on plus receive specific technical fixes that don't affect enough players to require hotfixing into the public build.

And here are our development blog posts from the middle of December to the middle of January (the holidays forced us to do the obligatory holiday post, and there's a vegan-themed homage to that awful TNG season 1 clip show episode with Riker; you know the one).

(You can read the previous months' update notes and blog post listing at the bottom of this page, here. There are also pictures of cute animals.)


Project Timeline

In the broadest strokes, these are the major public-facing milestones of the Clockwork Empires project:


The Engine

This is the key component that brings every part of the game together. It makes sure that mouse and keyboard input is processed, that visuals display, that the game can pull information from the correct space on-disk, that the UI renders and responds correctly to input, that a character is drawn in the right place and is told what to do from the right script. Every part of this infrastructure must be in place in some form before player-visible game content can even be implement. As Nwabudike Morgan put it, "Each interdependent piece must be materialized simultaneously and in perfect working order; otherwise the system will crash out before it ever gets off the ground."

Nowadays most games are built on engines purchased from an outside company so the developer does not have to build their game from the ground-up. Popular examples of such engines are Unity, Unreal, CryEngine, and idTech. This category is easy to underestimate compared to other projects because we've built an engine from scratch. The game engine is hugely complex and, if everything works correctly, the player will not even notice it. The intangibility of the engine needs to be emphasized because it's such a huge portion of the work done on Clockwork Empires during development but it's one of the absolute least visible components to players. In short, it's a huge deal, but you won't be able to tell unless something goes wrong. Much of the work remaining involves making sure things don't go wrong with the wide variety of hardware and operating systems out there.

MacOS Clockwork Empires is out in the wild and Linux should follow shortly.

Project Progress: 94%

Project Progress: 94%

Playable Progress: 97%

Playable Progress: 97%

Latest Updates

Improvements in engine-land at this point are pretty much always some combination of "better performance" and "better stability". We got a little of each this time around plus the bonus of a couple features that let us script better AI (& a fix which makes for subtlely better-looking particles).

We dicussed bumping the "playable progress" %-done by a percent but decided against it. Although the game is indeed more playable and players will have a better, more stable experience, it didn't feel like a significant enough change for us to bump the numbers up through that last few percent. (These numbers are never an exact science, of course, and it's really difficult to define what precisely that last few percent mean because it's likely to be fixing problems we had no idea existed.)

(By the way, the status of the Linux build can be followed on the forum post here.)

Engine bullet points:

Completed Features

Upcoming Features


Human Characters

Simulating human characters is perhaps the cornerstone of Clockwork Empires, and as such it's one of the systems we've spent the most time on. As far as what's visible to the player, it probably appears about half as sophisticated as we intend the final product, but there's a lot of solid back-end code to support much more than what's been done. Now that we have a comprehensive design for characters as well as a completed framework to build that design on, most of the work that remains involves adding new 'jobs' (a job being what our engine calls any unit of a character's physical action eg. chopping down a tree or rubbing their stomach and making hungry, unhappy sounds), new memories, a more sophisticated relationship model, and physiological responses.

Project Progress: 85%

Project Progress: 85%

Playable Progress: 71%

Playable Progress: 71%

Latest Updates

The big item for human character behaviour was the long-awaited Memory System Rewrite. To summarize: the effect of a memory will now drop off gradually with the strength of the memory decreasing over time rather than very suddenly disappearing when the memory queue pushes it out of a character's brain. This will stop erratic, sudden mood swings that occur as an artifact of memory calculation. Of course if a character experiences several strong traumatic memories in a short time period they will indeed have an extreme mood swing, but this would be a correct and narratively acceptable outcome.

We also began a giant overhaul and rebalancing of the entire job/behaviour database to hook up some some new features which allow for better scripting control and improved performance, but we've pushed most of these changes off until next month's update. (To do this more effectively we also got a new internal tool to peek into colonist's decision-making, which is fun for us.) The job system is simply too large to overhaul completely in a couple shorts weeks; as mentioned, the December-January work period is full of interruptions. But that said, a few upgrades have been done for this month which should improve performance and gameplay. Expect the more comprensive upgrade next month!

In art-land, we've cleaned up a lot of missing hair and head art and done some additional polish to characters. You should be able to see more variety in your colonists now. We've also put in mining workcrews properly, so when you assign labourers to a mine they will wear proper miner outfits.

This month, in part:

Completed Features

Upcoming Features


Scripting System

Like the game engine, the scripting system is somewhat intangible to a player but exceedingly important to development of Clockwork Empires. The scripting system allows us to use a scripting language - Lua is this case - to control game logic without messing with the underlying functionality of the game engine, such as graphical rendering, or keeping assets loaded in memory.

The scripting system is also essentially complete. Almost all of the game object definition, and the interaction of these game objects is handled through Lua. These objects interact with each other by passing messages that are scheduled by the C++ engine code. We need to do a cleanup pass to make sure that all the strings for localization are out of C++ land, and we need to clean up leftover code used for various tests, but we're very pleased with the state of things.

As far as the player is concerned, this system is effectively done. A lot more content remains to be scripted, but the infrastructure to allow this to happen is all in place and works very well. Any error that occurs here would almost certainly an issue with an individual game object's script rather than the scripting system itself.

Project Progress: 96%

Project Progress: 96%

Playable Progress: 100%

Playable Progress: 100%

Latest Updates

This month we got some small features that will let us use our character AI job system more effectively and efficiently. We'll see more payoff in the next month with the big job overhaul, though we've got some definitely improvement for rev35.

We've also introduced a framework for game object ownership, so the game knows that this Bushel of Cabbage belongs to player 1 while that Bushel of Cabbage belongs to player 2 and if the bandits come along and steal them, they'll both belong to the "bandits" faction. Both your colonists and your friend's colonists now won't wander into the woods and get shot by bandits when all they wanted was some cabbage -- well, the framework now exists to do this properly even if all the applicable use-cases (like bandits) have not been populated to script. That'll be forthcoming!

Completed Features

Upcoming Features


Combat & Military

The combat system currently works pretty solidly as a base upon which to build deeper features: soldiers will defend the colonists who call for help, colonists tasked with hunting will shoot animals with slightly alarming zeal (even peppering the already dead bodies with an extra bullet or two, depending on their traits), and everyone from bandits to fishpeople to your colonists can be wounded, take afflictions, and be killed.

Now the lovely system of military control that we painstakingly designed while the project was still quagmired in engine code is beginning to be implemented! We needed to allow for the characters themselvesto be sufficiently complex that they would be affected by military service (this is done), for the job system to allow interrupts (also done), and for additional sophistication and UI support for work crews in general (getting there). We also needed enemies to be sufficiently complex that military controls are necessary (working on it). So the characters are able to do everything needed, and the scripting of complex, interesting enemies is starting to show off what it can do (though pretty much all of the art assets are done, as mentioned in the "Non-Human Characters" section).

There's a lot yet to come, but combat isn't interesting until you have something meaningful to protect and build plus some interesting enemies to try to take it away from you. It's important to note that we are not building a generic RTS where lines of troops slaughter one another. Everything is a bit messier because your troops are all simulated humans with their own feelings about what they're doing.

Project Progress: 54%

Project Progress: 54%

Playable Progress: 37%

Playable Progress: 37%

Latest Updates

This month did not see significant work done directly on combat, though the aforementioned job overhaul slated for next month will definitely impact combat behaviour - it'll just do it next month. (Well, it affected combat this month because some of the new features being implemented conflicted with the old job balance in the experimental builds, so that required some clean-up, but it's all fixed up now!)

Some UI work affects military control: conscripted civilian workcrews auto-disable work filters and cancel civilian jobs. And hey, we added pushups! Just like the little army guys in Command & Conquer 1!

Completed Features

Upcoming Features


Non-Human Characters (Animals, Monsters, Vehicles)

All of the character (human and otherwise) in Clockwork Empires are based on very similar code with different amounts of complexity added on. Various categories of NHCs (non-human characters) have been created and integrated nto gameplay but this code, aside from the animals, hasn't been generalized sufficiently that adding new monsters and non-colonist humans is quite as trivial as it should be. This isn't difficult per se but it hasn't been the most important task yet versus our priority on getting human colonist character behaviour feeling really good, plus all the supporting UI/UX features involved in allowing the player know WHY characters are doing what they do. It is only natural that the player focus on their own colonists, so that had to be our starting place. We're getting to the point where that structure is very solidly in place so we're starting to flesh out the other beings of the world/other worlds.

The benefit of having the human characters essentially done is that every other active entity (animal, horror, vehicle) in the world is a version of human characters with simpler behaviour, so they're relatively easy to create in comparison. This process is being done gradually, in thematic groupings, as development proceeds.

Project Progress: 75%

Project Progress: 75%

Playable Progress: 42%

Playable Progress: 42%

Latest Updates

We did a bunch of work on animals this month but it does not appear in the public update - sorry! This sets us up nicely for easy future implementation though. The aforementioned jobs overhaul and the new job system features also affect and improve animal behaviour, though animals have a much simpler subset of jobs which the player doesn't directly interact with, so improvement in the next month won't be quite so visible.

In scripting-land, we've worked on some more animal jobs/behaviours and associated gameobjects. Of note, we now have a framework for animals that create burrows and hide underground, all based roughly on the Dodo nesting code. And possibly zerglings. This is really cool and we can't wait to show it off.

In art-land we've done a cleanup pass through animals and animal animations preparing the mountain of existing animal models & animations for implementation when the thematically correct biomes are in place.

Completed Features

Upcoming Features


Buildings & Building Creation

This section includes everything the player can build: workshops, machine modules, dynamics (pipes), and zones (farms, stockpiles, graveyards) as well as any game mechanics that employ these structures.

Procedural building geometry is pretty solid unless you cram a lot of modules together in funny ways or manage to find an edge case in blueprint placing rules. With this more or less working, we're focusing on improving the UI for placing buildings and modules as well as the gameplay mechanics that use constructions generally. Right now buildings are very cheap, causing players to build walls with elongated structures, and there is otherwise little sense of progression. These will be our next focus with a series of economic updates. (The last major features required for building geometry proper is support for more varied building styles including gabled roofs and more exciting decorations, but this is all visual polish, so gameplay comes first.)

The backend for workshops is essentially done, though as with everything will see refinements in every update as necessary. Workshops don't however interface much yet with higher-level economic gameplay mechanics that are not yet implemented such as dynamics (steam/water pipes, mechanical axles), and module maintenance costs (though we got the first run of this in this month!). These could also use more cool visual and sound effects and lots of UI/UX enhancements.

Housing is a bit simple right now; people will use beds, but there is currently no concept of "property ownership", so people can't have their bed, their chair, their house, and their idol of Quaggaroth. Upper class characters can't complain about not owning a gilded throne and a painting of Uncle Ambrose. On the other hand, the communists are pretty happy with how things are looking right now.

Zones (stockpiles, farms, and graveyards) are working pretty well - though there are always incremental improvements to roll in when there's time - but farms in particular will need some better high-level controls for having one workcrew work multiple fields in a rational manner. Zone removal is needed so you can move stockpiles and farms when you figure out a better arrangement for them.

Project Progress: 89%

Project Progress: 89%

Playable Progress: 88%

Playable Progress: 88%

Latest Updates

The two big features in buildings done this month are the addition of underground Mines and a concept of module maintenence. There are also lots of random fixes and improvements, as befits the month's theme of "throw random improvements into the update".

Mines are basically a workshop that allow you to construct a "Mineshaft" module. Workers go into the mineshaft, dig around, and come out some time later holding a random piece of ore. There's a lot that we plan to do to expand this system (discussed in the blog post "Mining & Maintenance"), but we're starting with a simple introduction to the system that we can upgrade with complexity in thoroughly-tested stages.

As you may guess from the title, module maintenance is also discussed in that blog post and is similarly implemented in that we're starting with a simple version of the system that complexity can be added to as we see fit.

Because of increased resource demands due to repairs and upcoming building cost increases (next month!), we've added bamboo farming.

Other than that, lots of fixes:

Completed Features

Upcoming Features


Biomes & Terrain

We currently have two biomes: "Temperate Colorado" and "Tropical Jungle". Each has unique flora and fauna, and the tropical biome is much more difficult to play due to dangerous... things.

The terrain generator is capable of much more than is currently shown to the player, both on a small and large scale, and taking advantage of these abilities would tie into overworld development.

We've also got a lot of completed assets that aren't being shown yet. As perceptive readers may recall, we have generated desert and swamp biomes, and the art exists to support these and many more. So we have most of the technical capacity to expand the biome numbers, but we want to ensure that they really play differently from one another instead of just doing quick, superficial implementation of art. And besides, this requires a more fully developed economic system for biome-unique products well as more monster & animal content for unique challenges in each area. With all that in mind, new biomes will be rolled out over time in thematically appropriate chunks with accompanying economic and animal assets as development on the game proceeds.

Project Progress: 80%

Project Progress: 80%

Playable Progress: 38%

Playable Progress: 38%

Latest Updates

This month saw just a few tweaks to nature spawn balance, especially in the tropical biome..

Completed Features

Upcoming Features

Seemingly Random Aside


Metagame / Overworld

This category includes the world map itself, the ability for a player to found a new colony in different conditions based on where they choose to settle on the world map, tracking player progress through different settlements, interaction with different factions, and having in-game events (from the "events" category) tie in to what the player sees in their colony.

This is one of the least developed systems, but also one of the simplest with the fewest unknown variables because it interacts with the core character/colony simulation only sporadically and largely at the beginning and end of a game to provide context and consequences for actions taken in the body of the game. So far in development there's little point in having a meta-game without a strong core of the colony simulation game itself, so while we had a great time designing all the systems involved for the metagame and are eager to implement them, it's not going to get done until it's the best way to improve the game experience.

Project Progress: 16%

Project Progress: 16%

Playable Progress: 16%

Playable Progress: 16%

Latest Updates

Development has been quiet on this front. The overworld will become more meaningful once other major features flesh out games systems which enable observable effects of the overworld on gameplay. It will also benefit from robust biome generation tied into the embarkation map.

Completed Features

Upcoming Features


Multiplayer

Networked simultaneous multiplayer has been planned for Clockwork Empires from the start - and such a feature must be planned from the very start for any modern game because it requires that the game engine and gameplay mechanics operate based on architecture which enables multiple instances of the game to coordinate events. It should suffice to say that this is a significant investment of time, but as any fan of multiplayer games knows, the reward is great. The underlying system architecture of Clockwork Empires has been built from the ground-up to support networking, using a deterministic lockstep architecture. Most of the required code investment is already done, and we have successfully run networking code on our internal LAN. We simply need to take the last few steps for completion, give the system a nice frosting of user-interface and usability features, then undergo testing, optimization, and "hardening" against poor connectivity and Interfering Firewalls. We also wish to have a better concept of what a multiplayer "game" of what Clockwork Empires looks like, and will write additional gameplay code to support this.

We also plan to offer support for non-simultaneous "multiplayer" games of Clockwork Empires; in these "succession" games, you play a game for a period of time then hand the save file off to a friend to play. They may hand the save file back to you, or possibly to some random person on the internet. This is fairly straightforward compared to networked multiplayer, mostly requiring game saving & loading plus ease-of-use features. It will also require some design iteration as we discover the most interesting ways to convey the concept of "succession"; this will in turn require some unique interface features.

Project Progress: 86%

Project Progress: 86%

Playable Progress: 0%

Playable Progress: 0%

Latest Updates

We have a framework for object ownership! Every object in the world knows who (if anyone) is its proper owner so that you order your own guys around and get in the appropriate trouble if you take someone elses' stuff. Plus, eager colonists should no longer attempt to take Bandit Cabbage to cook stew. There is still work to be done scripting-side for full implementation of what ownership means in every case, but the important backend pieces are in!

Completed Features

Upcoming Features


Music & Sound

This category encompasses all of the audio assets, sound and music, heard in the game. The dynamic music system mixes up to six tracks of different moods together based on events in the game; for example, during combat more martial-feeliing music will play, and if weird monsters from another dimension show up, the music will get very strange indeed.

The dynamic music system was finished shockingly early, is implemented, and works. Not all of the events that should alter the mood of the music are set up to do so, however. This will require a series of housekeeping passes to go through all relevant events in the game and paste the one line of controlling script plus appropriate variables wherever needed. It's not difficult, it just needs to be done in a lot of places as development proceeds. In terms of sound effects, we need to tweak a few sounds, flesh out some more variety in assets, implement support for ambient and cleanly looping sound effects, and replace the placeholder character vocalizations. (Right now the character's are all voiced by Matthew Steele, whose voice you may recall as the announcer from Dungeons of Dredmor, though rest assured that he sounds nothing like that in Clockwork Empires).

All in all we're very happy with the way music and sound has come together so quickly.

Project Progress: 90%

Project Progress: 90%

Playable Progress: 82%

Playable Progress: 82%

Latest Updates

Nothing especially new to report here, though I did slip another Dredmor sound into CE. Don't tell anyone.

We're sitting on a lot of sound assets but a few features need fixing up and a few systems need implementation to be able to put in cool things like ambient sounds. On the upside, we have a ton of assets here just waiting to be implemented.

Completed Features

Upcoming Features


UI/UX

UI/UX is really important and deserves its own category! In terms of project assets this category includes the art for icons, art for UI elements (every window, every button), the illustrations for events and backgrounds, and any other visual effects used to signal the player about what is going on in the game that isn't a part of the game-world itself. Behind the art, there is an xml layer which controls UI layouts -- what goes where and controls what -- as well as how the art is applied to these layouts. Behind the xml is the engine's UI rendering system to draw the art to screen according to xml as well as the code to send player commands through UI layouts into the game itself.

It should be emphasized that the current state of the UI is not set in stone and we fully intend to continually iterate UI/UX based on player feedback throughout the course of development. Again, it's really important because the UI is what stands between the player and the game; it should have a facilitating, not frustrating, effect.

Project Progress: 85%

Project Progress: 85%

Playable Progress: 73%

Playable Progress: 73%

Latest Updates

The UI got lots of love this month and it's pretty much just a long list of random little things made better with a focus on improving the ability of the player to control what they're doing. Here you go:

Completed Features

Upcoming Features


Overview Of Additional Project Work

There is a great deal of work to launching a sucessful commercial project which is not directly related to the development of the game software and art assets. Most of it is invisible to gamers, which is fine, but it is important in this circumstance to acknowledge the hard work and effort involved which is absolutely essential to the game even though it doesn't appear in the game itself. This overview will be necessarily brief and should serve only to give an idea of what has been done and remains to be done.

Completed Tasks

Current & Ongoing Tasks

Upcoming Tasks


As a reward for anyone who read this far, we present to you a picture of Daniel's kitten:

CEO kitten

For those of you who stuck with us 'til now, here is David's cat in a basket:

Godiva in a basket

You lucky people! September gives you Nicholas' TWO cats just hanging out:

Vining Cats

This month? You get Mr.Hamilton's 'pig:

Hamilton Pig

Hello Margaret Catwood!

Margaret Catwood

Here's David's other cat. No, really, this is a different cat. I can tell which is which. Usually.

Leeloo is tall

We're running out of cats, so here's Daniel's other cat! Note that this is NOT Leeloo from the previous picture, Arya is a totally different cat. You'll pick up on the subtle differences with time. (Arya's paw is shaved because she had to go to the vet.)

Arya the kitten-cat

Old Update Notes

December 2014 update notes:
This month saw a few parallel streams of development. Perhaps most important was the continuation of developing economic gameplay with the ability to order dismantling of modules, buildings, and zones. These don't feel at first glance feel like "positive" feature developments, but what they do is introduce the essential element of iteration. Now a player can build a colony, tear it down, then re-build as a better, faster, more effective colony. Alongside this we wanted to introduce some fun themed gameplay elements, so we've fleshed out the behaviour of Naturalist characters, added the Laboratory along with Scientists and Laboratory Assistants to work in them, and sprinkled the world with Strange Artifacts to discover, study for prestige, and possibly (probably) make things go Terribly Wrong with. As usual there are also a ton of small changes and improvements which will be discussed in the appropriate sections below.

Oh, and we moved into a new office in the last month! The new place is rather nice, though we're still not sure about this "sun" that keeps shining through "windows"; it's all rather alarming and if anyone can explain what's going on, please do.

As ever, adventurous players should opt-in to the "experimental" build of the game using the properties>betas option in Steam. You can see the new content we're working on plus receive specific technical fixes that don't affect enough players to require hotfixing into the public build.

Here are our development blog posts from the middle of November to the middle of December (which appear slightly fewer than usual due to how the Wednesdays line up, but hopefully the title length makes up for it):


November 2014 update notes:
So, this ended up being a weird month. Our plan was to go in and crank out a pile of economic features and UI in support thereof, but our MacOS/Linux build ended up requiring a two-week+ rewrite of the entire renderer to work with OpenGL 3.2 standards which took most core coder time away from economic feature development. That said though, there are indeed a few important features snuck in, details below. While held up on the big features required for the economy-focused work, a lot of secondary coding and implementation got done on other parts of that game which did not depend on the planned features. So this is all good stuff, just not quite the good stuff we expected this month to be about, and much of what we wanted to accomplish has had to be pushed back due to unanticipated complexity in getting the MacOS and Linux ports working.

As ever, adventurous players should opt-in to the "experimental" build of the game using the properties>betas option in Steam. You can see the new content we're working on plus receive specific technical fixes that don't affect enough players to require hotfixing into the public build.

Here are our development blog posts from the middle of October to the middle of November:


October 2014 update notes:
This month we've focused less on big showy things and more on the player experience. We've made existing gameplay smoother, fixed as many little broken things as possible, and have otherwise started putting together the infrastructure for really getting the game economy working. In this update, notably, the module construction and workshop system have received attention to set us up for further economic features. With the foundation set by this month, we will be able to implement much stronger economic gameplay in the following month (with details revealed as we implement them). Meanwhile, we've also put time into making the save/load system more stable, reduced combat micromanagement with AI improvements, and added an ammunition system to tie combat to the economy.

As ever, particularly adventurous players should opt-in to the "experimental" build of the game using the properties>betas option in Steam. You can see the new content we're working on plus receive specific technical fixes that don't affect enough players to require hotfixing into the public build.

Here are our development blog posts from the middle of September to the middle of October:


September 2014 update notes:
This is our second month in the public eye and our first on Steam as an "Early Access" title. It's an intense experience for all of here at Gaslamp to be putting the game out in the public on Steam. The feedback has proven incredibly valuable and we hope it shows in how far we've brought the game in the last four weeks. Our big features are new Cult actions, an entire new biome to play in (with new flora, fauna, crops, and cooking products), improved Fishpeople behaviour, conscription of militia soldier and better squad control, improved farming, and lots of general UI and stability fixes. All the details will be described in the categories below.

Here are our development blog posts from the middle of August to the middle of September:


August 2014 update notes:
Our first month of the public playing Clockwork Empires had generated a tremendous amount of feedback and a great deal of work has been done as a result. As expected, much of the initial technical was necessarily focused on getting the game to run at all on the huge variety in hardware and software setups that gamers own. Apart from that, the range of perspectives vastly increased which gave us a huge amount of user interface and "user experience" feedback concerning how the game is controlled and how information is presented to the player. Upon reviewing our changelogs from mid-July to mid-August, we realized that we did not include a UI/UX category on this page even though it's an essential component of Clockwork Empires. So we added a new category to track UI/UX progress! You will find it below.

More details about the month's work will be added to each section below. In the meantime, here are the development blog posts from the last month:


July 2014 update notes:
The overall status of the project is, as one would expect, quite far along. We've hit the point (as of July 2014) where the game is getting very visibly better with each update we send to testers, and the experience is becoming less about basic functionality as it is about playing the game itself. Hitting this tipping point was the most important criterion for us for any form of early access and we're at the point where people who want to participate will be able to watch the project take shape, submit bugs, help us prioritize features, suggest how to resolve design issues, and play the game largely crash-free.