What a Cocos Sprite Sheet Needs
Cocos Creator draws sprites from a texture plus a SpriteFrame that defines a region. An animation switches those frames over time, so the region data is what actually determines what appears on screen, not the image alone. If the region rectangles are wrong, frames crop or overlap and the art tears at the seams.
The sheet must match the region data exactly, or the animation looks broken in ways that are hard to diagnose late. A manifest lists each frame as an absolute rectangle, and you create a SpriteFrame per rectangle and add them to a SpriteAtlas. Every region then becomes precise and repeatable across a whole team.
The manifest also records fps and a loop flag, which map to an AnimationClip's sample rate and wrap mode. Timing stays with the asset instead of living in a settings panel someone forgets, and the engine plays what you previewed rather than its own default pace.
Because regions are data, an editor script can rebuild the SpriteFrames whenever the sheet changes. That keeps the project reproducible and the art and engine data in step, so a new character set reuses the same import routine and no one hand-slices regions under time pressure.

