Spine Event Values Never Change? Compare Key Payloads and Defaults

Both footstep keys reach the callback, but the sound branch always sees the same parameter. Log the event name, animation time and effective payload for each callback. Establish whether the wrong value is being read or the expected key was never received before changing any art.

Give the two keys clear identities

The official reference describes default Integer, Float and String values and values that can differ per event key. In a test copy, keep one event name and assign two keys integer values 0 and 7, floats 0.25 and 0.75, and strings left and right. These values identify the keys. They are not a Tooliva gameplay or audio protocol.

Compare received data with the definition

Distinguish the current event instance payload from the event definition defaults using the API for the runtime version in use. Log both beside the key time. A handler that always reads the definition can hide the key-specific values. In JavaScript, keep zero as a valid integer test value instead of replacing it merely because it is falsy. Record the loaded asset revision as well, so an old export cannot masquerade as a payload bug.

Restore the full playback conditions

First verify the two payloads in one animation without mixing. Then restore loops and transitions and check callback counts and branch selection. If no event arrives, the related diagnostic guide covers that earlier part of the chain. Use the Spine Workbench to review compatible character motion. Validate payload handling and sound or gameplay actions in the integration code; audible editor playback alone does not establish runtime audio wiring.