can you add the ability to create plugins and connect them to the spine or create an api?
Plugins
A lot of the things that can be done by a plugin have to be asked to add the developers to the spine. Judging by the workload of developers, most requests will never be satisfied. All programs that have added plugins have benefited from this.
I looked on the forum and the first post asking to add plugins dates back to 2013. People really need the ability to write spine plugins.
Please do not ignore the request!
We are not ignoring your requests. We also wish we could add a plugins feature, but there are still many issues that need to be improved in the core of the editor, and we prioritize implementing them. We know it may seem like we are improving the functionality slowly since we are also fixing bugs and dealing with minor fixes, but we are making progress every day to improve Spine.
You may find some of past threads that we have not replied to, but we check the forum daily and have re-checked when similar issues have surfaced, so it is not in vain that you all leave requests like this and we highly appreciate it that you took the time to share your thoughts and suggestions with us.
- 已编辑
I would like to use the official spine support for plugins.
No matter how you justify the lack of functionality, 10 years is a long time.
The need for plugins arose precisely because the development is slow and does not keep up with the requirements of the animators.
I am a programmer and can easily implement the functionality I need, if I have the opportunity to write plugins.
But as a result, I have to write to support asking them to do it for me and I know that I will never get the functionality I need, because you still have 100500 other requests from other people.
+1, think it would improve spine
+1!!
Plugins make life easier for animators!
Tell me, is there any hope that plugins will be added to the development plan?
While we have not gotten to the feature you want, we have done an enormous amount in 10 years. Go back and run the early versions and compare.
It is unlikely we will provide plugins in the short term, sorry. A plugin system is a massive undertaking, both to implement well by providing good APIs that do the many things people want to do and to document how to use it. We do understand the value there, but it needs careful planning and proper execution. We are working on many things and have no been able to get to this one.
I am very sad to read this, but thanks for the honest answer. I hope someday you will change your mind and someone will convince you of the importance of plugins for Spine. I'm sorry I didn't make it.
- 已编辑
Urr
Depends on your situation, using other tools which allow you write custom plugins may be a better choice for you. IMO, spine is currently the best choice for making 2d game animation. I noticed other options which is not that bad if you want extensibility more than the provided features.
If your are making game with Unity, AnyPortrait from unity asset store is worth a look. If I remember correctly, It came with full source code so you can do whatever you want to make it better. However, it seems to lack certain features like skin. I bought it a long time ago during a sale but never have time to get into detail but its so cheap that I don't feel bad putting it aside.
Another interesting alternative is Moho Pro. According to their website, you can write custom script to personalize it. To be honest with you, I never tried it but it show some interesting features on their website that I really want them to be available in Spine so it got my attention. However, its expensive if you want to keep you version up-to-date. The approach to integrate to game engine is also different. It use standard fbx file which allow them to support game engine without custom runtime library. However, some special features that is provided by the spine runtime will not be possible using fbx.
@Everyone
Regarding the topic about Spine plugin support, you guys are ... asking for too much. You don't need full feature well defined API to create tools for spine if you don't mind your tool floating outside the spine editor window. In opinion, it would be great if plugin support is available. However, as I suggested a long time ago, a lot of things can already be done IF ...
- Spine Editor can have a setting to make it save/load the project using the current json import/export format as default. (parsable text file is the key point)
- have another setting to have Spine auto detect project file change and auto reload the project.
With these 2 very simple changes, we can write external tools to parse and update the project and have spine auto reload and apply with the changes.
In fact, we can already do this kind of patch using the import/export feature to extend the spine editor but the workflow is not smooth without the 2 suggestions mentioned above. If spine team really want to help regarding the extensibility aspect for the spine editor, I think this little change could be a good start because it is really an easy task with big gain.
p.s. I am just saying what can be improved easily, it doesn't mean I am making a feature request. I am not!
Nick p.s. I am just saying what can be improved easily, it doesn't mean I am making a feature request. I am not!
You are and you know it! 
With these 2 very simple changes, we can write external tools to parse and update the project and have spine auto reload and apply with the changes.
It's an interesting idea and you are right that would be a lot easier than providing a plugin system. Spine can import into an existing skeleton. One way to do it would be to have CLI commands to take actions on a Spine editor instance that is already running, eg to export to JSON and to import JSON into an existing skeleton.
Another idea between nothing and a plugin system is to provide a REST API. This would give more control than the CLI, eg for setting/manipulating the selection or other minor UI tasks that might be part of a larger script.
Nick
Thank you very much. I started with moho and did not know that can be exported to fbx and scripts are really good.
Nate
By switching to Spine, I was hoping for the development of the program, but I do not understand why it is so slow.
I will not use CLI or import -> export.This is a battle with the program, and I just want to work.
Perhaps for you the program has changed a lot in 10 years. But I do not have this experience and I see that in a year there are almost no innovations and even improvements in the program.
- 已编辑
After two or three hours of setting frame offsets with a whip, my hands and eyes pains. Guides have been requested since 2016. Yes, they are not always needed, and they can be replaced with thin PNGs, but these are all stubs.
I know that you are developing physics and I remember that you added a handy Favor Tool, it's all cool, but it doesn't help at all in the routine.
Most routine operations, as it was difficult to do a year ago, are so difficult to do now.
The suggestion to use the CLI looks like a mockery.
How you develop the program is up to you, but can you make the routine operations a little less painful?
This is my personal observation and maybe other people need something different. I just briefly described my impressions of the program for a year of work.
@Urr I'm curious about what kind of animations you are making to have so many problems. If you can share your project and maybe I can help with finding the easiest and fastest workflow for you. The thing with animation is that it's hard. Making convincing motion requires laser-sharp focus, and usually years of practice. When you look at the usual 3 years of bachelor's + 3 years of junior position you need around 6 years of constant work to be a decent animator. Some get it faster, some slower, but it's still years of concentrated work. We are constantly working on how to make Spine easy to use and intuitive with new features, but that is a huge challenge as there are so many use cases, plus users coming from different backgrounds with different skill sets and different necessities.