Spine Completion Callback Fires Again? Distinguish complete from end

The animation appears to finish once, but several completion notifications arrive. Identify the listener method and object before exporting again. A loop completing, an entry ending and an application action finishing once are separate contracts.

Name the callback precisely

The current Spine 4.3 API reference describes complete as occurring whenever an entry completes a loop, including possible delivery while mixing out. end means the entry will never be applied again. They are not interchangeable.

Check the installed runtime and wrapper. No cross-version listener implementation is supplied. Completion does not establish a hit or a server-confirmed action.

Make each source identifiable

1. Record the instance, track, entry, animation and callback type.
2. Retain looping configuration, mix-out state and observation time.
3. Inspect global and entry listeners, including registration on repeated screen entry.
4. Distinguish another loop, another entry and multiple handlers receiving one notification.

These branches require real logs. Repeated registration is not the universal diagnosis, and no identifiers or event sequence are invented here.

Define what the application accepts

A looping idle and a one-off action need different acceptance rules. Define the action instance, cancellation and interruption conditions, then handle repeat notifications through existing state management.

A single global completed flag across all characters can suppress later legitimate actions. Do not bypass authorization or server decisions merely to make a visible test succeed.

Separate notifications, events and pose exit

If playback works but a sound or specific gameplay event never arrives, use the event-reception and handling checklist. If notification arrives but the pose remains, inspect track exit. Repainting images does not establish correct listener behavior.

This article does not recommend restarting an animation inside every complete callback. Check callback-triggered changes against the actual update flow and runtime reference.

Use one export across the required paths

Retain the resources and animation in Spine Workbench with its guide. Compare one-shot playback, looping, interruption, mixing out and re-entry in the receiving project.

No engine experiment was performed here. Record notification origin, the rule accepting it and the final result. A call without an exception is not proof of exactly-once application handling.