User talk:BenHorner

---

The old wiki content is still available, but not so easy to access. Voidious posted a note somewhere about how to access it -- I can copy it over if you like. Talk pages are for comments, yes. You should also sign your posts, on this wiki you just need to put in four tildes (~~~~) and it'll add your name + timestamp. The rumble is definitely running but on a new server. See RoboRumble and Darkcanuck/RRServer for details. I also put a copy of most older bots on my webserver since the repository wasn't behaving: http://darkcanuck.net/rumble/robots --Darkcanuck 04:03, 8 May 2009 (UTC)

If you want to know basic of this new wiki, look at {{Welcome}}. It contain basic information about using this wiki. » Nat | Talk » 10:38, 8 May 2009 (UTC)

Thanks for the info and the link(s). --BenHorner 21:52, 8 May 2009 (UTC)

I wouldn't mind having that link to the old wiki, or to the page that describes how to get there. I'm sure I put some stuff on there that I'd like to reread now. --BenHorner 00:42, 11 May 2009 (UTC)

There's some instructions on Talk:Migration#Now_at_RoboWiki.net. I will move the old wiki content to a subdomain at the new server. Actually, I already did, but last time I brought it up, the server ended up totally crashing. We had another bout of downtime after that, though, so maybe it wasn't really my fault - will be trying again soon. --Voidious 14:07, 11 May 2009 (UTC)

min/max/avg battle length (in turns/ticks)?

Can anyone give me a feel for how long battles average? I want to use an array list to keep track of the ticks as they go by, for the random access, but I'd rather not make it reallocate itself unnecessarily often, especially when it's big. Thanks for any help. --BenHorner 23:48, 24 May 2009 (UTC)

Obviously it varies, but for 1v1, I usually ballpark it as 700-800 ticks per round. I think 25k in a 35 round battle is a good estimate. --Voidious 00:01, 25 May 2009 (UTC)

But for wave surfer battle, is usually over 1,000. I think it's around (for surfer) 1,300 - 1,500 ticks. » Nat | Talk » 11:53, 25 May 2009 (UTC)

So surfers get hit by bullets way less often? I'm really going to have to look into that sooner or later. --BenHorner 14:24, 25 May 2009 (UTC)

Sorry, to make more clear, a battle with two wave surfers are over 1,000 ticks since the well-implements surfers usually almost dodge every enemy bullets, I have to said well-implements since some surfer, like BlackHole 0.1.11 cannot dodge even HOT (really, I had broke something in it and I don't wanna fix it). And even perfect AS gun can't make over 50% hit rate now. » Nat | Talk » 14:47, 25 May 2009 (UTC)

Well, not just because of that. Also because most wave surfers favour huge distances compared to most other bots. About 400 is a typical wave surfer distance for instance, whereas many smaller bots prefer 200 to 300 distance from what I see. --Rednaxela 15:47, 25 May 2009 (UTC)

I really don't think 1v1 battles ever last 1300 ticks per round... I just fired up some Dookious vs Dookious and Dookious vs Ascendant battles, and the longest round I saw was mid-700s. I'm not sure surfers have anything to do with battle length. Things that would make a battle long are firing low power bullets and/or the battle being close (so the longest-living bot gains back as much energy as possible before dying). --Voidious 15:54, 25 May 2009 (UTC)

discrepancy between HitRobotEvent and ScannedRobotEvent?

I was wondering if anyone else has noticed a discrepancy between the enemy energy reported by the HitRobotEvent, and the ScannedRobot event...? I have my bot which currently doesn't move, going up against Crazy in 35 round battles to test my radar and bookkeeping code. It seems like about twice per (35 round) battle I get a discrepancy of exactly 0.1 energy points. I believe the HitRobotEvent happens first, and reports lets say 54.60 for the enemy energy, and in the same round a ScannedRobotEvent happens reporting 54.50 for the enemy energy. This is a small difference, but I'm wondering if I should be accounting for fuzziness (something like sensor noise) in my bookkeeping code, rather than planning for exactness. Does this kind of thing happen many places? --BenHorner 17:11, 25 May 2009 (UTC)