Archived talk:User:Nat 20090406

Just wanted to say welcome, and glad you're already making yourself at home. :-) Best of luck with your bots! --Voidious 21:59, 3 January 2009 (UTC)

Thanks, Voidious for your warm welcome! Therefore, I think my robots have the best luck already :) (How many time you see 3-months-experienced robocode programmer has his robot in top 10?) --Nat 07:51, 4 January 2009 (UTC)

Hey, I have problem with the old wiki! I can't update participant list! Does anyone know what happen? --Nat

Maybe you're running into the protection the old wiki had against edits which modify too many external urls at once? It did have an anti-spam measure where edits that added/changed too many urls would silently be dropped. If this is it could can just spread your editing of the list over multiple edits to make it work --Rednaxela 17:41, 17 February 2009 (UTC)

• Thanks, I will move all my bot to my new download page (http://nat.robothai.net/robots/) I'm changing 6 urls on Participants page and 3 urls on MeleeParticepants page. I soon found out that the limit is 2 urls. I have one question to ask, is it your code? If it is, could you increase that? I must scroll to bottom of the page to edit it again. » Nat | Talk » 13:52, 18 February 2009 (UTC)

Hi, I've read about your competitions. You are very lucky to have such contests in you country. And the prizes are nice, too. ;) --HUNRobar 17:45, 17 February 2009 (UTC)

Thanks, Robar!

To all robocoders, I've some question:

1. How many of you still active? I have some list that I post to Robar, but I really know how many are they?
2. David Alves start developing roborumble.org since 2007, 2 years passed, nothing happen! Where is him
3. Are still Paul, Kawigi, David Alves and many more remember robocode?
4. Is ABC take a break from robocode?
5. Are Voidious and other robocoder still active or semi-active?
6. Are there anyone except me, Robar and CrazyBassoonist‎ still developing their robot? Almost every bot is the same as last six months.

These are stupid questions, but feel lonely in this robocode world now. I'm almost last user entered robocode community. (Not sure on which me or CrazyBassoonist is last.) I've read on (mostly) quality articles by Paul, Kawigi, David Alves, ABC and many others. (these 4 people is one who I want to talk to) Thanks. » Nat | Talk » 13:52, 18 February 2009 (UTC)

I'm active, as is Rednaxela. I haven't been doing much with my bots mostly due to lack of time. In the limited time for testing that I have had, the changes that I tried didn't help, so I haven't released a new DrussGT. My melee wavesurfing algorithm is about half completed. So far I can keep track of all the waves that get (or may have been) fired. I still have to add some logic for deciding which wave hit a bot based on which firing bot gets an energy bonus. But it's already a monster... --Skilgannon 14:58, 18 February 2009 (UTC)

Like Skilgannon noted, I'm active. Well, as far as David Alvis and roborumble.org, it's a matter of life being busy and getting in the way. See this post for more information. Paul/Kawigi/David I don't know details of indeed haven't been active. ABC did make some tweaks to Shadow a few months ago I believe so not entirely inactive, not to mention he put significant effort into hosting a temporary RR server during the transition between the old one and DarkCanuck's one, and also is to credit for nice things like the shiney LRP graph on DarkCanuck's server. Some like Kev have been mostly sleeping, though Kev was briefly awoken by LunarTwins taking the crown he held in TwinDuel, and also to make a multiple choice pattern matcher in attempt to take the micro crown. GrubbmGait while inactive in 2008, has here expressed intent to be more active in 2009. As far as "still developing their robot", I believe a number of people, such as myself are not actively working on any robot we already have released much, but instead are slowing working on new robots/ideas. Personally class is keeping me rather busy, but I am squeezing in some Robocoding time, which I was earlier spending on SaphireEdge and more recently on the SaphireSlippers (speaking of which I just had some promising results for yesterday). --Rednaxela 15:30, 18 February 2009 (UTC)

Hi! I saw you uploaded nano.AW at almost the same time I did with nano.Prestige. :) Great one, but not better than Prestige. :P Take a look at fighting each other, both in rankings and battles. ;) --HUNRobar 20:43, 18 February 2009 (UTC)

Melee wavesurfing

In reply to your question:

I think I must keep track of enemy gunheat instead of energy drop.
I also think that TrueSurf is impossible for extend-robot so I
''must'' use goto-style surfing. Anyone have idea?

Here are my thoughts:

In some ways, I would say the challenge is similar to that of melee wavesurfing which I've been thinking about, because in both you cannot keep a constant radar lock. I'd agree that you need be tracking gunheat in order to get reasonable precision with it. Here's the way I'd do it:

• Every time you see the enemy, do energy based calculations to see if they've fired since you last saw them, and if so, how powerfully they fired.
• Use gunheat tracking which presumes they always fire as soon as possible, in order to estimate WHICH tick tick they fired on and place the wave accordingly.
• In the event that they don't fire between times that you've seen them and their gunheat is 0, then your gunheat tracking data for the next time they fire is invalid for sure, and you'd either have to presume they fired in the middle of the time you didn't see them OR start making waves for every tick they could have fired during. Generally, this would not be an issue because this would only happen if they stopped firing.
• To know where they fired from you need to use interpolation of their location of course

That's the approach I'd take to melee/extend-robot wavesurfing anyways. Really, I'd say the only difference between melee goto wavesurfing, and extend-robot wavesurfing, would be that the extend-robot also wouldn't be able to turn while moving forward or scan while moving. The basic challenges in the algorithm seem the same to me.

--Rednaxela 21:14, 4 February 2009 (UTC)

Well, I think melee wavesurfing is too hard ;) I had seen melee wavesurfing challenge, and I saw that almost index is under 1! Turning doesn't take too long if velocity is zero but I must have a very unique precise predictor. In order to get enemy fire time if his/her gunheat is still zero, I think I'll use statistic-base algorithm. I also think that some bot doesn't fire until its gun correctly aligned. I think I must use the onHitByBullet plus some enemy gun projection in order to place wave correctly. Here are some more of my ideas for it (which can add to your above):

• Don't remove waves until it fully out of battlefield.
• If you get hit by bullet, calculate how many tick it flight and set new gunheat.
• In a rare case of 2 bullets were flight during missing scans, I don't know how to do!

» Nat | Talk » 12:26, 5 February 2009 (UTC)