Jiggle bones are also known as procedural bones and I don't know if you can actually import the setting they have when you import the model. However, there is an addon out there for jiggle bones for Blender. I haven't used it, but I would suspect that after installing and enabling the addon, you would have to go through the bones that are suppose to be jiggled and set them up individually....

This is a pretty good tutorial on the subject with a link to the addon in the description of the video...

https://www.youtube.com/watch?v=f1P8RvM-Fwg

Apply the transforms before exporting ( Select all objects, Ctrl+A, Check Rotation, Rotation and Scale ON in the options.) then export the SMDs and compile. Also, if bones don't have mesh assigned to them, the optimization process in the compile will removed them. To keep bones that don't have mesh assigned, they have to be defined in the QC. If you define bones in the QC, ALL bones you want in the model have to be defined. If a QC contains $defineBone (name Coords) any bone not defined will be removed, attached to mesh or not.

Have you applied the Transforms (Location, Rotation and Scale) to your model before exporting (Select all objects, Ctl+A, Check on Location, Rotation and Scale in the options)

I am thinking that the Eagle is on a different UV Map that the other objects...

Select your objects and look here.

https://i.imgur.com/JAs20Nj.png

I think you'll find the Eagle UV map name is not the same as the armour before you joined them.

If it is a new bug, that is a good thing for the community and a bad thing for the developer. You've let us know that there may be a problem with the current Beta and the newest (well the release of Blender you're using) of 2.80 and now the developer has to figure out what is going wrong and fix it. It's the nature of software!

If I remember correctly, you've downloaded a nightly build and patched that into your Blender 2.80. The nightly batch may have input code into Blender that has broken the work that Artfunkle has done on the 2.11 beta for 2.80. In order words, you may have found a new bug!! Good Show!!

I didn't see anywhere in any of your pictures that you were using 2.11 until I zoomed in really close. 2.11.0b1

If you are using Blender 2.80, then yes, you should be using 2.11.
If you're using 2.79b, then no, you should be using 2.10.2.

But at least now we know which version of BleST you are using.

question that I would ask though is are you sure you have BleST ver 2.11 in the 2.80 addons folder and not 2.10.2 The error looks pretty much like the one when using the wrong BleST version.

Now it makes sense...

I think what you should have said was something like.. I was using BleST 2.11 with Blender 2.80 and it was working, I upgraded Blender 2.80 to the latest build and now I'm getting this error (see Picture)...

I think something has changed between builds. Is there an update to the BleST Beta?

The better the detail, the more it is likely to help the developer fix something

Hmmm, BleST not working with 2.8. Not sure what's going on, but I'm not working with 2.8 anymore...

Picture show error while using Blender 2.80...

WT_, Can't help you if your going to ask questions that aren't related to your problem and you don't tell us what that problem is...