Adds back the addClientSideModDependency and modIsInstalled to controller instance with an explicit deprecation warning in console and an path to intended API.
Imma be honest, "months" is a very small timeframe and the way it currently handles breaking change is not very obvious to plugin developers. I'm all for better API, but breaking changes like that seem excessive.
My proposal woudl be to bring those back with one of:
Log a warning about deprecation (and show intended API), but retain bad behavior.
Log an error about deprecation and always return not installed
Throw an error with more descriptive message pointing at the right API.
Not saying to keep it indefinitely, but at least provide a better window to spot the deprecation issue.
Adds back the
addClientSideModDependencyandmodIsInstalledtocontrollerinstance with an explicit deprecation warning in console and an path to intended API.Reasoning provided in Discord;