temporarily diable senstive blocks check (#4077)

Co-authored-by: Daniel Walsh <[email protected]>
Slimefun · Jan 3, 2024 · e339503 · e339503
1 parent 4d710fa
commit e339503
Showing 1 changed file with 4 additions and 0 deletions.
diff --git a/src/main/java/io/github/thebusybiscuit/slimefun4/implementation/listeners/BlockListener.java b/src/main/java/io/github/thebusybiscuit/slimefun4/implementation/listeners/BlockListener.java
@@ -303,8 +303,11 @@ private void checkForSensitiveBlockAbove(Player player, Block block, ItemStack i
      * @param count
      *      The amount of times this has been recursively called
      */
+    // Disabled for now due to #4069 - Servers crashing due to this check
+    // There is additionally a second bug with `getMaxChainedNeighborUpdates` not existing in 1.17
     @ParametersAreNonnullByDefault
     private void checkForSensitiveBlocks(Block block, Integer count, boolean isDropItems) {
+        /*
         if (count >= Bukkit.getServer().getMaxChainedNeighborUpdates()) {
             return;
         }
@@ -326,6 +329,7 @@ private void checkForSensitiveBlocks(Block block, Integer count, boolean isDropI
         // Set the BlockData back: this makes it so containers and spawners drop correctly. This is a hacky fix.
         block.setBlockData(state.getBlockData(), false);
         state.update(true, false);
+        */
     }
 
     /**