A sprite sheet maker can produce a perfectly valid larger PNG while an existing animation starts showing the wrong poses. Before adding more art, write down which identity your game promises to preserve: a named frame, an ordinal in a sequence, or a physical cell. Those are different migration contracts.
Disclosure: This article was generated with AI for the FrameSprite team, which has a commercial interest in the linked website. Examples are constructed production exercises, not measured model performance or customer results.
Put the compatibility decision in the change request
Consider a hypothetical sheet with five columns. A named pose occupies column three, row two, using zero-based coordinates. Its row-major index is 2 × 5 + 3 = 13. Extend the same physical layout to seven columns, leaving that pose in the same cell, and its index becomes 17. Keeping the old integer now addresses a different cell. The PNG encoder has not necessarily failed.
A repack creates another situation. If the exporter preserves the order of named frames but moves them into a new grid, ordinal 13 can remain ordinal 13 while its rectangle changes. A consumer holding cached rectangles needs a refresh even though its sequence numbers look unchanged. A migration must say which of these situations applies before anyone chooses a repair.
Rehearse the migration with labels
Use diagnostic cells carrying unmistakable identifiers before inserting finished character art. Select examples from the first row, a later row, and the last occupied row. Compare the old named-frame map with the proposed one. A first-cell-only preview is a weak compatibility check because that cell often stays at the origin under both layouts.
Then write a small acceptance record: old layout revision, new layout revision, identity being preserved, mapping regenerated, and animations exercised. Release the image and its manifest together. If a scale variant or multipack export is involved, give every resulting page a distinct output path; a correct rectangle map is useless if another variant overwrites the file it names.
Make rollback address the same contract
Keep the previous image and mapping as one recoverable pair. Rolling back only the PNG can leave the game using new rectangles against old pixels. Conversely, restoring only an animation file can leave stale ordinals against the expanded grid. The useful rollback question is whether one complete layout revision has been restored, not whether a familiar filename is visible.
Appending rows at unchanged width may preserve existing grid indices when the receiving format permits it. That is a design option, not a universal requirement to avoid repacking. Named frames and regenerated metadata can support a different choice. Test the real importer, including its cache behavior, before accepting either path. This arithmetic exercise does not certify an engine or imply that FrameSprite manages those runtime references automatically.
Continue with the specific check you need
- Distinguish fixed-cell and ordinal-preserving migrations
- Use labeled cells to test traversal
- Keep atlas pages and variants from overwriting each other
- Explore the complete 210-guide workflow collection
These links open our own FrameSprite documentation. Each control states its tested scope and limitations.
Top comments (0)