Difference between revisions of "Geomancy/Version History"

From Robowiki
Jump to navigation Jump to search
m (bah)
m (score added for version 4a)
Line 3: Line 3:
 
== Versions ==
 
== Versions ==
  
;4a - ? - Not ProGuarded
+
;4a - G1940.9 - Not ProGuarded
 
:Same as 4 but no after-compile optimizations.
 
:Same as 4 but no after-compile optimizations.
  

Revision as of 19:23, 8 September 2009

Pages: Main page · Code · Version History · Discussion

Versions

4a - G1940.9 - Not ProGuarded
Same as 4 but no after-compile optimizations.
4 - ? - Lots of bugfixes
Resolved some silliness where multi-wave surfing was falsely seeing a safe spot.
Improved statistic calculations.
Updated debug graphics slightly.
Narrowly avoided adding a false optimization (thanks Rsim!).
Corrected firing wave origin point.
Adjusted aim location to fire through the center of wave bins rather than at the first corner.
Optimized by ProGuard - likely why it fails on many clients.
3 - G1936 - 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.
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.
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.