Not everything is so easy. When someone creates an API of this type, they are aware that later on they will have to add, or worse, change (delete something old to replace it with something new). Are two totally different things. Adding generally does not imply breaking back. In fact, version 3.2, just add new features for API6, does not change anything, as far as I know (maybe I am wrong). In this case, there will be no problem automatically updating the tools. The only thing that makes the auto update is to edit the file “manifest.xml”, replacing a 5 with a 6 in a line
However, removing something old to replace it with something new does mean breaking something backwards. In fact, version 3.2 includes some “patch” added precisely to avoid this. Anyway, I think that if something is “badly designed” in the previous versions of the API, it is better to correct it for something new, instead of keeping that code and adding a patch. That patch is very likely to confuse programmers, even. And if there are tools that do not work, it is not the fault of Taktik or Renoise, but of their creators. If there is no support desisnteresado by these users (who do not charge anything, and in most cases do not receive any kind of gratitude, but rather the opposite), forget about that tool. It is the best. You will lose the tool, but “obsolete tools” will also be cleaned.
In summary, if you have used 3.1 and you change to 3.2 you will not have problems with the tools autoupdates. But, if you use a 3.2 tool and change to 3.1 for whatever reason, you will have problems, as usual. But this scenario is neither logical nor usual.
Finally, if you are so concerned about the issue of tools, it is enough to learn a little about the API and LUA and solve these problems yourself. They may only involve changing a line of code, even a single character.
What does all this mean? That it is very likely that all tools for 3.1 or 3.1.1 are fully compatible with 3.2. But if the tool programmer wants to use the new features of API6, he must launch a new version of his tool for 3.2 or higher.
- Renoise 3.1.0 or 3.1.1 use API5.
- Renoise 3.2.0 use API6.
By the way, version 3.2 is quite important. It is not a minor update, but it has a lot of weight. It is likely that a series of bugs or problems are detected that should be solved soon with a new version 3.2.1. In this case, you will continue to use the API6, unless that new package has something new in API6, something unlikely. If so, it will surely be an aggregate.