Osmium API (Bukkit/Sponge Abstraction Layer)

[kmecpp]

@pie_flavor

There is no market for anything like this. People only use Bukkit at all for the massive existing plugin library.

It’s not really clear who you mean by people. Plugin developers or server owners? I’m not targeting server owners and plugin developers don’t normally care about the existing plugin library unless their hooking into another plugin to add functionality or whatever.

The target audience currently would be developers making new and small plugins who want to support multiple platforms. And I know there are at least some people who would use it, because if Osmium did turn out to be a good API I would write 95% of my plugins with it.

@pie_flavor

Your API must by definition be as bad as the Bukkit API and as convoluted as the Sponge API, at least where it abstracts over Minecraft (commands, for instance, being an exception).

My intention is NOT to create a fully fledged Minecraft API. I recognize there are differences in Bukkit and Sponge which would probably make this impossible. In those cases it is up to the mod author to handle what happens on each platform. This way only the best parts of each API can be used and it wont be as bad as Bukkit or as complex as sponge.

The goal of Osmium is to be extremely concise and make it easy for smaller plugins to be cross compatible. Even if only 10% of a plugin uses Osmium I still think thats enough to save developers loads of time.

I believe ryantheleach said it best in the thread you referenced:

@ryantheleach

Pore is substantially different from Phoenix.

The design of Phoenix is basically just an abstraction layer over both Sponge, Spigot and potentially more.

Pore was flawed in that it was trying to make Bukkit compatible events over the Sponge events which just wasn’t going to happen as they are fired in different places.

An abstraction layer like Phoenix has the possibility of succeeding, but needs a solid team behind them.

WorldEdit, CommandHelper, CraftBook, NoCheatPlus, are several plugins that have used abstraction layers successfully to work over multiple API’s or Minecraft internal versions.

That said, There probably is several others doing the same, WetSponge comes to mind as one I’ve seen on Spigots side that supports Sponge. There are probably more.

As for people that go, “Please just support Pore”

Pore was doomed, Phoenix isn’t, provided they can stay maintained, and maintain trust.

Also

@pie_flavor

there would be no point whatsoever to an Osmium plugin which only works correctly on one implementation

If Osmium plugins only worked correctly on one implementation then clearly the project would be an utter failure because the whole point is to make it work so that plugins are cross compatible.

@pie_flavor

If you invested your development energy on maintaining Pore, and got flagship Bukkit plugins to a working state with it, you would get an actual audience

All useful flagship Bukkit plugins already exist or have an alternate Sponge version so I don’t really see what use Pore even has anymore. I’m sure you could also agree that a better solution to that problem would not to maintain Pore, but to have a larger developer community making more Sponge plugins.