Difference between revisions of "Geomancy/Version History"

From Robowiki
Jump to navigation Jump to search
(Version 2, now with velocity snapping)
(bug escaped containment)
Line 8: Line 8:
 
;2 - ''unknown'' - Velocity snapping added
 
;2 - ''unknown'' - Velocity snapping added
 
:In the two turns before enemy gunheat reaches zero, I limit my velocity to 0, 4, or 8 (whichever's closest) so that the enemy's segmentation has lowered resolution.
 
:In the two turns before enemy gunheat reaches zero, I limit my velocity to 0, 4, or 8 (whichever's closest) so that the enemy's segmentation has lowered resolution.
 +
 +
;2a - ''unknown'' - my first upload of version 2 called AdvancedRobot.setDebugVariable, which is not present in Roborumble-sanctioned versions of Robocode. As a result a few clients who got the buggy version are seeing crashes 100% of the time. 2a has the function removed.
  
 
;3 - ''in development'' - Anti-mirroring added
 
;3 - ''in development'' - Anti-mirroring added

Revision as of 05:14, 13 July 2009

Pages: Main page · Code · Version History · Discussion

Versions

1 - G1937.0, 59th - Release
Cleaned up Watermelon, removed old code it didn't need, fixed some minor issues, tweaked some numbers, and gave it a shiny new name.
2 - unknown - Velocity snapping added
In the two turns before enemy gunheat reaches zero, I limit my velocity to 0, 4, or 8 (whichever's closest) so that the enemy's segmentation has lowered resolution.
2a - unknown - my first upload of version 2 called AdvancedRobot.setDebugVariable, which is not present in Roborumble-sanctioned versions of Robocode. As a result a few clients who got the buggy version are seeing crashes 100% of the time. 2a has the function removed.
3 - in development - Anti-mirroring added
Added a gun/movement scheme for detecting and responding to mirror movement. If the midpoint of the two bots stays the same within a certain tolerance, it swaps in, displacing the normal movement and gun. It plans its movement far enough into the future to have a map of the opponent's expected location. It fires power 3 shots at the expected future location of the enemy. The movement is intended to be reasonably flat.
Issues:
  • Mirrorbots that use delayed mirroring or that mirror around an axis instead of a point are not detected. I consider them much less of a threat since they are discarding movement data, making them more vulnerable to my regular targeting.
  • Anything else?