CraftBukkit 1.7.2-R0.3 is now available!

A new CraftBukkit Beta Build (1.7.2-R0.3) that provides Minecraft 1.7.2 compatibility is now available. Please note: the stability of this build is relatively unknown due to the impact Minecraft 1.7 had on the core code.

Will plugins break with this build?
Minecraft 1.7 is one of the most involved and impactful updates to date, bringing about many changes to the core of Minecraft. As a result, there is a chance that plugins might break with this build. Even if that isn't the case, we have not completed work on API changes for 1.7 yet so future builds might still break plugins.

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 few Beta builds 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 order to reach a Recommended Build.

Notable changes include:
New Minecraft Command Handling
One of the larger issues we've had with the Minecraft 1.7 update is due to the recent trend of new commands being added to Minecraft. Basically, whenever a new Minecraft command is added we need to do a lot of work to make it available through Bukkit. While this process made sense when Minecraft commands were simple, the new commands that are being added to Minecraft have significantly grown in complexity. As a result, we're now forced to add code to the project that purely exists to make the commands work and provides no benefit to plugin developers. This extra work puts an unnecessary strain on the project and leads to avoidable delays in our development process while providing very little benefit to Bukkit.

Thankfully, with the introduction of our new Minecraft Command Handling we're able to alleviate this issue by providing a fallback system for commands. This lets the server make use of Minecraft's built in commands whenever a plugin and Bukkit version of it does not exist. What this means for server admins is that you'll no longer be waiting for us to add a new Minecraft command to Bukkit before you can use it and, instead, should be able to use them in our very first compatible build right away.

If you're interested in more detailed information on the thought process behind this system, I wrote an article on my blog here:
http://evilseph.com/post/75608917830/bukkit-supporting-minecraft-commands

CommandBlock Command Overrides
For server admins that are wanting to run custom maps that make heavy use of CommandBlocks, we've added an easy way to force CommandBlocks to use the Minecraft version of a command while using the plugin or Bukkit version everywhere else. This system works on a command by command basis, allowing server admins to provide a list of commands they'd like to override in our new commands.yml. Hopefully this already results in the majority of custom maps working with Bukkit but we're still investigating potential issues that could cause unintentional custom map incompatibility.

For more detailed information on how to use the new command-block-overrides system, see the command-block-overrides section of our commands.yml article on our Bukkit Wiki.

Ultimate Command Fallbacks
With the introduction of the new Minecraft command handling mentioned above, we're also providing an ultimate command fallback system. This provides an untouchable safety net for commands and gives power users more control over commands through our improved aliases system explained below.

On the surface this means that every command has an explicit way to access them:

• Bukkit provided commands can be accessed by using the "bukkit:" prefix
  • Example: /bukkit:time
• Mojang provided commands can be accessed by using the "minecraft:" prefix
  • Example: /minecraft:time
• Plugin commands can be accessed by using the plugin's name as a prefix
  • Example: /scrapbukkit:time

These fallbacks are completely untouchable by plugins and exist for every command on the server. If you're looking to prevent access to a command, we recommend removing the permission instead of trying to hide the command. For Mojang provided commands, the default access level for all of them is op but access to each can be controlled by their permissions.

For more information on these ultimate command fallbacks and command permissions, see our commands.yml and command list articles on the Bukkit Wiki.

Improved Aliases System
For our power user server admins, this release also contains a greatly improved aliases system that supports command arguments, command remapping and more - all controllable through our new commands.yml file.

See the aliases section of our commands.yml article on the Bukkit Wiki for detailed information on this powerful system.

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

Download CraftBukkit 1.7.2-R0.3 here

 

Feels like this project is nearing death.. 5 months since 1.7 and still in beta...

 

wrecktify have you ever written code? I think not! It's hard especially since you can't use most of the work you did from all the past updates, because mojang wanted minecraft to be minecraft, not modcraft! They are trying their hardest... so you cant wait till 1.8 comes out in may then you can be allowed to complain. (I still wouldn't though...)

 

They should have released 1.7.2-R0.2 as a R.B. back in early January.

 

I don't have to write code to voice an opinion. Secondly, It was an observation, not a complaint. Lastly, trying their hardest is laughable. The last dev build was February 12th. They clearly need some more programmers, because nobody is trying hard. And what does 1.8 have anything to do with current bukkit development? Your points are loaded with fallacies

 

http://evilseph.com/post/76009605147/bukkitlog-1-7-craftbukkit-1-7-2-r0-3-minecraft-1-7-4

 

Great.. that was posted february 8th almost 6 weeks ago. An update would be nice. But thanks for sharing that info, even though it is old

 

Good Now my server can update!

 

when will 1.7.2-RO.3 become the recommend build?

 

Probably never (although it should have been 6 weeks ago!).

 

Sorry if this is the wrong place guys. I am new to hosting a minecraft server having only really played on one a friend ran for 3 of us and it was hosted by a company. I have a home server and installed 1.6.4 bukkit with mcmyadmin and all working great.

Would this be the most stable release that would allow us to use the 1.7 features? I can see non of the 1.7 releases have been given recommended status so not really sure is best to go for? Are the newer releases more stable? Any where I can find out the known issues with these?

 

I would recommend the latest beta build. It's 1.7.2.

 

Locked. New Beta released!
http://forums.bukkit.org/threads/craftbukkit-1-7-9-r0-1-is-now-available.268270/