Let's Talk Publishing

NOTE: Let me know if a thread on this topic is already made.

So, let’s take a look at what we have so far.

  1. A website.
  2. A Google doc explaining the basics of the Sponge project.
  3. A useable, un-frustating forums.

We also have a GitHub that can be forked, allowing users to submit pull requests.

However, once the project is at a useable state, people are going to want to use the thing as an API. Not only that, but they’ll be submitting their plugins for download. Where will they do it, though?

I know this is jumping ahead a little, but I don’t think it could hurt to think about how users will be publishing their Sponge plugin/mods/whatever we’re calling them (I vote module!), like BukkitDev. Which of course means that we’ll have to have some sort of team that moderates and approves plugins.

Why is this necessary? Well, there’s been talk (meaning I can’t confirm it as fact) that Sponge will be able to download a mod to the client as well dynamically. This is all well and good, but you need to remember that there are a lot of ways you can mess with the client maliciously, with password-grabbers and other nasty cyber-devil spawn. The way to do this effectively must be considered.

TL;DR: What do you think is the best way to get developers’ plugins out there, but at the same time, insuring the safety of the server-owner who receives it?

I’d check this section, there’s alot of talk regarding it already on a fair amount of threads: http://forums.spongepowered.org/category/sponge/sponge-development

1 Like

Guys… HeisenBugDev…

1 Like

That’s not specific to Sponge, nor is it managed by them, by the looks.

So? You said publishing. Bukkit hosted it themselves, that doesn’t mean Sponge has to. HBD has already decided to support Sponge plugins.

1 Like


I do like the module idea @ColonelHedgehog

  • TangentSpy