Along with experience as developers, many of our Team members, including myself run popular and large Minecraft communities and servers. Furthermore, the core Bukkit Development Team consists of the people who have been maintaining hMod for the past few months.
In fact, the birth of the Bukkit Project resulted from a discussion between Dinnerbone and myself about the many changes we were interested in making to hMod which would result in complete breakage of current hMod compatibility. That being said, we have a few months of experience under our belt already maintaining and developing mods both our own and by other people.
If you have any questions, please feel free to join us on our chat by connecting to bukkit on irc. Log in or Sign up. Bukkit Forums. About Us. We believe our first announcement revealing the project to the Minecraft community says it best: Bukkit is an up-and-coming Minecraft Server mod that will completely change how running and modifying a Minecraft server is done - making managing and creating servers easier and providing more flexibility.
The overall design of Bukkit has been inspired by other mods and our experience as Minecraft players just like yourselves, giving us a unique perspective and advantage going into the creation of the Bukkit Project Your server, your way Creating the dream Minecraft server you have always wanted has never been easier.
Ease of use The days of guessing what a command or feature does are over. Not only will this site allow you to find and download plugins manually, Bukkit will have a built-in command that makes installing a new plugin as easy as typing a simple command. As of September 3, , all Bukkit download pages are currently unavailable as per a DMCA takedown request filed from one of the former Bukkit team members.
For the most part Bukkit has been succeeded by Spigot , an updated fork of Bukkit's code that is backwards-compatible with its plugins.
BukkitDev was the Plugin repository for Bukkit plugins. In the interim, a plugin list is maintained here. On October 11, it was announced that the Official transition to BukkitDev had started. ChatBukkit was an official plugin by the Bukkit Dev. Team, that was discontinued due to other plugins such as HeroChat, and Essentials. CraftBukkit was the Minecraft multiplayer Server mods.
It was a variant of the official Minecraft server executable capable of understanding Bukkit API calls, i.
You must have CraftBukkit to run a Bukkit server. HomeBukkit was an official plugin from the Bukkit team, but is now discontinued due to plugins like Essentials.
ScrapBukkit is a Bukkit plugin that contains server commands for give, take, teleport and time. Somehow hMod picked up speed and people started to extend upon it with plugins, adding yet more functionality to such an already ambitious project. I loved the concept of this strange and curious project. I wanted to check it out and maybe try my hand at making my own plugin. The chance of customising a game to how I want it? Yes please! I hadn't really played with Java much before, but I'm quick to pick up new programming languages and I was quite familiar with C so it was easy enough to work with.
I knew exactly what I wanted to try to make, and I had a bunch of friends who supported me and were willing to try it out with me. Minecraft multiplayer was an extremely new and broken thing at the time, and things like Minecarts would just be invincible crashing machines at this point seriously; you couldn't destroy them and rails crashed your server and your clients , so there was a desperate need for getting around quickly on a server.
I set out to make a plugin called " Stargate ", which I'd like to imagine set the standards for modern portal plugins.
There simply weren't any previously, and I went all out trying to get Stargate working how I thought it should; you'd orient and position properly between the portals, kept momentum, and they utilized signs as a means of interacting with them something that nothing else did at the time - it's now the norm! During my time making Stargate, I somehow took burden of maintaining hMod with a few other people who equally just found themselves in such a position without any knowledge of how it happened.
Hey0 had vanished, and Minecraft had started to be updated much more frequently than before. We needed to know what to do! Myself and Grum took control and spent our time updating hMod ourselves, which was a scary task and took us a long time, but we got through it.
We had very little control over the project, and couldn't even make releases ourselves, so this was an extremely difficult position to work from - but we did it. We spent a few months updating hMod between Grum and myself, and eventually we just grew tired of having to support broken things without being able to even attempt to fix them. I spoke to a few people in private and proposed that we started up a new project from scratch, where we can actually work on the things that need to be worked on and hopefully make something just that much more awesome.
Some of the guys I spoke to thought it wasn't worth the time, whilst others Grum, Tahg, EvilSeph thought it was a good idea.
I figured that any positive reaction was enough to get it started, so I went forwards with my plans. People often ask me, "why 'Bukkit'? I proposed "CraftBucket", and people agreed that it was a good name. After we realized that splitting the project into two parts an API and an implementation , we decided to go for "Bucket" and "CraftBucket" - but then Grum jokingly suggested "Bukkit" for the whimsy name.
Needless to say, it stuck :. So there we had our group and our plans, and we were ready to take over the world. We drafted up an announcement that we'll no longer be supporting hMod ourselves and will be creating a new project, and this was published on a few sites.
The minecraftforum thread is still available for reading , and is worth a few giggles if you're interested. Initial community reaction to the announcement was mostly fantastic, but it did spawn up the usual craze of "one project may die; we need to fill in the void with a new one! Lots of other projects suddenly popped up to compete with us to replace our own work, but they didn't really take off. I was excited, there was so much to do and I can really get a lot done if I'm focused.
Full steam ahead, and the project just grew like nothing else. Over the next couple of months, the initial team that said they'd help create the project kinda fell away, and we were left with just 4 people as the "core". Myself, Grum, EvilSeph, and Tahg. I'd come to learn from my time making this project that people may mean good, and some may even mean bad, you just can't rely on them to be available as much as you are a few months down the line - life gets in the way!
Tension was already high between the the trinity of business owners, open source developers, and Mojang. By , Mojang was a multi-million dollar company even before their multi-billion Microsoft buyout. The EULA tension placed a heavy burden on the open source developers, who received pressure from both ends. Then, the unexpected happened on August 21st, This was sad news. But the real shock came an hour later when the lead developer of Minecraft at Mojang shot back on Twitter:.
Warren over at bukkit seems to have forgotten that the project was bought by Mojang over two years ago, and isn't his to discontinue. We'll see what happens from here. To make this clear: Mojang owns Bukkit. I'm personally going to update Bukkit to 1. It was now revealed that the Bukkit open source developers hired by Mojang in had given up their personal copyright and rights to their open source contributions as part of their employment contracts.
The open source developer and business owner communities both learned this abruptly over a character tweet. I was completely unaware that I had spent the last two years of my life as a Bukkit Administrator, and successor to the project lead, under the illusion that the project was independently ran. Had I known back then perhaps my choice would have been different, perhaps not.
The only visible contribution made by Mojang to Bukkit was the explicit permission to continue their endeavor in the legal gray area. On September 5th, , a lead developer not hired by Mojang, who had contributed over 15, lines of code to the project, invoked a Digital Millennium Copyright Act DMCA take-down on all of his personal contributions to the project and all derivative projects.
It is easy to understand why this lead developer did what he did. To find out the last few years of your life spent volunteering on a game project that was secretly owned by a multi-million dollar company is a shattering experience.
But at the same time, this was a project used by hundreds of thousands of people around the world. It was more than a project; it was also a community. One of the lead developers of Bukkit said this of the project in their resignation letter to the community :.
The Bukkit API gave people the ability to change the behavior of Minecraft, but it would have meant nothing without the contributions from the plugin developers in the community. The overnight disappearance of Bukkit left a huge power vacuum full of bitterness, personal harassment, and doxing. The project I participated with, Spigot, was a fork of Bukkit created in Like Bukkit, Spigot was also hit by the DMCA take-down, although the Spigot team worked out a clever legal workaround to continue development.
The unusual thing was, with few exceptions, most of the leaders of these communities were young adults in their 20s, teenagers, or even 11 year old kids. It was just what everyone did. The messaging around licensing was not always great , but working in the open was the nature of how this gaming community operated.
0コメント