"Come on, 100 posts and no TCOD binary ? And it's not vapourware ?"
( just an allusion to one of my favorite roguelike developers :D )
Nothing really hot here, but I couldn't resist writing the post #100. To refer to another roguelike legend, I'm not going to step in the room, guns blazing. No need to duck.
Indeed, I started dusting the old TCOD code. After a few months on the brand new clean Arena, it takes courage to get back to that old bag with his geological layers of code stacked the ones on the others... I even forgot that TCOD time code was completely based on frames. I have a lot of work to bring it to the level of the Arena where I can tweak the game speed with a single float parameter... Anyway, cleaning things here and there is a good way to slowly get back to the real work. I even already backported a few things from Arena, like the red flashing effect when you're hit and the player's conditions panel. If the Arena and libtcod don't take me too much time, you may here from TCOD soon (not for a release, but at least for new features).
Concerning libtcod, it seems that the BSP toolkit is going to win. I may also add a default parser listener in the parser module. For basic config files, it would save yourself from writing it and you could simply read properties with a basic getProperty( name ) function. For more advanced configuration files, writing your own listener is still the most flexible solution. There are also a lot of feedback on the various artefacts in the Fov toolkit. I won't get out of it, I'll have to add a more robust algorithm. Maybe in the 1.4 too.
Finally, I started fixing a few bugs on the Arena. There are still some missing features like the armor and tiresome bugs like the sleeping AI, but I'll treat this more in a coffee break fashion, getting back to Arena from time to time when I'm bored with TCOD or libtcod.
