When will Bukkit be updated for Minecraft 1.6?

Discussion in 'Bukkit News' started by EvilSeph, May 26, 2011.

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

    EvilSeph Retired Staff

    Staff Update - July 1, 2013:
    This thread is not from 2013. This thread is about the 2011, BETA version of Minecraft 1.6. There is no ETA for the 2013 Minecraft 1.6 update, as always. Please do not ask staff about when an update will happen, as they have no estimate for you. Again, this thread is not relevant to today's update.

    Update 2 - June 23, 2011 at 9:12PM EST:
    New Recommended Build #928.

    This Recommended Build addresses a few API issues and provides Plugin Developers with more events to work with, allowing more awesome plugins to be made. Unfortunately, this new RB WILL break some plugins (mostly plugins that deal with controlling a player's movement - details can be found near the end of this announcement). As always, please be sure to backup your server before updating just in case!

    See this post for more information.

    Update - May 30th, 2011 at 5:55PM EST:
    Since the release of Minecraft 1.6, we've seen quite a few rapid-fire bugfix updates from Mojang addressing issues the community has noticed and reported back on. While we're glad Mojang are on top of things and getting updates out there quickly to improve the community's experience, this does result in extra work on our part since we have to re-do some of the work we've completed for the previous update. As a result, I made the decision to hold off on getting a build out for Minecraft 1.6 until we were able to evaluate the update and decide if that is what we feel we should do or not.

    Over the weekend, that is what we have been busy doing. Unfortunately, I was out of town and unable to handle the situation as much as I would have liked, leading to a lack of communication on our part with you guys, our community. Nevertheless, my team was happily and diligently working on the update and in regular contact with me. Still, I would like to apologise for our lack of communication, I simply was not in a position to do so.

    That being said, we have noticed a few issues with the update that we've been able to address, so we are leaning towards bringing out a build for Minecraft 1.6.5. Though this build may not address all the issues we've found, it is still usable and produces a playable server with a decent experience. However, I am not yet sure if this build will qualify for recommendation.

    Please bear this in mind when using the build: it is not fully supported (though we welcome detailed, useful bug reports) and not recommended (we can't guarantee stability) to use. There are some Minecraft vanilla issues that Mojang need to address that are beyond the scope of our project to fix and we are still touching things up (like Nether/multiworld support).

    If you want to use the build we'll be pushing soon, please backup your server and make sure you understand the risks before doing so. Once again, we cannot guarantee that it won't eat your cake or spawn tiny creeper babies that take over your world.

    --------------------------------------------------------------------------

    As I'm sure we're all aware, Mojang released Minecraft 1.6 today (Thursday, May 26, 2011) around 5AM EST and we've been hard at work getting a build out that is compatible with Minecraft 1.6 out. Since the release, Minecraft has seen quite a few small bugfix updates addressing some unnoticed bugs and we've pretty easily kept up with them. Unfortunately, there appear to be some issues with the update that is making the game unplayable for SMP players, so we've decided to wait for a bugfix update before we recommend any builds.

    Will there be a CraftBukkit for Minecraft 1.6?
    Given the reports of showstopping bugs present in 1.6, there's a high chance a new bugfix update for Minecraft will be out tomorrow or even several times this week. As a result, it is unlikely we will be releasing a Recommended Build for 1.6 until we have something stable to work with.

    That being said, we recommend everyone stay on 1.5 for a while until the showstopping issues are fixed and we can get a new, stable, compatible build out.

    You can already get CraftBukkit for Minecraft 1.6.4, but it is unsupported and not recommended.

    I'll be scouring the internet for further reports on how Minecraft 1.6 is performing, but preliminary research and our own testing has revealed it as unplayable due to chunks sporadically loading or not loading.
     
    jeussa, Azell, khamseen_air and 34 others like this.
  2. Offline

    Schro

    @maystorm
    yea there should be betatesters for the patches. oh wait.
    Right now you are betatester and have no claim on a working game at all, that you paid money before 1.0 was ultimately your choice. Just that the current update didn't fit the current hype doesn't mean mojang did anything wrong.

    No you are not whining, you just don't understand the concept of betatesting.

    Sure this patch angered those, who aren't experienced with betas, but whatevs.
     
  3. OK.I hope that a recommended bukkit build for 1.6.4 will be done quickly-just like everyone of us[zombie]
     
  4. Offline

    sfxworks

    It would be amazing if all the kids didn't flock to my sever...
    (google "minecraft server 1.6 compatible)
     
  5. Offline

    Kazer101

    YA no i dont think its a 1.6 prob cuz im runing the 1.5 version and im having that prob also. i have to save the server like 2 times every 10min for my server not to have block lag.
     
  6. Offline

    Mordenkainen

    I do software RDT (Research Design Test) for a living.

    What we have here is not a Beta Test.

    This is how software design works:

    DVT: Development Verification Testing
    All new features are tested, one by one, as they are developed to ensure they work properly. This ensures that each new feature works with the EXISTING code base without issue. There will be several rounds of DVT, one for each new feature and/or bug fix.

    Integration test:
    All fixes and new features are put into a single build and tested together to ensure that they do not conflict or interact together in a bad way. There may be several rounds of this until all new features and fixes "play nice" together.

    (If an Alpha test is going to be done, it happens here)

    Regression test:
    All features and functions of the software are tested to ensure the new changes do not impact existing functionality. New test cases for new features are developed and added to the suite of tests for the next regression. Regression test will be repeated until no new issues that may cause data loss, or inability to use the software are found, and all existing issues of these types have been corrected by development. All known issues that have not been deemed data loss or showstoppers are documented in a Beta Release Note document.

    Beta test:
    The software and known issue list are given to Beta testers to abuse and exercise in ways the regression test may not have. While beta is ongoing, the previous 3 cycles repeat to generate new Beta code to fix remaining issues, as well as new issues found during beta.

    Release:
    Beta is done and all major issues have been addressed or workarounds documented. Software is released for general consumption.
    -----------------------------------------------------------------------------------------------------------------

    This is standard industry wide practice.

    Given the scope and nature of the problems in the 1.6 release, it is NOT Beta software.

    I appreciate the work that Mojang has done, but they need to tighten up the development and testing practice they use for their software as it is obviously well below the acceptable standards for a commercial company in the software industry.

    And no, I am not complaining, escapes do happen. I'm just pointing out to the people who say "But it's Beta" that even beta software is expected to perform to a higher standard that what is seen here.

    Morden.
     
    Plush Ninja likes this.
  7. Offline

    maystorm

    Jesus Christ! I am in the software industry for three decades now. You don't have to tell me what beta testing is all about. lol

    The point is: The software vendor should also do some beta testing. Beta software means that the software still has some bugs but does not mean that it doesn't work at all. lol

    And normally nobody pays for beta software. And if a vendor asks for money he should do some work on his own...
     
  8. Offline

    Bman212121

    I feel sorry for the server hosts who have to listen to users complain about updating. It would be nice if there was a client side mod which would intentionally break the updater so people wouldn't be tempted to download the update. I do know that if you have the older launcher without the web login page on it you won't get a choice, so they also need to get the latest .exe or .jar launcher.

    That said IMO if you already posted this information and told them to not update, it's like darwin at it's finest. I'd rather play in an empty server than a full one with a bunch of people who can't follow directions as they probably cause you a lot of other headaches as well.
     
    BSkup and LegendarySandwich like this.
  9. Offline

    evilMonkey

    I don't usually post on the forums, but all I really have to say is this:

    You don't have to play. You don't have to like the releases. For those of you who bought Alpha, you get all updates free for life. Don't like what's going on? Come back in November.

    For those of you who bought Beta, you get the full game free when it is released. Don't like what's going on? Come back in November.

    @Mordenkainen Mojang doesn't have to do anything anyone here says.

    Also, I'd like to point out the Terms of Use, Paragraphs 1-2:

    Lastly, I've said it twice already. Don't like what's going on? Come back in November.
     
  10. Offline

    TimeDeatH

    Wow, I can't believe with the 20+ plugins I have, not one of them was broken during the update, but im not totally updating until there is a stable version.
     
  11. Offline

    asdaarg

    There are whiners and whiners about whiners. If I buy something that doesn't work, even if its in the terms of service that it doesn't have to work, I can whine about it. Its not the terms of service that I can't. If people couldn't whine about products they buy they wouldn't be able to communicate to each other what products are useful to buy and what are not that useful. And producers would have no idea what to do to make their products sell better.
     
  12. Offline

    Carnage104

    You'll all live, im sure, no matter whose side ur on. Shit Happens, i dont care who to blame.
     
  13. Offline

    evilMonkey

    @asdaarg Just because you can whine, doesn't mean anyone will care; which seems to be the consensus here.
     
  14. Offline

    asdaarg

  15. Offline

    Lupo cani

    ahh, it was the map that made my game crash. I was really confused why the chunks stopped loading. But still, its better than nothing.
     
  16. Offline

    Bman212121

    I think the main thing is simply they need to change how they handle releases. It's fine if Notch wants to give everyone access to bleeding code so they can test it and find all of the issues. Just by looking at the bug list on the wiki page there are obviously a lot of people who do that already. If they handled the releases similar to the way bukkit does where you don't get untested code unless you go looking for it. Wait until the community says the update works okay before you push it out to 2 million clients. It would save the majority of the headaches we see and he could still blindly hit the commit button without having to do extra work.
     
  17. Offline

    Drei Gyuu

    Amen, I wish everyone would think like this guy.
     
  18. Offline

    CoZmicShReddeR

    Normally I would blindly update all of our servers but am glad this time I left our current 2 servers running 1.5 and the third server for the 1.6 update for people who want to try out the newest update. And I am headed to E3 this year not to do anything special but I am thinking it's not a bad thing Mojang is going there as I am sure they can just as easily fix and squash bugs in their hotel rooms as it is in their offices. Might even do them some good to have a change of scenery...
     
  19. Offline

    sfxworks

    Yes. Mine.
     
  20. Offline

    maystorm

    Those terms of use -- as any other out there in the world of software -- are just there so that nobody can sue them if they really decide to cancel the whole project before it is finally released.
     
  21. Offline

    nonentity

    That's an interesting definition of "consensus" you've got.

    I'm not (directly) whining about bugs. I'm not experiencing any bugs, because I don't allow my main systems to upgrade any more without first seeing what people are saying (having been burned too many times when the upgrades were not optional). So, I really don't care if you yell "beta" or "as-is" at me, because I've already done more than my share to protect myself.

    However.... software isn't usually released to the public with severe issues that are run into the moment people try to put that software to normal use, even in a beta test. These are the kinds of warts that professionals do their best to prevent from ever reaching the eyes of the public. Endless debate on the definition of "beta" or the terms of purchase does nothing to change the fact that it just looks unprofessional. The lack of an easy way to downgrade once you've committed to a new version just makes things worse (yes, there are methods, but they aren't easy... especially for someone who is new to Minecraft and might not even know where the jars get stored). Yes, beta software is going to have bugs. Yes, sometimes those bugs will end up being showstoppers. No, that doesn't excuse putting out an untested release right before the person who would fix those bugs has a previously scheduled commitment.

    Notch clearly gets excited by adding bullet points to the game - a bug fixed here, a feature added there, etc. That's a great thing in a developer. I just wish he were a little more diligent in making sure that code was clean before pushing it on his customers.

    And on a completely different note, I absolutely love the work the bukkit folks are doing to help smooth over the rough edges. The quick responses to notch's updates, and the creation of the "recommended" system, are doing a lot to make things at least bearable for those of us who are dealing with unsupported mods on top of the issues with the vanilla releases.
     
  22. Offline

    Xanadar

    Please not another "MY OS IS BETTER THAN YOUR OS" bullcrap. Save that for another topic at least?

    I am going to run my main server on both 1.5 and 1.6, let people decide which they want.I do have a feeling that sticking to 1.5 will be the choice after all. Build 814 has been solid for about 15 hours now... but the issues I have seen are not related to CB as much as Minecraft itself.

    Most of my plugins are workable, as well. There are a few glitchy things, but nothing game-breaking. The ones that don't work at all are Command Book and Citizens, for now.

    Good luck to the bucket team, you guys are a dedicated bunch.
     
  23. Offline

    noahwhygodwhy

    they did fix lots of bugs but they made a lot of the main ones worse.

    Can i use this as my essay? jk, but how long did it take you to write that?

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 16, 2016
  24. Offline

    Rich Boos

    I held the same opinion during the 1.5 upgrade - I just wanted Notch to not turn on the upgrade prompt for end users (or a beta of the beta). I was flamed beyond belief. "Beta this, Buzzword this" - it is so obvious who knows their stuff and who will buy into any train of thought just because of a buzzword.

    Agree 100%
     
  25. Offline

    Mordenkainen

    Oh, I'm well aware of that. I was not making a suggestion to Mojang, just clarifying what the term "Beta test" implies in regards to the standardized software dev process.

    Obviously Mojang is not using this process.
     
  26. Offline

    beatcomet

    Well I tried CB 814 and it works pretty well (no plugins but still).
    CraftBukkit FTW
     
  27. Offline

    Schro

    Aaand where exactly is the problem if the vendor fixes the new major bugs right after the update? I personally didn't feel a world of agony because the patch had bugs.

    He does work on his own. Did you see the bugfix list of the release?
    If you are too lazy to do your part, the actual "beta testing", then wait a week after each release.

    No, beta testing is NOT "lulul fun tiems before the release". Your job is to play and find bugs. And if you find bugs, then you don't whine, you report them.

    Well ok, on the other hand, Mojang could have waited another month to sort out the bugs themselves, so that the beta testers don't get angry finding bugs in a beta. *coolface*
     
    TheDeejay likes this.
  28. Offline

    maystorm

    I do. Others do. The only people not doing are obviously the developers themselvers.

    Don't worry, I do my part.

    This is exactly what I have written. Please read my posts more carefully next time. However, Mojang has not been fixing the critical bugs after the update. This is the only thing I am criticizing, not the fact that there are still bugs in a Beta release.
     
  29. Offline

    gonk

    Thanks for the update! You're doing a great job!
     
  30. Offline

    Lioele

    Thanks for the update! I appreciate your hard work! :)
     
  31. Offline

    Nuinbot

    *nods head* Thanks for the update! Bukkit crew is the best!

    To all the whiners: *insert obligatory beta comment here* ;)
     
Thread Status:
Not open for further replies.

Share This Page