It’s vacation time… so for the next couple of weeks things will slow down quite a bit. My current goal is to start having something that resembles a game… e.g. something that allows you to do a few things.

But I expect serious work on the game to commence starting with the update #9 on the 6th of August. In the meantime we enjoy paradise and regroup creative energies…

A little work still got done before vacation time started though:

Settlements are a big focus in Realms of Ancardia and I want them to feel extremely detailed and vivid. Thus the first activity opportunities will focus on settlements. Since we need to test the combat system this will probably bring you into contact with local law enforcement. Which brings me to the primary focus this week:

Law enforcement generation

Realms of Ancardia already has a framework for crime and punishment. But so far I did not spent any time thinking about the makeup of local law enforcement in settlements.

This could be anything from a single old sheriff in some hurthling hamlet to a legion of undead guards led by death knight generals in a dark metropolis ruled by an undead necromancer (and lots of other setups inbetween).

I devised a complex system to determine the types of beings used in settlement watches and militia, determine their training level, morale, composition and equipment quality. All this factors in settlement sizes, dominant races, alignment and naturally government types.

As a side effect more than 50 new monster types were added (although the stats still need to be worked out).

Total size of the codebase after this week

  • 37,361 LOC in 625 files for the actual Realms of Ancardia game
  • 24,280 LOC in 408 files in my own underlying TBRLAPI framework library supporting my most recent roguelike games
  • plus extra external configuration files, images, tilemaps, audio files, etc.

The running total is available here.

State of our internal ticket system

We use YouTrack to manage ideas and bugs that pop up. The listings are by no means complete – it’s more of a “don’t eventually forget to fix this bug / add that amazing feature” pipeline that gives a little structure to our development process without turning it into a managed project 😉

  • 132 open issues in total
  • 56 closed issues in total