Closed deathcap closed 7 years ago
First one is useless for a server implementation, we need a version command. I think the second one was only done so they could override it for Pore's use. Though plugins could possibly use this to make their own custom APIs suited for their plugins on top of Bukkit. Third one seems good. 4th one seems only applicable to Pore. 5th is useful.
In my opinion, we should use only 3 and 5.
I took the first patch (committed in https://github.com/deathcap/Glowkit/commit/18d92a429a99d64e814858d59e444361fbeb20e3), it only disables Spigot's online API version check (queries https://hub.spigotmc.org/stash/rest/api/1.0/projects/SPIGOT/repos/) in /version
, which with Glowstone++ always fails (but we could re-enable it if we have a similar stash API for this project, at some point)
Oh, I didn't see that part, sorry.
Pore has since added three additional patches:
This ticket needs categorization on the waffle board.
Has this ticket seen any movement or has there been any action expected since the previous comment?
Closing due to Pore being dead, and the patches don't seem to add much for Bukkit plugins.
The Pore project (an implementation of Spigot's 1.8.3 update to the Bukkit API) has a handful of its own patches to the API, some might make sense to pull into Glowstone++'s:
https://github.com/LapisBlue/Pore/tree/master/patches
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.