Do you think caring about our community means allowing customer projects to continue to get ruined over the next few years, and possibly risking some huge disaster, when we know we can take action to prevent that?
You are forgetting the fact that WE are customers, advanced customers, and probably we are the serious ones making money out of construct. You really have no idea of how many projects will break up permanently, this decision won't help us, the CUSTOMERS. I don't see Scirra considering allowing the v1 of the SDK to live forever, why removing it? Improving it is perfectly fine, but removing it?!?! I'm affraid this decision will cause more problems than benefits, even for those addons that didn't hack the SDK. And I'm pretty sure you are not fixing your customers projects, we have done it in a daily basis every time construct breaks. I had had to workaround Construct 3 bugs so many times, much more commonly than by using a 3rd party plugin. My in-house plugins had never broken a project on every c3 release, but the c3 release itself had, even delaying my delivery schedule for months several times because it broke existing functionalities that are c3 features, or because your priorities don't align with the bug fixing. Yeah I've lost money because of this. I perfectly know what I'm talking about, already been in the software industry for over 20 years. Do not neglect that v1 sdk must be kept alive. Investing time and money in the projects and accelerators I've developed for the past 5 years is a huge project. It will only push me to evaluate alternatives where the accelerators and features already exist, where I don't have to develop them again just because sdk v1 will be removed. Some of my addons took me over a year to be properly developed, of course all of that is not public, you are missing that important part: what you don't see in the forums/community.