Animation events aren't getting included in json file when exporting to Spine format (2.1/3.3) from DragonBones 5.0.0.0003.
On a related note, is this actually the best place to report bugs? It doesn't look like the devs pay much attention to these forums.
No, the spine export doesn't work. You should post bugs on github.
If this is for unity, buy Spine. Or Unity just made an Skeleton animation plugin for free on their store.
I considered posting on github, but where exactly? This issue pertains to the editor, and there's no repository for that.
It's not for Unity.
Mind me asking what your affiliation is with Egret?
I'm not with Dragonbones. I was using DB for unity and gave up with so many bugs so I bought Spine to save headaches.
What are you using it for? It works fine for Starling.
Ah, a disgruntled former DB user? 
Believe me, I've been very close to purchasing Spine a few times, myself. Problem is, I want IK, free-form mesh deformation, etc. and those are only available in the Pro version, and that's currently $300.
I plan to use it with Defold, or possibly with other third-party Spine runtimes that don't require a Spine license to use.
I wouldn't say the Spine export doesn't work. I was able to get the "Ubbie-Mesh" model running on a Spine runtime without any hassle using the export. The "Robot-IK" model needed a few tweaks, since it uses IK and DB exports to an old (3.3) version of the Spine format. The event data not getting exported is annoying, although one could always do an export of both Spine and DB formats and just grab the event data from the DB file and add it to the Spine file. Worst case scenario, if the Spine export was completely broken, it probably wouldn't be too much trouble to write a converter from DB to Spine.
Of course, it would be nice if the DB team just fixed the export
post issues here
https://github.com/DragonBones/dragonbones.github.io/issues
You can ask them to support Defold too but it'll take a long while if they decide to do it.
I think Egret bought DB.
Thanks, but not a single issue in that repo has a response from a dev. I'd probably be wasting my time.
I've emailed them at the address associated with their github account. Let's see if I get a response.
Thanks for the report!
We will fix it in next version which should be published on March 8th.
Good to hear! Is this the best place to report issues like this? A few days ago I emailed the address on your github page but haven't received a response:
You must log in to post.
