It's been awhile since I posted a dev journal. There always seems so much stuff to be done, that it's hard for me to take the time to write one. While all of us have been working on Dark Avatar, I've also been spending a lot of time on 1.3. Bug fixing can be satisfying, because it's not hard to come up with a huge list of stuff, whereas you might hours (or longer) working on a particular feature and it ends up being one or two lines in the log. However, bug fixing can also be very frustrating while you're actually tracking down the bug in question. Creating features, while it can have its own share of frustrations, is enjoyable because it is an act of creation.
In Dark Avatar, I'm currently working on the civilization code. I've already done a lot of the work to allow you to make your own custom opponents. Most of this involved moving data from following a hardcoded pattern involving the race ID to the RaceConfigXML and making the conversations/flavor text use string tags instead of the raceIDs. You'll be able to specify the AI personality, the "voice" to be used in conversations and flavor text, the Abilities Descriptions, and the robot images. I also added a tag for the leader gender, but as that will require additional work on the conversations, I don't know if it will actually be used.
Now, I have to make sure that the races are independant of the player ID so that the custom opponent using player ID 4 doesn't have to act like the Torians. I also have to make the custom star systems work for the custom opponents, and I hope to make it so that you can even create your own minor races since some of my changes will put me at least halfway there. I'll probably also have to make changes to how the starting techs are specified, since you'll need to be able to add techs for the custom opponents.
One really cool thing I worked on this week was making a special test mode where the AI takes over for the human race. It would be neat to add this as a feature so that you could test your custom opponents, but I'm worried that it may cause problems that I haven't thought of yet, so I haven't committed these changes to our code server.