Iβm the one who has been porting dozens of these addons recently, and I have to weigh in here because this isn't just about "fixing broken projects"βit's about a massive security liability that hasn't been fully addressed in this thread.
Ashley is 100% right about the security risk, but I want to take it a step further. Weβre not just talking about a plugin "not working." Weβre talking about Supply Chain Attacks. A malicious actor could easily "port" a popular SDK v1 addon, use the same ID, and hide a script inside a bundled dependency (e.g., import { core } from './bundle.js';). If a user unknowingly updates to this "ported" version and publishes their game, they risk:
App Suspension: Google Play/App Store detecting malicious SDK behaviors.
Account Termination: The "death penalty" for mobile developersβlosing their Play Console account permanently.
Financial Loss: For many, this is their livelihood.
As someone doing the heavy lifting of porting these addons, I absolutely refuse to be held responsible for what happens if we allow a "free-for-all" on ID reuse. If I port a plugin and someone else "shadow-updates" it with a malicious ID-match.