The removal of SDK1 — especially without a proper path for advanced plugins like Mikal’s 3D Object — really hurts teams working on long-term projects. We’re not just talking about hobby projects here, but commercial games, demos for events like Gamescom, and studios with years of investment into the ecosystem.

Yes, I get that SDK1 had risks and technical debt, but:

Why not allow SDK1 in a “Legacy Mode” for non-breaking use-cases?

Why drop NW.js so abruptly when it’s the main route for native integration with platforms like Steam?

I respect Ashley’s commitment to long-term stability, and the LTS option is appreciated, but locking advanced users into a frozen version until end of 2026 feels like a temporary band-aid — not a solution.

A few thoughts moving forward:

Could we get official support for a compatibility layer, or at least some guidance for rewriting complex plugins into SDK2?

Could Mikal or other devs collaborate with the Construct team to extend SDK2 to support the missing functionality?

Removing SDK1 may reduce technical risk, but it creates a community trust risk. Construct has always been popular because of its flexibility and plugin ecosystem. Breaking that ecosystem without a clear migration path could push devs elsewhere.