[BLEEDING] Typo.

[BLEEDING] just to note blockinteract changes may alter things. Currently it looks like only blockplace.against is using the last move of BlockInteractData - later other checks are intended to use that too, in terms of a data source.
NoCheatPlus · May 1, 2017 · 01b311b · 01b311b
1 parent c07b1fb
commit 01b311b
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/NCPCore/src/main/java/fr/neatmonster/nocheatplus/checks/blockinteract/BlockInteractData.java b/NCPCore/src/main/java/fr/neatmonster/nocheatplus/checks/blockinteract/BlockInteractData.java
@@ -238,7 +238,7 @@ public boolean getLastAllowUseBlock() {
         return lastAllowUseBlock;
     }
 
-    public boolean getLastisCancelled() {
+    public boolean getLastIsCancelled() {
         return lastIsCancelled;
     }
 

diff --git a/NCPCore/src/main/java/fr/neatmonster/nocheatplus/checks/blockplace/Against.java b/NCPCore/src/main/java/fr/neatmonster/nocheatplus/checks/blockplace/Against.java
@@ -51,7 +51,7 @@ public boolean check(final Player player, final Block block, final Material plac
         if (!violation) {
             if (BlockProperties.isAir(againstType)) {
                 // Attempt to workaround blocks like cactus.
-                if (!bdata.getLastisCancelled() && bdata.matchesLastBlock(TickTask.getTick(), blockAgainst)) {
+                if (!bdata.getLastIsCancelled() && bdata.matchesLastBlock(TickTask.getTick(), blockAgainst)) {
                     // Block was placed against something (e.g. cactus), allow it.
                     // TODO: Later reset can conflict, though it makes sense to reset with placing blocks in general.
                     // TODO: Reset on leaving the listener rather - why could it conflict?