Comment: More abstraction feasible for loop checks?

This commit is contained in:
asofold 2017-04-05 12:43:05 +02:00
parent ba4001a0b5
commit ed6db25338

View File

@ -413,6 +413,12 @@ public class FightListener extends CheckListener implements JoinLeaveListener{
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.)