My idea is to improve on it until it is able to show common conflicts and eventually suggest solutions. The best part about it is that plugin makers wouldn't be forced to implement any new code. Then again, eventually, a more structured and mature dependency tree could be suggested.
I know that this is not the priority of the engine right now, but I'd love to hear your thoughts on it.
Cons of my idea: At the time being, only modern browsers are supported and the shipped NW.js version of MV does not have support for ES6 Proxies. This could (eventually) be solved.
I wrote a plugin that uses ES6's Proxies to observe many game objects and all managers.
You can find it here
My idea is to improve on it until it is able to show common conflicts and eventually suggest solutions. The best part about it is that plugin makers wouldn't be forced to implement any new code. Then again, eventually, a more structured and mature dependency tree could be suggested. I know that this is not the priority of the engine right now, but I'd love to hear your thoughts on it.
Cons of my idea: At the time being, only modern browsers are supported and the shipped NW.js version of MV does not have support for ES6 Proxies. This could (eventually) be solved.