[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.
This commit is contained in:
parent
c07b1fb8a3
commit
01b311bcd3
|
@ -238,7 +238,7 @@ public class BlockInteractData extends ACheckData {
|
|||
return lastAllowUseBlock;
|
||||
}
|
||||
|
||||
public boolean getLastisCancelled() {
|
||||
public boolean getLastIsCancelled() {
|
||||
return lastIsCancelled;
|
||||
}
|
||||
|
||||
|
|
|
@ -51,7 +51,7 @@ public class Against extends Check {
|
|||
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?
|
||||
|
|
Loading…
Reference in New Issue