When will CraftBukkit for 1.4 be released?

Discussion in 'Bukkit News' started by EvilSeph, Oct 24, 2012.

Thread Status:
Not open for further replies.
  1. Offline


    Update (Oct 27 @ 10:24 PM EST): We've just pushed out our first CraftBukkit for Minecraft 1.4.2 development build, see this post for more information.


    With the Minecraft 1.4 release date fast approaching, a lot of people are wondering when we will be releasing a CraftBukkit Recommended Build for Minecraft 1.4. We hope this short announcement will answer those questions.

    Due to the rapid release of preview builds for the impending 1.4 update, we are unable to guarantee that we'll have a compatible CraftBukkit Recommended Build out in time for the release of Minecraft 1.4.2. Although we started working on the update immediately after the Minecraft 1.4 preview was made available to the public, each new preview build leads to delays in our update process as we, essentially, need to start over with each one.

    In the past releasing a Recommended Build has caused apparent confusion within the community, as a result for this release, and moving forward, we will follow the "Dev -> Beta -> Recommended Build" release methodology. We are going to release a Beta build as soon as we can get a stable build devoid of any significant bugs.

    As we have done a significant amount of important work on CraftBukkit 1.3.2 builds, we have promoted a new Recommended Build recently. This was done so that people have a reliable, stable build to use until we can get a 1.4 compatible build out and so that everyone who relies on Recommended Builds are able to take advantage of all the fixes, improvements and so on we've done since the last 1.3.2 RB.

    Thank you for your patience, understanding and continued support; we greatly appreciate it!
  2. Offline


    Looking forward to 1.4, great job bukkit team!

    regarding the mod-api that was going to be in 1.4, whats the target version now for the mod-api?
    Nedmaster, wwwnic, apie382 and 6 others like this.
  3. Offline


    apie382 likes this.
  4. Offline


    sounds great I think all people can understand that!
    apie382 likes this.
  5. Offline


    Nedmaster and apie382 like this.
  6. Offline


    This is great to know, thanks for putting up a more stable version of 1.3.2 for the meanwhile!
    And take your damn time!
    bigdan3434 likes this.
  7. Offline


    I heard 1.5, though don't quote me on that. I don't remember where I heard it and can't cite it.
    1mpre55 likes this.
  8. Offline


    I want to understand something. Why do you guys always have to start over for a new craftbukkit? Why can't you just build on what you've already programmed? And why is there NEVER any backward compatibility between version i.e. 1.3 to 1.4? Why can't they work together so we don't have to wait? This is such a down fall of Mojang and bukkit that the two parties can never seem to work on the same level and make it backward compatible. Seth please help me understand this.
  9. Offline


    Thanks, I now have something to link to! This is going to be on my clipboard for a while.
  10. Offline


    I don't understand either why minor updates (x.1, x.2) are backward compatible, but major updates (1.x, 2.x) aren't.
    Tadas159 and kian123 like this.
  11. Offline


    Thanks for the heads up!

    - ThaSource Gaming
  12. Offline


    Instead of guesses, I would much rather wait till someone who knows responds, no idea why you would respond unless you did....
  13. Offline


    The major updates are usually bugfixes that aren't gameplay-altering. Major updates have new stuff in them, usually. An example, the new beacons that are coming out, or the Wither Boss.

    The Wither Boss is likely a new, unused entity ID - thus, a client pre-dating the Wither Boss would throw an NPE.
  14. Offline


    Notch didn't have that in mind when he originally made Minecraft. Nowadays it's very hard to implement without breaking a bunch of stuff. 1.4 network protocol is a lot different from the 1.3 server protocol. Just look on the protocols wiki (http://www.wiki.vg/Pre-release_protocol)
    oftendeaddotcom likes this.
  15. Offline


    Good news! Thank you!
  16. Offline


    This is getting old that Mojang and bukkit can never work in reverse with each other and I've had enough and it's bad programming. In a government systems they make sure all the software will work or they don't release anything until it does. It's unfair to the users and developers for it to work like this and this has got to change now! We've gone on long enough. Mojang needs to wait until bukkit updates and they are sure there ready and give bukkit special rights to the early build versions of minecraft. We all depend on bukkit and because Mojang needs to get that and understand they when two software's aren't going to work they need work closer together as ONE group.
  17. Offline


    Thanks for the new naming scheme!
  18. Offline


    To be fair bukkit is not technically a part of mojang, even though its main leaders work for mojang. Bukkit is a separate entity, a third party, that does not get paid for what it does except through donations. Be happy it is there and not the alternative, plain minecraft... That being said, mojangs answer to this issue is Mod-API, though it seems it have been delayed.
    Bobfan, Unscrewed and 1mpre55 like this.
  19. Offline


    Cant wait until the full update :)
    thanks for keeping us updated :)
  20. Offline


    I understand the issues with maintaning backward compatibillity in the new code and I understand why The Bukkit Team has to start over with every release from Mojang.

    I just don't understand why the Minecraft client launcher can' ship with say two jars: the new version and the previous major version (or have an option to download a previous version it if nedded). In doing so, the launcher can check the serververions and load the appropriate jar version prior to connection to the server. Yes, the minecraft client/launcher would be bulkier, but maintain backward compatibility with the previous versions. Essentially a build in, automatic version downgrader if you will. Jeb the wizard could implement that in a day...
  21. Offline


    And I am thankful but the third party should be a part of Mojang and work as one. I know this API stuff is involved but even still this is still a short coming of said issue. I wish this could be better put together and they would build on what version they have made instead of starting over everytime which is another short coming of Bukkit. I love Bukkit and believe in what it does but for goodness sake this really could be better if Mojang would just wait for third parties to catch up and have Mojang release it only to the devolpers before it goes public.
    Quester and Unscrewed like this.
  22. Offline


    If a third party becomes part of Mojang, it's no longer a third party.

    Mojang, a multimillion dollar company, can't just wait around for these small developer teams/nonprofit organizations (such as Bukkit) to 'catch up' and release stable builds.

    And how would Mojang be able to differentiate between developers and the public? I could say that I'm developing a mod, get the build, then release said build to the public. They can't release it to only a few, preapproved developers; they're not going to spend all of this extra time and energy trying to release stable builds only to certain people before the actual release date.
  23. Thanks for 1.3.2 updates!

    You´re doing a great job Bukkit team .
    Looking forward to 1.4.x.
  24. Offline


    Thanks for the update, EvilSeph!

    And especially for following the "correct" release methodology this time, which is absolutely the right way.
    IIRC the reason for pushing the ReleaseBuild out too soon last time was so that users of third party server hosts (like nitrado) could update too, because their provider only allowed to update to those builds. But tbh they really should change their regulations instead of you changing a release system which is really important to be correct ;-) So I'm glad that you changed that again!

    As every time I'm looking forward to the first beta, so we could try to check all of our 50 plugins to be compatible ;-) Keep up your good work guys! I hope I may help with some bug reports or pull requests as soon as I can.
  25. Offline


    Calm down. It will be a 4-7 days or something. Read a book.
  26. Offline


    Your whole team has done an awesome job keeping pace and ensuring fewer bugs are present within craftbukkit Builds. Everyone on my server including myself look forward to the next recommended Build release.
  27. Offline


    Good Luck !
  28. Offline


    As of right now, Yes it was set to 1.5 (as the other poster thought)
    Although it was originally meant for 1.3 until it was pushed to 1.4, so who knows if they wont just push it again..
  29. Offline


    Brilliant job guys! Bukkit has always been the life blood of MineCraft! Well..... ever since Hmod went inactive.... :rolleyes:
Thread Status:
Not open for further replies.

Share This Page