About bukkit =)

Discussion in 'Bukkit Discussion' started by zipron, Mar 9, 2012.

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

    Don Redhorse

    so where does it say that it is a requirement to pull tons of commits into betas which are not relevant to support the transition from an old minecraft version to a new minecraft version?

    without checking every commit in the last couple of days in detail around 50% of them are features or don't have anything to do with 1.2.3 directly.

    Dinnerbone commited the last time to bukkit at the 2nd of March and to craftbukkit on the 9th.. at least on the official branch... EvilSeph is doing a lot, but also mainly accepting commits from bleeding.

    atm the main effort at least to an outstander is going into bleeding and fixing old stuff, not really going for an RB of 1.2.3

    oh... and btw: that post neither explains why we don't have an RB yet..

    I know that the beta was introduced and why.. but perhaps I have a different idea what to expect AFTER a minecraft update and during the normal time of developing.

    so enlighten me mbaxter:

    The release schedule is now like this:

    MC Update => Beta => Beta => Beta times X => RB => ?????

    and also please enlighten me and the others here:

    what are the 4 core members of the bukkit team doing? EvilSeph is explained by pulling commits, backreving fixes for 1.1 and making own commits.
     
  2. Offline

    zipron

    I think we two already discussed the mojang updates and RB's somewhere else and I can only fully agree.. But yea, bukkit was independant of mojang for a long time, and now that they are dependent, they need to start from scratch. Like someone already said here, we'll have to wait a few months to see what will come =) However, I still have faith in the bukkit and mojang team, and certainly now they work together =)
    zip
     
  3. Offline

    Waterflames

    I strongly believe the bukkit project is a zombie. Perhaps a fork of Bukkit will be maintained for a while when the team leaves, thats possible, but history tells us that that fork is likely to fail over time, so I don't think that project will live for very long.

    I think vanilla MP will be replaced by a bukkit-like API, and bukkit will be replaced by spout.

    The only other option I can think of right now is that somebody sets up a team that manages a fork of bukkit that gets the biggest flow of users from bukkit and gets maintained well. But due to the fact that Spout is working on a brand new system, build from scratch and has a big part done, I think it is more likely that Spout replaces Bukkit.

    Please don't flame me. ktnxbai :)
     
    Don Redhorse likes this.
  4. Offline

    mbaxter ʇıʞʞnq ɐ sɐɥ ı Retired Staff

    Don, until you actually read the post I will be unable to reply to you. Specifically, read up about what beta vs RB means currently as you seem confused about the addition of features.
     
  5. Offline

    Don Redhorse

    I did, several times, and I asked questions, several times....

    did you?

    The post even contradict itself in some places.

    There is a very big grey zone between Beta and RB's... to me atm it looks like like the old RB's got a little bit moved in the direction of the Beta and the new RB's are somewhere as a point between two MC updates.

    Which means for a developer to support beta's which are more prone to breaking than the old rb's or to wait for the new RB's which are far slower to come than the old ones.
     
  6. Offline

    mbaxter ʇıʞʞnq ɐ sɐɥ ı Retired Staff

    The betas aren't any more prone to being broken than 1.1-R1 was, pretty much. People just react to "beta" with "OMG ITS BUGGY" when you must realize that the reason we've had so many RBs in the past was bugs that crop up. The betas represent a way to declare something as fairly usable in order to reserve RB status for something more refined, which must take time.
     
  7. Offline

    zipron

    Luckely for us, now bukkit works with mojang, in a few months, the RBs will always be up-to-date, maybe another API yes.
     
  8. Offline

    emericask8ur

    Well one good thing is that, since Bukkit is helping Mojang update Minecraft, they are now another step ahead knowing what will be changed/updated/etc.
     
  9. Offline

    Windwaker

    Well one bad thing is that it will most likely be closed source and bugs will get fixed a lot slower and there would be no contributions from outside sources. But I digress, I don't like to be a pessimist, I'm just worried about the future of Minecraft modding.
     
    Mukrakiish and emericask8ur like this.
  10. Offline

    zipron

    why not asking a member of the team?
     
  11. Offline

    Windwaker

    I am a member of the SpoutDev's "Vanilla Team". However, I in no way represent SpoutDev, but I think my argument is still valid.
     
  12. Offline

    zipron

    I meant member of the bukkit team
    zip =)
     
  13. Offline

    Windwaker

    It doesn't matter what the individual opinions of the Bukkit team think, it comes down to legal stuff. Im sure they want it to be open source, but the chances of that are very slim.
     
  14. Offline

    LinkterSHD

    How can CraftBukkit be illegal when Mojang hasn't contacted asking them to make it. They would of asked Notch before they started Bukkit if they wernt sure
     
  15. Offline

    Don Redhorse

    that's what I meant... the OLD RB was stability wise in an area between the beta and the new RB now.. so a RB should be a lot more stable now (YEAH) and the Beta less stable...

    I like that...

    what I don't like is that the focus after a new minecraft release is not about working mainly on the support of the new minecraft release, pushing out betas for that, and after fixing the bugs release a RB... and after that focus on feature enhancements, more bug fixes, api completness etc.

    AND what I really don't like is that an RB was announced for 1.2.4 which isn't even out yet and hasn't seen any beta at all.

    This contradicts again everything which was said before.

    And I know already the answer for my post...
     
  16. Offline

    zipron

  17. Offline

    Windwaker

    CraftBukkit is illegal because they wrap around the Minecraft server code so they are essentially distributing Mojang code.

    No, not really. I have said several times that Bukkit will live on for another few weeks/months etc but when the Minecraft API comes out I see no reason why they would continue to work on it after that. There may be people who pick it up after Bukkit is succeeded but it will soon become outdated. This isn't opinion, it's fact.
     
  18. Offline

    zipron

    sure you're right, but we'll get a better solution when bukkit is gone =D
     
  19. Offline

    Mukrakiish

    That still won't fix this chlorinated community that is a result of the inattentive and inept work that has been paid to it (the community) in lieu of that.
     
  20. Offline

    zipron

    Afforess how's the spout community doing?
     
  21. Offline

    Windwaker

    Indeed, Spout

    Not to mention the project is going to be closed source which will cut of the influence the community ha on it. Hiring Bukkit Team does nothing for the modding community; they don't represent all of us.
     
  22. Offline

    Afforess

    Awesome.

    But this is a terrible place to ask me questions, I fully except this post to be censored.
     
Thread Status:
Not open for further replies.

Share This Page