Talk:Diamond
I can't believed it, it almost the same thing I'm doing in my TheRiver! (I have the ideas about displacement vector, but never known that it is called displacement vector) Anyway, nicely done! Here are my result that I just ran if you want (EDIT: more, and the debugging graphics is the exactly same as one I'm creating)
The one problem of this robot is lack of one-on-one performance (or you will never see 9 2nds). I saw it lost to Shadow and Phoenix a lot.
» Nat | Talk » 06:16, 15 May 2009 (UTC)
| Rank | Name | Score | Surv. | Bonus | Bullet Dmg. | Bonus | Ram | Bonus | 1st | 2nd | 3rd |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1st | voidious.Diamond 1.0 | 14361 (13%) | 10850 | 540 | 2807 | 164 | 0 | 0 | 6 | 9 | 5 |
| 2nd | abc.Shadow 3.83c | 13453 (12%) | 10100 | 630 | 2633 | 89 | 1 | 0 | 7 | 3 | 5 |
| 3rd | rz.Aleph 0.34 | 12804 (12%) | 9600 | 270 | 2861 | 73 | 0 | 0 | 3 | 4 | 5 |
| 4th | abc.Tron 2.02 | 12261 (11%) | 8450 | 630 | 3052 | 127 | 2 | 0 | 7 | 3 | 3 |
| 5th | kawigi.mini.Coriantumr 1.1 | 11909 (11%) | 450 | 360 | 2998 | 101 | 0 | 0 | 4 | 3 | 3 |
| 6th | florent.XSeries.X2 0.7 | 9472 (9%) | 695 | 90 | 2349 | 84 | 0 | 0 | 1 | 4 | 2 |
| 7th | ags.surreptitious.MiniSurreptitious 0.0.1 | 9411 (9%) | 6550 | 0 | 2785 | 68 | 8 | 0 | 0 | 4 | 5 |
| 8th | tzu.TheArtOfWar 1.2 | 9240 (9%) | 6750 | 90 | 2355 | 42 | 2 | 0 | 1 | 3 | 4 |
| 9th | abc.tron3.Tron 3.11 | 8050 (7%) | 5400 | 360 | 2245 | 42 | 4 | 0 | 4 | 2 | 1 |
| 10th | davidalves.Phoenix 1.02 | 7443 (7%) | 5550 | 180 | 1679 | 32 | 2 | 0 | 2 | 0 | 2 |
Not so bad... 6th place. Lost to Mellaris, Shadow, Tron and Aleph. But it used to win them in battle full of top melee bots! » Nat | Talk » 10:03, 15 May 2009 (UTC)
I haven't focused on the 1v1 movement much yet, because it doesn't matter as much as other things and I don't want to get distracted by it. (There's no hiding what a 1v1 nut I've been so far in my Robocode career.) But the 1v1 performance is pretty decent, I think it's mainly that the gun has trouble hitting surfers (no accounting for firing waves or gun heat yet). --Voidious 13:38, 15 May 2009 (UTC)
Decent? It's very strong in 1v1! It's 1v1 pairings are nearly complete and it's sitting in 11th place. Though... it does get beat by the top mirror-bot in the rumble :)
Man... all these new bots are not only topping RougeDC which used to be in 12th, but are also causing shifts in ranking of old bots so they're now above RougeDC... damn... I really got to get my new stuff out of the garage to join in on this fun! --Rednaxela 15:38, 15 May 2009 (UTC)
- Thanks! The gun doesn't segment on firing waves or gun heat or anything, so it's not a huge surprise that a mirror movement that is reacting to bullet fire ('cause I'm surfing) works well against it. What kind of gun is on PolishedRuby? And why is there no page anywhere for it? --Voidious 17:38, 15 May 2009 (UTC)
- PolishedRuby is just the gun of the latest RougeDC version, on top of a basic 'goto location' based mirror movement, with very slight alterations to energy management. No page for it because 1) Not much to say about it 2) I'm lazy. Diamond is the highest ranking bot I can see that it beats I think, so it shows well how Diamond's gun is notably lacking (in 1v1) against it's own surfing movement. Of course, I'm considering making a second version of PolishedRuby, which mirror's the enemy's firepower and firing time as well... that might demonstrate it even more clearly... ;) --Rednaxela 18:21, 15 May 2009 (UTC)
Wow -- takes me over a year to make a decent gun and you churn out a brand new top melee and 1v1 bot in what, a month or less? --Darkcanuck 15:46, 15 May 2009 (UTC)
- Thanks, but that's so not a fair comparison. =) Basing anything off the Dookious movement would yield a really nice rating in 1v1, and I've got plenty of experience with DC and Minimum Risk Movement from Lukious and BrokenSword. --Voidious 17:38, 15 May 2009 (UTC)
It lost to a LOT of surfer, count from lowest score: Phoenix, Dookious, Ascendent, RougeDC, CassiusClay, Chalk, Shadow, YersiniaPestis, Gauss, DrussGT, Garm, WeeksOnEnd, Hyperion, LifelongObsession, CunobelinDC, MathcupAGF (not a surfer actually) and PolishedRuby (mirror, as Rednaxela mentioned) Perhaps some weight on firing scan will make you score better. » Nat | Talk » 16:12, 15 May 2009 (UTC)
- Don't remind me, I'm trying not to focus on 1v1 here... :-P --Voidious 17:38, 15 May 2009 (UTC)
I'll give you some time before I resume working on a melee bot :-D Seriously, nice work! And it seems strong in 1v1 too! Are you also using your displacement targeting in 1v1? Or do you switch to regular GFs? --Skilgannon 16:14, 15 May 2009 (UTC)
- I also use the displacement targeting in 1v1, getting about 87 in the TCRM right now (full results soon). One point of note is that I invert the vectors depending on the enemy's orbit direction, just like GFs, but I calculate orbit direction relative to the bot closest to the target (whether that's Diamond or another enemy). In 1v1, it's probably not acting much different than GuessFactors, but in Melee, I think it should work better than GFs. If nothing else, it seems far more "right" to me. I was actually considering "wall smoothing" the vectors instead of throwing out ones that would end up off the battlefield, then it would act even more like GFs. ;) --Voidious 17:38, 15 May 2009 (UTC)
Awesome (re)entrance you made in melee! You and justin really shake up that rusty top-10 there. Seems that in melee the gun is more important than in one-on-one. Maybe it is time to say farewell to my old CT-gun . . . --GrubbmGait 17:29, 15 May 2009 (UTC)
- Thanks. I was surprised how much the gun mattered in Melee. I had it in my head that HoT is OK in Melee because of bots like HawkOnFire. This is partly true, of course. But I developed the basic movement first using only HoT, and when I upgraded the gun, the performance in my test beds shot up dramatically. --Voidious 17:38, 15 May 2009 (UTC)
Just asking quick, does this robot select enemy or do the thing like the one describe at Shadow/ShadowsMeleeGun? » Nat | Talk » 06:42, 18 May 2009 (UTC)
