Fixed redstone current being sent even if a BlockPlace was cancelled.
Dieser Commit ist enthalten in:
Ursprung
053e05dd37
Commit
0c24f86a09
@ -49,8 +49,6 @@ public class ItemRedstone extends Item {
|
||||
if (Block.REDSTONE_WIRE.canPlace(world, i, j, k)) {
|
||||
BlockState blockState = CraftBlockState.getBlockState(world, i, j, k); // CraftBukkit
|
||||
|
||||
world.setTypeId(i, j, k, Block.REDSTONE_WIRE.id);
|
||||
|
||||
// CraftBukkit start - redstone
|
||||
BlockPlaceEvent event = CraftEventFactory.callBlockPlaceEvent(world, entityhuman, blockState, clickedX, clickedY, clickedZ, Block.REDSTONE_WIRE);
|
||||
|
||||
@ -58,6 +56,8 @@ public class ItemRedstone extends Item {
|
||||
event.getBlockPlaced().setTypeIdAndData(blockState.getTypeId(), blockState.getRawData(), false);
|
||||
return false;
|
||||
}
|
||||
|
||||
world.setTypeId(i, j, k, Block.REDSTONE_WIRE.id); // CraftBukkit - Must take place after BlockPlaceEvent
|
||||
// CraftBukkit end
|
||||
|
||||
--itemstack.count; // CraftBukkit - ORDER MATTERS
|
||||
|
In neuem Issue referenzieren
Einen Benutzer sperren