I am finalizing the update of my plugins to R21, and am working on the documentation right now, especially the part about explaining how/where to "install" plugins.
However, my recent experiences have somewhat conflicting results, to the point I am starting to wonder if I am becoming delusional, or my eyes and mind are just playing tricks on me.
I remember from the early days of R20, when installing the application there was NO plugins folder being created, nor in the main application installation folder, nor in the user's location (where library, scripts, prefs, ... are stored by default).
If a user wanted a similar location as was default available in pre-R20 times, one had to create that folder manually and add it as an entry into the Plugins section of the Cinema4D Preferences.
And now comes the weird part ...
On my main development machine, which had the originally release R20.0xx installed, I had manually created this "plugins" folder in my user location, and added that path as an entry in the Plugins section of the preferences. Plugins are thus available in that folder, and when I start Cinema 4D, in the console I see each plugin printing its "welcome-message", indicating it's loaded and ready to perform.
In the meantime I had upgraded to R20.057 and behavior remains the same: plugins get loaded, with welcome-messages in console window.
For various reason R21 is installed on a different machine.
On that same machine, I now have installed R20.059 in order to compare behavior of my plugins between the two Cinema 4D releases.
Strange thing is that after the installation the plugins folder already exists in my user's location. No need to manually create one. Was this change added in recent updates?
More strangely: when I add the path to the plugins folder in the preferences, and restart Cinema 4D I get conflicts in the console windows telling me the plugin IDs are colliding. As if the plugins are loaded twice (twice from the same location, since only a single path was added to the preferences). When I remove the paths from the preferences and restart Cinema 4D, all is fine, no collisions ... and yet the plugins are loaded.
So R20.059 creates a plugins folder, and internally already knows about that path without the need to add it to the preferences?
R20.057 might create a plugins folder, no way to test this as I already had such folder before upgrading to R20.057, but it doesn't complain about colliding plugin IDs. as such it ignores duplicate paths. And when removing the path from the preferences it still does load the plugins. Nice!
Now R21.026 does also create a plugins folder in the user's location (again: Nice!), and when this path is added to the preferences it doesn't complain about colliding pluginIDs. When removing the path from preferences the plugins still get loaded. Just as with R20.057 it seems to internally know about this "default" path, and ignores the duplicate when it's added by the user.
Both R20.057 and R21.026 behave identical where they know about the default path and ignore duplicates. While R20.059 knows about the default path but cannot handle duplicates.
So, R20.0xx did not create the default plugins folder, and obviously didn't internally know about.
Then R20.057 (or earlier) introduced the default plugins folder creation and internally knew about this, ignoring duplicate paths in the preferences.
Then R20.059 came along, still creating the default plugins folder but breaks the "ignoring duplicate paths".
Finally R21.026 creates the default plugins folder and again ignores duplicates.
Could this be confirmed, please.