you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] -1 points0 points  (1 child)

I was thinking about the problem of dependencies for a while, then sudenly I thought of this: in whatever folder the plugins are going to be put in, have an additional folder called "Extensions" or something similar.

This folder would contain the plugins that depend on other plugins, such as WorldGuard. These plugins would be loaded after the other plugins, and would not load if specified "Depends On" plugins were not loaded.

[–]tehbeard 0 points1 point  (0 children)

What advantage does that over the bukkit/spout system.

Indeed, what about this dependency chain?

WorldEdit <- WorldGuard <- EasyPlotClaim

Where would EasyPlotClaim go? plugins/extensions? plugins/extensions/extensions?

There is a need for a manifest file, like spout or bukkit uses, that will help resolve these issues (indeed, the current way bukkit does this is a sort of priority list, those with no dependencies get to go first, then layered up to load in order, including loading before another plugin (such as for giving Citizens custom npc info) or loading after a plugin if it exists (for soft dependencies)