Oops, I broke your plugins!

The upcoming RB will contain a few breaks:

• Plugins that teleport players within the PlayerMove event will need to switch to just using event.setTo() as this now handles teleporting. This means that event.setTo() can now handle multi-world too.

After the upcoming RB, the following API changes will occur:

• onSnowForm will be replaced with onBlockForm.
• NoteBlock.getNote() that returns a byte will be changed to getRawNote()
• NoteBlock.getNote() will then be changed to return a Note instead.

We're still working on this RB so there might be more to add to this list, but mostly it is the Portal event revamping we're doing.

The initialize method of plugins will now be called before the first world is created, instead of after. This is to accommodate a new option to select if your plugin should be enabled before or after the world is created.

Nothing in the initialize method should actually touch the world, so this shouldn't break any smart plugins.

Jukebox materialdata has been removed (not deprecated), a jukebox blockstate has been made in its stead. This is an overdue change and while we apologise for the lack of deprecation, it's not really possible to sanely deprecate this (plus, the materialdata hasn't worked in quite some time I believe)

All the server.createWorld methods are now deprecated, and in their stead we have a new system for creating/loading worlds. It may look a little ugly at first, but consider just how many optional vars there are (and will be, with more on their way) and how many dozens of constructors we'd need to make that work.

New way to create/load worlds:

Code:

World world1 = WorldCreator.name("nameofWorld").seed(12345).generator("somePlugin:meep").createWorld();
World world2 = WorldCreator.name("nameofWorld").copy(world1).environment(NETHER).createWorld();
World world3 = WorldCreator.name("nameofWorld").createWorld();

PaintingBreakByWorldEvent has been removed. You need to use PaintingBreakEvent instead and the new RemoveCause enum additions.

Blocks are no longer guaranteed to be the same object when retrieved. You should now use .equals instead of == to check if two Blocks are the same.

Code:

Block block1 = world.getBlock(0,60,0);
Block block2 = world.getBlock(0,60,0);
(block1 == block2) == false
block1.equals(block2) == true

Well, I finally went and did it.

I fixed BlockFace, by doing so I apparently broke plugins that were accounting for the fact that this was broken.

See the commit for more information: https://github.com/Bukkit/Bukkit/commit/49690f9620b7ed1ed9769cec35d095a3cac33ab0

42

From Wolvereness: