An overview, with examples, of actual game development I’ve been doing with very few silly jokes.
Daniel has suggested that the fine readers of our humble development blog would not be so interested in the finer points of small business accounting even though it is utterly essential to our ongoing operations. Nor, he contended, would something so removed as a personal “Clockwork Empires Reading List” actually be relevant to the nitty-gritty of development as-such. Indeed, it is not always easy coming up with something to write here as many, many needs must be somehow balanced and the same goes for this.
I suspect, somehow, that a changelog direct from out SVN would not be helpful, though it contains gems (each an individual SVN commit entry) such as:
5836 – work*
5798 – fixing stew**
5796 -Making laudanum and sulphur tonic should theoretically work (when modules are fixed)***
* It was a vague day, one supposes.
Choose wisely.
** It works now. Before, stew was a valid ingredient for itself. This is in fact Realistic but also Not Useful for the purposes of game logic.
*** This is a valid sentence, as “should theoretically work” refers to both “making laudanum” and “sulphur tonic”. The description is incorrect however, in that just the making of these things should work; the Sulphur Tonic does not actually work.****
**** It was observed in a design discussion that the Sulphur Tonic should not actually work, just that it should cause people to think that it worked. This is a valid game mechanic in Clockwork Empires. I recall also Daniel wrestling with the problem of making people not go mad when they consume human flesh if they don’t know it’s human flesh when they eat it.
See the things we have to deal with?
