Thread history

In the log above, there are 25 lines of "Hit by a wave that was not being correctly tracked", indicating MoxieBot losing energy. That would be consistent with MoxieBot stalling and MyFirstRobot getting a 100% hitrate on it. MyFirstRobot fires 1.0 power bullets, which cause 4.0 damage, and 100 / 4 = 25 hits to kill = 25 log messages.

I also made a video of MoxieBot vs. TrackFire on that computer. It stalls for 2 rounds, but works on the other 8. It doesn't seem so bad when not minimized.

I wonder if the bug is that MoxieBot loses its radar lock and cannot regain it, which wouldn't be that hard of a fix...

Yep. This is what I see as well. It seems to be a bug in the MoxieBot logic. Not in the robocode.

By the way ThreadDeath is also there. Looks like I need to try java7 or earlier and see if ThreadDeath related losses are there.

I also checked the historical robocode 1.8.3, MoxieBot has the same buggy behaviour.