Scenario value of Image Splitter in sprite
`sprite-grid-split` supports 等距网格与索引导出场景. Keep seam safety, tile readability, and publishing order stable with pilot validation, staged rollout, and anomaly logging.
`sprite-grid-split`: write the engine’s `cellW/cellH/rows/cols` contract, then prove the master dimensions divide evenly
- Agree on premultiplied alpha, power-of-two needs, and odd-width bans; capture cell size and gutter in `atlas.json`. Total canvas size should follow a closed formula like `(cellW+gutter)*cols - gutter` so nobody eyeballs math incorrectly.
- Inset each sub-frame with 1px transparent or solid gutters, zoom exported cells to catch neighbor color bleed, and for pixel art disable sub-pixel anti-aliasing with integer grids. Spot-check hashes against manual crops.
- Version ZIP and JSON together; CI should assert file count equals `rows×cols` and every PNG shares identical dimensions. For huge atlases emit diff mattes so tooling updates only frames that actually changed.
Sprite grid FAQ: even alignment, filtering bleed, pipeline naming, incremental builds
Code assumes 64×64 cells but some exports are 63 px—where does that drift sneak in?
Almost always indivisible masters or accidental non-integer scaling. Resize or pad the canvas until both axes divide cleanly; script `identify` across outputs instead of trusting hand zoom. Never “looks close enough” a texture atlas.
UI strokes show gray halos on gutters—is that the blade or blending?
Usually bilinear sampling across cells: add explicit gutters in art and verify engine wrap modes. If you need a continuous strip, skip naive equal slicing and use authored coordinates.
Pixel art exports look soft—like Photoshop secretly smoothed them—how do we ban that in process?
Stay on nearest-neighbor scaling, forbid fractional canvas transforms, force integer slice origins, and disable anti-aliased strokes. Add CI sharpness or histogram checks that fail blurry tiles automatically.
Build farms need deterministic enums—what breaks when row-major and column-major mix?
Animation data points at the wrong texture—classic “plays frame A, shows frame B.” Document traverse order in README and JSON, add unit tests for maps, and prefer filenames like `r02_c05` over bare integers.
Two hundred tiles mean full rebuilds take forever—how do splits pair with incremental packaging?
Track per-cell sources in VCS and let scripts compose atlases; CI diffs parent hashes and rebuilds only touched cells. Never overwrite versioned ZIP folders in place—keep bundles for rollback and binary diff reviews.