Thanks for this link to the documentation, that made the difference clear.DaleStan wrote:Please make sure you are keeping the concepts of "Container version" and "Content version" separate. I am only changing the container -- the format documented here.
Well, changing it to xyxyxy does make sense to me... if coordinates and offsets for real sprites are coded in (x/y) order it doesn't really come naturally to code x- and y-extend in (y/x) order; having other places of similar inconsistency is IMO not the best argument to keep it.Remembering that the realsprite params are xyyxxy is not the worst part of NFO.
I don't know of sprites with heights around 255 pixels. Maybe TTRS?
Apple uses since Mac OS 9 als \n as line feed.
No strong feelings, but go straight for it. It keeps things simpler, at least within this container, even though not cross-container.Also, I'm thinking about going straight for dword sizes (and word heights), rather than extended-word (and extended-byte). If anyone has any strong feelings either way, speak quickly, or I may end up just flipping a coin.