CraftBukkit for Minecraft 1.7.9 DEVELOPMENT build is now available!

Discussion in 'Bukkit News' started by EvilSeph, Apr 17, 2014.

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

    EvilSeph Retired Staff

    A new CraftBukkit for Minecraft 1.7.9 DEVELOPMENT build is now available!

    As of this post, we've shifted development over to Minecraft 1.7.9 compatibility and now have development builds available. We strongly suggest that you only use this build if you would like to help us get a Beta build out sooner and are experienced with using unsupported development builds.

    Minecraft 1.7.6+ contains important changes to enable support for the upcoming switch to UUIDs and name changing. We strongly recommend you read our previous article on the switch to UUIDs to help you understand what it means for servers and how to prepare for Mojang allowing name changes by Minecraft 1.8.

    WARNING: Minecraft 1.7.9 is an update that requires clients to update before being able to connect. This means that players will not be able to connect to your server if they have not updated to at least Minecraft 1.7.6.

    Will plugins break with this build?
    Minecraft 1.7 is one of the most involved updates to date, with Mojang having touched a reported ~220k+ lines of code. As a result, a significant amount of the code base has shifted making it difficult to ensure any stability with regards to our API. That being said, it is difficult to determine if plugins will be breaking with our 1.7.x update and the state of the API in our earlier development builds should NOT be relied upon in any way.

    What is a Development Build?
    A Development build is provided AS IS and COMPLETELY UNSUPPORTED. You should only be running these builds if you are completely aware of how to properly make use of them. Support requests of ANY KIND will be removed without warning. If you have to ask where or how to get the development build, you should NOT be running it and posts of that nature will be deleted.

    Known Issues:
    • None
    Download the development build CraftBukkit 1.7.9-R0.1-SNAPSHOT here
     
  2. nice work.
     
  3. So many changes.
     
  4. Offline

    Dunkelfalke

    Still hope for a stable 1.7.x
    Netherless "Great Job" :)
     
  5. Offline

    LarsNitro

  6. Nice work!
     
  7. Offline

    bardya

    Reporting bug:
    I use TCAdmin. Every craftbukkit version has worked fine before, now with 1.7.9, I get a "Connection timed out" error when I or anybody else attempts to connect.

    *EDIT* Nevermind, I was an idiot and I was downloading bukkit, not CraftBukkit. It works fine on TCAdmin
     
  8. Offline

    ThaSourceGaming

    Watch Mojang release a new version just because Bukkit is keeping up. I'm telling you guys, Mojang is trying to outdate bukkit on purpose!
     
    Boeing747guy and DrPyroCupcake like this.
  9. Offline

    AstramG

    Is there something wrong with Scoreboards in this build? Some of the previous builds gave me a bunch of scoreboard errors for a scoreboard that was working fine before.
     
  10. Report that to the TCAdmin team.
     
  11. Offline

    General

    I doubt that, seeing as Bukkit is pretty much free publicity/revenue for Mojang. Doesn't make too much sense to oust your own assets when they can only do you good. Unless, that is, you were being sarcastic in your statement.

    That's probably a hidden way of saying "if you're not willing to read, get out of here" - whether intentional or not, I like this message. :p
     
  12. Dinnerbone is in this forum... SO... He works at Mojang
     
  13. Offline

    xbenas

    UPDATES AFTER UPDATES AFTER UPDATES AFTER UPDATES AFTER UPDATES AFTER UPDATES AFTER UPDATES AFTER

    I am seriously waiting for the times when Minecraft would stop updating, for like, a year. Then it would be nice to have some stability, so CraftBukkit and plugins could prosper.

    Anyways, thanks for the quick update! Nice work! [diamond]
     
    Jozeth likes this.
  14. Offline

    ThaSourceGaming



    So? cool.
     
  15. Offline

    LarsNitro

    ThaSourceGaming Dinnerbone is one of the (if not the) main founder(s) of Bukkit, and he is responsible for most of the internal rewrites that cause the updates.
     
  16. And he still is not the only one working on it. So better say: THANK YOU BUKKIT TEAM FOR YOUR AWESOME WORK GUYS <3
     
  17. Offline

    ThaSourceGaming


    Okay, your point is? anyone can register on a forum.
     
  18. Offline

    LarsNitro

  19. Offline

    Lyndon321

    Has anyone been running the 1.7.9 Dev builds? Wondering how stable it is even though it is a dev build.
     
  20. Offline

    wrecktify


    I am. I notice a few bugs but its worth dealing with when no new players come to your server because of the protocol change. Also make backups every time you update anything. Plugins are beginning to convert to uuid instead of player names. I use towny and essentials released a dev version to convert to uuid. Well it also converted all the towny town & nation bank accounts and broke them. Be very careful when updating and backup EVERY time.
     
  21. I see people having trouble with whitelists.
     
  22. Offline

    wrecktify


    They fixed those problems in one of the newer dev versions. same with banlist issues
     
  23. Huh? If you're not on the whitelist, you can't join in the first place.

    I have 300 people on my whitelist.
     
  24. Offline

    spanker

    OK, this is starting to get ridiculous. i'm grateful that the Bukkit team vowed to release updates more often and more at parity with official Mojang releases, but i was expecting that they'd actually finish updates instead of just moving on to the next one. the last six months has just been an endless stream of dev and beta builds: 1.7.2, 1.7.5, 1.7.8, and now 1.7.9. will we even see a 1.7.x stable at all? i only run stable releases on my server, so this approach really isn't any better than the old days of waiting months for updates.

    is there any project management in action here? yes, i'm very thankful for everyone's efforts, but those efforts are wasted if no one gets to use the software! the point of updates are to update, not just for coding exercises.

    i have been planning on making a donation upon the release of a stable 1.7 (yay, a big update! take my money!), but i guess that will have to wait.

    - spanker
     
  25. Offline

    TnT Retired Staff

    spanker
    You seem to forget the two Beta builds that have come out for 1.7. These are considered stable builds.

    While we try to get our Recommended Builds more often, it is a lot of work. With Mojang's releases coming faster and faster, we're left with the difficult decision of leaving server owners without any build to use with new releases and working toward an RB, or updating to new releases and starting fresh with an RB.

    While you may like the idea of us pushing toward an RB instead, someone else will want us to push toward a new release. We cannot please everyone, so we do what we can with what we have.
     
    Black Hole likes this.
  26. Offline

    Menissalt

    TnT
    I have to agree with you. I realize just how much work you guys have to go through and the Mojang releases have been relentless in the build-up to 1.8. Also, with 1.7.5+ (1.7.4+?) they have completely changed how users are managed on servers. I'm sure there will be a ton of demand for 1.8 and that means working on this new system now rather than later.

    Users are often unaware of server admin's woes and are very demanding, and server admins can just as easily be unaware of developer's woes.

    spanker
    Give 1.7.2 a shot, I think you will be pleased with just how well it runs. Just make sure to update your plug-ins accordingly.


    Dev team, keep up the work; we all appreciate it. Excited to get a 1.7.9 beta, not excited for all the potential plug-in errors due to the new user system.
     
  27. Since you start over reverse-engineering each Minecraft release, it might be better if you manage the releases in parallel in your code management system. i.e., start a new project with each new Minecraft release. As an example, this would allow you to release 1.7.2-R0.3 as a Recommended Build without interfering with 1.7.4 and subsequent releases.

    I don't mean that you should actively maintain multiple releases. But having parallel code management paths would allow you to go back and take a Beta build with significant mileage under it and create a Recommended Build using essentially the same code. This would mean very little additional work but would add a lot of value to users like spanker.
     
  28. Offline

    TnT Retired Staff

    Bobcat00
    That suggestion assumes we have limitless time. You underestimate the amount of work that goes into working on CraftBukkit and Bukkit.
     
Thread Status:
Not open for further replies.

Share This Page