Difficulty in Dividing up Existing Skeleton (Monogame)

ZubbyBoy

I have a working skeleton for a character with many animations that work great in the Monogame runtime when I export all of the meshes and regions together to one atlas/png/json file combo from the Spine software. Now, I am attempting to split that character into multiple skeletons, each with a unique atlas/png/json, in order to mix and match weapons and reduce the total number of skins that will be required.
To accomplish this, I have saved copies of the of the base Spine file, one for the right_arm, left_arm, and right_weapon, and in each one I uncheck the "Export" boxes on the unique meshes and regions that I do not need for that particular skeleton. Then, I create copies of the skeleton and skeleton data in the runtime and run them at the same position.
This all worked great, except for one big problem. In the skeleton I have for the main body, the skeleton has no problem switching between images for the Body_01 and Eye_01 slots whenever a new image is keyed in the animation; however, this is not the case for the right_arm or right_weapon skeletons. In those cases, when the image in slot Right_Arm_01 changes from Right_Arm_01 to Right_Arm_02 for example, the new image is not drawn in the runtime. This is the case despite the fact that is works with the same setup for the main body skeleton slots, it works when all the elements are combined into one skeleton, and these images do show up in the spine software itself.
I experimented around for a while to try and figure out what was causing this, but really with no big development. So to ask a few questions: is there anything with my setup that should be fixed? Is there a better approach I should be taking here? Any idea on why these images are not showing up in the new skeletons?
Any help is appreciated as always.

Spinebot

It seems like you are encountering issues with image switching in your split skeleton setup. When splitting a character into multiple skeletons, it's crucial to ensure that each skeleton's setup is correctly configured to handle image switching. Here are a few suggestions to address your problem:

Ensure Correct Attachment Loading: Make sure that the attachments for the right_arm and right_weapon skeletons are correctly loaded and that the paths to the images are accurate. If the images are not appearing, it might be due to incorrect paths or missing attachments in the runtime.
Check Animation Keys: Verify that the animation keys for image switching are correctly set up in the Spine editor for the right_arm and right_weapon skeletons. Sometimes, keys might not be exported correctly if they are not set up properly.
Use a Custom AttachmentLoader: If you are using multiple skeletons, consider implementing a custom AttachmentLoader to manage the loading of attachments dynamically. This can help ensure that the correct images are loaded and displayed at runtime.
Repack Atlases: If you are using separate atlases for each skeleton, ensure that the atlases are correctly packed and that the images are included. You might need to repack the atlases to ensure all necessary images are present.
Debugging: Use debugging tools to check if the images are being loaded and if the slots are being updated correctly at runtime. This can help identify if the issue is with the loading process or the animation keys.

By following these steps, you should be able to identify and resolve the issue with image switching in your split skeleton setup.

ZubbyBoy

I checked this, the images are loaded correctly and the pathway to the images are correct.
Anything in particular to look out for with animation keys? I checked just now and these slot keys on the right_arm appear to be setup the same as the other elements. Not to mention they work fine when all slots are combined on one skeleton
Any guides/place to start on doing this? Kind of seems like a hastle; I think I'd rather not... but I'd take a look for sure
Yes, the images are included and all the png files contain the correct images associated with their respective atlases.
From what I can tell, the images being switched are either not be loaded correctly or they are not being drawn correctly to the screen, although monogame does not give any kind of "failed to load" error

ZubbyBoy

Sorry if this was confusing for anyone who may have read; I got a little ahead of myself here but there is a method outlined in the runtime tutorial for skins for Monogame that looks like it should work fine for what I want to do without having to divide up the character into separate skeletons.