@kumakun said in What's out there now and what has been attempted? A codebase discussion.:
I wonder though if treating the plugin system in a way that's similar to Nodes NPM or Python's PIP, where dependencies are installed with the plugin, might help alleviate some of that pain.
Not really. Because it's not just a matter of "X plugin depends on Y" but "X plugin depends on Y in this particular way." In other words, it's not just a dependency but an API with dynamic qualities.
Just for example - Ares supports plugins for several different RPG skills systems (FS3, Cortex, Fate, FFG). You can easily install the base code for the plugin, but what if you want to:
- Display the character sheet on the character's web portal profile.
- Incorporate tabs for assigning abilities into the web portal chargen.
- Warn them about any errors in the chargen app review?
There are tons of these kinds of dependencies throughout a MU system, and making all of that "100% plug and play" was a level of complexity far and above what I was willing to do for Ares.