Talk:Selecting Fire Power/Albert

Credits - Selecting Fire Power/Albert Old wiki page: SelectingFirePower Original author(s): Albert

Has anyOne used this ?? I wonder how well this works ? -Jlm0924

As can be seen on the talk on the old wiki page there, I have used my own take/improvement/refinement on this in "RougeDC suvival". It was excellent for gaining survival points, but worked out poorly for score. To fix this, the most recent versions of RougeDC takes a 50/50 balance between optimizing energy gain, and optimizing for bullet damage score, and that seems to work very well overall. I do plan to eventually adapt the concept to the melee environment for Glacier but lately I'm really not getting much time for Glacier... --Rednaxela 06:20, 6 January 2010 (UTC)

I also tried something like this in Dookious 1.60, with similar results. Then again, simply firing less or with lower power might be what gained the survival points, not the fancy calculations. You can see the improved survival: Dookious 1.60 vs 1.573c. The way Robocode scoring works, it's just hard to balance the weight of survival vs bullet damage scoring in a formula. It may work better in melee, though, since survival means so much more there. --Voidious 15:05, 7 January 2010 (UTC)

One note about melee, is I think it's significantly more difficult to implement in melee, plus I've found from experience that exact bulletpower has less impact in melee than 1v1 despite survival being important. This post has reminded me of the automatic firepower selection stuff... and revived my interest... so I've created 'Midboss 1a1c' which is my SaphireEdge gun on RougeDC surfing (with a couple bugfixes), with RougeDC's automatic bulletpower selection. I'm not sure where it'll rank, except above RougeDC. Unfortunately I misuploaded so I'll have to re-upload to the rumble when I get home. But anyway, my plan is to make version '1b''1d''1e' as an experiment in real score optimization ;) --Rednaxela 16:07, 7 January 2010 (UTC)

Didn't see a page for "Midboss" so posting here: version 1b is throwing an exception because RobotStatus.getTime() isn't implemented in 1.6.1.4. --Darkcanuck 15:17, 8 January 2010 (UTC)

Yep, I know. That's why I quickly released 1c within 12 minutes of 1b to fix that, with the comment "Doh, used function from new robocode version only" in my edit to the participants page. I need to make sure to watch out for that closer in the future, because unfortunately clients keep running the stuff despite it being removed from the page within a 12 minute time span. --Rednaxela 15:42, 8 January 2010 (UTC)