Based on my knowledge, there isn't a specific known issue with PixiJS runtime 4.2 that prevents replacing or hiding placeholder images. The developers should be able to handle this in several ways:
Possible Solutions:
Hide the placeholder slots - Instead of removing the images from your Spine files, the developers can set the slots containing placeholder images to be invisible at runtime:
// Hide a specific slot
skeleton.findSlot("placeholderSlotName").color.a = 0;
Replace attachment visibility - They can remove or swap attachments programmatically:
// Remove an attachment from a slot
skeleton.setAttachment("slotName", null);
Preserve your opacity animations - If you keep the placeholder images in your Spine files, any opacity/alpha keyframes you've set will be preserved. The developers can then:
- Either hide the entire slot (as shown above)
- Or swap the attachment but still benefit from your existing alpha animations
Your Workflow:
You should be able to continue using placeholder images in your Spine files. The issue isn't with the runtime itself - it's about how the developers are implementing the text replacement. They have full programmatic control over slot visibility and attachments in PixiJS.
The advantage of keeping placeholders is that you maintain all your timing and animation data (including opacity keys), which the developers can apply to their dynamically-created text elements.
If they need more specific guidance on the PixiJS implementation, they should refer to the spine-pixi documentation for details on slot and attachment manipulation.
