From f834bcec082df7d487f4331bb47cec640ce232c2 Mon Sep 17 00:00:00 2001
From: Leijurv <leijurv@gmail.com>
Date: Sat, 25 Aug 2018 17:09:35 -0700
Subject: [PATCH] add BlockFalling check for MovementFall, fixes #94

---
 .../baritone/pathing/movement/movements/MovementFall.java     | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/src/main/java/baritone/pathing/movement/movements/MovementFall.java b/src/main/java/baritone/pathing/movement/movements/MovementFall.java
index 6d96b3653..1910c928a 100644
--- a/src/main/java/baritone/pathing/movement/movements/MovementFall.java
+++ b/src/main/java/baritone/pathing/movement/movements/MovementFall.java
@@ -30,6 +30,7 @@ import baritone.utils.InputOverrideHandler;
 import baritone.utils.Rotation;
 import baritone.utils.Utils;
 import net.minecraft.block.Block;
+import net.minecraft.block.BlockFalling;
 import net.minecraft.init.Items;
 import net.minecraft.item.ItemStack;
 import net.minecraft.util.math.BlockPos;
@@ -65,6 +66,9 @@ public class MovementFall extends Movement {
         if (frontTwo >= COST_INF) {
             return COST_INF;
         }
+        if (BlockStateInterface.get(positionsToBreak[0].up()).getBlock() instanceof BlockFalling) {
+            return COST_INF;
+        }
         for (int i = 2; i < positionsToBreak.length; i++) {
             // TODO is this the right check here?
             // miningDurationTicks is all right, but shouldn't it be canWalkThrough instead?