(Completed tasks have "done" and a date afterwards.)
(Fixed bugs have "fixed" and a date afterwards.)
Nearly all of my timeout bugs have been infinite loops in my targeting system where I'll assume that something has to happen eventually that never does. As a precaution I have a maximum time-to-target beyond which I don't bother taking a shot, which also ends my loops, but sometimes I get foolhardy and don't use it. Hence the infinite loops. -- Martin Alan Pedersen
Thanks - I'll look at that and see what I can do. It only seems to happen about once in 30 rounds, so it's not a big issue, but it's annoying nonethelesss. Also, I think I've only seen the timeout occur when robocode is minimized. -- Greywhind
Added some more to-dos. I think it's time to enter Constitution into the RoboRumble@Home competition now, since his targeting is already better than my other robots. This way, I'll have something to compare future versions to. -- Greywhind
I'm happy to see the 40-point jump in rating from Wisdom, my previous best robot, and I hope that the addition of the Musashi trick will give Constitution another boost in the rankings as soon as I put in the new version. -- Greywhind
Although Constitution went up 14 points, I think you still have some problems with the MusashiTrick. My HOT-bot GrubbmOgre for example, still wins. I looked at a battle between those two, and I noticed the following three things, although only the first (and maybe the second) is Musashi-related.
I appreciate the tips, Grubbm, although I hadn't noticed the disabled Musashi trick because of the turning, I had seen all of the above. I'll look into fixing them. -- Greywhind
I've made changes based on your suggestions, Grubbm. -- Greywhind
Apparently, WallSmoothing is not likely to help my bot. Also, dynamic distancing has mixed results, and random velocity does more harm than good. The one thing that I have found useful so far is trying to avoid full-lead targeting by switching directions if I haven't switched since the bullet I'm dodging was fired. Anyone care to comment on the usefulness of the above?
Also, I found that my attempts at energy management did little (although not firing when it will disable you is definitely a good idea).
Another possible change I've thought about but have not implemented yet is head-on avoidance (since my movement has a head-on spike). That would mean finding the probable head-on targeting angle of each bullet and avoiding the area where it would hit. Any comments? -- Greywhind
Now releasing Constitution v. 0.7! Wish it luck with its new GF targeting. -- Greywhind
Constitution v.0.7 was using low power bullets even against ram bots, which is a bad idea, since they kill you unless you fire 3.0. Now it's fixed... hopefully that will put it above v.0.5.1's rating. -- Greywhind
I think its not easy to desing a dynamic distancing bot, i failed. But i think there is no need to do dynamic distancing, its better to adjust your gun and movement to one distance. Something about 350 seems to be a good distance for your bot. --Krabb