Construct 3 r391

You're viewing a single comment in a conversation. View all the comments
  • 2 Comments

  • Order by
    • [-] [+]
    • -1
    • Ashley's avatar
    • Ashley
    • Construct Team Founder
    • -1 points
    • (1 child)

    The problem is in the long run, pretty much all parts of the internal engine will be rewritten/upgraded/improved, which means all addons accessing internal details of the engine will be broken, and all projects using them will be broken. There is a real risk of a serious disaster in future with a great many projects being ruined. We have a difficult choice between taking disruptive action to guarantee that cannot happen any more, or continuing to allow increasing disruption from customer projects being ruined in future. I strongly believe that despite the disruption, taking action now is the right choice to ensure compatibility on a 5-10 year time scale.

    • Yeah, I understand…. But, there are still a lot of Addons using the old SDK that do not access internal features and will likely not cause any issues at all. I‘m using like 10+ addons that do not in any way (except from adding objects with actions/conditions) mess with the engine.

      I just hope there is a way to like catch errors regarding older Addons and then maybe automatically disable them / or show the behaviors/effects/events/objects in red to indicate that they are broken etc. I assume this would not be an easy feat but if possible, definitely worth it if you could somehow isolate them from the main project to ensure integrity.