Is this a sensible way to do it?
The highlighted comment was created in this revision.
My AdvancedRobot, Thor, is currently using a static boolean "scanning" to determine whether to turn the radar or not.
This should provide a degree of locking by setting "scanning" to false when we scan a robot, setting it to "true" after we execute, and turning if it's true.
I know it's a naive approach and doesn't lock very well, but it doesn't appear to lock -at all- currently.
Is it my methodology that's flawed, or should I hunt for a bug in the code? (No point debugging if I'm going about it the wrong way from the start).
I think the way most of us do it is to simply scan towards the last known location of the enemy every single tick, making sure we overshoot by a little bit in case they move. I've never put too much effort into radar myself (at least 1v1 radar), because extremely simple solutions tend to work perfectly...
