: It's a file size issue... any resource fork can only hold up to a certain
: amount of data. I've got two very large images in there, the Prologue and
: Epilogue screens (I'm trying to find an acceptable way do ditch the
: prologue screen, since it's huge).... plus five chapter screens and about
: thirty full-color detailed terminal picts (by which I mean things with
: gradients and shading, things that aren't flat colors, and thus take up
: more data space). I'm hoping I won't have to index-color my terminal picts
: to make room for others that will be needed, although now that I think
: about it a lot of them use a limited color palette anyway and so might
: index quite well.
I'm pretty sure Rubicon has more images than Eternal, and they're all indexed (most of them, anyway). There are images that won't index very well, but most of them should do just fine. Indexing your images could easily reduce the file size to a third, so I think you should go for it.