What a Godot Sprite Sheet Needs
Godot animates sprites through SpriteFrames, which holds a list of textures and a frame rate. Each texture is usually an AtlasTexture that points at one region of a sheet, so the region data is what the engine actually draws. If those regions are off by a few pixels you see seams, missing limbs, or frames that drift.
The grid must match the art exactly, not approximately, because small errors are very visible in motion on a character with a clean outline. A manifest lists each frame as an absolute rectangle, and you read those rectangles to create one AtlasTexture per frame. Every region then becomes precise and repeatable across a team, with no recounting of columns.
The manifest also records fps and a loop flag per state, which maps cleanly to a SpriteFrames animation's speed and its loop setting. Timing survives the export, and the engine reproduces what you previewed rather than defaulting to its own pace. That consistency is the difference between a prototype and a shipped animation.
Because the rectangles live in data, you can regenerate the SpriteFrames from a script whenever the art changes. That keeps the sheet and the engine resource in sync, which avoids the classic drift between art and engine data. It also means a new character set can reuse the same import routine.

