>Also, the flash is a limited resource that can only be
>burned X number of times before it doesn't work any more

A random animation selector (something I suggested here months ago) would not be an issue in that regard. The flash savearea is updated far more often than the animation ever would be, and the savearea will be the first to go, by a longshot.

The slight worry of messing things up with a sudden powerfail while writing a new animation is a minor issue. We don't really care if the animation gets corrupted, and we could add a checksum or crc to them for Hijack to examine before "trusting" the table of offsets at the start of each animation.

But a bigger powerfail issue is that, if the player is busy writing the animation, then it cannot update the savearea. Again, probably a non-issue, since this will be immediately at power on, before the player runs, and therefore before the player can modify the savearea buffer (Hijack might change it, but no big deal there).

So, if we added a CRC to the animation, I don't see an issue here.

Cheers