Strange results for v3.67a

Now not all pairings for v3.67a completed, but after 782 pairings this version get - ~0.4 APS and it's strange, because the change is fix for used data for surfing. Tomcat for a long time use data from two ticks before fire detection for range search. For example, if Tomcat detect a energy drop at 10th tick, then it use for range search data from 8th tick, while, theoretically, enemy uses data from 9th tick for aiming. And v3.67a try to use data from 9th tick. Without success. Anyone has any suggestions why?

I may not remember right... but IIRC, if you detect an energy drop on the 10th tick, then the enemy called "fire()" on the 9th tick, last had an opportunity to turn their gun on the 8th turn (because fire() takes effect before setTurnGun()), and their scan data of you was from the 7th tick actually.

So to construct the search data for an energy drop you detected at the 10th turn, you should use:

1. The enemy scan that you received on the 9th tick (they turned their gun at the 8th, and 1 tick delay in your scan)
2. Your robot data from the 7th tick (Last one they would have got scan data of before turning their gun)

(As an aside, gunheat waves work because if their energy drop is 10th turn, they wouldn't have seen what you did in the 8th turn, therefore gunheat waves can (without giving off hints) happen 2 ticks before energy drop.)