Minecraft Forge vs Bukkit, what does Forge have what Bukkit dont?

[terraya]

Hello Dear Community,

 

im asking myself, what does forge makes better then bukkit?

 

bcuz , i see ppl do "RPG" server on "bukkit" servers but why?!?,

 

i mean, on bukkit you cant add "custom armor/weapons/items" or ?

 

so where is the point

 

on other hand forge allow to do all this stuff but why does forge isnt as bukkit?

I mean the same stuff which you code on "bukkit" you can code them on "forge" aswell or am i wrong?

[Animefan8888]

You are correct, but on Bukkit you do not need to download anything to your client. And you can technically make custom blocks and items with vanilla. You do this with a custom resource pack for items, and for blocks in Bukkit it is a bunch of entity manipulation.

[desht]

Let me offer my perspective as a former Bukkit plugin dev, and now (relative newbie) Forge dev...

 

The big difference back when Bukkit/CraftBukkit appeared was that modding your client back in 2011 was a considerably tougher affair than it is today.  Coupled with the fact that there weren't many mods around then (the original Industrial Craft was announced in Feb 2011), the client modding scene was a little... specialist.  On the other hand, CraftBukkit was a pretty much drop-in replacement for the vanilla server, and it meant your players could just connect with their vanilla client - no hard-to-install client mods needed, no battling item ID conflicts or manually inserting classes into the client JAR.  Perfect for running big multiplayer servers; you got protection plugins to combat griefing, mini-games, RPG plugins - there's quite a bit you can do without adding custom items.  And as Animefan8888 alluded to, it did allow sort-of-custom items with a little server-side trickery - as it happens, I created a fairly extensive custom item framework myself: https://dev.bukkit.org/projects/sensible-toolbox

 

Things have changed though, for two big reasons: 1) Forge is here to stay, and it's a very capable system; as far as I can tell there's nothing Bukkit can do these days that Forge can't, and 2) it's really really easy these days to download a modpack and just start playing.  Of course, actually modding for Forge is still a lot harder than for Bukkit - you need to understand the client/server separation, you need to understand models & textures (and possibly some OpenGL), you need to peer inside the vanilla code on a fairly regular basis, and you need to accept that there will be pain when a major new MC release comes out (something Bukkit makes 99% transparent).  But that's for developers to worry about; players mostly need not care.

 

tl;dr When Bukkit came out, it was the obvious choice for a multiplayer server.  Nowadays, not so much - Bukkit (and its derivatives) are mostly around because of inertia these days.

 

[terraya]

Excellent answer so i think to stay on Forge makes alot easyer for me,

 

since i never realy learn java only through lookin at tutorials of minecraft coding and this forum is very special to me bcuz all their help

made me a small minecraft forge coder.

 

thanks@all for your answers and have a happy new year since i forget to say that here !

[jeffryfisher]

Excellent answer so i think to stay on Forge makes alot easyer for me...

 

Wow, over 150 posts with no karma, plus or minus ? That takes some special skill. Here, have a point 

[desht]

I agree, except for one thing: if you just want to write a server-side mod with Forge you don't need to understand the client-server difference or OpenGL any more than you do with a Bukkit Plugin.

Yep, very true.  The one thing Bukkit still has over Forge, then, is the version-transparent API (e.g. the 1.10 -> 1.11 ItemStack changes would be a non-issue for plugin devs).

 

Out of interest, what are your thoughts on Sponge (on top of Forge) as a server-side plugin API?

[gurujive]

forge is not against bukkit and bukkit is not against forge.

 

so there is not a "forge vs bukkit".