CraftBukkit 1.2.5-R0.1 is now available!

Discussion in 'Bukkit News' started by EvilSeph, Apr 3, 2012.

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

    EvilSeph Retired Staff

    A new CraftBukkit Beta Build (1.2.5-R0.1) that provides Minecraft 1.2.5 compatibility is now available. Please only use this build if you'd like to help us get a Recommended Build out when Minecraft 1.2.5 is officially released and don't mind running a preview build to help us test things. For those of you waiting for a Recommended Build, you'll be happy to hear that we'll be getting one out tomorrow shortly after Minecraft 1.2.5 is released.

    Will plugins break with this build?
    Unless the plugin developers of your plugins have been keeping up with Bukkit development, plugins will most likely be broken due to the recent optimisation and cleaning of our code. However, if the plugins you use have already been updated to work with at least 1.1-R7 or at least 1.2.3-R0.1, then you should be fine.

    What is a Beta Build?
    A Beta Build is in between a developer build and a Recommended Build. These builds simply work and are promoted much more frequently than a Recommended Build. While we will do some testing before promoting a beta build, we will not be running it through our extensive test process. As such, there are no guarantees that they will not contain minor bugs. If we do find out they are broken, we will mark it as such on DLB and promote a new one. A beta build may contain incomplete API and new features but they should not interfere with running the build in any way.

    This particular Beta build, like every first Beta build for a Minecraft update, is primarily made available to help facilitate more testing coverage to bring us closer to a Recommended Build sooner. Please consider running this Beta build to give us a hand with discovering issues we need to address in time for the official release of Minecraft 1.2.5.

    Known Issues:
    • None

    For more detailed information on what is contained in this update, please see the changelog here

    Download CraftBukkit 1.2.5-R0.1 here
     
    Santar0, efstajas, Magnavoid and 5 others like this.
  2. Offline

    ArcheCane

    Great job guys!
     
  3. Offline

    RiotShielder

    That was FAST, thanks for this uber epic udate :D
     
  4. Offline

    slipcor Retired Staff

    Good job :)

    except the changelog, it has a holey ^^
     
    Technius and ArcheCane like this.
  5. Offline

    mrlwiggy

    Nice work guys! But I'm getting pretty pissed now because of the period between minecraft updates :( Slow down Mojang!!
     
  6. Offline

    RiotShielder

    I know right? Yesterday I finally fixed all my plugins and now we get a new update? Meh, I guess it's awesome for the people playing the game :p
     
  7. Offline

    mrlwiggy

    It doesn't look like too much has changed so most plugins should be ok :)
     
  8. Offline

    Jay98d

    Nice
     
  9. Offline

    Grizzmo

    Awesome release guys! Looking forward to the update :D
     
  10. Offline

    palisade

    The changelog page is broken btw.
     
  11. Offline

    Rytis

    Nope :p
     
  12. Offline

    HunterT

    Sweet, Hopefully not much will break!
     
  13. Offline

    MistaGhost

    Grate Updating to the Beta Build thanks for the quick update!
     
  14. Offline

    ThaSourceGaming

    Glad to see Bukkit update at quick paste :)
     
  15. Offline

    Sayshal

    Holy crap great job Bukkit!

    Since you now work for/with Mojang, can you whisper to them that these constant updates make Server owners & plugin developers die a bit inside? I mean, I know it's not your fault in any way, but even you guys must think that a 1.2.5 is a bit ridiculous. They should spend a bit more time checking for bugs, also this made me lol: http://www.minecraftwiki.net/wiki/Version_history/Development_versions#Minecraft_1.2_Snapshots

    Confirmed bugs in the 1.2.5! And they'll probably release it anyways!

    +100 Bukkit
    -100 Mojang

    Keep up the great work team.
     
  16. Offline

    Joe.

    Wow, amazing. Hope this is the last update until 1.3
     
  17. Offline

    TnT Retired Staff

    Should be fixed now. Its working for me again.
     
  18. Offline

    EvilSeph Retired Staff

    We're only bringing updates out because we have to. Minecraft 1.2.4 contains a severe crash bug in the generation code that affected (or will affect) a lot of servers. So no, we do not think a 1.2.5 is a bit ridiculous at all, but rather the right move. Unlike with the jump from Minecraft 1.2.3 to 1.2.4, you can connect to a 1.2.4 server with a 1.2.5 client or a 1.2.5 server with a 1.2.4 client.

    If you run plugins that use the Bukkit API like they are meant to, these Minecraft updates would mean no downtime for you at all. Plugins only break if we have to break the API and we haven't had to do that.

    The bugs shown in the wiki are minor and ones we were aware of before releasing the Minecraft 1.2.5 pre-release, so yes, we will be releasing 1.2.5 anyway.

    In conclusion, for the most part: it doesn't matter how many updates come out as long as the protocol doesn't change and you use plugins that stick with the Bukkit API. This is what an API is for - it allows you to run a Bukkit server with plugins without fear for the plugins breaking and no downtime between updates.
     
  19. Offline

    palisade

    In the other thread I mentioned that you guys were fixing a serious bug with 1.2.5, so there is a good reason for it. I agree with this.

    It is unfortunate that updates have come in this fast that have broken plugins, but I understand the need for them when there are severe issues to resolve. The 1.2.3 and 1.2.4 releases were devastating and there are still plugins that never bounced back. Maybe we need some kind of shim inside bukkit that can allow older plugins to continue to work correctly, even when protocols change.

    I remember discussing with a coworker once the concept of having version numbers on interface names for example. The way he described the idea is that you could have MyInterface_1_0 and then later if methods are added, removed, or renamed you could create a second interface MyInterface_1_1 while still leaving MyInterface_1_0 in the codebase. The idea is that code could still use the previous interface, and anyone needing the new functionality could use the new interface.

    This is essentially how the DirectX SDK has worked for years. And, this is why you can still target their older SDK and expect results, which prevents older programs from suddenly not working anymore. However, this doesn't prevent developers from choosing their newer SDK which provides a significantly upgraded experience. The opposite of this theory of development is Android development, where all builds are completely incompatible with one another. Google constantly breaks the API and developers grind their teeth as they're forced to upgrade to the new sdk designs where methods have been completely removed, renamed, signatures changed, etc. It's a very unpleasant experience.

    Regarding bugs, all software has bugs at all times. There's no such thing as perfect software. The fact that you have known bugs shows that you're aware of it and working on correcting it, but that they weren't severe enough to hold back a much needed patch. It is good for users to be aware of known issues, so they aren't surprised. Stating known bugs is useful, and shouldn't be the target of complaints.

    I'm glad to see you guys solved the animals clipping through fences and disappearing over time. That bug made it very hard to maintain a proper farm.
     
  20. Offline

    Ameo

    Thx !
     
  21. Offline

    hatstand

    The funny thing is, all of the plugins had weeks to update to the new Event API, and months to update to the new Configuration API. Any developer that did not do so is, in my opinion, a bit stupid.
     
  22. Offline

    Amaranth Retired Staff

    The Bukkit API generally maintains backwards compatibility as much as possible for some time via deprecation. There were plugins written back in June that still worked until 1.1-R5, probably some from even further back. Considering how much Minecraft changed in that time I consider that rather impressive. As far as CraftBukkit goes, you aren't supposed to be using anything in there and if you are you get to constantly update to keep it working. There is no way to make that backwards compatible without skewing further and further away from vanilla minecraft and making updates take longer and longer.
     
  23. Offline

    HappyPikachu

    Wow, this is a nice surprise. Can't wait for the RB tomorrow! ^.^
     
  24. Offline

    AravanFox

    AHH, I just had to delete old broken plugins and find new ones doing the same thing. Came on to finish up my updating.. and O_O.

    I really wish there was a way to "subscribe" to plugins so I can get notices when they update, rather than manually searching each day after a bukkit update!
     
  25. Offline

    palisade


    Or busy in real life and their world doesn't revolve around some plugin they wrote a long time ago. Though we love their plugins and what they make possible in Minecraft, some plugin developers might not feel like dealing with the constant churn of the patch system Mojang has forced on them. There are also server admins that ran really fun servers that gave up on them because keeping up with Mojang made them miserable.

    Also, it's summer now, and it's harder for a lot of people to focus like they did the rest of the year. Also, some of us have jobs and it takes a lot out of you. When you get home sometimes the last thing you want to do is work more. Sometimes you do though! It just depends on if it was a hectic day or not.

    I love doing hobby projects at home, but there's got to be some me time in there. Also, programmers tend to have MANY things going on at once, even when they do hobbies. They might be doing many different plugins, and they might be making their own game or software tool, or going through college, working two jobs, etc.

    Putting unnecessary strain on plugin developers when it can be avoided is silly to me. We should be making it as easy as possible for plugin developers and server administrators to keep their servers working correctly and their players happy so we can all enjoy the game and life.

    That goes for any project, not just bukkit and minecraft. There's too little time in this life to be spending it spinning your wheels because of some odd bureaucratic decision to make life hard for everyone. IMHO.

    We all want to make this game more fun, which is why any of us have dedicated time to it. I say let us make it fun to maintain it too! :)
     
  26. Offline

    ClearTranquil

    Good job guys! As a server admin this is the first update that won't be a pain in the ass.
     
  27. Offline

    Sayshal

    Oh don't get me wrong I like updates and I know bugs need to be fixed. But similar to how Bukkit delivers RB's when they are ready, Mojang seems to have to update quick MAJOR bug fix patches almost every update.

    In other games like SC2, Garrysmod, TF2, and generally any other game I've played, an updated never made you have to reset everything you've done (biome changes). I love MineCraft and I love Bukkit, but the constant patches for bugs that should've been noticed is really annoying.

    I guess that's why I'm a big fan of the prereleases/weekly builds.
     
  28. Offline

    mmob18

    Someone has the same thoughts as me!
    My plugins break like every two and a half weeks now!
     
  29. Offline

    robinsousa

    wow awesome a new recommended build shortly after the release of 1.2.5? that's really awesome, thanks bukkit team.
     
  30. Offline

    Sayshal

    It's not recommended and it hasn't been released yet.
     
Thread Status:
Not open for further replies.

Share This Page