為何精靈圖熱修補只會破壞較舊的發佈分支？

Disclosure: This draft was generated with AI and checked against the cited primary sources, with a separate AI editorial review. It was prepared for the FrameSprite team, which has a commercial interest in FrameSprite. Proposed examples are not executed tests unless explicitly identified as recorded fixture results.

Check the sprite hotfix's earlier dependencies before copying it to a release branch. A cherry-pick can apply cleanly while importing an image that expects a newer frame layout, attachment table, or loader behavior. A conflict-free patch is not proof that the older game can use it.

Key Takeaways

Identify the exported texture's required metadata and importer behavior.

Review the release branch's contract before applying the change.

Validate the backported package in that branch's actual consumer.

Clean application and compatibility are different

Git cherry-pick applies changes introduced by selected commits. It does not infer the semantic prerequisites of an art export. An updated PNG can have the same filename while assuming a layout added several commits earlier.

Read the original change description and inspect the commits that established its inputs. Ask whether cell dimensions, origin conventions, animation names, frame ordering, or event references changed. For an AI-assisted asset pipeline, also identify any manual cleanup that was incorporated before the hotfix.

Trace the dependency before choosing the backport

Compare the release branch and source branch using a deliberate Git diff range. List the complete delivery set: texture, timing file, frame map, importer configuration, and any scene changes needed to interpret them.

Choose one of three explicit paths. Backport the prerequisites and the fix together; adapt the visual fix to the older layout; or postpone the asset change because the older consumer cannot safely support it. The choice depends on release risk and testing capacity, not on whether the patch tool reports success.

Keep the adapted export distinct from the original source-branch export. A backport can be visually equivalent while requiring different packing. Document which version belongs to which release branch so later maintenance does not mix them.

Example: an attack pose inside a changed grid

The development branch changed a six-cell attack sheet into an eight-cell sheet, then fixed the final recovery pose in a later commit. The release branch still assumes six cells. Copying only the later PNG may apply without a conflict because the path exists in both histories.

For the older branch, either retain its six-cell layout and repaint the corrected pose there, or bring in the eight-cell layout with all consumers that depend on it. Inspect attack timing and any frame-indexed event after the change. A successful image decode would not catch a hit event attached to the wrong pose.

Review after integration

A backport may encounter a genuine content conflict. The merge documentation is useful for understanding conflicts, but resolving one does not replace art review. Preserve the old delivery until the release candidate is verified.

The acceptance record should identify source commit, adapted commit, retained layout contract, affected actions, and the consumer version used for validation. Test the patched action and its transitions rather than only the corrected still image.

This scenario is derived from version-control and dependency behavior. No specific branch, engine execution, or backport success rate was tested here. If the old consumer is unavailable, mark integration unverified instead of declaring the hotfix release-ready.

Continue the workflow

Use the asset-package folder contract to separate editable masters, runtime exports and previews before backporting. Keep the animation handoff checklist with the delivered package, and preserve its visual decisions in the game-art reference board.

Sources and editorial responsibility

Prepared by the FrameSprite Workflow Team. See the editorial method or contact the team with a reproducible correction. Sources checked 2026-10-20.