Added a new “autopilot” testing command that plays through the game on its own by selecting randomly from available quips (though on average preferring ones that belong to the current conversation thread). Ran the game through it a number of times.
As tests go, this is merely mediocre — it doesn’t really simulate the behavior of a real player, but it also isn’t as thoroughly systematic as automated testing sometimes can be. Still, it did expose several bugs and infelicities, so I guess it was worth doing.
Things I still need to do before official release:
- figure out why the game sometimes hangs under Filfre (what do we know about Filfre, anyway? Is it fairly reliable? I have reports of it failing consistently in one place, but I can’t reproduce this under Zoom.)
- do some profiling and streamline the performance
- get a few more human beta-testers through the thing (will look some up if no more volunteers appear on their own)
- (most vexing): figure out why sometimes, apparently randomly, I get a runtime “too many activities” error after printing the name of a fact
Grrr.
Emily Short's Interactive Storytelling 
I’m aware that it’s hanging under Filfre. I’ll try to figure out why… soon. I suspect this is an interpreter problem, not a problem with your game. If I should determine it’s the opposite, though, I’ll be in touch, of course. ;)
Fantastic — thanks!