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.
Give playback direction one owner. If your exported sequence already includes the return journey, applying ping-pong again in the game creates another traversal. If you export only forward poses, the consumer must deliberately implement any return. A tag's name does not establish which behavior an importer actually supports.
Key Takeaways
- Separate source frame order, tag direction metadata and runtime playback policy.
- Compare pose identities, including repeated endpoint holds, rather than counting files alone.
- A reversed opening animation is not automatically a correctly authored closing animation.
Write the intended journey before exporting
Label a short source sequence with recognizable pose IDs. For a door, use closed, crack, half and open. Record whether the desired action is opening once, closing once, or continuously opening and closing. A developer can then inspect direction without guessing from near-identical thumbnails.
Aseprite's Tags documentation describes Forward, Reverse and Ping-pong playback directions. Treat that setting as source information. It does not guarantee that a particular export format or game importer will expand the same pose journey. A PNG image has no universal mechanism for declaring a named animation's direction.
Choose metadata-driven or explicitly expanded playback
For a metadata-driven handoff, keep the source range and deliver its direction alongside the frame list. The importer must read and honor that information. For an explicit handoff, deliver the intended ordered pose list and configure the consumer to play that list normally. Avoid silently mixing these approaches between actions.
The command-line reference documents frame/tag export and JSON metadata options. Inspect the actual output from your selected command and installed version. Do not assume an atlas containing four regions means the runtime should visit only four time slots: metadata and repeated references can describe a longer journey without storing extra unique images.
| Handoff | Export responsibility | Consumer responsibility |
|---|---|---|
| Forward frames plus direction | Preserve source order and direction field | Apply supported direction exactly once |
| Explicit outward-and-return list | Preserve complete ordered pose list | Play that list without another reversal |
This is a proposed contract comparison, not a tested importer compatibility claim. Check the native animation workflow when creating a small reference action, then validate the real exported files separately.
Audit the turnaround as a time slot
Suppose your project chooses closed, crack, half, open, half, crack for a repeating display. That is an authored example, not a promise about Aseprite's export expansion. If the delivered action instead includes open twice, determine whether the extra hold is intentional before deleting it. The total time at the endpoint depends on both repeated references and individual frame duration.
Slow the preview and record successive pose IDs for one complete cycle. Compare that record with the intended list. If the error occurs only after import, preserve the source and change the import/playback policy. If it already appears in the exported list, fix that expansion stage. Renaming a tag cannot repair duplicated time slots.
Know when reversal is the wrong repair
An opening treasure chest may settle with a bounce while its closing action needs a different anticipation and impact. Reversing every pose also reverses those events. Use direction changes for actions whose intended motion supports them, rather than as a blanket way to manufacture another action.
Continue with authored returns versus reversed animation, tag range overlap and frame tags with duration metadata. Acceptance means the delivered pose journey and endpoint timing match the action brief in the actual consumer. No editor or engine execution is claimed here.
Written by the FrameSprite Workflow Team. Send a correction.
Top comments (0)