CraftBukkit 1.6.2-R1.0 is now available!

A new CraftBukkit Recommended Build (1.6.2-R1.0) that provides Minecraft 1.6.2 compatibility is now available. As this new Recommended Build also contains a CRITICAL security fix, updating is HIGHLY recommended.

Will plugins break with this build?
Provided the developers of the plugins you are using are keeping up with the development of Bukkit, all your plugins should work fine.

Known Issues:

• None.

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

Download CraftBukkit 1.6.2-R1.0 here (if this link doesn't work, try this one instead).

 

Great work guys!

 

Hey, just to mention it: I'm using the recommended build with the new release of Java (Version 7 Update 40; just came out yesterday or the day before). It works fine.

 

They did on my server and wreaked loads of havoc. I now have to rebuild the whole server again and get players back. <name and shame removed>

 

That's why you make regular backups, right?

 

Actually this time Ive been busy so we hadnt had an uptodate backup done. Thats not anyones fault. And im not complaining at anyone. Just saying whats happened.

 

EvilSeph
Do you know how I would fix Enchantment.getById(NUMBER)?
And also, do you know how to fix ITEM.getId();

 

Bukkit team: We have finally released a recommended build for MC 1.6.2!
Mojang: Minecraft 1.6.3 pre-release is now out!

 

Just don't use it! Check the enums instead!

 

What do you mean?

 

The thing with the ids is, that they are magic numbers. So, if these numbers change, your code wouldn't do the same. But if you check ItemStack.getType() == Material.??? the code won't lose its functionality.

You can also get Materials (for example) from Strings using the build-in function in enum.

 

Janmm14
I'm using it do display the id

 

EvilSeph
Is there an important reason why these methods have become deprecated, I have no idea why there is no point for a deprecation towards a Magic Value:

Code:

new ItemStack(int, int);
getTypeId();
getTargetBlock(HashSet<Set>, int);

 

I have the same concern. My plugin deals with arbitrary item IDs, that's what it is supposed to do in the core of its concept. Deprecation means that something will be removed in the future, and if Bukkit removes all the ID based functions that will force me to re-implement id-to-Material conversion in my own code. It won't be any less "magic" and will just increase the amount of stuff I have to maintain between versions.

 

Material.getMaterial(id) is also deprecated so I'm not sure how it's supposed to work now short of every plugin implementing lookup tables.

 

hope mojang will slow down,and we will have some rest without those build rushes.
now only plugin updating is left.

 

Finally now running my Server with this Build. Good Job!

 

Nope, just got a 1.6.4 patch a few min ago lol

 

My client just updated to 1.6.4 but my bukkit server is still running 1.6.2. How do I fix it so that I can get people back on the server?

 

You have to wait for a new release now..

 

Well that sucks, how long does it take to release the newest bukkit?

 

Uh no, you can select the 1.6.2 in the profile editor.

​

 

Thank you! I'm still kind of new to this server running thing.

 

YAy

 

​

I meant for bukkit but

Not but a day or two on average, sometimes hours, sometimes days. Some servers can get them in an instance (like the server I play on) but I don't know how they do it, I think they edit something within the jar.

EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

Man...I hate losing players to an update :/ I used to have 20+ people on at once...now I have 6 because of 1.6.4. I don't mind though. I don't want the 1.6.4 craftbukkit to be rushed and full of bugs/glitches. I'd rather just keep my small player base than have a big one full of bugs <3