Comment: More abstraction feasible for loop checks?

NoCheatPlus · Apr 5, 2017 · ed6db25 · ed6db25
1 parent ba4001a
commit ed6db25
Showing 1 changed file with 6 additions and 0 deletions.
diff --git a/NCPCore/src/main/java/fr/neatmonster/nocheatplus/checks/fight/FightListener.java b/NCPCore/src/main/java/fr/neatmonster/nocheatplus/checks/fight/FightListener.java
@@ -413,6 +413,12 @@ private boolean locationTraceChecks(final Player player, final Location loc,
             final Location damagedLoc, LocationTrace damagedTrace, 
             final long tick, final long now,  final boolean reachEnabled, final boolean directionEnabled) {
         // TODO: Order / splitting off generic stuff.
+        /*
+         * TODO: Abstract: interface with common setup/loop/post routine, only
+         * pass the ACTIVATED checks on to here (e.g. IFightLoopCheck...
+         * loopChecks). Support an arbitrary number of loop checks, special
+         * behavior -> interface and/or order within loopChecks.
+         */
         boolean cancelled = false;
 
         // (Might pass generic context to factories, for shared + heavy properties.)