Difference between revisions of "Geomancy/Version History"

Revision as of 18:18, 14 July 2009

Pages: Main page · Code · Version History · Discussion

1 - G1937.0, 59^th - 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 - NA - Velocity snapping added
2a - G1898.9 - bugfix release: 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.; My first upload of version 2 used 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 - unknown - removed velocity snapping, refined bot width calculation: Rolled back changes from version 2 -- while the velocity manipulation is quite effective against some bots, notably Geomancy 1, it hurts my overall ranking badly.; Added more precise bot width calculation, including partial bin addition for bins at the edges of the bot width.

@@ Line 11: / Line 11: @@
 :My first upload of version 2 used 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 - ''unknown'' - removed velocity snapping, refined bot width calculation
-;3 - ''in development'' - Anti-mirroring added
+:Rolled back changes from version 2 -- while the velocity manipulation is quite effective against some bots, notably Geomancy 1, it hurts my overall ranking badly.
-: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.
+:Added more precise bot width calculation, including partial bin addition for bins at the edges of the bot width.
-: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?
--->
 __NOTOC__