Viewing a history listing
|16:32, 20 June 2013||Voidious||(Reply to Rumble Topping)|
|15:24, 20 June 2013||Sheldor||(Reply to Rumble Topping)|
|19:28, 18 June 2013||Skilgannon||(Reply to Rumble Topping)|
|15:58, 18 June 2013||AW||(Reply to Rumble Topping)|
|15:49, 18 June 2013||Voidious||(Reply to Rumble Topping)|
|14:39, 18 June 2013||Chase-san||(Reply to Rumble Topping)|
|01:22, 18 June 2013||Nz.jdc||(Reply to Rumble Topping)|
|16:33, 17 June 2013||Chase-san|
With this you are at the top of every one of the one vs one rumbles. Now all you have to do is melee nano, micro and mini rumbles, then the team and twin duel.
Yes, he is winning a bit much. Someone should do something about that. Trouble is he is winning because he is good and he puts in a lot of effort. Talent+work, a hard combination to beat :-/
I am working on updating my microbot at the moment as it is languishing down in 7th. I am pretty sure I can raise it a few spots but I doubt it will be able to challenge 1st.
My next project is to make a mini bot by adding wave surfing to my micro, but as a new minibot entrant that is unlikely to be a contender for a long while.
I have put a lot of effort into my nanos, even stealing Yatagan's movement, but have only managed to get up to 2nd. I have one bot that might win (my bechmarks suggest it will rate 80.6 APS, just above Yatagan), but am hesitant to release it as it uses an opponent table, which is cheesy.
The only other option I can think of to topple Yatagan is to update LittleBlackBook, which as I mentioned in a previous post should be able to get up to around 84 APS. Updating all those tables would be hard work. I dare say Mike had lots of testing and table generating code for LBB that I would have to rewrite from scratch to do a proper job.
I might've been the last to come "close" to stealing of his crowns, in General 1v1 (RumbleArchives:RoboRumble 20120730). So it's one of your turns. :-P
I'm trying, I'm trying. I've just been spending my robocode time writing the guide to Gilgalad (about 1/3 of the way done with the javadocs). I find that taking a break from robocode has been very bad. It means I need to re-learn lots of the stuff I was working on, but hopefully documenting Gilgalad will get me back to where I left off...
Well, I share Nano with Sheldor, so I don't think that really counts. He got it most of the way there with the main structure, I did the tuning and feature-cramming.