01-07-2016, 02:26 PM
I guess the reason is that TaskTracker needs to run it's init code, and if the order of execution is just wrong, the init code doesn't get executed since the removeSwitchableUnits causes an error.
I would guess that more things fail, but for the Task tracker, it's most obvious
I would guess that more things fail, but for the Task tracker, it's most obvious