Spine Skin Label Exists, but Lookup Fails? Check the Full Name

The AI-generated cover illustrates several character appearances. It is not a skin tree, exported data view, or runtime lookup test.

An artist calls a skin red, but the developer cannot find red in the loaded data. Before renaming or exporting again, establish whether red is a short display label, a resource name, or the complete skin name in this export.

Folders can contribute to the runtime name

The official Spine skin documentation explains that skin folder names are prepended to the exported name used by the runtime. A short label in a project is therefore not always the full lookup string.

For a hypothetical project that places red under outfits/winter, the complete name may be outfits/winter/red. This is an example, not a claim that Tooliva always exports this hierarchy or a requirement to add that prefix to your data.

Confirm the name from the actual export

Keep the original package. Ask the integrator to inspect its skin names through a workflow suited to the actual data format. Do not search-and-replace a binary file as if it were text, or build a simplified parser merely to inspect names.

Page image names, workbench resource names, and weapon variant names can serve different purposes. A file does not establish the existence of a skin with the same name. One working default name is also not a reason to rename every other skin to that value.

Make the label-to-name mapping explicit

• Short label: the term used in the interface or team notes.
• Full name: the exact string confirmed in this export.
• Batch: the delivery and paths actually loaded by the project.
• Result: whether lookup succeeds and what happens afterward.

Record red and outfits/winter/red as a pair when that relationship is established. Editing the original data is unnecessary merely to simplify conversation. Short labels can repeat across folders, so preserve the complete string, case, and separators rather than assuming the consumer normalizes them.

Separate lookup failure from incorrect display

For a failed lookup, check the loaded batch and complete name first. If lookup returns an object but the appearance is wrong, investigate skin application, attachment selection, and animation state instead of repeatedly changing names. A confirmed key is not a successful rendering test.

Use the project's real logs or state to distinguish these cases. A character screenshot alone does not reveal the lookup result. Project code changes belong with its owner and the relevant runtime documentation, not an unverified cross-engine snippet.

Use the real export name in the workbench handoff

In Spine Workbench, confirm completed resources and export skin names using the public guide. The Spine editor's folder rule does not establish a matching folder-management feature in the workbench.

For the broader naming distinction, see resource, skin, and variant names. Keep the actual name, lookup result, and planned animation observations in the acceptance record rather than merely saying that red was exported.