What a 2D Character Sheet Needs
A 2D character sheet holds the frames for one character's states: idle, walk, jump, attack, and more. Each state is a short animation of its own, but they all belong to the same character and share the same proportions. All those states must align to the same ground line, or the character appears to hop or shrink at each transition.
A manifest records each frame's rectangle and per-state timing, so the engine maps states without ambiguity. The data replaces guesswork about cell counts and per-state offsets, and it lets a loader pick frames by name rather than by a fragile index. Consistent cell size across states is the simplest way to keep the character stable.
The manifest also carries a loop flag, so a looping walk and a one-shot attack can live in the same file with correct behavior. Without that flag, an engine might loop an attack forever or play a walk once and freeze, and the bug would be in the data rather than the art.
A character sheet is also the unit of iteration. When you want to add a dash or a hurt state, you add frames to the same sheet and re-pack, and the manifest grows with it. Keeping one sheet per character avoids scattering related frames across many files.

