Well, if the birds (or creatures with wings) all have the same movable parts and dimensions, not a problem.
If they have different dimensions or the parts have pivots in different places, it might be useful to have an animation import script. This would assume the models have the same parts (with identical names) and the script would create new keyframes based on predefined animation information.
So all in all, we require 2 scripts, scripts 1 exports only the keyframes of an animation, for each model part.
Script 2 imports the data of the previous script into a new model, matching the keyframe data for all parts with matching names. This sounds actually like something some 3d tools might already do on their own…copy/paste keyframe data between 2 models. We’d have to try that sometime. This would mean, people would ideally share their raw animation files (in Blender, Softimage, Maya or 3DS Max format) for other people to re-use the animation data. If we use import/export animation scripts, it would suffice to just share the exported animation files.
The current exporter scripts I wrote would not allow us that yet, since Radiant’s engine (current version) requires animation files that define each position/rotation of every part (not only animated parts) for every frame (each of the 30 frames). Using this data (instead of only keyframes) to import for another model, would not make much sense. But the scripts could easily be modified to not export each value for every frame, but only export keyframe data, for only animated parts.
…sorry for the rambling…I was typing while thinking about it…