mirrors/papermc
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
papermc/Spigot-Server-Patches/0355-Fire-BlockPistonRetractEvent-for-all-empty-pistons.patch

51 lines
2.6 KiB
Diff
Raw Normal View History

Update upstream & fix some chunk related issues (#2177) * Updated Upstream (Bukkit/CraftBukkit) Upstream has released updates that appears to apply and compile correctly. This update has not been tested by PaperMC and as with ANY update, please do your own testing Bukkit Changes: 45690fe9 SPIGOT-5047: Correct slot types for 1.14 inventories CraftBukkit Changes: 4090d01f SPIGOT-5047: Correct slot types for 1.14 inventories e8c08362 SPIGOT-5046: World#getLoadedChunks returning inaccessible cached chunks. d445af3b SPIGOT-5067: Add item meta for 1.14 spawn eggs * Bring Chunk load checks in-line with spigot As of the last upstream merge spigot now checks ticket level status when returning loaded chunks for a world from api. Now our checks will respect that decision. * Fix spawn ticket levels Vanilla would keep the inner chunks of spawn available for ticking, however my changes made all chunks non-ticking. Resolve by changing ticket levels for spawn chunks inside the border to respect this behavior. * Make World#getChunkIfLoadedImmediately return only entity ticking chunks Mojang appears to be using chunks with level > 33 (non-ticking chunks) as cached chunks and not actually loaded chunks. * Bring all loaded checks in line with spigot Loaded chunks must be at least border chunks, or level <= 33
2019-06-14 02:27:40 +00:00
From 0eaf215550416941914cf236977f29d2b6a52c2a Mon Sep 17 00:00:00 2001
Fire BlockPistonRetractEvent for all empty pistons There is an explicit check in the handling code for empty pistons that prevents sticky pistons from firing the event. However when we look back at the history we see that this check was originally added so that ONLY sticky pistons would fire the retract event. I'm not sure why. https://hub.spigotmc.org/stash/projects/SPIGOT/repos/craftbukkit/commits/1092acbddf07edfa4100bc6824504ac75088e913 Over the course of several updates, the meaning of that field appears to have changed from "is NOT sticky" to "is sticky". So now its having the opposite effect. Only normal pistons fire the retraction event. And like all things in CB, it's just been carried around since. If we are to believe the history, the correct fix for this issue is to flip it so it only fires for sticky pistons, but that puts us in a bind. It's already firing for non-sticky pistons, changing it now would likely result in breakage. Furthermore, there is little documentation as to WHY that was ever intended to be the case. Instead we opt to remove the check entirely so that the event fires for all piston types. Fixes GH-1829
2019-01-31 21:45:43 +00:00
From: Zach Brown <zach@zachbr.io>
Date: Thu, 31 Jan 2019 16:33:36 -0500
Subject: [PATCH] Fire BlockPistonRetractEvent for all empty pistons
There is an explicit check in the handling code for empty pistons that
prevents sticky pistons from firing the event. However when we look back
at the history we see that this check was originally added so that ONLY
sticky pistons would fire the retract event. I'm not sure why.
https://hub.spigotmc.org/stash/projects/SPIGOT/repos/craftbukkit/commits/1092acbddf07edfa4100bc6824504ac75088e913
Over the course of several updates, the meaning of that field appears to
have changed from "is NOT sticky" to "is sticky". So now its having the
opposite effect. Only normal pistons fire the retraction event. And like
all things in CB, it's just been carried around since.
If we are to believe the history, the correct fix for this issue is to
flip it so it only fires for sticky pistons, but that puts us in a
bind. It's already firing for non-sticky pistons, changing it now would
likely result in breakage. Furthermore, there is little documentation as
to WHY that was ever intended to be the case.
Instead we opt to remove the check entirely so that the event fires for
all piston types.
diff --git a/src/main/java/net/minecraft/server/BlockPiston.java b/src/main/java/net/minecraft/server/BlockPiston.java
Updated Upstream (CraftBukkit) Upstream has released updates that appears to apply and compile correctly. This update has not been tested by PaperMC and as with ANY update, please do your own testing CraftBukkit Changes: 17543ecf SPIGOT-5035: Error Using Virtual Merchant GUI 0fc6922b SPIGOT-5028: Villager#setVillagerExperience() doesn't work bdbdbe44 SPIGOT-5024: Fox error - Unknown target reason
2019-06-06 15:36:57 +00:00
index b41750f22e..d548b27b8a 100644
Fire BlockPistonRetractEvent for all empty pistons There is an explicit check in the handling code for empty pistons that prevents sticky pistons from firing the event. However when we look back at the history we see that this check was originally added so that ONLY sticky pistons would fire the retract event. I'm not sure why. https://hub.spigotmc.org/stash/projects/SPIGOT/repos/craftbukkit/commits/1092acbddf07edfa4100bc6824504ac75088e913 Over the course of several updates, the meaning of that field appears to have changed from "is NOT sticky" to "is sticky". So now its having the opposite effect. Only normal pistons fire the retraction event. And like all things in CB, it's just been carried around since. If we are to believe the history, the correct fix for this issue is to flip it so it only fires for sticky pistons, but that puts us in a bind. It's already firing for non-sticky pistons, changing it now would likely result in breakage. Furthermore, there is little documentation as to WHY that was ever intended to be the case. Instead we opt to remove the check entirely so that the event fires for all piston types. Fixes GH-1829
2019-01-31 21:45:43 +00:00
--- a/src/main/java/net/minecraft/server/BlockPiston.java
+++ b/src/main/java/net/minecraft/server/BlockPiston.java
More 1.14 patches now we can rebase
2019-05-05 17:19:34 +00:00
@@ -121,7 +121,7 @@ public class BlockPiston extends BlockDirectional {
Fire BlockPistonRetractEvent for all empty pistons There is an explicit check in the handling code for empty pistons that prevents sticky pistons from firing the event. However when we look back at the history we see that this check was originally added so that ONLY sticky pistons would fire the retract event. I'm not sure why. https://hub.spigotmc.org/stash/projects/SPIGOT/repos/craftbukkit/commits/1092acbddf07edfa4100bc6824504ac75088e913 Over the course of several updates, the meaning of that field appears to have changed from "is NOT sticky" to "is sticky". So now its having the opposite effect. Only normal pistons fire the retraction event. And like all things in CB, it's just been carried around since. If we are to believe the history, the correct fix for this issue is to flip it so it only fires for sticky pistons, but that puts us in a bind. It's already firing for non-sticky pistons, changing it now would likely result in breakage. Furthermore, there is little documentation as to WHY that was ever intended to be the case. Instead we opt to remove the check entirely so that the event fires for all piston types. Fixes GH-1829
2019-01-31 21:45:43 +00:00
}
// CraftBukkit start
- if (!this.sticky) {
+ //if (!this.sticky) { // Paper - Prevents empty sticky pistons from firing retract - history behind is odd
org.bukkit.block.Block block = world.getWorld().getBlockAt(blockposition.getX(), blockposition.getY(), blockposition.getZ());
BlockPistonRetractEvent event = new BlockPistonRetractEvent(block, ImmutableList.<org.bukkit.block.Block>of(), CraftBlock.notchToBlockFace(enumdirection));
world.getServer().getPluginManager().callEvent(event);
More 1.14 patches now we can rebase
2019-05-05 17:19:34 +00:00
@@ -129,7 +129,7 @@ public class BlockPiston extends BlockDirectional {
Fire BlockPistonRetractEvent for all empty pistons There is an explicit check in the handling code for empty pistons that prevents sticky pistons from firing the event. However when we look back at the history we see that this check was originally added so that ONLY sticky pistons would fire the retract event. I'm not sure why. https://hub.spigotmc.org/stash/projects/SPIGOT/repos/craftbukkit/commits/1092acbddf07edfa4100bc6824504ac75088e913 Over the course of several updates, the meaning of that field appears to have changed from "is NOT sticky" to "is sticky". So now its having the opposite effect. Only normal pistons fire the retraction event. And like all things in CB, it's just been carried around since. If we are to believe the history, the correct fix for this issue is to flip it so it only fires for sticky pistons, but that puts us in a bind. It's already firing for non-sticky pistons, changing it now would likely result in breakage. Furthermore, there is little documentation as to WHY that was ever intended to be the case. Instead we opt to remove the check entirely so that the event fires for all piston types. Fixes GH-1829
2019-01-31 21:45:43 +00:00
if (event.isCancelled()) {
return;
}
- }
+ //} // Paper
// PAIL: checkME - what happened to setTypeAndData?
// CraftBukkit end
world.playBlockAction(blockposition, this, b0, enumdirection.a());
--
Updated Upstream (Bukkit/CraftBukkit/Spigot) Upstream has released updates that appears to apply and compile correctly. This update has not been tested by PaperMC and as with ANY update, please do your own testing Please note that this build includes changes to meet upstreams requirements for nullability annotations. While we aim for a level of accuracy, these might not be 100% correct, if there are any issues, please speak to us on discord, or open an issue on the tracker to discuss. Bukkit Changes: 9a6a1de3 Remove nullability annotations from enum constructors 3f0591ea SPIGOT-2540: Add nullability annotations to entire Bukkit API CraftBukkit Changes: 8d8475fc SPIGOT-4666: Force parameter in HumanEntity#sleep 8b1588e2 Fix ExplosionPrimeEvent#setFire not working with EnderCrystals 39a287b7 Don't ignore newlines in PlayerListHeader/Footer Spigot Changes: cf694d87 Add nullability annotations
2019-03-20 00:28:15 +00:00
2.21.0
Fire BlockPistonRetractEvent for all empty pistons There is an explicit check in the handling code for empty pistons that prevents sticky pistons from firing the event. However when we look back at the history we see that this check was originally added so that ONLY sticky pistons would fire the retract event. I'm not sure why. https://hub.spigotmc.org/stash/projects/SPIGOT/repos/craftbukkit/commits/1092acbddf07edfa4100bc6824504ac75088e913 Over the course of several updates, the meaning of that field appears to have changed from "is NOT sticky" to "is sticky". So now its having the opposite effect. Only normal pistons fire the retraction event. And like all things in CB, it's just been carried around since. If we are to believe the history, the correct fix for this issue is to flip it so it only fires for sticky pistons, but that puts us in a bind. It's already firing for non-sticky pistons, changing it now would likely result in breakage. Furthermore, there is little documentation as to WHY that was ever intended to be the case. Instead we opt to remove the check entirely so that the event fires for all piston types. Fixes GH-1829
2019-01-31 21:45:43 +00:00
Reference in a new issue Copy permalink