...once more, with feeling...

Just released 1.1.1; should correct a couple of nasty crash bugs in 1.1. Need to be more careful, need to test more. This kind of stuff is unacceptable.

MageGuild 1.1 out the door

And it is done, MG 1.1 has been turned loose. Got a flood of last minute bugs in, fixed them, and got it turned around.

Two New Tidbits

Two new bits of information to share...

The first, I've released the code for the display library that MG uses, after renaming it Phasma. If you're developing some sort of tile-based (be it ascii or bitmap) game in C#, it might be worth a look.

The second...The code that will become MageGuild 1.1 is caught up. All of the ugly little bugs  that were reported about 1.0 have been caught and squashed, and I've gotten in a little bit of tweaking for balance and so forth. Added a few new things as well. The question becomes...how long do I wait before chunking it out? I'd like to give people more time to play with 1.0 before I go throwing a new version at them. Partly because I don't want to push people to constantly download new versions of things, and partly because I want more time to let the bugs sift to the top.

This really brings up a bigger issue...in a stable game, how often does one release patches and fixes? More to the point, regardless of the general process, how often do I want to release patches and fixes?