Spine Attachment Exists but Lookup Fails? Check the Placeholder Key

The package contains the weapon image, yet a runtime lookup cannot select it. Keep the failing export and call intact before renaming anything. A file in a folder does not establish that its filename is the key expected by the attachment lookup.

Write down the mapping, not just the picture name

The official Runtime Skins guide explains that a skin maps a slot and a skin-placeholder name to an attachment. That lookup name need not match the attachment's own name.

For a fictional handoff example, slot hand might use key weapon, mapped by a particular skin to an iron-sword attachment. These are illustrative names, not fields verified in your template. Ask the integration owner to extract the real mapping from the exact export under investigation.

Trace one call through one unchanged export

1. Record the export batch, active skin and actual slot being queried.
2. Capture the method and its supplied slot or index and name argument.
3. Compare that argument with the real placeholder key, preserving spelling and hierarchy.
4. Correct one confirmed mismatch in a test copy and observe the same animation and skin again.

This is a proposed diagnostic, not an engine test performed for this article. If the call returns the intended attachment but it remains invisible, move to attachment state, animation writes or rendering. Repeatedly changing a successful lookup key obscures the next problem.

Separate three different failure reports

A missing skin, a missing attachment and a failed texture load require different evidence. Record the exact method and parameter, rather than an ambiguous note saying the weapon name is wrong. Keep the image path in its own handoff field.

A thumbnail or a familiar export filename is useful for a person identifying an asset, but it is not a substitute for the runtime mapping. If different builds disagree, compare their real batch identifiers before adjusting names in both places.

Avoid a rename that changes the entire experiment

Renaming every image and configuration field at once also changes the references used to reproduce the failure. Preserve the original package, isolate the incorrect mapping and assess other consumers before introducing a naming change. A migration needs a reference list and a rollback plan.

Accept the handoff in the receiving project

Use Spine Workbench and its current guide to retain the chosen template and export batch. The workbench is not presented here as a runtime lookup debugger.

Check the intended skin, slot and selected attachment, plus a control skin. Keep proof that the unchanged baseline still loads. Acceptance means the intended object is found and displayed according to the design, not simply that an error message disappeared.