Hippo manual

I have a problem.

I wrote this thing, called Hippo, that is an environment for writing games (mostly RPGs, strategy, and puzzle games; the kinds I like).

It's getting really complex, with lots of clever features and idioms.

It was at one time half-documented, but it's grown so much since then that it's now about one-quarter documented.

Ordinarily I wouldn't care, but it's getting hard for even me to remember how some of these things work. Several times today I've had to load up the code and reverse-engineer from that how to use some feature I know exists.

Under normal circumstances, this is when I'd be asking other people to help document it, but that's the problem: nobody else can document it any better than I can, and in order to show them how, I would actually have to document it.

So I'm stuck. The one good thing is that there are test cases for it that exercise most of the features, and by reading the test cases one can figure out how to use it.

Still wish I had the time and energy to write a manual though.