Difference between revisions of "Thread:Talk:Épéeist/Code mods"

From Robowiki
Jump to navigation Jump to search
(mod to account for distance)
 
Line 5: Line 5:
 
I'm using Jikes as a compiler, and then I post-process the .jar with ProGuard to shrink another 1 to 4 bytes off.
 
I'm using Jikes as a compiler, and then I post-process the .jar with ProGuard to shrink another 1 to 4 bytes off.
  
I modded the first gun to also take distance into account on everything except the match position, after compile and shrink it is a healthy 249.
+
I modded the first gun to also take distance into account on everything except the match position and added <code>setAdjustGunForRobotTurn(true);</code>, after compile and shrink it is a healthy 249.
  
 
Here it is: [https://dl.dropbox.com/u/4066735/sheldor.nano.Epeeist_2.0.jar]
 
Here it is: [https://dl.dropbox.com/u/4066735/sheldor.nano.Epeeist_2.0.jar]

Latest revision as of 21:51, 19 March 2013

OK, I've looked over the code. Even on a regular compiler you should be able to get this under 250, just use the gun with the hard-coded distances, then make chancesOfReversing final, since you aren't changing the contents anywhere.

However, with my tuned compiler/shrinker setup, I have this bot down to 237 bytes.

I'm using Jikes as a compiler, and then I post-process the .jar with ProGuard to shrink another 1 to 4 bytes off.

I modded the first gun to also take distance into account on everything except the match position and added setAdjustGunForRobotTurn(true);, after compile and shrink it is a healthy 249.

Here it is: [1]