Ashley In this case:
For example this suggestion appears to involve code reaching in to the internal engine and risking compatibility disaster when a static method could have sufficed and would have worked robustly indefinitely.
It is more mixed, yes the original author should not have go into the internals, but also the SDK could have supported the required function, but it was not available at the time.
Yes, the suggested work around is possible by editing every addon that needs the workaround. I think we can agree having the top level SDK method which did not require that is more beneficial and more compatible across all addons. You mentioned adding the top level SDK in the discussion, which is a good idea.
So, please keep this in mind for V2 SDK, don't expose the bare minimum to match SDK V1, it should be a nice rounded, powerful superset. That will put C3 and SDK V2 authors on a nice trajectory to make the C3 community successful. Which in turn makes Scirra successful. Also, it would be less work for you in the long run in terms of back and forth requests for V2 additions and more importantly if SDK V2 is too limited, prior C3 addons may no longer be possible to be ported to SDK V2, creating a compatibility disaster for users of these addons.
I want to add that I think the discussion on that suggestion is a good back and forth between C3 dev and addon dev. Both sides working to come to a solution working towards improving C3 for the community, users and business.
Ashley As guidance I would be very interested to hear what some of your top 2-3 3rd party addons are - that you think substantially help the C3 community and Scirra? I think this would help us understand what type of addons you are thinking about as you update the V2 SDK.
If you have devs that are having issues with their current projects and addons that they need help with _now_, please also tell them to post in the forums or the Construct Community Discord or connect us with them. We (the C3 dev community) can help - we can potentially contact the original addon devs and we can fix the addon ourselves in the community as a stopgap until V2 SDK is comprehensive enough to handle a good forward compatible version of the addon.