Easy Question?

@MN: check out http://robowiki.net/wiki/Robocode/Game_Physics#Collisions
@Wompi: I detect accelerating/decelerating bots, except when they only do it that last tick before hitting the wall, like your example. That's why I said it is not 100% proof.

As for the inactivity timer, a top bot would not have that situation often. Usually they fire until 0.1 energy left, and then just keep moving. When inactivity timer kicks in, the battle is immediately over. To counter that, you could move closer or even ram the opponent when it stops firing.

Just out curiosity, what is the purpose of keeping track of your own energy? I can't think of anything useful for me.

Tracking your own energy helps detect inactivity damage kicking in. If the opponents energy drops 0.1, it could be due to inactivity or due to a 0.1 power bullet being fired. You can't be sure. But if your own energy drops 0.1 and you didn't shoot, it should be due to inactivity.

Not tracking inactivity damage results in a bunch of false 0.1 power waves being detected at end game. Usually not an issue, but having highly accurate wave detection is cool.

Remembered one case where inactivity damage is a big issue. Reference bots of targeting challenges don't shoot and always outlast candidates with inactivity damage. If they wrongly detect 0.1 power waves, it introduces a lot of noise in their wave histories and makes dodging weaker.