Geomancy/Version History
< Geomancy
Jump to navigation
Jump to search
Pages: Main page · Code · Version History · Discussion
Versions
- 7 - ? - Major tweaks
- Switched to sane rolling depths for surfing.
- Made surfing and gun rolling depths variable based on degree of segmentation.
- Increased minimum distance for dynamic distancing.
- Fixed equation for orthogonality. (Thanks Voidious)
- Decreased velocity weighting to 12.5%.
- 6 - G1941.7 - Tweaks and adjustments
- Decreased surfing rolling depth a lot - from 50 to 15. Should be much more adaptable now.
- Added dynamic distancing.
- Added axis weighting, permitting a degree of influence on which segments are trusted more, regardless of how their data looks.
- Weighted velocity 25% higher than other axes. This should produce solid gains against simple targeters.
- 5 - G1940.9 - Added Orthogonality and BulletFlightTime axes
- Added two new axes.
- Updated debug graphics.
- 4a - G1941.1 - 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.
