» Custom Server Core «

[taber]

EDIT: By "core", I mean a replacement to CraftBukkit/Spigot

Preface:
The world of Minecraft server cores is barren and dry. Spigot works perfectly fine for what everyone does with their servers, and the amount of plugins that have been developed for the API is insane. However, in recent years more and more different forks came out that optimize the "already optimized" Spigot. I have an idea. What if, there is one core that does it all. With an extremely modular API, an extensive "plugin" database, a built-in web panel, and a place where everything is modifiable.

Introducing TaberCore. (If you did not read the Preface, I would like you to.)

TaberCore is a new take on the non competitive market of CraftBukkit/Spigot cores. There are many different variants of Spigot especially, since the so-called better CraftBukkit isn't as good as it can be. For example, PaperSpigot and TacoSpigot. The new BeerSpigot seems to be a popular choice among Factions servers as well. I had an idea though. What if a new and completely redesigned server core came to the world.

"But thetabergroup, Why on earth would you do that? Everyone is doing fine and dandy with Spigot and the existing forks!" Well, for one, I love to waste money on projects that could be revolutionary. TaberCore would be a standalone jar, that would not require a batch file to start. All that would be required is a double click on the jar file, and a GUI would appear. Albeit may be laggy, there would still be support for a terminal window. TaberCore would be nothing like Spigot internally, and would be an entire new API programmed from the ground up. It would be easy to convert a Bukkit API plugin over to the new Taber API, but would take some time. This may be a complete flop, since there is no need for this, but just take it as an idea. If anyone is willing to maybe go through with this new idea, let me know.

Sam Taber#5620
(Discord)

You can make fun of me all you want, but I just wanted to throw this out there into the world just so others can hear my idea.

Thanks,

Sam

 

[Norska]

This would be entirely pointless

 

[Harry]

Most people associate a server core with an actual plugin - not a standalone server launcher.

What would this 'core' be able to do over PaperSpigot and TacoSpigot? Why would people use this?

What's the point of creating a whole new API for plugin development, when the Spigot/Bukkit API is so widely adopted?

Just seems like a big waste of time to me, but :/

 

[taber]

This would be entirely pointless

I want to drop money on a custom core at least for my network. I want everything to be entirely custom, down to the API that is used to design the "plugins". It is entirely pointless, however I still want to do it. Initially, the post was aimed at the public market. Now that I think about it, I believe not entering the Spigot land would be a better thing to do. I just want a brand new API and custom core, that's all.

Most people associate a server core with an actual plugin - not a standalone server launcher.

What would this 'core' be able to do over PaperSpigot and TacoSpigot? Why would people use this?

What's the point of creating a whole new API for plugin development, when the Spigot/Bukkit API is so widely adopted?

Just seems like a big waste of time to me, but :/

This would not be a server launcher. There would be a built in launcher for this core. This core would be associated with plugins that would be made by anyone would is willing to develop for the API. Also, official plugins would be made by my development team for my current network. The point behind creating a whole new API for plugin development is because of all the classes that Spigot carried over from Bukkit. From my point of view when programming a Bukkit/Spigot plugin, When I try to import the "ChatColor" class, there is the Spigot ChatColor class and the Bukkit ChatColor class (This is just an example.) This core would be fairly more capable when it comes to optimization in game. People pay up to 2,300 dollars for a cannoning jar. My mission is to combine everything the hosting community is looking for into a modular and highly configurable core. Programming plugins would be extremely easy, since conflicting classes wouldn't exist, there would be official and extensive documentation on how to develop for the Taber API, and a good group of trusted developers willing to help other people out.

 

[Harry]

From my point of view when programming a Bukkit/Spigot plugin, When I try to import the "ChatColor" class, there is the Spigot ChatColor class and the Bukkit ChatColor class

So? You just import the correct one - nothing to worry about.

This would be an insane amount of work, and capital, which could be spent elsewhere to better your server.
Just look at the Javadoc tree: https://hub.spigotmc.org/javadocs/bukkit/overview-tree.html

I'm still confused about why you still describe this as a core? It's not like you just drop it into the plugin folder and off you go? Unless I'm missing the point of this entire thread?

 

[taber]

So? You just import the correct one - nothing to worry about.

This would be an insane amount of work, and capital, which could be spent elsewhere to better your server.
Just look at the Javadoc tree: https://hub.spigotmc.org/javadocs/bukkit/overview-tree.html

I'm still confused about why you still describe this as a core? It's not like you just drop it into the plugin folder and off you go? Unless I'm missing the point of this entire thread?

Sorry, I didn't understand that the term "core" meant a plugin core. By core, I mean a replacement to Spigot/CraftBukkit.

 

[NahuLD]

 

[Mark4234]

You can easily fork a spigot and make a custom api with stuff like player.getPing() player.getVersion() player.getRank() and all that stuff if that's what you wanna achieve. I didn't understand your point clearly.

 

[taber]

You can easily fork a spigot and make a custom api with stuff like player.getPing() player.getVersion() player.getRank() and all that stuff if that's what you wanna achieve. I didn't understand your point clearly.

I want to make an entire new system. with nothing like "Bukkit.getServer()". etc. Nothing can be bukkit, or spigot. It all has to be remade, from the ground up.

 

[Norska]

I want to make an entire new system. with nothing like "Bukkit.getServer()". etc. Nothing can be bukkit, or spigot. It all has to be remade, from the ground up.

There is simply no point in making something like that, you pretty much want "spigot but not spigot", in the end it's going to be the same and I doubt you (or anyone else) would even have the funds and be willing to spend them on something like this.

 

[taber]

We can’t garantee full plugin support

Obviously it would be complicated and overwhelming to port Bukkit over to TaberAPI. Since internally nothing is the same.[DOUBLEPOST=1556299977][/DOUBLEPOST]

There is simply no point in making something like that, you pretty much want "spigot but not spigot", in the end it's going to be the same and I doubt you (or anyone else) would even have the funds and be willing to spend them on something like this.

Secured an investor. Although it may sound idiotic, I find it more or less as a long term investment that may or may not pay off in the future.

 

[taber]

Happy 2019 where you waste money to do already done stuff!

Yep.