Construct 3 r391

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

  • Order by
  • Sooo... according to the forum thread about addon SDK 2.0, you plan to break every single addon ever made for Construct 3 and every single project ever made with C3 using at least 1 addon on purpose in approx 1 year ?

    What are you doing Scirra ?

      • [-] [+]
      • -8
      • Ashley's avatar
      • Ashley
      • Construct Team Founder
      • -8 points
      • (8 children)

      Addon developers need to update their addons to SDK v2 and they will continue working.

      • 2 months ago you promised you will support Addon SDK V1 documented features indefinitely in this thread. So it looks like the plan is to break this promise.

        construct.net/en/forum/construct-3/scripting-51/method-access-engine-181244

        The exception to all this is the documented, supported APIs. If you use those, we promise to support them indefinitely

        You can of course stick to the documented APIs and do anything you like, and we promise to support that indefinitely

        • right :O im working 1,5 year on my one project so dont update my c3 upper than 388.2 stavble relase until all addons will not be updatet (if will be updated, i have no guarante)

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

          All the documented APIs in the v1 SDK are still supported in the v2 SDK.

          • No the APIS won't be the same and all add-ons ever created will need to be rewritten from scratch (+ many of them will be impossible to port), which is MUCH more tedious than fixing 1 line of code every 5 years if something broke by accident

      • What makes the Addon SDK v2 so important that it's worth breaking all 3rd party plugins?

        If I understood correctly, v2 is mainly to prevent plugin developers from using undocumented APIs.

        In other words, you value your control more than the projects of your customers.

        Your engine is so slow on Android and iOS; you complain of lacking time to accommodate the most requested essential features, but still have time for this?

        Stop lying to us!

          • [-] [+]
          • -4
          • Ashley's avatar
          • Ashley
          • Construct Team Founder
          • -4 points
          • (2 children)

          What makes the Addon SDK v2 so important that it's worth breaking all 3rd party plugins?

          Ending compatibility disasters that ruin customer's projects.

          • By creating a compatibility disaster ruining EVERY customer's project ?

            I'm using 4 years old add-ons and it's fine. If one break by accident, it's likely it would be fixable in some way by renaming a function or rewriting a little chunk of the code.

            But soon, EVERY addon will break, EVERY addon will need to be rewritten from scratch and some of them (all the best ones) won't be possible to port.

              • [-] [+]
              • -2
              • Ashley's avatar
              • Ashley
              • Construct Team Founder
              • -2 points
              • (0 children)

              Customer projects will continue working fine if addon developers co-operate and update their addons to the SDK v2.