Hammer of Code

After missing out on blogging monday I was really looking forward to a longer blog today. Unfortunately I can hardly see straight for some reason or another, so this won’t be terribly long.

I was really happy to notice yesterday evening that one of my fellow Thousand Parsec GSoC students gave Risk a whirl. Things didn’t quite get going for him, but he gave it a try; In retrospect I think the reason things didn’t work was because the quickstart-risk config file doesn’t really get things rolling, especially on the smaller map (as of yesterday.) Until an official release anyone wanting to try out risk should use the “testing-risk.conf” file located in modules/games/risk (from your main git folder.) Reason being, I haven’t set up the default config to launch a suitable game. At present that config will launch a game where no one gets any objects. To rectify that my testing config turns on the “random assignment” option that gives out planets in a pretty high proportion (again, because of the testing config.) I should REALLY get around to changing that quickstart config file

Other than that the week sort of kicked off to a slow start. I spent yesterday incapacited by a migraine and only got around to real work today. Today was spent tidying up, implementing little features, and a lot of bug testing. I have to say I didn’t have very high expectations for bug testing, and I haven’t been let down. While the guys on the mailing list got me set up with a lot of great tools, the one thing I am missing is something to automate client testing. It gets tedious launching a server, 2 clients, connecting with the clients, issuing a bunch of orders via mouse, and then repeating after a recompile. I know there is a text-based client and maybe that can simplify my woes. If anyone has any suggestions or anecdotes as to how they tested their rulesets, please let me know.