Difference between revisions of "Toorkild/VersionHistory"
< Toorkild
Jump to navigation
Jump to search
m (category) |
Skilgannon (talk | contribs) (0.1.1CT, 0.1.3) |
||
| Line 1: | Line 1: | ||
| + | 0.1.3: | ||
| + | *Made the random factor exactly +-1 pixel instead of a random value somewhere between -4 and +4 pixels | ||
| + | |||
| + | 0.1.1CT: codesize: 733 score: 80.9 APS | ||
| + | * Matches across rounds again for more codesize | ||
| + | * CT: Catch This! Introduces a random factor in aim to prevent enemy from shooting down bullets | ||
| + | |||
0.1.2: codesize: 749 score: pulled | 0.1.2: codesize: 749 score: pulled | ||
* Somehow managed to squeeze the codesize down even further | * Somehow managed to squeeze the codesize down even further | ||
Revision as of 22:49, 8 October 2009
0.1.3:
- Made the random factor exactly +-1 pixel instead of a random value somewhere between -4 and +4 pixels
0.1.1CT: codesize: 733 score: 80.9 APS
- Matches across rounds again for more codesize
- CT: Catch This! Introduces a random factor in aim to prevent enemy from shooting down bullets
0.1.2: codesize: 749 score: pulled
- Somehow managed to squeeze the codesize down even further
- Shoots 3 power bullets if the last tick revealed a match over 30 ticks long
- There was a bad bug somewhere...
0.1.1: codesize: 749 score: 2008
- Switched to bit-shifting to store both adv-vel and lat-vel in one char, instead of a different char for each. Prevents 'half-off' matches that don't get rebuilt properly.
- Doesn't match or rebuild across rounds
- Utilized the Arrays.sort and Arrays.binarySearch to reduce my codesize - so now depends on Java 1.5+ (as does Robocode, so it shouldn't be a problem)
0.1: codesize: 742 score: 2006 after 1576 First release!
