Shared colour table, I believe?
Hmm, do you really need to go that far in space saving?
If I get a working assembler/disassembler class built from scratch I'll throw it your way and give you the rights for it.
don't bother too much with that, because:
- I would have to forward it to this guy who writes stb_image (which SFML uses to load images)
- Neither SFML not stb_image has support for animated images, so how would this be integrated to the existing API?
Besides, it's easier to manage than hundreds of images named map_2011090100500 (incremental).
A sprite sheet is rather a single image containing a grid of all animation frames.