Choose plugin contents

[adrian_hornung]

Hi
I have a question and mabe a suggestion.
So is it possible to build something like the jquery ui download builder for plugins (Mods)? What I mean is that on can choose additional functions (or less functionality) for some plugins like essential. (Where we had one huge jar, with some not from all appreciated functions)
If yes how and would a builder even be of any use?
Thanks

Ps. If i am i the wrong section, I apologize.

[simon816]

There’s a suggestion for ‘Plugin Packs’ which is similar to your suggestion here. See PluginPacks

[OffLuffy]

I think loading modules would be the best way to do it, like Lapis Commons

[Abandoned] Lapis Commons: Unified toolkit for rapid Sponge plugin development

Note: LapisCommons is not actively maintained and deprecated. The Sponge API has become mature enough to contain almost all functionality LapisCommons once had. Please depend on the Sponge API instead. These past few weeks have been a fantastic example of the community pulling together. I’ve never seen so many brilliant minds working towards the same goal. We’re even seeing plugin projects already underway! It is in this environment that we’re proud to announce Lapis Commons. We’re a small gr…

Trying to setup a web form to build custom mods would likely need a very complicated setup and for the mod to be recompiled for that particular combination. Probably not worth the trouble.

[tebbenjo]

could a plugin be coded such as to have each feature have it’s own class file within the jar, and it’s own folder for resources and not expect to have every class file. So as to allow the user to delete with very fine precession certain features even within modules without screwing up everything? Just a question.

[adrian_hornung]

Like multiple jar to a single jar?

[bdubz4552]

I’m not quit sure I understand what you’re saying… Are you asking if it would be possible to only download parts of a plugin, or additional features? If so, this is more of a packaging and distribution issue on the plugin developer’s end.

[adrian_hornung]

like this:

Core (has nothing exept helper classes) + features (usually added jars) = new compiled file

We have 1 Core (always), which we always download and N features (based on the Core), we can choos the Features (/nuke or /tpnew …) in a single file

I am sorry if this is not clear

[MrMysteri0us]

From what I get, you want plugins to have their own plugins (kind of).
Well, thing is, Sponge can’t force developers to code such complex plugins, it would depend on the developer wether or not he’d code something like that.

[adrian_hornung]

I only am talking about the very complex plugins which are huge like essentials.
But knowing it is technically possible is nice.
Thanks for answering my questions

[MrMysteri0us]

Glad I could help.

[Jake0oo0]

I think this is more something that the plugin developers should handle themselves. Essentials is already split up into smaller modules too.