Discussion in 'Bukkit Discussion' started by mattrick, Nov 5, 2013.
They left too
They couldn't handle having deadlines.
lol jk jk
If you've seen the size of craftbukkit, that thing is 11MB. Minecraft is barely 5MB. Disclaimer: I don't know much about coding but I'm saying what I do know and I am not bukkit staff/dev.
Dinnerbone has said (not going to quote) that they've changed over 500,000 lines of code for 1.7, added so much and yet 1.7.2 is still barely 5MB. Craftbukkit will likely have to add and change that or even more code(Don't trust me on this, I suck at viewing source code).
tl;dr There's a lot to dig up, so it will definitely take a long time.
I think its something to do with the plugin API they have to implement in. Of cource, Minecraft clients actually have to render.....
I run a Private Server using this free solution! Its really hard having to tell my friends to downgrade to 1.6.4 just to play on my server, but it is what it is. Don't blame the Bukkit Development Team because Mojang decided to change a lot of code. Even Minecraft Forge isn't updated for 1.7.2 yet so the only option is to be patient.
What the team is reading right now:
You would be suprised how easy it is to make a great vanilla server using command blocks.
I think I have seen this posted 3 places now.. so I will give you what you want... Hahaha that's so funny! There someone heard you you can stop saying it now
You know what Bukkit should do? Release an early development build. Tell everyone not to use it, except for testing. Allow everyone to report bugs, but restrict forum posts about it so that they don't end up with a ton of forum spam getting blamed for their servers getting messed up. I know that everyone will try to use these Dev builds, but let's just say it's their fault if all their servers get screwed.
that is basically what 'a normal' dev build does.
As easy at that sounds, the Bukkit team can't afford to have the entire website flooded with people saying "it r broked".
Bukkit team is having issues getting a dev build out, so I am talking about like early early stuff.
Early-early stuff that isn't a dev build, likely wouldn't function at all.
Separate names with a comma.