Difference between revisions of "Geomancy/Version History"

From Robowiki
Jump to navigation Jump to search
m (→‎Versions: ranking posted)
(feel free to comment on the discussion page)
Line 5: Line 5:
 
;1 - G1937.0, 59{{sups|th}} - Release
 
;1 - G1937.0, 59{{sups|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.
 
: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 - ''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?
  
 
__NOTOC__
 
__NOTOC__

Revision as of 01:31, 5 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 - 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?