http://robowiki.net/w/api.php?action=feedcontributions&feedformat=atom&user=Miked0801 2026-04-30T01:12:34Z User contributions MediaWiki 1.34.1 http://robowiki.net/w/index.php?title=User:Miked0801&diff=55281 2019-03-08T04:21:21Z

<p>Miked0801: </p> <hr /> <div>I'm primarily a nano-bot author as that is where my passions lie. I'm still active in creating new bots along with helping anyone I can. Below are my current bots.<br /> <br /> ----<br /> <br /> My Bots:<br /> * [[NanoBots]]:<br /> ** [[DustBunny]] - Melee Anti-grav bot. Nano Melee Champion<br /> ** [[Infinity]] - Melee Pattern mover with decent gun<br /> ** [[Moebius]] -1v1 pattern matcher. <br /> ** [[Tide]] - Rambot - retired<br /> ** [[LittleBlackBook]] - String Based Guess Factor bot. Nano Rumble Champion, Currently 3rd in Micros and rising<br /> <br /> ----<br /> <br /> Uh oh, I think I just figured out how to completely cheat the codesize thing. I could probably fit all of [[Toorkild]]'s code into a nanobot. How? Running Java Byte code from a static buffer. Take any robot's byte code and drop it statically into an array/string/whatever. Array values do not count towards size. Write a routine that jumps the code pointer into the array. You are now running a nearly infinite amount of code without a major size hit. I could probably write a bot like this in an evening if I really wanted to cheat and win this badly. Thoughts? --[[User:Miked0801|Miked0801]] 01:02, 28 May 2009 (UTC)<br /> <br /> : Oy! Not sure how we'd deal with that. I wonder if Robocode's classloaders could prevent this from happening? Or the code size utility produce some kind of &quot;N/A&quot; code size for classes that do this? --[[User:Voidious|Voidious]] 02:56, 28 May 2009 (UTC)<br /> <br /> : I'm fairly sure the Robocode security manager wouldn't allow this, I once tried using Java Reflection and the security manager disabled my bot immediately. However, if it is possible, I think we should either 1) modify the Codesize util so it looks for bytecode in strings as well or 2) fix the security manager so that it isn't possible to jump the code pointer into a static buffer. But why don't you try it and see if it works =) --[[User:Skilgannon|Skilgannon]] 09:19, 28 May 2009 (UTC)<br /> <br /> : Er, I'm 90% sure that jumping the code pointer into a string or array, is completely impossible in java bytecode in the first place. I'm pretty sure that program memory and data memory are considered comletely seperate in the VM... So all this to do with the classloaders/security managers/codesize util is unnecessaary... --[[User:Rednaxela|Rednaxela]] 12:45, 28 May 2009 (UTC)<br /> <br /> : I don't think this is impossible with either javac or Jikes, but how about Jasmin you are working on, Rednaxela? I'm quite sure we can do that in assembly, but not sure with Java assembly. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 13:02, 28 May 2009 (UTC)<br /> <br /> :: In machine code for x86 or ARM or most other physical architectures, that is possible, but java bytecode follows a different model. In most physical architectures, &quot;program memory&quot; and &quot;data memory&quot; are the same thing, so one can use the same memory for both purporses. The Java VM follows a different architecture pattern, where &quot;program membory&quot; and &quot;data memory&quot; are seperate and no bytecode instruction has a parameter that can refer to either, only one. (By the way, I'm pretty sure you meant to say &quot;I think this is impossible&quot; or &quot;I don't think this is possible&quot;. Only need one negative :)) --[[User:Rednaxela|Rednaxela]] 13:10, 28 May 2009 (UTC)<br /> <br /> ::: Thank you for the info. I mean &quot;I don't think this is possible&quot; =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 13:25, 28 May 2009 (UTC)<br /> <br /> Next Codesize question :) - Is there any way to tell the compiler that you no longer a paramter and to use that register for a local var? That's free bytes if you can do it. --[[User:Miked0801|Miked0801]] 23:39, 28 May 2009 (UTC)<br /> <br /> : With javac/jikes? No. With an assembler for java bytecode? Sure! ;) --[[User:Rednaxela|Rednaxela]] 23:49, 28 May 2009 (UTC)<br /> :: Bah, I program in dozens of asm languages already. One more wouldn't be hard. Of course the source file would no longer compile... --[[User:Miked0801|Miked0801]] 00:59, 29 May 2009 (UTC)<br /> [[Category:Bot Authors|Miked0801]]<br /> ::: I hate to put another weapon in your arsenal, but since this inspired me to audit my codesize in a new way I think it's only fair. [http://andrei.gmxhome.de/bytecode/index.html Check this out]. In a nano there's a small enough amount of code that you really can audit where every single byte is going. -- [[User:Kuuran|Kuuran]] 03:32, 7 October 2009 (UTC)<br /> <br /> - Hi Mike, congrats on getting LittleBlackBook to the top. I was surprised my Neophytes lasted as long as they did. LBB is a very sneaky concept and impressively scrunched into nanosize. I especially like the way you index into the beginning of the GF string to add custom movement.<br /> I thought of using a string buffer for bytecode way back. I had a few tries playing with the classloader and got the concept to work in isolation, but the securitymanager would not permit it to run in robocode. Didn't try very hard though, so not totally sure. <br /> --[[User:JohnCleland|JohnCleland]] 21:44, 22 October 2009 (UTC)<br /> : Thanks for the kind words :) --[[User:Miked0801|Miked0801]] 19:04, 18 January 2010 (UTC)<br /> <br /> ----<br /> <br /> Hi all,<br /> <br /> I come back here every now and then and am always impressed to see things humming quietly along. When I first started my nano adventure, it was while staying up late watching and helping to feed my infant daughter. I was a wide eyed game programmer with some extra time. Now, a father of 3 with my eldest approaching high school, this site and hobby helps me to reflect on just how far things have come here. Getting LBB tuned required more computer processing power than I had at the time, so I occasionally used a &quot;few&quot; computers at my place of employment late at night to run all the tables. Now, my home system could probably chew through the calcs by itself it the same amount of time. I always promise myself that I will spend a week here or there getting LBB or Moebius whipped back into shape, but life has other ideas. So, I will continue to stop by every now and then, I will tune LBB here or there as I can, and I will continue to enjoy watching people discover this awesome little distraction that we have poured so much effort into. --[[User:Miked0801|Miked0801]] 10:59, 23 August 2014 (UTC)<br /> <br /> ----<br /> <br /> Another year or so has passed and I still grin to see my [[DustBunny]] doing its thing. Thanks to the author who fixed up [[LittleBlackBook]]'s tables. A fun idea that went way to far. I'm still working in the game industry after all these years. Found this page by accident after a bit of time and had some nice memories. Keep things humming!<br /> <br /> --[[User:Miked0801|Miked0801]] 21:51, 17 December 2015<br /> <br /> : A belated hello and good to see you. :-) Been pretty quiet around here lately. Happy Holidays! --[[User:Voidious|Voidious]] ([[User talk:Voidious|talk]]) 19:07, 30 December 2015 (UTC)<br /> <br /> : Still alive. Still watching my bots tear up the nano ranks after all these years :) ---[[User:Miked0801|Miked0801]] ([[User talk:Miked0801|talk]])<br /> <br /> [[Category:Bot Authors|Miked0801]]</div>

Miked0801 http://robowiki.net/w/index.php?title=User:Miked0801&diff=34689 2015-12-18T05:52:23Z

<p>Miked0801: Quick hello world, I'm still alive :)</p> <hr /> <div>I'm primarily a nano-bot author as that is where my passions lie. I'm still active in creating new bots along with helping anyone I can. Below are my current bots.<br /> <br /> ----<br /> <br /> My Bots:<br /> * [[NanoBots]]:<br /> ** [[DustBunny]] - Melee Anti-grav bot. Nano Melee Champion<br /> ** [[Infinity]] - Melee Pattern mover with decent gun<br /> ** [[Moebius]] -1v1 pattern matcher. <br /> ** [[Tide]] - Rambot - retired<br /> ** [[LittleBlackBook]] - String Based Guess Factor bot. Nano Rumble Champion, Currently 3rd in Micros and rising<br /> <br /> ----<br /> <br /> Uh oh, I think I just figured out how to completely cheat the codesize thing. I could probably fit all of [[Toorkild]]'s code into a nanobot. How? Running Java Byte code from a static buffer. Take any robot's byte code and drop it statically into an array/string/whatever. Array values do not count towards size. Write a routine that jumps the code pointer into the array. You are now running a nearly infinite amount of code without a major size hit. I could probably write a bot like this in an evening if I really wanted to cheat and win this badly. Thoughts? --[[User:Miked0801|Miked0801]] 01:02, 28 May 2009 (UTC)<br /> <br /> : Oy! Not sure how we'd deal with that. I wonder if Robocode's classloaders could prevent this from happening? Or the code size utility produce some kind of &quot;N/A&quot; code size for classes that do this? --[[User:Voidious|Voidious]] 02:56, 28 May 2009 (UTC)<br /> <br /> : I'm fairly sure the Robocode security manager wouldn't allow this, I once tried using Java Reflection and the security manager disabled my bot immediately. However, if it is possible, I think we should either 1) modify the Codesize util so it looks for bytecode in strings as well or 2) fix the security manager so that it isn't possible to jump the code pointer into a static buffer. But why don't you try it and see if it works =) --[[User:Skilgannon|Skilgannon]] 09:19, 28 May 2009 (UTC)<br /> <br /> : Er, I'm 90% sure that jumping the code pointer into a string or array, is completely impossible in java bytecode in the first place. I'm pretty sure that program memory and data memory are considered comletely seperate in the VM... So all this to do with the classloaders/security managers/codesize util is unnecessaary... --[[User:Rednaxela|Rednaxela]] 12:45, 28 May 2009 (UTC)<br /> <br /> : I don't think this is impossible with either javac or Jikes, but how about Jasmin you are working on, Rednaxela? I'm quite sure we can do that in assembly, but not sure with Java assembly. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 13:02, 28 May 2009 (UTC)<br /> <br /> :: In machine code for x86 or ARM or most other physical architectures, that is possible, but java bytecode follows a different model. In most physical architectures, &quot;program memory&quot; and &quot;data memory&quot; are the same thing, so one can use the same memory for both purporses. The Java VM follows a different architecture pattern, where &quot;program membory&quot; and &quot;data memory&quot; are seperate and no bytecode instruction has a parameter that can refer to either, only one. (By the way, I'm pretty sure you meant to say &quot;I think this is impossible&quot; or &quot;I don't think this is possible&quot;. Only need one negative :)) --[[User:Rednaxela|Rednaxela]] 13:10, 28 May 2009 (UTC)<br /> <br /> ::: Thank you for the info. I mean &quot;I don't think this is possible&quot; =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 13:25, 28 May 2009 (UTC)<br /> <br /> Next Codesize question :) - Is there any way to tell the compiler that you no longer a paramter and to use that register for a local var? That's free bytes if you can do it. --[[User:Miked0801|Miked0801]] 23:39, 28 May 2009 (UTC)<br /> <br /> : With javac/jikes? No. With an assembler for java bytecode? Sure! ;) --[[User:Rednaxela|Rednaxela]] 23:49, 28 May 2009 (UTC)<br /> :: Bah, I program in dozens of asm languages already. One more wouldn't be hard. Of course the source file would no longer compile... --[[User:Miked0801|Miked0801]] 00:59, 29 May 2009 (UTC)<br /> [[Category:Bot Authors|Miked0801]]<br /> ::: I hate to put another weapon in your arsenal, but since this inspired me to audit my codesize in a new way I think it's only fair. [http://andrei.gmxhome.de/bytecode/index.html Check this out]. In a nano there's a small enough amount of code that you really can audit where every single byte is going. -- [[User:Kuuran|Kuuran]] 03:32, 7 October 2009 (UTC)<br /> <br /> - Hi Mike, congrats on getting LittleBlackBook to the top. I was surprised my Neophytes lasted as long as they did. LBB is a very sneaky concept and impressively scrunched into nanosize. I especially like the way you index into the beginning of the GF string to add custom movement.<br /> I thought of using a string buffer for bytecode way back. I had a few tries playing with the classloader and got the concept to work in isolation, but the securitymanager would not permit it to run in robocode. Didn't try very hard though, so not totally sure. <br /> --[[User:JohnCleland|JohnCleland]] 21:44, 22 October 2009 (UTC)<br /> : Thanks for the kind words :) --[[User:Miked0801|Miked0801]] 19:04, 18 January 2010 (UTC)<br /> <br /> ----<br /> <br /> Hi all,<br /> <br /> I come back here every now and then and am always impressed to see things humming quietly along. When I first started my nano adventure, it was while staying up late watching and helping to feed my infant daughter. I was a wide eyed game programmer with some extra time. Now, a father of 3 with my eldest approaching high school, this site and hobby helps me to reflect on just how far things have come here. Getting LBB tuned required more computer processing power than I had at the time, so I occasionally used a &quot;few&quot; computers at my place of employment late at night to run all the tables. Now, my home system could probably chew through the calcs by itself it the same amount of time. I always promise myself that I will spend a week here or there getting LBB or Moebius whipped back into shape, but life has other ideas. So, I will continue to stop by every now and then, I will tune LBB here or there as I can, and I will continue to enjoy watching people discover this awesome little distraction that we have poured so much effort into. --[[User:Miked0801|Miked0801]] 10:59, 23 August 2014 (UTC)<br /> <br /> ----<br /> <br /> Another year or so has passed and I still grin to see my [[DustBunny]] doing its thing. Thanks to the author who fixed up [[LittleBlackBook]]'s tables. A fun idea that went way to far. I'm still working in the game industry after all these years. Found this page by accident after a bit of time and had some nice memories. Keep things humming!<br /> <br /> --[[User:Miked0801|Miked0801]] 21:51, 17 December 2015<br /> <br /> [[Category:Bot Authors|Miked0801]]</div>

Miked0801 http://robowiki.net/w/index.php?title=Thread:Talk:LittleBlackBook/Updated/reply_(4)&diff=33681 2014-09-01T16:29:32Z

<p>Miked0801: Reply to Updated</p> <hr /> <div>Went and downloaded latest client and found it is not supported by rumble. Will try an earlier one when I get a chance. Confirmed that NZ did indeed figure out very well indeed how LBB works. I've found my old test harness and it all still works. Now to find the 2 hour block required to get a couple of bots added. BTW, if anyone is a student of Digipen, I now teach a class there in addition to my current job so come look me up. --[[User:Miked0801|Miked0801]] ([[User talk:Miked0801|talk]]) 16:29, 1 September 2014 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=User:Miked0801&diff=33612 2014-08-23T17:17:11Z

<p>Miked0801: Quick wow the world has changed update.</p> <hr /> <div>I'm primarily a nano-bot author as that is where my passions lie. I'm still active in creating new bots along with helping anyone I can. Below are my current bots.<br /> <br /> ----<br /> <br /> My Bots:<br /> * [[NanoBots]]:<br /> ** [[DustBunny]] - Melee Anti-grav bot. Nano Melee Champion<br /> ** [[Infinity]] - Melee Pattern mover with decent gun<br /> ** [[Moebius]] -1v1 pattern matcher. <br /> ** [[Tide]] - Rambot - retired<br /> ** [[LittleBlackBook]] - String Based Guess Factor bot. Nano Rumble Champion, Currently 3rd in Micros and rising<br /> <br /> ----<br /> <br /> Uh oh, I think I just figured out how to completely cheat the codesize thing. I could probably fit all of [[Toorkild]]'s code into a nanobot. How? Running Java Byte code from a static buffer. Take any robot's byte code and drop it statically into an array/string/whatever. Array values do not count towards size. Write a routine that jumps the code pointer into the array. You are now running a nearly infinite amount of code without a major size hit. I could probably write a bot like this in an evening if I really wanted to cheat and win this badly. Thoughts? --[[User:Miked0801|Miked0801]] 01:02, 28 May 2009 (UTC)<br /> <br /> : Oy! Not sure how we'd deal with that. I wonder if Robocode's classloaders could prevent this from happening? Or the code size utility produce some kind of &quot;N/A&quot; code size for classes that do this? --[[User:Voidious|Voidious]] 02:56, 28 May 2009 (UTC)<br /> <br /> : I'm fairly sure the Robocode security manager wouldn't allow this, I once tried using Java Reflection and the security manager disabled my bot immediately. However, if it is possible, I think we should either 1) modify the Codesize util so it looks for bytecode in strings as well or 2) fix the security manager so that it isn't possible to jump the code pointer into a static buffer. But why don't you try it and see if it works =) --[[User:Skilgannon|Skilgannon]] 09:19, 28 May 2009 (UTC)<br /> <br /> : Er, I'm 90% sure that jumping the code pointer into a string or array, is completely impossible in java bytecode in the first place. I'm pretty sure that program memory and data memory are considered comletely seperate in the VM... So all this to do with the classloaders/security managers/codesize util is unnecessaary... --[[User:Rednaxela|Rednaxela]] 12:45, 28 May 2009 (UTC)<br /> <br /> : I don't think this is impossible with either javac or Jikes, but how about Jasmin you are working on, Rednaxela? I'm quite sure we can do that in assembly, but not sure with Java assembly. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 13:02, 28 May 2009 (UTC)<br /> <br /> :: In machine code for x86 or ARM or most other physical architectures, that is possible, but java bytecode follows a different model. In most physical architectures, &quot;program memory&quot; and &quot;data memory&quot; are the same thing, so one can use the same memory for both purporses. The Java VM follows a different architecture pattern, where &quot;program membory&quot; and &quot;data memory&quot; are seperate and no bytecode instruction has a parameter that can refer to either, only one. (By the way, I'm pretty sure you meant to say &quot;I think this is impossible&quot; or &quot;I don't think this is possible&quot;. Only need one negative :)) --[[User:Rednaxela|Rednaxela]] 13:10, 28 May 2009 (UTC)<br /> <br /> ::: Thank you for the info. I mean &quot;I don't think this is possible&quot; =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 13:25, 28 May 2009 (UTC)<br /> <br /> Next Codesize question :) - Is there any way to tell the compiler that you no longer a paramter and to use that register for a local var? That's free bytes if you can do it. --[[User:Miked0801|Miked0801]] 23:39, 28 May 2009 (UTC)<br /> <br /> : With javac/jikes? No. With an assembler for java bytecode? Sure! ;) --[[User:Rednaxela|Rednaxela]] 23:49, 28 May 2009 (UTC)<br /> :: Bah, I program in dozens of asm languages already. One more wouldn't be hard. Of course the source file would no longer compile... --[[User:Miked0801|Miked0801]] 00:59, 29 May 2009 (UTC)<br /> [[Category:Bot Authors|Miked0801]]<br /> ::: I hate to put another weapon in your arsenal, but since this inspired me to audit my codesize in a new way I think it's only fair. [http://andrei.gmxhome.de/bytecode/index.html Check this out]. In a nano there's a small enough amount of code that you really can audit where every single byte is going. -- [[User:Kuuran|Kuuran]] 03:32, 7 October 2009 (UTC)<br /> <br /> - Hi Mike, congrats on getting LittleBlackBook to the top. I was surprised my Neophytes lasted as long as they did. LBB is a very sneaky concept and impressively scrunched into nanosize. I especially like the way you index into the beginning of the GF string to add custom movement.<br /> I thought of using a string buffer for bytecode way back. I had a few tries playing with the classloader and got the concept to work in isolation, but the securitymanager would not permit it to run in robocode. Didn't try very hard though, so not totally sure. <br /> --[[User:JohnCleland|JohnCleland]] 21:44, 22 October 2009 (UTC)<br /> : Thanks for the kind words :) --[[User:Miked0801|Miked0801]] 19:04, 18 January 2010 (UTC)<br /> <br /> ----<br /> <br /> Hi all,<br /> <br /> I come back here every now and then and am always impressed to see things humming quietly along. When I first started my nano adventure, it was while staying up late watching and helping to feed my infant daughter. I was a wide eyed game programmer with some extra time. Now, a father of 3 with my eldest approaching high school, this site and hobby helps me to reflect on just how far things have come here. Getting LBB tuned required more computer processing power than I had at the time, so I occasionally used a &quot;few&quot; computers at my place of employment late at night to run all the tables. Now, my home system could probably chew through the calcs by itself it the same amount of time. I always promise myself that I will spend a week here or there getting LBB or Moebius whipped back into shape, but life has other ideas. So, I will continue to stop by every now and then, I will tune LBB here or there as I can, and I will continue to enjoy watching people discover this awesome little distraction that we have poured so much effort into. --[[User:Miked0801|Miked0801]] 10:59, 23 August 2014 (UTC)<br /> [[Category:Bot Authors|Miked0801]]</div>

Miked0801 http://robowiki.net/w/index.php?title=Thread:Talk:LittleBlackBook/Updated/reply_(3)&diff=33611 2014-08-23T17:02:32Z

<p>Miked0801: Reply to Updated</p> <hr /> <div>Wow - thank you for that! It's awesome that you were able to figure out what the heck those tables were about. I came here expecting to see LBB towards the middle and was pleasantly surprised. :)</div>

Miked0801 http://robowiki.net/w/index.php?title=Thread:Talk:Main_Page/FightCodeGame_%3F/reply_(26)&diff=29844 2013-03-19T23:30:34Z

<p>Miked0801: Reply to FightCodeGame ?</p> <hr /> <div>BTW, I still feel very that LBB is a pretty cheezy bot. Abusing tables like that probably shouldn't be fair. It takes hours and hours though to get each bot optimized so maybe that makes it a little better overall. besting Moebius is a better accomplishment. At least he doesn't cheat...</div>

Miked0801 http://robowiki.net/w/index.php?title=Thread:Talk:Main_Page/FightCodeGame_%3F/reply_(25)&diff=29843 2013-03-19T23:27:37Z

<p>Miked0801: Reply to FightCodeGame ?</p> <hr /> <div>His code cannot be completely decompiled as he obfiscated it, but if you look around a bit, there are ways of figuring out what he did. Honestly, you can reverse engineer his good pretty easily by the fact that he cannot hit stop and go targets. His radar is lock onto nearest person and charge - which against weaker melee guns and movement works great. The bots that hide in the corner and make small movements counter him well though. Dustbunny does well because it runs from him (and everyone else) :)</div>

Miked0801 http://robowiki.net/w/index.php?title=Thread:Talk:Main_Page/FightCodeGame_%3F/reply_(24)&diff=29842 2013-03-19T23:24:46Z

<p>Miked0801: Reply to FightCodeGame ?</p> <hr /> <div>I'll look at this a bit tonight. There is a savings that can be had by compiling with a different Java compiler. I remember that :)</div>

Miked0801 http://robowiki.net/w/index.php?title=Thread:Talk:Main_Page/FightCodeGame_%3F/reply_(17)&diff=29816 2013-03-19T03:06:14Z

<p>Miked0801: Reply to FightCodeGame ?</p> <hr /> <div>Thanks! I have uncovered may of Doctor Bob's secrets. You can nearly 100% him if you watch energy drops and reverse direction at around 120 distance. Then just aim a little behind him.</div>

Miked0801 http://robowiki.net/w/index.php?title=Thread:Talk:Main_Page/FightCodeGame_%3F/reply_(16)&diff=29815 2013-03-19T03:05:04Z

<p>Miked0801: Reply to FightCodeGame ?</p> <hr /> <div>And work. Thanks for the good words! I am still attempting to get caught up with a new job and such. I do intend to keep track of things a bit better though going forward and maybe even update things as time allows.</div>

Miked0801 http://robowiki.net/w/index.php?title=Thread:Talk:Main_Page/FightCodeGame_%3F/reply_(12)&diff=28328 2013-01-23T07:12:04Z

<p>Miked0801: Reply to FightCodeGame ?</p> <hr /> <div>Boo :)</div>

Miked0801 http://robowiki.net/w/index.php?title=Talk:Talon/source&diff=19912 2011-07-02T17:20:38Z

<p>Miked0801: </p> <hr /> <div>It's 242 bytes, removing the colors nets it another 7 to 235 bytes (javac). I need to find a way to give this little guy some center avoidance, but I am at a loss. I am not to good at writing nanos. If anyone can squeeze anything in there, might be OK for the melee nano rumble. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 11:57, 30 January 2011 (UTC)<br /> <br /> Now down to 230 with colors or 223 without them. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 16:02, 30 January 2011 (UTC)<br /> <br /> Down to 220/213 (javac). &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 17:11, 30 January 2011 (UTC)<br /> <br /> <br /> Going back over this code, I found some errors I am going to fix. Mostly with the direction choosing. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 16:05, 2 July 2011 (UTC)<br /> <br /> EJC 229 bytes, needs work to avoid the walls and it should be pretty good, maybe if I have room add in something to get that missed scan back. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 16:32, 2 July 2011 (UTC)<br /> <br /> I'll check it out as well to see if there's anything else to be squeezed. Never thought about using try catch blocks... --[[User:Miked0801|Miked0801]] 17:20, 2 July 2011 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=Talk:Darkcanuck/RRServer/KnownIssues&diff=19582 2011-06-12T17:18:46Z

<p>Miked0801: /* Dropping of ELO and Glicko rating */</p> <hr /> <div>== Survival count should total 35 ==<br /> <br /> I want to confirm what has already been mentioned: survival count should not necessarily total 35. It appears that when bots die on the same tick, they both get credited with a first place finish. --[[User:Simonton|Simonton]] 22:49, 27 September 2008 (UTC)<br /> *There was only one unmatching battle (17+14) in the over 5000 results I sent to this server. But indeed, 34 and 36 should be accepted too in my opinion. I think that battles against rambots (used to) have the most chance on getting these non-35 results. --[[User:GrubbmGait|GrubbmGait]] 23:16, 27 September 2008 (UTC)<br /> <br /> The current check is that the survival totals ''at least'' 35 should that should take into account ties. But the results that are getting stuck on my clients are for &lt;35 1st place survivals. One client has 24-8 (32 total) for Cephalosporin vs UrChicken2. Two of my clients (not physically here, checked on them yesterday) had about a dozen battles involving RougeDC Classic, also with less than 34. What to do? --[[User:Darkcanuck|Darkcanuck]] 23:55, 27 September 2008 (UTC)<br /> <br /> Well, could you try running the normal Robocode (non rumble) with pairings like you're seeing this with in rumble? If you can't reproduce it that way, than it sounds like it might be a bug in the rumble client, and if you can reproduce it it should become evident what's happening by watching the battles when this happens (perhaps use the replay feature? Not sure how well that works though). I can't seem to see anything at all like that happening here. --[[User:Rednaxela|Rednaxela]] 00:02, 28 September 2008 (UTC)<br /> <br /> :I only see those clients once every few weeks, so it will be awhile. They're running 1.5.4 with the latest version of Java on Windows 2000. It's only ~12 battles out of 1500+, so a very low occurrence. If I turn off the survival check, you'll see them come through... --[[User:Darkcanuck|Darkcanuck]] 00:19, 28 September 2008 (UTC)<br /> <br /> I would not accept results lower than 34 or higher than 40. This check is mainly to intercept results from wrongly setupped clients, as that can be devastating for the rankings. A rare glitch of Robocode or the client can easily be repaired (when noticed). --[[User:GrubbmGait|GrubbmGait]] 01:16, 28 September 2008 (UTC)<br /> <br /> == HTTP response code: 503 ==<br /> <br /> Hmm, I started getting a bunch of &quot;HTTP response code: 503&quot; errors when uploading results. Anyone know why? --[[User:Rednaxela|Rednaxela]] 18:09, 2 December 2008 (UTC)<br /> <br /> I've got the same problem, and sometimes downloading rating page --[[User:Lestofante|lestofante]] 19:04, 2 December 2008 (UTC)<br /> <br /> Yeah, also when the client tries to download the ratings here too. One thing I've noticed is that when it tries to download the rating pages is that sometimes it's 503 and sometimes it's 500, but it's always 503 for uploading. Anyways right now I'm running my RR client with upload/download disabled in order to build up battles to upload in bulk when uploading is working again. --[[User:Rednaxela|Rednaxela]] 21:06, 2 December 2008 (UTC)<br /> <br /> : Hmm, the server does not look happy -- some sort of high load condition, I'll what I can do. --[[User:Darkcanuck|Darkcanuck]] 04:04, 3 December 2008 (UTC)<br /> <br /> '''ATTENTION!''' Someone has a bad participants list -- almost half the bots in the rumble have been removed! This is a very slow operation, especially when other clients are trying to add them back in. I've disabled bot removal for now while I investigate the source... --[[User:Darkcanuck|Darkcanuck]] 04:43, 3 December 2008 (UTC)<br /> <br /> Mea culpa, yesterday I've run for at least &lt;strike&gt;20 minutes&lt;/strike&gt; 5 hour the rumble with an empty participants list before I see, understood and fixed my client's problem.. next time I will play with his option with Upload flag set to false! Now everything is running and I've over 2000 battle's to upload --[[User:Lestofante|lestofante]] 11:29, 3 December 2008 (UTC)<br /> <br /> : Ok, I've re-enabled your username + IP so you can upload again. 2000 battles, eh? Just make sure you're using one of the approved clients (1.5.4 or 1.6.0). Participant removals are still disabled just in case since the participant list can't change anyway.<br /> <br /> == Retired Bots ==<br /> <br /> In details pages like [http://darkcanuck.net/rumble/RatingsDetails?game=roborumble&amp;name=abc.Shadow%203.83c this], bots that are 'retired' like Cunobelin 0.2.1 are showing up (see ELO score 0 bots on details pages). Did this accidentally happen when you disabled removal/retiring of bots temporarily? (Also, would it be possible to make details pages for retired bots viewable with the [http://darkcanuck.net/rumble/RatingsDetails?game=roborumble&amp;name=jk.mini.Cunobelin%200.2.1 right URL]? :)) --[[User:Rednaxela|Rednaxela]] 16:52, 3 December 2008 (UTC)<br /> <br /> : Thanks for pointing that out -- I was trying to figure out why the rumble pairings weren't going back to normal. I'm not quite sure how those bots got reactivated, need to think on that a bit. (Could be the economic crisis has affected their retirement plans?) It doesn't look like any rumble clients are trying to remove them though -- probably due to the failure to download the participants list. I'll see what I can do to remove them. --[[User:Darkcanuck|Darkcanuck]] 02:31, 4 December 2008 (UTC)<br /> <br /> :Hm, I think its a bug in the reactivation process... if both participants in a pairing have been retired, reactivating either also reactivates the pairing, ugh. --[[User:Darkcanuck|Darkcanuck]] 02:48, 4 December 2008 (UTC)<br /> <br /> == Performance ==<br /> <br /> I'm uploading many battle I've run off-line, but the server is too slow. in 29 minutes I've uploaded only 262 battles, about 9 for minute!! Maybe are you updating all scoring system at every battle upload?--[[User:Lestofante|lestofante]] 13:30, 4 December 2008 (UTC)<br /> <br /> The scoring is calculated for each upload yes. If it wasn't the results page and such wouldn't be nice and live and such. Apparently [[User:Darkcanuck|Darkcanuck]] is planning some things that may improve performance such as getting rid of table locking in favor of transactions, but really, I do think the roughly 2 seconds per battle that you describe is very acceptable. After all, running a battle takes considerably longer than 2 seconds in almost all cases, so it's not like it's that huge an impact on the total number of battles uploaded. --[[User:Rednaxela|Rednaxela]] 13:47, 4 December 2008 (UTC)<br /> <br /> I think the scoring system have to be updated only when requested the scoring page or similia.. so we have to update only WHAT we need WHEN we need, saving many time and resources. <br /> Pay attention: the upload relay is about 60sec/9battle=6sec/battle, not 2... acceptable? lets see. <br /> #1 execute of roborumble.sh = 1 iteration<br /> #1 iteration = 10 battle<br /> #6sec/battle * 10 battle = 60second of upload time for iteration<br /> #150-200 seconds = 1 iteration on amd64 x2 4000+, ubuntu OS, openJDK as virtual machine, UPLOAD=NOT,DOWNLOAD=NOT + roborumble loading time (calculate with unix script &quot;time&quot;)<br /> Result: upload time is about 1/4 of my rumble running time in the best case...add the ratings downloads time+new bot check and as result use on-line rumble takes about DOUBLE time than off-line(300-360 sec, calculated with unix script &quot;time&quot;), IMHO it's not acceptable<br /> If you have unix(machintosh is unix) you can calculate your execution time (I don't know how do it for windows), it's easy: time -p ./roborumble.sh, results is the first line, expressed in seconds--[[User:Lestofante|lestofante]] 14:30, 4 December 2008 (UTC)<br /> <br /> Whoops, I read it as &quot;262 in 9 minutes&quot;. Still 6 seconds is acceptable I think. Certainly far from ideal, but acceptable enough. I believe the real fix is making the RR client upload in the background while battles are running. And... er.... updating the scoring system when loading the scoring page would... often take a few minutes or longer if the scoring page hasn't been viewed in a while I believe. I'm quite sure updating it incrementally is a necessity. --[[User:Rednaxela|Rednaxela]] 15:02, 4 December 2008 (UTC)<br /> <br /> The background upload is a great idea! now I will try to implement it, a little java program that grab the 1vs1result.txt(roborumble must have UPLOAD=NOT) copy it in RAM, clean the original, and in background upload the copy in RAM. we will see. --[[User:Lestofante|lestofante]] 15:59, 4 December 2008 (UTC)<br /> <br /> :Haha, well, I kind of think it would be easier to just implement it as a patch to the normal roborumble client that just moves the upload process into another thread that runs in the background. Plus as a patch to the existing RR client, I think it's likely it would be adopted for the next official release of Robocode ;) --[[User:Rednaxela|Rednaxela]] 18:11, 4 December 2008 (UTC)<br /> <br /> I agree that 2 seconds would be nicer... Think of it as break to let your processor cool off a bit? If you look elsewhere in these pages, scoring used to be batched but performance degraded dramatically as the database grew. Its faster (and more reliable) when scoring is done on each upload -- only the two bots uploaded get updated, but the Elo algorithm requires a lot of data to do so. Right now there's a scaling problem where many simultaneous uploads cause each one to slow down and I'm planning to addres this soon. But if lots of clients are recovering from the past two days problems (I took the server offline several hours last night) then we have a higher volume of uploads right now too. --[[User:Darkcanuck|Darkcanuck]] 16:08, 4 December 2008 (UTC)<br /> <br /> : I think most clients should be done recovering by now. I noticed the server refusing uploads for a bit last night and my client was easily back to normal long before I woke up. --[[User:Rednaxela|Rednaxela]] 18:11, 4 December 2008 (UTC)<br /> <br /> I've implemented a the Radnaxela idea (see [[Talk:RoboRumble/Development#Background_Uploader]]), and in about 5 hour I've duplicated my month upload... wow! And no collateral effect ^^&quot; --[[User:Lestofante|lestofante]] 01:11, 5 December 2008 (UTC)<br /> <br /> : Very cool! But can you do like Rednaxela suggested and make this another thread in the rumble client? You guys are determined to push my poor server to its limits... :) --[[User:Darkcanuck|Darkcanuck]] 01:29, 5 December 2008 (UTC)<br /> <br /> :: Well don't worry, I won't be using background upload on my laptop here... at least not until I get an external cooling fan to boost airflow... because if it's maintained at high CPU use with no chances to cool off... it gets up past 93C sometimes which I call iffy when the processor is only designed to operate up to 95C (and the builtin auto-shutoff limit is at 105C) --[[User:Rednaxela|Rednaxela]] 03:11, 5 December 2008 (UTC)<br /> <br /> ::: Another performance tip: I've had several hard drive failures/corruptions on machines I've used as clients which run continuously. My guess is that it's provoked by the constant disk writes caused by bots writing to their data directory at the end of each round. So I now have my robotcache dir mounted on a ramdisk -- its much quieter and battles run faster too. But I do put in a nice delay in between iterations for cooling to keep the cpu under 80. --[[User:Darkcanuck|Darkcanuck]] 04:04, 5 December 2008 (UTC)<br /> <br /> : Ok, look at [[Talk:RoboRumble/Development#Background_Uploader]] for the last really working version and use instruction. Now I'm running (and uploading) 1 iteration of 10 battle in 150 seconds (p.s. total CPU use under 60% with amule + azureus + firefox + eclipse + compiz). Now I'm going to implement a patch for the 1.6.0's code, is only one class to modify (UploaderResult) but my SVN client don't want run and manually import robocode's code in Eclipse give me some path problem (help me please, see [[Talk:Robocode/Developers_Guide_for_building_Robocode]]) --[[User:Lestofante|lestofante]] 23:14, 5 December 2008 (UTC)<br /> <br /> With the last server revision is not either necessary run the script cause upload's speed as been considerable incremented --[[User:Lestofante|lestofante]] 12:53, 6 December 2008 (UTC)<br /> <br /> I hope this is the right place for this considering the time since the last post... Are there any ideas in the works to improve scalability of the server to accept more concurrent users submitting battle results? It works just fine when there are only the normal 2-5 clients working, and even works well when I add another 44 clients. However, the one time I unleashed 80 clients the upload process was very very slow for each individual client and slowed the response time of the web server greatly. Perhaps accepting uploads immediately and adding them to a queue to be processed? This would cause the rankings to no longer be real-time, however if you could accept 10+ battles per second then that point may be moot. I also understand due to participation and available time that this is likely not a high priority. --[[User:Bwbaugh|bwbaugh]] 12:44, 12 June 2011 (UTC)<br /> <br /> While I believe that queueing the request and use daemon to process the result, there are also many problem that may arise. What if the daemon can't process the input fast enough? (It's likely to be the case here if you fire up all your clients). The queue may group to hundreds of thousands of request, and that wouldn't help the situation. Also, queueing in database add more work to the disk, while if you cache in memory, it may run out quickly. I don't know if the server is currently running on dedicate box (or VPS, for that matter) or could hosting, but I think the server is already scratch to its limit. RoboRumble server is very database-write intensive, thus making it disk-intensive. (Replacing the disk with SSDs in RAID-0 might help, but that might make CPU the bottleneck, and the cost of SSDs)<br /> <br /> I am not sure, but Darkcanuck, if you replace Apache with nginx or lighttpd (I prefer nginx) with php-fpm, would it work slightly faster due to lower amount of threads/processes? --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 14:45, 12 June 2011 (UTC)<br /> <br /> == Proofing against add/remove wars ==<br /> <br /> I was just thinking, in order to proof against add/remove wars in the future, maybe it would be good to make the server check the participants list itself to verify the addition/removal? It make make addition/removal of a bot to/from rumble slightly slower, but those two operations are rare under normal conditions. --[[User:Rednaxela|Rednaxela]] 22:54, 4 December 2008 (UTC)<br /> <br /> : I was thinking along similar lines too, but I would make it a periodic check. Say every hour, the server gets the new participant list and does the add/removes directly and preventing clients from doing so. Also, the list could be obtained from the server so we can easily point to new locations or handle cases when the wiki is unavailable. --[[User:Darkcanuck|Darkcanuck]] 01:29, 5 December 2008 (UTC)<br /> <br /> :: Maybe have it also double-check the participants list again whenever a client sends results for a new bot? I'm saying that just because I think it's nice to be able to see your bots show up in the results as soon as the first battles are uploaded. --[[User:Rednaxela|Rednaxela]] 03:11, 5 December 2008 (UTC)<br /> <br /> ::: True. This feature is not high on my list yet -- I want to fix the locking first, then look at the details comparison stuff (including retired bot details). --[[User:Darkcanuck|Darkcanuck]] 04:04, 5 December 2008 (UTC)<br /> <br /> == Sort order on &quot;Glicko-2 (RD)&quot; ==<br /> <br /> Really minor thing, but I noticed the &quot;Glicko-2 (RD)&quot; column doesn't sort correctly - eg, for descending, all 3 digit numbers list before all 4 digit numbers. Super minor, but figure it's worth letting ya know. Rankings page looks ''great'', btw, nice work. --[[User:Voidious|Voidious]] 00:02, 5 January 2009 (UTC)<br /> <br /> Just to note, a fair number of columns are like that not just the Glicko-2 one. Also in the bot details pages. --[[User:Rednaxela|Rednaxela]] 00:42, 5 January 2009 (UTC)<br /> <br /> : Thanks for the heads-up. Looks like tablesorter gets confused by the parentheses around the RD value and possibly the class attributes for high/low scores... --[[User:Darkcanuck|Darkcanuck]] 05:49, 5 January 2009 (UTC)<br /> <br /> Just a reminder about this ;-) It seems &lt;b&gt;all&lt;/b&gt; the columns are being sorted as text, not numbers. For instance, when sorting highest to lowest, 900 comes before 2000. --[[User:Skilgannon|Skilgannon]] 16:00, 30 April 2009 (UTC)<br /> <br /> : Ah, good catch. I fixed this problem on every table *but* the main rankings during the last update. Should work for the main tables now too. --[[User:Darkcanuck|Darkcanuck]] 03:43, 1 May 2009 (UTC)<br /> <br /> : Thanks =) It still seems to sort by text on the Glicko-2 column though... I'm not sure how easy the fix would be because of the RD value. Can you set custom comparators? Or is this nothing like Java? :-) --[[User:Skilgannon|Skilgannon]] 10:31, 1 May 2009 (UTC)<br /> <br /> == Dropping of ELO and Glicko rating ==<br /> <br /> I don't know where was the discussion located, so I post it here. Maybe the drop of ELO and Glicko rating is due to imprecision of calculation? Because your current system and DB only store them in INT(5) field, not floating-point field? --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 15:01, 25 May 2010 (UTC)<br /> <br /> Not yet. I'm still trying to 2k it :) --[[User:Miked0801|Miked0801]] 17:18, 12 June 2011 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=Talk:Darkcanuck/RRServer/KnownIssues&diff=19581 2011-06-12T17:18:32Z

<p>Miked0801: /* Dropping of ELO and Glicko rating */</p> <hr /> <div>== Survival count should total 35 ==<br /> <br /> I want to confirm what has already been mentioned: survival count should not necessarily total 35. It appears that when bots die on the same tick, they both get credited with a first place finish. --[[User:Simonton|Simonton]] 22:49, 27 September 2008 (UTC)<br /> *There was only one unmatching battle (17+14) in the over 5000 results I sent to this server. But indeed, 34 and 36 should be accepted too in my opinion. I think that battles against rambots (used to) have the most chance on getting these non-35 results. --[[User:GrubbmGait|GrubbmGait]] 23:16, 27 September 2008 (UTC)<br /> <br /> The current check is that the survival totals ''at least'' 35 should that should take into account ties. But the results that are getting stuck on my clients are for &lt;35 1st place survivals. One client has 24-8 (32 total) for Cephalosporin vs UrChicken2. Two of my clients (not physically here, checked on them yesterday) had about a dozen battles involving RougeDC Classic, also with less than 34. What to do? --[[User:Darkcanuck|Darkcanuck]] 23:55, 27 September 2008 (UTC)<br /> <br /> Well, could you try running the normal Robocode (non rumble) with pairings like you're seeing this with in rumble? If you can't reproduce it that way, than it sounds like it might be a bug in the rumble client, and if you can reproduce it it should become evident what's happening by watching the battles when this happens (perhaps use the replay feature? Not sure how well that works though). I can't seem to see anything at all like that happening here. --[[User:Rednaxela|Rednaxela]] 00:02, 28 September 2008 (UTC)<br /> <br /> :I only see those clients once every few weeks, so it will be awhile. They're running 1.5.4 with the latest version of Java on Windows 2000. It's only ~12 battles out of 1500+, so a very low occurrence. If I turn off the survival check, you'll see them come through... --[[User:Darkcanuck|Darkcanuck]] 00:19, 28 September 2008 (UTC)<br /> <br /> I would not accept results lower than 34 or higher than 40. This check is mainly to intercept results from wrongly setupped clients, as that can be devastating for the rankings. A rare glitch of Robocode or the client can easily be repaired (when noticed). --[[User:GrubbmGait|GrubbmGait]] 01:16, 28 September 2008 (UTC)<br /> <br /> == HTTP response code: 503 ==<br /> <br /> Hmm, I started getting a bunch of &quot;HTTP response code: 503&quot; errors when uploading results. Anyone know why? --[[User:Rednaxela|Rednaxela]] 18:09, 2 December 2008 (UTC)<br /> <br /> I've got the same problem, and sometimes downloading rating page --[[User:Lestofante|lestofante]] 19:04, 2 December 2008 (UTC)<br /> <br /> Yeah, also when the client tries to download the ratings here too. One thing I've noticed is that when it tries to download the rating pages is that sometimes it's 503 and sometimes it's 500, but it's always 503 for uploading. Anyways right now I'm running my RR client with upload/download disabled in order to build up battles to upload in bulk when uploading is working again. --[[User:Rednaxela|Rednaxela]] 21:06, 2 December 2008 (UTC)<br /> <br /> : Hmm, the server does not look happy -- some sort of high load condition, I'll what I can do. --[[User:Darkcanuck|Darkcanuck]] 04:04, 3 December 2008 (UTC)<br /> <br /> '''ATTENTION!''' Someone has a bad participants list -- almost half the bots in the rumble have been removed! This is a very slow operation, especially when other clients are trying to add them back in. I've disabled bot removal for now while I investigate the source... --[[User:Darkcanuck|Darkcanuck]] 04:43, 3 December 2008 (UTC)<br /> <br /> Mea culpa, yesterday I've run for at least &lt;strike&gt;20 minutes&lt;/strike&gt; 5 hour the rumble with an empty participants list before I see, understood and fixed my client's problem.. next time I will play with his option with Upload flag set to false! Now everything is running and I've over 2000 battle's to upload --[[User:Lestofante|lestofante]] 11:29, 3 December 2008 (UTC)<br /> <br /> : Ok, I've re-enabled your username + IP so you can upload again. 2000 battles, eh? Just make sure you're using one of the approved clients (1.5.4 or 1.6.0). Participant removals are still disabled just in case since the participant list can't change anyway.<br /> <br /> == Retired Bots ==<br /> <br /> In details pages like [http://darkcanuck.net/rumble/RatingsDetails?game=roborumble&amp;name=abc.Shadow%203.83c this], bots that are 'retired' like Cunobelin 0.2.1 are showing up (see ELO score 0 bots on details pages). Did this accidentally happen when you disabled removal/retiring of bots temporarily? (Also, would it be possible to make details pages for retired bots viewable with the [http://darkcanuck.net/rumble/RatingsDetails?game=roborumble&amp;name=jk.mini.Cunobelin%200.2.1 right URL]? :)) --[[User:Rednaxela|Rednaxela]] 16:52, 3 December 2008 (UTC)<br /> <br /> : Thanks for pointing that out -- I was trying to figure out why the rumble pairings weren't going back to normal. I'm not quite sure how those bots got reactivated, need to think on that a bit. (Could be the economic crisis has affected their retirement plans?) It doesn't look like any rumble clients are trying to remove them though -- probably due to the failure to download the participants list. I'll see what I can do to remove them. --[[User:Darkcanuck|Darkcanuck]] 02:31, 4 December 2008 (UTC)<br /> <br /> :Hm, I think its a bug in the reactivation process... if both participants in a pairing have been retired, reactivating either also reactivates the pairing, ugh. --[[User:Darkcanuck|Darkcanuck]] 02:48, 4 December 2008 (UTC)<br /> <br /> == Performance ==<br /> <br /> I'm uploading many battle I've run off-line, but the server is too slow. in 29 minutes I've uploaded only 262 battles, about 9 for minute!! Maybe are you updating all scoring system at every battle upload?--[[User:Lestofante|lestofante]] 13:30, 4 December 2008 (UTC)<br /> <br /> The scoring is calculated for each upload yes. If it wasn't the results page and such wouldn't be nice and live and such. Apparently [[User:Darkcanuck|Darkcanuck]] is planning some things that may improve performance such as getting rid of table locking in favor of transactions, but really, I do think the roughly 2 seconds per battle that you describe is very acceptable. After all, running a battle takes considerably longer than 2 seconds in almost all cases, so it's not like it's that huge an impact on the total number of battles uploaded. --[[User:Rednaxela|Rednaxela]] 13:47, 4 December 2008 (UTC)<br /> <br /> I think the scoring system have to be updated only when requested the scoring page or similia.. so we have to update only WHAT we need WHEN we need, saving many time and resources. <br /> Pay attention: the upload relay is about 60sec/9battle=6sec/battle, not 2... acceptable? lets see. <br /> #1 execute of roborumble.sh = 1 iteration<br /> #1 iteration = 10 battle<br /> #6sec/battle * 10 battle = 60second of upload time for iteration<br /> #150-200 seconds = 1 iteration on amd64 x2 4000+, ubuntu OS, openJDK as virtual machine, UPLOAD=NOT,DOWNLOAD=NOT + roborumble loading time (calculate with unix script &quot;time&quot;)<br /> Result: upload time is about 1/4 of my rumble running time in the best case...add the ratings downloads time+new bot check and as result use on-line rumble takes about DOUBLE time than off-line(300-360 sec, calculated with unix script &quot;time&quot;), IMHO it's not acceptable<br /> If you have unix(machintosh is unix) you can calculate your execution time (I don't know how do it for windows), it's easy: time -p ./roborumble.sh, results is the first line, expressed in seconds--[[User:Lestofante|lestofante]] 14:30, 4 December 2008 (UTC)<br /> <br /> Whoops, I read it as &quot;262 in 9 minutes&quot;. Still 6 seconds is acceptable I think. Certainly far from ideal, but acceptable enough. I believe the real fix is making the RR client upload in the background while battles are running. And... er.... updating the scoring system when loading the scoring page would... often take a few minutes or longer if the scoring page hasn't been viewed in a while I believe. I'm quite sure updating it incrementally is a necessity. --[[User:Rednaxela|Rednaxela]] 15:02, 4 December 2008 (UTC)<br /> <br /> The background upload is a great idea! now I will try to implement it, a little java program that grab the 1vs1result.txt(roborumble must have UPLOAD=NOT) copy it in RAM, clean the original, and in background upload the copy in RAM. we will see. --[[User:Lestofante|lestofante]] 15:59, 4 December 2008 (UTC)<br /> <br /> :Haha, well, I kind of think it would be easier to just implement it as a patch to the normal roborumble client that just moves the upload process into another thread that runs in the background. Plus as a patch to the existing RR client, I think it's likely it would be adopted for the next official release of Robocode ;) --[[User:Rednaxela|Rednaxela]] 18:11, 4 December 2008 (UTC)<br /> <br /> I agree that 2 seconds would be nicer... Think of it as break to let your processor cool off a bit? If you look elsewhere in these pages, scoring used to be batched but performance degraded dramatically as the database grew. Its faster (and more reliable) when scoring is done on each upload -- only the two bots uploaded get updated, but the Elo algorithm requires a lot of data to do so. Right now there's a scaling problem where many simultaneous uploads cause each one to slow down and I'm planning to addres this soon. But if lots of clients are recovering from the past two days problems (I took the server offline several hours last night) then we have a higher volume of uploads right now too. --[[User:Darkcanuck|Darkcanuck]] 16:08, 4 December 2008 (UTC)<br /> <br /> : I think most clients should be done recovering by now. I noticed the server refusing uploads for a bit last night and my client was easily back to normal long before I woke up. --[[User:Rednaxela|Rednaxela]] 18:11, 4 December 2008 (UTC)<br /> <br /> I've implemented a the Radnaxela idea (see [[Talk:RoboRumble/Development#Background_Uploader]]), and in about 5 hour I've duplicated my month upload... wow! And no collateral effect ^^&quot; --[[User:Lestofante|lestofante]] 01:11, 5 December 2008 (UTC)<br /> <br /> : Very cool! But can you do like Rednaxela suggested and make this another thread in the rumble client? You guys are determined to push my poor server to its limits... :) --[[User:Darkcanuck|Darkcanuck]] 01:29, 5 December 2008 (UTC)<br /> <br /> :: Well don't worry, I won't be using background upload on my laptop here... at least not until I get an external cooling fan to boost airflow... because if it's maintained at high CPU use with no chances to cool off... it gets up past 93C sometimes which I call iffy when the processor is only designed to operate up to 95C (and the builtin auto-shutoff limit is at 105C) --[[User:Rednaxela|Rednaxela]] 03:11, 5 December 2008 (UTC)<br /> <br /> ::: Another performance tip: I've had several hard drive failures/corruptions on machines I've used as clients which run continuously. My guess is that it's provoked by the constant disk writes caused by bots writing to their data directory at the end of each round. So I now have my robotcache dir mounted on a ramdisk -- its much quieter and battles run faster too. But I do put in a nice delay in between iterations for cooling to keep the cpu under 80. --[[User:Darkcanuck|Darkcanuck]] 04:04, 5 December 2008 (UTC)<br /> <br /> : Ok, look at [[Talk:RoboRumble/Development#Background_Uploader]] for the last really working version and use instruction. Now I'm running (and uploading) 1 iteration of 10 battle in 150 seconds (p.s. total CPU use under 60% with amule + azureus + firefox + eclipse + compiz). Now I'm going to implement a patch for the 1.6.0's code, is only one class to modify (UploaderResult) but my SVN client don't want run and manually import robocode's code in Eclipse give me some path problem (help me please, see [[Talk:Robocode/Developers_Guide_for_building_Robocode]]) --[[User:Lestofante|lestofante]] 23:14, 5 December 2008 (UTC)<br /> <br /> With the last server revision is not either necessary run the script cause upload's speed as been considerable incremented --[[User:Lestofante|lestofante]] 12:53, 6 December 2008 (UTC)<br /> <br /> I hope this is the right place for this considering the time since the last post... Are there any ideas in the works to improve scalability of the server to accept more concurrent users submitting battle results? It works just fine when there are only the normal 2-5 clients working, and even works well when I add another 44 clients. However, the one time I unleashed 80 clients the upload process was very very slow for each individual client and slowed the response time of the web server greatly. Perhaps accepting uploads immediately and adding them to a queue to be processed? This would cause the rankings to no longer be real-time, however if you could accept 10+ battles per second then that point may be moot. I also understand due to participation and available time that this is likely not a high priority. --[[User:Bwbaugh|bwbaugh]] 12:44, 12 June 2011 (UTC)<br /> <br /> While I believe that queueing the request and use daemon to process the result, there are also many problem that may arise. What if the daemon can't process the input fast enough? (It's likely to be the case here if you fire up all your clients). The queue may group to hundreds of thousands of request, and that wouldn't help the situation. Also, queueing in database add more work to the disk, while if you cache in memory, it may run out quickly. I don't know if the server is currently running on dedicate box (or VPS, for that matter) or could hosting, but I think the server is already scratch to its limit. RoboRumble server is very database-write intensive, thus making it disk-intensive. (Replacing the disk with SSDs in RAID-0 might help, but that might make CPU the bottleneck, and the cost of SSDs)<br /> <br /> I am not sure, but Darkcanuck, if you replace Apache with nginx or lighttpd (I prefer nginx) with php-fpm, would it work slightly faster due to lower amount of threads/processes? --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 14:45, 12 June 2011 (UTC)<br /> <br /> == Proofing against add/remove wars ==<br /> <br /> I was just thinking, in order to proof against add/remove wars in the future, maybe it would be good to make the server check the participants list itself to verify the addition/removal? It make make addition/removal of a bot to/from rumble slightly slower, but those two operations are rare under normal conditions. --[[User:Rednaxela|Rednaxela]] 22:54, 4 December 2008 (UTC)<br /> <br /> : I was thinking along similar lines too, but I would make it a periodic check. Say every hour, the server gets the new participant list and does the add/removes directly and preventing clients from doing so. Also, the list could be obtained from the server so we can easily point to new locations or handle cases when the wiki is unavailable. --[[User:Darkcanuck|Darkcanuck]] 01:29, 5 December 2008 (UTC)<br /> <br /> :: Maybe have it also double-check the participants list again whenever a client sends results for a new bot? I'm saying that just because I think it's nice to be able to see your bots show up in the results as soon as the first battles are uploaded. --[[User:Rednaxela|Rednaxela]] 03:11, 5 December 2008 (UTC)<br /> <br /> ::: True. This feature is not high on my list yet -- I want to fix the locking first, then look at the details comparison stuff (including retired bot details). --[[User:Darkcanuck|Darkcanuck]] 04:04, 5 December 2008 (UTC)<br /> <br /> == Sort order on &quot;Glicko-2 (RD)&quot; ==<br /> <br /> Really minor thing, but I noticed the &quot;Glicko-2 (RD)&quot; column doesn't sort correctly - eg, for descending, all 3 digit numbers list before all 4 digit numbers. Super minor, but figure it's worth letting ya know. Rankings page looks ''great'', btw, nice work. --[[User:Voidious|Voidious]] 00:02, 5 January 2009 (UTC)<br /> <br /> Just to note, a fair number of columns are like that not just the Glicko-2 one. Also in the bot details pages. --[[User:Rednaxela|Rednaxela]] 00:42, 5 January 2009 (UTC)<br /> <br /> : Thanks for the heads-up. Looks like tablesorter gets confused by the parentheses around the RD value and possibly the class attributes for high/low scores... --[[User:Darkcanuck|Darkcanuck]] 05:49, 5 January 2009 (UTC)<br /> <br /> Just a reminder about this ;-) It seems &lt;b&gt;all&lt;/b&gt; the columns are being sorted as text, not numbers. For instance, when sorting highest to lowest, 900 comes before 2000. --[[User:Skilgannon|Skilgannon]] 16:00, 30 April 2009 (UTC)<br /> <br /> : Ah, good catch. I fixed this problem on every table *but* the main rankings during the last update. Should work for the main tables now too. --[[User:Darkcanuck|Darkcanuck]] 03:43, 1 May 2009 (UTC)<br /> <br /> : Thanks =) It still seems to sort by text on the Glicko-2 column though... I'm not sure how easy the fix would be because of the RD value. Can you set custom comparators? Or is this nothing like Java? :-) --[[User:Skilgannon|Skilgannon]] 10:31, 1 May 2009 (UTC)<br /> <br /> == Dropping of ELO and Glicko rating ==<br /> <br /> I don't know where was the discussion located, so I post it here. Maybe the drop of ELO and Glicko rating is due to imprecision of calculation? Because your current system and DB only store them in INT(5) field, not floating-point field? --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 15:01, 25 May 2010 (UTC)<br /> <br /> Not yet. I'm still trying to 2k it :) --[[User:Miked0801|Miked0801]] 17:18, 12 June 2011 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=User_talk:Bwbaugh&diff=19580 2011-06-12T17:17:28Z

<p>Miked0801: /* Genetic Algorithms */</p> <hr /> <div>== RoboRumble ==<br /> <br /> '''Question: Number of Client Instances'''<br /> <br /> If I have computers that are multicore (some dual some quad), is there a way to safely run multiple instances of the RoboRumble client without causing skipped turns? Would I need to set the affinity of each instance to separate CPUs? I'm a bit new to this, and my parallel computing class doesn't start until the Fall. =) --[[User:Bwbaugh|bwbaugh]] 10:05, 8 June 2011 (UTC)<br /> <br /> Welcome to the wiki, glad you are contributing to the rumble =) If you're worried about causing skipped turns first open up robocode and reset the CPU constant, then close robocode and open up the config/robocode.properties file with notepad. Manually increase the CPU constant there to something you feel would account for anything like cache thrashing, possible external logins etc (I'd say just double it...) and save the file. Make sure you run each instance of roborumble from a different install, otherwise there will be issues with all of them saving to or uploading from the same file concurrently. Hope this helps! --[[User:Skilgannon|Skilgannon]] 10:28, 8 June 2011 (UTC)<br /> <br /> Personally, in addition to boosting the CPU constant, I prefer to run one fewer robocode instance than the number of CPUs on the system. This is because robocode seems to use some processor power outside it's handling it a separate thread than the robots run in (perhaps the Java GC? Perhaps part of the robocode engine itself? I'm not sure). About setting affinity, I doubt it would make much difference. Robocode is already alternating between running each robot, which I'd expect to limit how long-lived things are in the cpu cache, which I'd expect to mean that affinity probably wouldn't help much. That's just a guess though, it's not like I've tested. --[[User:Rednaxela|Rednaxela]] 13:57, 8 June 2011 (UTC)<br /> <br /> Agree with everything these guys said. About the affinity, I think this may depend on OS. I know on Mac, and I think on Linux, it will just work running one instance per core. I recall some people on Windows (XP days?) having to set affinity. FYI, [[RoboResearch]] is a great tool to leverage multiple cores for development. And yes, welcome and great to see you already contributing to the rumble. :-) Good luck! --[[User:Voidious|Voidious]] 14:33, 8 June 2011 (UTC)<br /> <br /> I personally used to run two RoboRumble clients (1v1 and melee) on Dual Core machine (Core 2 Duo P8400 2.26GHz) with about 1.1x increased cpu constants without trouble (I've checked the result on the server). I have also run two RoboRumble clients (1v1 and melee) on my Core 2 Quad 2.4GHz server without increased cpu constants without any trouble too. (but my server do esnot do anything other than consuming power when not explicitly used, it host my class' online judge system) --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 14:40, 8 June 2011 (UTC)<br /> <br /> Thank you all for the replies and information! I went ahead and configured 40 of my workstations to run 2 instances of RoboRumble each. Unfortunately, I noticed that after processing the battles, the upload process was much slower than it was during the past two days. In addition, the web interface for the rumble server was very slow to respond. So, it appears that the rumble server can't accept that many connections / uploads at once. I therefore reduced the number of stations running from 40 to 22, still running 2 instances each, and may reduce it further if it still seems to be overloading the rumble server. I wonder if there is a way to scale up the server to accept more simultaneous uploads... --[[User:Bwbaugh|bwbaugh]] 15:20, 8 June 2011 (UTC)<br /> <br /> Holy cow. In one or two nights, you've managed to contribute more power than just about everyone one else this year. Wow and thanks! --[[User:Miked0801|Miked0801]] 15:31, 8 June 2011 (UTC)<br /> <br /> : You're welcome! Though, I am missing a small number of bots due to the [[Robocode Repository]] currently being inaccessible. Maybe I'll have to get a copy of the bots I'm missing from one of you sometime. =) --[[User:Bwbaugh|bwbaugh]] 15:44, 8 June 2011 (UTC)<br /> <br /> :: I zipped up all the bots in my RoboRumble dir recently, it probably has whatever you're missing: [http://www.dijitari.com/void/robocode/roborumble_bots.zip roborumble_bots.zip] (69 MB). It also has lots of versions of lots of bots, so I'd just cherry pick what you need. --[[User:Voidious|Voidious]] 17:58, 8 June 2011 (UTC)<br /> <br /> :: Thanks! Got the 18 bots I was missing. I'll have to re-package the distro that I use tomorrow. About to turn off the farm for the night. --[[User:Bwbaugh|bwbaugh]] 04:48, 9 June 2011 (UTC)<br /> <br /> <br /> == Genetic Algorithms ==<br /> <br /> Does anyone have experience with genetic algorithms and robocode, whether it be [[RobocodeJGAP]] or otherwise? As you can see from the [[RoboRumble]] contributors list, I have quite a bit of processing power available, and was curious if I could use that to my advantage. I tried downloading the JGAP but could not get it to run (gave an error about not being able to compile the generated file), and no matter what security policy permissions I tried giving to it, it did not want to run. There was also mention on their website about the future possibility of using a grid. Obviously any sort of distributed computing would be a big plus, but not a requirement. Thanks for any pointers in the right direction! --[[User:Bwbaugh|bwbaugh]] 11:04, 12 June 2011 (UTC)<br /> <br /> RobocodeJGAP is largely outdated. I believe you could perform the same thing via Robocode API. There is an article about genetic algorithm here: [http://hvilela.com/robocode-and-genetic-algorithms/], but it didn't speak of the integration with Robocode API. ---[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 14:28, 12 June 2011 (UTC)<br /> <br /> I have worked with genetic algorithms a bit recently, but only with [[User:Voidious/WaveSim|WaveSim]] to evaluate fitness, not directly with Robocode. I wrote a small framework to do the GA stuff instead of using JGAP or another existing framework. I could share that if you want, but need to get permission from work first (signed over my soul, etc, but should be np). You might be thinking [[wikipedia:Genetic programming|Genetic Programming]], though - evolving code for a robot, as opposed to evolving a bit string that's interpreted by other code. And yes, my mouth waters a bit with the thought of all that CPU power for my GA runs. =) --[[User:Voidious|Voidious]] 16:19, 12 June 2011 (UTC)<br /> <br /> With the way LBB works, it could really use this kind of power to work through all its possible string combinations :) --[[User:Miked0801|Miked0801]] 17:17, 12 June 2011 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=Talk:Slime&diff=19556 2011-06-11T22:28:52Z

<p>Miked0801: </p> <hr /> <div>Lol - glad to see one of my older bots still alive. Check out Sledgehammer for a wonderful yet nano RamBot. --[[User:Miked0801|Miked0801]] 22:28, 11 June 2011 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=Talk:Slime&diff=19555 2011-06-11T22:28:38Z

<p>Miked0801: Created page with &quot;Lol - glad to see one of my older bots still alive. Check out Sledgehammer for a wonderful yet nanon RamBot.&quot;</p> <hr /> <div>Lol - glad to see one of my older bots still alive. Check out Sledgehammer for a wonderful yet nanon RamBot.</div>

Miked0801 http://robowiki.net/w/index.php?title=Acero&diff=19538 2011-06-11T00:10:04Z

<p>Miked0801: Added a page for Acero since it still causes people fits after all these years</p> <hr /> <div>{{Infobox Robot<br /> | name = Acero<br /> | caption = The anti-pattern match bot.<br /> | author = ahf<br /> | released = Days of yore<br /> | extends = [[AdvancedRobot]]<br /> | targeting = [[HOD]]<br /> | movement = Anti-Pattern at distance<br /> | current_version = 1.0<br /> | license = None<br /> | download_link = http://www.robocoderepository.com/BotFiles/2151/ahf.Acero_1.0.jar<br /> | isOpenSource = yes<br /> | isOneOnOne = yes<br /> | isMelee = no<br /> }}<br /> <br /> == Background Information ==<br /> <br /> ; Bot Name<br /> : Acero<br /> <br /> ; Author<br /> : ahf<br /> <br /> ; Extends<br /> : [[AdvancedRobot]]<br /> <br /> ; What's so special about it?<br /> : This nano bot is an amazing test-bed. It's movement gives many advanced bots issues. Many people use it in their standard testbed and many more should. Even though it only uses Head on Targeting, its movement is good enough that it more than makes up for this deficiency.<br /> <br /> ; How competitive is it?<br /> : Fairly - it's #44 in the nonrumble and #460 in the general rumble, but its true power is how well it scores against advanced bots.<br /> <br /> ; Where can I get it?<br /> : Just click the download link to the right.<br /> <br /> == Strategy ==<br /> <br /> ; How does it [[Movement|move]]?<br /> : Anti-pattern match at distance<br /> <br /> ; How does it fire?<br /> : [[HOT]]<br /> <br /> ; How does it [[Dodging Bullets|dodge bullets]]?<br /> : Anti-pattern match at distance<br /> <br /> ; How does the [[melee]] strategy differ from [[One-on-one]] strategy?<br /> : None<br /> <br /> ; What does it save between rounds and matches?<br /> : Not sure<br /> <br /> == Additional Information ==<br /> <br /> ; Can I use your code?<br /> : This bot is open source and has been around for ages.<br /> <br /> ; What's next for your robot?<br /> : Beat up on future opponents until they solve my movement riddle.<br /> <br /> ; Does it have any [[White Whale]]s?<br /> : [[LittleBlackBook]], LifeLongObsession, all the top bots who can dodge HOT perfectly.<br /> <br /> ; What other robot(s) is it based on?<br /> : Unknown.<br /> <br /> [[Category:NanoBots]]<br /> [[Category:Bots]]<br /> [[Category:1-vs-1 Bots]]<br /> [[Category:Open Source Bots]]</div>

Miked0801 http://robowiki.net/w/index.php?title=Talk:XanderCat&diff=19536 2011-06-10T23:31:44Z

<p>Miked0801: </p> <hr /> <div>Congrats on breaking the 50% barrier. Seems that you have the planning of your bot on scheme, now it's just the translation into the right code. One small remark: You don't have to have 'zillions of versions' present in the rumble, the details of older versions still are available when not in the participants list anymore. Comparisons between two versions are quite easy to do like [http://darkcanuck.net/rumble/RatingsCompare?game=roborumble&amp;name=xandercat.XanderCat%202.0&amp;vs=xandercat.XanderCat%201.0] . Just click on your bot in the rankings, then the details and a few older versions are shown. Good luck with your further development! --[[User:GrubbmGait|GrubbmGait]] 08:37, 25 May 2011 (UTC)<br /> : Thanks GrubbmGait, though I'm not sure how much praise I deserve for being officially average. :-P I'm trying out a slightly revised version today, version 2.1. No major component changes, but it modifies the bullet firing parameters, driving parameters, some segmentation parameters, and has improved gun selection. [[User:Skotty|Skotty]] 20:43, 25 May 2011 (UTC)<br /> <br /> == Version 3.1 ==<br /> <br /> Interesting results for version 3.1. No real change in rank from 3.0, but using an entirely new drive. I've done away with the borrowed wave surfing drive from BasicGFSurfer and replaced it with a drive of my own design.<br /> <br /> Despite the new wave surfing drive (which I will call a Stat Drive) which I crafted almost entirely from scratch, I think it shares a lot in common with other wave surfing drives. It's just naturally where you end up when working out the best way to drive. I really haven't tried to tweak the segmentation yet, so I think it can be further improved with a few parameter changes.<br /> <br /> Here is what my new drive does (you will likely see a lot in common with other drive strategies out there):<br /> <br /> * Segmentation - Much like other wave surfing drives, my Stat Drive supports segmentation. I can't remember what it is actually segmenting on right now (don't have the code in front of me at the moment). I'll add that detail later. It is very easy to change the segmentation parameters. The Stat Drive relies on a seperate component to determine the segment or combination of segments, and the segmenters can be swapped in and out easily.<br /> * Tracking danger - Each segment has a fixed number of &quot;buckets&quot; or &quot;bins&quot; that represent the danger at a particular &quot;factor&quot;, where a factor represents an angular offset of the robot from an original bearing of the bullet wave origin to the robot at the time the bullet was fired. When a particular factor is determined to be more dangerous, a value is added to the corresponding bin or bins around that factor. Initially when I wanted to add danger, I just added to one bin. One thing I did steal from from the BasicGFSurfer wave surfing drive was the manner of adding danger to all the bins, trailing off sharply from the most dangerous bin. I don't know why I didn't think to do this initially. Once my eyes glanced over it, it was obvious it was what I should have been doing from the start.<br /> * Bullet Hits - The most dangerous of events -- actually getting hit by a bullet. When hit by a bullet, the Stat Drive records danger of a certain amount (lets say a value represented by the variable d) to the matching bin of corresponding segment. One tenth that amount (d/10) is currently added to all other segments, though this is just experimental; I may modify or remove that effect as I tune it a bit more.<br /> * Wave Hits - When a wave hits (but not necessarily a bullet hit), the Stat Drive currently records one fifth the amount of danger (d/5) for the matching bin of the corresponding segment. Thea idea being that the opponents gun, likely being a &quot;Guess Factor&quot; gun, might be more likely to aim for that bin next time, so lets try to avoid it. This also probably needs some fine tuning. Part of the same experiment as with bullet hits, adding one tenth of that amount (d/50) is added to all other segments.<br /> * Wall Avoidance - While I wrote it from scratch myself, wall avoidance right now is doing pretty much the exact same thing as the &quot;wall stick&quot; approach. I have some ideas that would be fancier, but the &quot;wall stick&quot; approach works for now.<br /> * Rolling danger - Rolling danger is the idea of removing danger previously added from bullets or waves that are over a certain age. The Stat Drive is not doing this right now, but I'm planning on experimenting with the idea.<br /> * Figuring out where it can get to - One of the first steps to avoiding a bullet wave is determining how far you can go in each orbital direction before the bullet hits. At first I used some crude approaches to this with the Stat Drive, but they just won't cut it if I want to be really competitive. I now have it predict our position into the future, taking pretty much everything into account (turn rates, acceleration/deceleration rates, wall smoothing, etc) to make the prediction as accurate as possible.<br /> * Figuring out where to go - once we know how far we can go, we have to decide where in that range we want to go. I'm experimenting with a few approaches. For now, it looks for the bin with the lowest value and heads there.<br /> * Figuring out how to get there - Once we know where we want to go, we have to figure out how to get there. This seemed simple enough, but one problem I ran into was overshooting the target and being in the wrong place when the bullet arrives. This problem turned out to be significant in my testing. So I had to do additional work to ensure that if I will reach my target before the wave hits, I slow down before getting there so I land right on target. This sounds easier than it actually was to implement.<br /> <br /> Where to go from here?<br /> <br /> Performance was roughly equal in the rumble to the BasicGFSurfer drive. I need to tweak the segmentation approaches and parameters. I need to tweak the manner of adding danger. And I need to play around with rolling danger to see what effect that has. Once that is done, I don't believe I will make any more changes to the Stat Drive or it's use in XanderCat.<br /> <br /> I may employ other drives in combination at some point using a &quot;drive selector&quot;, an ability that is built into the Xander framework. For example, I would like to build a drive and gun built specifically for &quot;mirror&quot; bots that mirror their opponents drive; the drive selector would switch to these components whenever a mirror bot is detected.<br /> <br /> Outside of drives, my Stat Gun is still a bit crude. I know I can improve there. And then I also have a few other little tricks up my sleeve I would like to try when I have the time.<br /> <br /> <br /> It's neat to see you taking such a systematic approach with robocode! If I may a few suggestions:<br /> <br /> * If I understand correctly, you add d/10 danger to every bin (except the one that hit you) rather than (in addition to?) adding bin-smoothed danger to each bin. I don't think this will help anything. The bin-smoothed danger should be enough.<br /> <br /> * Logging hits from every wave, regardless of whether the other robot hit your robot, ''will'' give you a flatter movement; however, you may not actually want a flatter movement, even against GF guns. Before wave surfing was invented, I imagine that GF guns didn't roll their averages very much. Because of this, a flat movement will be worse against these guns. Rather than giving the enemy a flat movement to shoot at (which will make their targeting very close to random), you should move to the same GF repeatedly. When they hit you there, you know there is a peak in their stats, so you move somewhere else, and hopefully they keep shooting there for a while, allowing you to dodge bullets. Did I explain that well?<br /> (I had thought of doing something like that but didn't for the reasons described above. It sounds rather similar to [[YersiniaPestis]], but without the adaptive weighting of the flattener.)<br /> --[[User:AW|AW]] 19:52, 6 June 2011 (UTC)<br /> <br /> Nice job! Implementing Wave Surfing correctly can be a huge undertaking. My first suggestion would be to try just disabling the &quot;every wave&quot; logging of hits. You're right this ''should'' make you more unpredictable to learning guns. What most of us have found is that straight dodging from bullet hits actually works better against the vast majority of guns - only against the best guns does a &quot;flattener&quot; (what we call that mode) help. But more importantly, a flattener also destroys your scores against simple targeters.<br /> <br /> I see you're getting 80% vs [[Barracuda]] and 88% vs [[HawkOnFire]]. Those could both be over 99% with no segmentation. My best advice would be to work on distancing, dive protection, and ironing out bugs until you can get that before trying to refine other aspects. Working on other stuff will only make it harder to fix the core stuff, and you may have to re-tune everything anyway once it's fixed. (Just turning off the flattener may go a long way!)<br /> <br /> Good luck! --[[User:Voidious|Voidious]] 20:37, 6 June 2011 (UTC)<br /> <br /> :Thanks for all the suggestions. I've been intentionally trying to come up with a lot of the ideas and code myself, as that makes it more rewarding for me. On the down side, this has made it harder to learn all the terminology used by the Robocode community. Not until both of your comments did I know what a &quot;flattener&quot; was, though I had seen the term pop up here and there. I hadn't spent too much time thinking about what the effects of it would be against different opponents, but your comments give me food for thought. I actually have my system set up now to run different configurations of my robot against a test base of robots, so I am now at the point where I can see some real results rather than just trying to deal with the theoretical. I'll try turning off the flattening and see what happens. [[User:Skotty|Skotty]] 22:18, 6 June 2011 (UTC)<br /> <br /> :I assume by &quot;distancing&quot;, you mean trying to keep my robot a reasonable distance away from the opponent. I was thinking maybe try to refine my drive path so that it will move slightly away from the waves if the wave origins are too close, and possibly favoring non-smoothing directions when near a wall and the calculated danger in each direction is similar. &quot;Dive protection&quot; as I understand it is not driving towards the enemy excessively; I don't see how this would happen except to a limited degree when wall smoothing, or on startup before bullets start flying (at the moment, when no bullet waves are in action, XanderCat will just move in a straight but wall-smoothed path, causing it to circle around the edges of the field; I should probably change this to make it move into a more desireable position before bullets start flying, rather than relying on chance). [[User:Skotty|Skotty]] 17:46, 7 June 2011 (UTC)<br /> <br /> == Version 3.2 ==<br /> <br /> Had a bad night of tweaking where everything I did seemed to make my robot worse. I've turned off the flattening but I don't think I have a proper test bed of opponents to determine what kind of effect it might have. It did increase the score on Barracuda and HawkOnFire, but only to the about 90%. I did, however, finish some new anti-mirror components. PolishedRuby 1 is soooo dead. :-D I haven't tested against any other mirror bots yet, but my tests against PolishedRuby put a big smile on my face. As you might guess, when mirroring is detected, I have a drive and gun that work in tandem, where the drive plots a semi-random route in advance that the gun can process to fire on the mirror of the future positions. Awesome. My framework makes it easy to add it on to any existing gun combinations. It's not perfect, but it gets the job done, and might can be improved a bit more. With the mirror components active, my gun hit ratio on PolishedRuby jumped from something very sad up to a wicked 70%.<br /> <br /> I've got my score on Barracuda up to the low 90s, and HawkOnFire up to about 98%. I've disabled the flattening, and I've implemented a new drive that takes command on the first few moments of a round to try and obtain better positioning before bullets start flying. Also, my StatDrive will now change it's angle a little to back away from waves when it deems itself too close to them. I also have the anti-mirroring operational. I was going to try and update my StatGun for this version (3.2), but I think I may hold off on that until version 3.3. I want to see what effects the changes so far have made.<br /> <br /> === Rumble Results ===<br /> <br /> Fascinating results in the rumble. Despite winning fewer rounds than version 3.1, version 3.2 ranks about 30 places higher. Presumably by beating the simpler robots by quite a bit more than previously. Lots of variations in the PBI. I'll have to play around with some of the ones version 3.2 performed poorly against. I'll probably come up with a way to turn the flattening on and off automatically, which I think some of the other robots do. Only other thing I can think of to do for driving is to put some work into not running into the opponent robots, which is something I have ignored previously. AntiMirror components rocked.<br /> <br /> Next version I will update the StatDrive. I know of a couple of ways it could be reasonably improved. And after that? Not sure...<br /> <br /> <br /> My suggestion is that you need to up your score against Barracuda - there are still lots of points to be gained there. Until you are getting 99+% you are losing points due to not getting far enough away. If you watch your battles against Barracuda note every bullet hit and think about what your bot could have done differently to avoid it, be it reversing, being further away, not being against a wall, etc and then code something to get it to (not explicitly, but generally) avoid that situation next time. I'm not sure how your drive system works but in my bots I modify the desired angle towards the orbit centre proportional to the distance from the orbit centre, so as it gets farther away it moves towards the centre, and as it gets closer it moves away. Anyways, some food for thought. --[[User:Skilgannon|Skilgannon]] 08:58, 8 June 2011 (UTC)<br /> <br /> :Were you looking at version 3.2 or 3.3? Version 3.2 gets about 93% against Barracuda. Yeah, it could be better. Version 3.3 in the rumble only got 80% against Barracuda. I can't explain that. I've run 3.3 myself against Barracuda many times, and it always gets around 93%, same as version 3.2. Ignoring that anomaly, where is that other 7%? It may be from collisions. Right now, XanderCat ignores collisions with the opponent, and can get stuck rammed against them. Also, it may be from getting too close when wall smoothing. I had mentioned the possibility of moving away from the wall in cases where danger each direction is similar in order to not get jammed against the wall as much, but I haven't implemented that idea yet. [[User:Skotty|Skotty]] 14:21, 8 June 2011 (UTC)<br /> <br /> :: I'd suggest hunting for bugs really. Even 98% against HawkOnFire, is low enough that I think that notable surfing bugs could be likely, (and having a large hidden influence against other bots). It should be possible to get to 99.9% or so if the surfing algorithm is reasonably precise and the bugs of implementation are worked out. --[[User:Rednaxela|Rednaxela]] 14:48, 8 June 2011 (UTC)<br /> <br /> ::: Version 3.4 moves up the ranks, but still gets 98% on HawkOnFire and 95% on Barracuda. I believe this is due to not having any dive protection when wall smoothing (I do employ distancing, if I understand correctly what this is -- attempting to back away some when in too close -- but this doesn't help if you are getting smoothed into a wall). I'm still working on a good solution for dive protection near walls. I tried a few things when developing version 3.4 but haven't come up with something that improves performance yet. Perhaps for the next version. -- [[User:Skotty|Skotty]] 17:16, 9 June 2011 (UTC)<br /> <br /> A quck note for you in relation to ucatcher. That bot is uses bullet shielding. Basically, the better you shoot at it, the better chance it has to deflect your shot. Not too hard to detect when it happens either, just check the bulletHitBullet event and see if it happens a bunch. If so, don't aim for the center of the bot, but an edge of it instead. --[[User:Miked0801|Miked0801]] 23:31, 10 June 2011 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=Talk:LittleBlackBook&diff=19524 2011-06-10T05:16:39Z

<p>Miked0801: /* Bot Blog */</p> <hr /> <div>== Congrats! ==<br /> <br /> Congrats! It's nice to see some movement in the nano scene lately. I was pondering predefined data bots myself actually. I'm curious though, you say &quot;Any perfect dodge stop and go will kill it&quot;, which seems odd to me. It should be quite trivial for a distance/lateral segmented GF gun to hit that I'd think... --[[User:Rednaxela|Rednaxela]] 01:51, 15 June 2009 (UTC)<br /> : Math.signum() off e.velocity screws up 0 velocity checks and I have no velocity averaging. I'll check other bots for inspiration though. Has to be TINY though<br /> : What about... &lt;code&gt;static double foo = 1; foo = e.velocity + 0.01*foo; foo /= foo;&lt;/code&gt;? Not sure if that would be small enough, and I haven't checked it's codesize, but I think it's smaller than any others ways to handle that which come to my mind. I think it's smaller than &lt;code&gt;static double foo = 1; foo = (e.velocity == 0) ? foo : Math.signum(e.velocity);&lt;/code&gt; anyway, since conditionals and function calls are expensive if I remember right. I'd also suggest seeing if you can get rid of the need to normalize the value to 1/-1 all together, but that may not be possible in this case. --[[User:Rednaxela|Rednaxela]] 04:15, 15 June 2009 (UTC)<br /> :: Anything having to do with statics are expensive. Your above code is probably around 25 bytes or so. Math.signum(e.getVelocity()) is 6 or so. I can easily fix my problem by adding +1 to the e.getVelocity() check on the inside of the gun( for 2 bytes)... But! It will only hit perfect stop/go 50% of the time as it is setup to use the velocity to know how far to lead. Also, bots like FretNano who have good guns, but get stuck on walls randomly, would then be unhittable. I get 1 lead value per distance segment at the moment. I've got a few ideas on how to improve this, though it will double+ the size of my string table. I will adhere to the 200k max limit and with 1000 or so bots to profile, I have to be careful on size. --[[User:Miked0801|Miked0801]] 13:38, 15 June 2009 (UTC)<br /> <br /> Hi! Awesome results! Now that I looked at the code, I think there is one little problem with the overall concept: every time a new robot or a new version of a robot appears, you have to update the stats in your bot. --[[User:Robar|HUNRobar]] 10:31, 15 June 2009 (UTC)<br /> : And a decent problem it is. I'm going to review the string libraries today to see if I can find a &quot;closest to this name&quot; type function for my search. That'll at least handle versioning. The version in there right now is using default behavior against [[Pugio]] because my table is setup for 1.40. When all your other versions get cleared from the rumble, my rating will go up another .5 or so. --[[User:Miked0801|Miked0801]] 13:38, 15 June 2009 (UTC)<br /> :: &lt;code&gt;HashMap&lt;String, String&gt; enemyGF; enemyGF.get(e.getName().split(&quot; &quot;)[0]);&lt;/code&gt; =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 14:03, 15 June 2009 (UTC)<br /> ::: Um, wow. That does work: e.getName().split(&quot; &quot;)[0]. I rediscovered it myself and you had it here the whole time. I feel very stupid. Thanks for the advice! --[[User:Miked0801|Miked0801]] 06:13, 23 June 2009 (UTC)<br /> :::: No problem at all. =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 11:05, 23 June 2009 (UTC)<br /> <br /> Nice! I may re-release [[Ocnirp]] 1.0 to screw your stats =) Updated Wikipedia page for you now. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 12:00, 15 June 2009 (UTC)<br /> : Don't bother, I'm already using default values against that bot so it wouldn't make any difference so Nyaa Nyaa! :) --[[User:Miked0801|Miked0801]] 13:48, 15 June 2009 (UTC)<br /> :: Really? I don't think so. (default is 50-40-30-20-10-0, right?). Beside, I'm working on Nano adaptive movement (Mysterious is its fail attempt) =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 14:03, 15 June 2009 (UTC)<br /> ::: Ok, you win. There are quite a few bots taht got default cases though. For some reason I thought Ocnrip was one. And, yeah, nice string match there. I could fit that if, oh I don't know, I took out all my movement code ;) --[[User:Miked0801|Miked0801]] 14:20, 15 June 2009 (UTC)<br /> :::: That doesn't call fit, really. :P &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 14:53, 15 June 2009 (UTC)<br /> <br /> Thanks! Links and work email address removed. --[[User:Miked0801|Miked0801]] 15:27, 15 June 2009 (UTC)<br /> <br /> : He he, the revision system still have it. =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 15:32, 15 June 2009 (UTC)<br /> :: Yep - but at least basic spider bots won't pick it up and spam be about male enhancement products :) --[[User:Miked0801|Miked0801]]<br /> <br /> Ok, new version in the wild. I expect this release to be better against stronger bots, but I also expect some startlingly poor results against a few bots. These I can tune back to either the old values or a combo of new and old. Stelo.MirrorNano being an example. My next release will beat this bot 90/10, but now LBB is losing 45/55. No panic :) --[[User:Miked0801|Miked0801]] 02:04, 18 June 2009 (UTC)<br /> : Good result. My next update tomorrow is going to absolutely destroy the competition. This is going to be a 1900+ rating bot. --[[User:Miked0801|Miked0801]] 05:45, 18 June 2009 (UTC)<br /> <br /> == Bot Blog ==<br /> Seems like a decent place for random ramblings. The averaging code is doing its job, it just needs some table number TLC. Alas, it also screwed with some other scores that will need attention. I also commited a cut and paste errored with nat's SNG 1.0b bot resulting in a 6% score. Lame. I may try taking the averaging back out and using firepower control instead. It'd probably help me more overall to fire at 3.0 firepower at range 80 or 120 and closer against everyone. The Micro scores have been decent thus far with their first autogeneration pass. 19th is a good starting point and I know I can get to 15th or even 10th with some work there. I'll drop the mini scores in Tuesday or so and for another overall ranking boost. I still believe I can get this bot to a 2k points score with over 80%APS in nanos with a few revisits to lagging numbers.<br /> <br /> Wow, a good day. Found another 10 bytes by just re-arranging the stack vars. Used that space to try out variable move distances. Helps quite a bit against the weakest bots. Also fixed bugs with a few bots that came from typos. Finally, I fixed poorer results against rambots wehre I wasn't aiming right at range 40 and in. My scores are now approaching [[DrussGT]]'s against the low-end bots. Using that bot's scores gives me a reasonable target to short for. I'm also going to experiment with variable firepower as well, though for some reason I keep pushing back on that - dunno. Next release tomorrow night. Shooting for APS of 78ish in nanos. That would put me close to my goal of a 2k score. Hopefully, my micro score will get me top 15 there as well. I'll start running Minis by end of week to see if I can get top 25 there and perhaps top 100 overall (aiming real high, I know.) --[[User:Miked0801|Miked0801]] 03:38, 23 June 2009 (UTC)<br /> <br /> : You should to remember the [[Code Size/Cheat sheet|Code Size/Cheat sheet]]. The most important part is the vars-on-register, which is discover by Simonton I think. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 11:02, 23 June 2009 (UTC)<br /> :: I just rearrange them all until I get the smallest result :)<br /> <br /> Another good day, but I found a dumb bug I introduced to my table generation a few days ago which will require me to revisit all the nano values. Sigh. Good news though, found another 8 bytes or so by declaring the string table final (never changes so I should have done it ages ago) and by rearranging a few typecasts to make sure we got int on int math wherever possible. That means I now have both distance and firepower control in the table! It hurts by aim a touch from 80 pixels and in, but for 1 more free byte I could fix this. I'll keep looking. 8 more bytes and I get variable string matching, though if firepower or move control prove poor, I can always swap this in for the other. Because I have to do a table revisit, I'm pushing my release back one more day. Who'd have though a variable GF, variable firepower, variable move distance, variable turn control bot could be done through a silly string table. It's like the synthesis of all the best nanos in one place. Next release will have some bugs, but the one following will be absolutely epic. --[[User:Miked0801|Miked0801]] 18:48, 23 June 2009 (UTC)<br /> <br /> Bleh. Had to work late a few nights. I'm just now getting all my initial micro/nano runs complete. Good news is that only [[Moebius]] is currently able to consistantly beat me now in nanos. I'm going to experiment with distance control next as many bots are optimized for certain ranges and I expect I will do well at varying ranges against many bots. If it works well, I'll trade something off to get it. We'll see about a tomorrow release, work allowing. --[[User:Miked0801|Miked0801]] 07:39, 25 June 2009 (UTC)<br /> <br /> Played around with enemy distancing and found it helps (much) more than firepower control. But, my test cycle is too far along to scrap and start again so I'll go ahead with what I have. Besides, I believe I found a way to fit all 5 factors into this nano anyways - Fire Power, Chance to reverse direction, Min Distance to move, desired distance from enemy, and Guess Factors. It requires my tables to be created differently (again), but I'll go for that next version. This is why I haven't bothered with minis or megas yet - the tables flux dramatically with each version. It also means yet another multiplier when creating my tables. I'm already running 20+ versions per bot through roboresearch. Adding distance is another x4 or so. Yikes. Back to 1 good test run and cull, cull, cull so that I have time to balance what makes sense. At least my testing methods are improving so that this doesn't take too long. Just need 1 more set up data to finish up for the guess factors and then we'll put this bot back together again. --[[User:Miked0801|Miked0801]] 07:29, 26 June 2009 (UTC)<br /> <br /> Ok, version is up and we gained nearly another 2% APS in nanos and even more in Micros. Nice. There's still a few bots that came out a bit half baked, even with all the care I put into the tables before releasing. I'll revisit those for one last version 1.5x release and then go onto version 1.6x with distance control. Still shooting for 80+% APS, a perfect PL score in nanos, and 2k in ratings. 72 Glicko's to go. --[[User:Miked0801|Miked0801]] 02:59, 27 June 2009 (UTC)<br /> <br /> Hey, you've taken my micro's place in the microrumble! I really should do something right after I finished my flash game. ;) --[[User:Robar|HUNRobar]] 17:31, 27 June 2009 (UTC)<br /> <br /> Dang it. Screwed up robar.nano.Scytodes 0.3's table, which costed me 50-60 battle points and .33 APS in the Nano Rumble (.15 in micro). Savant values are weaker too, but that can be attributed a little to random luck. Beyond that, a very good update. Solidly in 11th now in Micros and 1.5% APS from 80 in nanos. That's only 260 battle % points and 50 of those are from my above mistake. But, without distance control, I'm running out of big gains. I can probably push this bot to 80% APS and 2k Glicko without distance, but it will take a lot of work. I made a lot of gain my swapping appropriate bots to 2.0 fire power. Some of those I can switch back to get some ground I lost between 1.52 and 1.53. I did tie for the PL score this time and would have had it if not for Scytodes. Next version I'll get it right. I think I'll release a 1.54 just to try for 10th/9th in the micros without distance help. --[[User:Miked0801|Miked0801]] 03:46, 29 June 2009 (UTC)<br /> <br /> Well fixed Scytodes and decided to alphabetize my list and lo and behold I had missed 4 other bots - all micros. Adding those gave a decent score increase for them as well and would probably challenge Jen for 10th. But, I went ahead and started the HUGE roboresearch database needed for my next release. We're talking around 1 Million battles to be run before all is ready. I'm guessing my computer running 24/7 will get through this info in around 3 days. Wow. The good news is that my previous run is compatible so I saved 150k battles or so. All this will put me over 80APS in Nanos and will put me well into top 10 in micros. I'll know for sure once I start seeing some comparison results against the micros. The top nanos appear to be weak against different ranges, but I'm not sure on Micros yet. I'll post tomorrow with some initial results. --[[User:Miked0801|Miked0801]] 21:30, 30 June 2009 (UTC)<br /> <br /> Test run about 15% complete. I'm tuning back to breadth of the first run to speed it up so I can play before next week. --[[User:Miked0801|Miked0801]] 02:18, 2 July 2009 (UTC)<br /> <br /> 33% done and I'm not patient enough to wait for it to go much further so I put together the next version - and had another awesome idea on how to make it do more for less. I now have distance control and! - all other factors also are available based on distance as well. This means variable firewpower on distance. This means I can change my move mode out of oscillation at those distances where I run into head-on shots (around 280 or so). I can even change my desired distance based on distance meaning I can ping-pong between values to help with multi-mode movers and to throw off pattern bots. That plus partial string matches and I'm sitting at exactly 249. That's enough tech for my goals. Now it's time to do my last pass through the nano/micros and see just how much pwnage will be wrought. 85+ nano APS isn't out of reach.<br /> <br /> Work, work work. My job is heating up to the point where things have been on hold for a bit. This will continue for a few more days - grr. --[[User:Miked0801|Miked0801]] 17:39, 8 July 2009 (UTC)<br /> <br /> And even more work. I'm in crunch mode now and barely have time for breathing. I've still got my next bot upgrade ready, jsut need to find a couple uninterrupted hours to fix a few minor things. I'm still alive guys :) --[[User:Miked0801|Miked0801]] 20:44, 27 August 2009 (UTC)<br /> <br /> Good to hear =) I'm also pretty snowed under, but it seems that when that happens Robocode becomes my outlet =) --[[User:Skilgannon|Skilgannon]] 20:55, 27 August 2009 (UTC)<br /> <br /> Project starting to wrap up - we'll see if life returns to normal soon... --[[User:Miked0801|Miked0801]] 16:30, 6 October 2009 (UTC)<br /> <br /> Project's done! Vacation is started. Updates to follow :) --[[User:Miked0801|Miked0801]] 16:28, 6 December 2009 (UTC)<br /> <br /> : Yay, welcome back! =) --[[User:Voidious|Voidious]] 17:18, 6 December 2009 (UTC)<br /> <br /> Ok, Nanos mostly refit. I want to find another 1.5% of APS then its back to micros. Mostly hand tuning at this point. --[[User:Miked0801|Miked0801]] 22:46, 17 December 2009 (UTC)<br /> <br /> Actually changed a little base code with this version. I removed the adjustTurnForGun() call and replaced it with a bit of randomness added to the range index. This results in slightly more random ranges when firing. It makes it easier to hit multi-modes, bullet catchers, and wave surfers, but hurts my score against really, really weak bots and the best nanos a bit. Still, seems like a decent upgrade. Broke 2 nano bot solutions with this chagne that I can easily retrofit back to pwnage. I will also be able to make a further micro pass to get above Jen on my next update. I beginning to believe that this might get top 5ish in micro before I'm done. --[[User:Miked0801|Miked0801]] 00:07, 9 January 2010 (UTC)<br /> <br /> FYI, this bot needs to be compiled with Sun's Java Compiler in order for it to remain byte size complient. Got bit with that today. Made a major pass through the tables using the top Mega bot's scores in comparison to mine for inspiration on who to fix. Found many, many bots that were improved 10% APS or more. This should be the version, barring bugs, that hits 80%APS or even 81% APS in nanos - and should also hit 2k Glicko. And there's still a bit (not much!) more tuning that can be done. There are countless ways of ordering my tables to get 1-5% individual APS tweaks that I probably need a seperate program to find. Overall, this has ben a wonderful experiment and mega contenders should take note. I'll continue to tune it a touch more, but I'm also going to investiage Lateral Velocity segmentation as well. If I get inspired, it may not cost too much :) --[[User:Miked0801|Miked0801]] 23:07, 13 January 2010 (UTC)<br /> <br /> Results looking very nice so far, though not sure if it'll quite end up getting past 2k Glicko. What I find most impressive is how you fit so many movement modes alongside a GF gun, in a nano, that's an awful lot of movement modes for a nano, particularly with the distance-based selection of them! :) --[[User:Rednaxela|Rednaxela]] 03:50, 14 January 2010 (UTC)<br /> : Thank you! I'm a rather proud parent of this bot and all comments make me grin :) --[[User:Miked0801|Miked0801]] 15:49, 14 January 2010 (UTC)<br /> <br /> BTW, the build system seems to be completely confused at the moment. Would it help if I released a 1.60 version to fix it? --[[User:Miked0801|Miked0801]] 15:49, 14 January 2010 (UTC)<br /> <br /> : What do you mean by &quot;build system&quot;? --[[User:Voidious|Voidious]] 16:24, 14 January 2010 (UTC)<br /> :: Was about to ask the same, nearly got edit conflict :) --[[User:Rednaxela|Rednaxela]] 16:33, 14 January 2010 (UTC)<br /> <br /> :: At the moment, the rumble is only running LBB 1.58 (retired), not LBB 1.59. I believe it is because 1.59 lost roughly 30ish nano battles whilst retaining the micro and up battles before I fixed an issue on my local client. I could upload the missing nano battles and that may fix it, but I wanted permission to do so first as I would need to edit the results.txt file manully to add the missing numbers. --[[User:Miked0801|Miked0801]] 17:42, 14 January 2010 (UTC)<br /> <br /> ::: &quot;... fixed an issue on my local client&quot;? Please don't edit results.txt or upload any old results! Best thing to do is delete all files in the roborumble/files and roborumble/temp folders and start fresh -- preferably with uploads disabled for the first run just to make sure. --[[User:Darkcanuck|Darkcanuck]] 21:27, 14 January 2010 (UTC)<br /> <br /> :::: Not what I did. I have 2 copies of Robo installed. I created 1.59 in version 1.6.1.4 and it was 256 bytes in size. oops. I then fixed the problem and recreated it in my other version of robocode, but stupidly called it the same thing. I then took this version and copied it to both builds. But, the codesize.txt never updated to the new, reduced size for the updated lbb. Therefore, it didn't record roughly 30ish nano battles. When i noticed this, I completely killed the cache, the local 1.59 file, and removed it from the codesize file so that it could recreate it. This worked, but those 30 or so nano battles were lost as has since confused the server quite a bit. Another side effect of this is that when you first run the client, it correctly runs version 1.59 of LBB, but further iterations always run the previous verion. Long story short, be careful about versioning of bots... --[[User:Miked0801|Miked0801]] 21:45, 14 January 2010 (UTC)<br /> <br /> :: This is weird... If you look at its roborumble details, 1.58 only has 3 battles: [http://darkcanuck.net/rumble/RatingsDetails?game=roborumble&amp;name=mld.LittleBlackBook%201.58]. Only 2 for mini, but lots for micro and nano. Not sure how that would happen... The server tries to run all pairings for each version (after a certain point), even if it's retired, so maybe that's what's going on. If you delete 1.58 from your rumble dir, it won't run 1.58 any more. (But anyone that has 1.58 will until it has all pairings, if that's the reason.) --[[User:Voidious|Voidious]] 18:51, 14 January 2010 (UTC)<br /> <br /> :: Wow... this is very weird... the &quot;Last Updated&quot; times for LittleBlackBook 1.58 keep going <br /> up in mega/mini (and different update times from mini/nano), but the battle count is only increasing in mini/nano! Something is broken on the server side I think.... because all clients with LBB 1.58 (like mine) are ONLY running LBB 1.58, but the Rumble isn't recording the mega/mini results so it looks like it'll go on forever... --[[User:Rednaxela|Rednaxela]] 19:46, 14 January 2010 (UTC)<br /> <br /> :: It should be fixed now. Looks like a concurrent retirement/reactivation. My guess is one client saw no battles for 1.58 in the last 4 hours and started to retire it, first for the general rumble then the mini. But then another client uploaded new battles (either due to old results not yet uploaded or an old priority file) while the retirements were in progress leading to the corrupted states. I have a permanent fix in mind, but it will require a lot of testing which I have yet to find time for... --[[User:Darkcanuck|Darkcanuck]] 21:27, 14 January 2010 (UTC)<br /> <br /> ::: Wow, 1.58 has 7963 battles in mega... yep... clients sure working away at it when things were messed up before... :) --[[User:Rednaxela|Rednaxela]] 03:55, 15 January 2010 (UTC)<br /> <br /> Today was a huge update! Managed to redo and find roughly 20ish more bytes!!! Desired distance from enemy table became approach angle table for a big savings. Found 2 bytes in the averaging code. Came up with a new way to do bullet detection that costs only a couple more bytes than my simple one from before. Added Ramming ability. Overall, this bot will be weaker as the dodging stuff was so tightly coupled into the random movement, but next version will keep the massive increases against the simpler, linear aim bots while improving the general movement. This bot could very well reach top 5 in Micros. I have also decided that my string tables will not exceed 200k as per the Rumble rules to make it fair. Right the tables are sitting at 100kish and won't get much bigger until I add the Minis some day. I am now awaiting the results to see which bots are now broken and need another revisit :) --[[User:Miked0801|Miked0801]] 01:33, 16 January 2010 (UTC)<br /> <br /> Tables, tables, tables. Fixed 30 or so bots thus far that I had weakened with the improved oscollation code. This put me above where I was at 1.59. I've got roughly 30 more bots to modify to get back to where 1.59 was against all bots. That's a good days work. Then, there's a revisit to change some bots from random movement back to oscollation for a nice boost. The new and improved energy detection code as made me weaker overall against PM bots. I'm working on a solution to this now. If I can find one, that's another 2APS overall or so and makes this a contender for the Micro crown. Then it would be on to the minis. Big talk though; gotta get there first! --[[User:Miked0801|Miked0801]] 19:15, 18 January 2010 (UTC)<br /> <br /> Reviewed the movement code a bit because it still felt heavy and figured out a way to do near perfect stop-n-go movement. Good enough to fool Smog 90/10. It requires a bit of table wrangling to do though so I'll wait for version 1.70 or so to do it. I've still got lots of bots to tweak before I add yet another movement mode for maybe 5% of my opponents. Actually, stop-n-go overlaps most of my current oscollator bots so I'll have to review which helps more. I could use my extra few bytes to improve my gun instead by increasing the random range it uses for the index a bit more. Or again, look perpendicular velocity segmentation which is still a bit out of reach. Lots of choices here. Perhaps it's time for some heavy roboresearch... --[[User:Miked0801|Miked0801]] 19:27, 20 January 2010 (UTC)<br /> <br /> Latest version I accidently bugged Fuatisha and lost 5aps on him. In addition, I removed the minor random added to the aim and lost .25 overall APS and gained back a bunch of bytes. Improved micros a ton though. Now, I'm sitting at 240 bytes and looking into its next improvement. It will cost 0 bytes to added near perfect stop'n'go, but I inherit another string table. That would give me another full overall APS though so I will probably do it. After that, it's time to look into improving aim with my extra bytes. I may finally be reaching the end of what I can do on movement alone. --[[User:Miked0801|Miked0801]] 16:32, 22 January 2010 (UTC)<br /> <br /> Added perfect stop n go with this version at the cost of 8 bytes. This, plus some TLC with some aim tables, has moved me up roughly 1 full APS in the rankings. I'm now #4 in micros and may hit #3 when things stablize - with a bugged ntc.Knowledge entry that cost me 40ish points in that battle. I also seem to have comfortably hit 2k Glicko in Nanos! Party! I'm also a hairs breath away from 2K in both rankings which would be a first. I found a new, flatter movement curve and randomized my aim a bit more on generic bots for a good overall catagory bump. The same pattern can be used to help my scores against the top micros next time around. Hopefully, no reds on the micro screen sometime in my future. Still have 4 or 5 nanos I just have a very hard time beating. I'll keep working at it though. [[Fuatisha]], you are an awesome bot. Next upload goal is 3rd in micros approaching 80 APS. We'll see if I can pull it off. --[[User:Miked0801|Miked0801]] 07:32, 27 January 2010 (UTC)<br /> <br /> Looks like 3rd in Micros is achieved. Also, this build may give me a perfect PL score in Nanos. [[Fuatisha]] is the only question mark right now. I actually found a movement pattern that confuses some of the string PM guns and gained a nice chunk off the top bots in nano land. That means next updated will be mostly concentrating on Micros to see if I can approach 81% in the Micro rumble. That will be difficult, but doable. If I get there, then I am a micro crown contendor with my silly little nano. I also have a new home computer coming online this weekend. Hopefully reobocode is 64-bit Windows 7 compatible. Should be. If so, I will have roughly 10x the computing power I have right now for roboresearch and should be able to put together a first pass on mini-bots sometime next week. If it goes smoothly, I may just setup some scripts and add all the bots just to see if I'm top 100 overall or not yet. That would be a trick. Wow this bot has come far... --[[User:Miked0801|Miked0801]] 22:51, 28 January 2010 (UTC)<br /> <br /> About 50% complete with first pass at minibot tables. I have good movement types for them all, now am porting across aim. Then, I test against distances. Then, rebuild with best distance and test. Should take another 2-3 hours. I might get to that tonight. I will also probably pass the nano/micros back through a test pass again as well, now that I have enough CPU power to do a decent pass in a couple hours as opposed to a couple of days. Next release, I will skip to 1.70 because I'll have updated roughly 20% of the tables. I have no idea where I'll land against the minis, but not top 10. Initial testing is showing just how strong the top 5 bots in that division are. --[[User:Miked0801|Miked0801]] 18:55, 2 February 2010 (UTC)<br /> <br /> Sigh - compiling with minibot data crashes the java compiler. My bot cannot get any bigger than micro with this technique. --[[User:Miked0801|Miked0801]] 05:47, 3 February 2010 (UTC)<br /> <br /> : Perhaps try a java bytecode disassembeler/assembler to hack the additional string length in? That might work to circumvent any compiler crashing unless it's a limitation inherent in the bytecode standard itself. --[[User:Rednaxela|Rednaxela]] 06:09, 3 February 2010 (UTC)<br /> <br /> Solved it! Too many character concats blowing up the compiler. How to fix? I just discovered how to put a unicode literal into a string &quot;\u008f&quot; becomes character 8f! This also has the added benefit of making many, many of my entries a much more readable single constant that I can static const final declare above. I will also be able to use a real IDE again as my current version crashes ecclipse and visual studio. Happy days for unicode literals! --[[User:Miked0801|Miked0801]] 16:20, 3 February 2010 (UTC)<br /> <br /> Learned some Java things the last few days:<br /> * \u000a, \u000c, and \u0022 (\r, \n, and &quot;), when put into a string literal, are treated as a raw symbol meaning you have to \ them or use a seperate symbol.<br /> * Non-aligned tables make for bugs that are very hard to find. Much debugging was needed to fix these bugs.<br /> * RoboResearch on broken bots doesn't help much in terms of strength judging.<br /> * The top minis are STRONG!<br /> I have 1 more day of tweaking and then an update. --[[User:Miked0801|Miked0801]] 05:26, 6 February 2010 (UTC)<br /> <br /> Chugging lots of numbers this weekend - ran roughly 100k battles over 2 days, testing ideal range from target from 100 to 380 units per opponent. The results of this tuning pass will appear as soon as I find 2 or so hours to comb through the results and adjust my range table. On average, I was getting a good 5-10% APS kick every 3rd robot or so, but I also know that with such a large update, I will accidently break a few bots as well. Still, when this pass is complete, I could be contending for micros overall. Minis - not sure where I'll land, but at least top 20. [[Fuatisha]], I may finally have a marginal (52/48) solution for, but that's too small to count on. --[[User:Miked0801|Miked0801]] 19:00, 8 February 2010 (UTC)<br /> <br /> BAH! 1.67 jar is partially corrupted so the source isn't available. Lame. It also has 10 or so bot bugs to fix. I'll get those taken care of tonight and get a new version reloaded. --[[User:Miked0801|Miked0801]] 18:16, 9 February 2010 (UTC)<br /> <br /> Just uploaded a test for initial movement vs no dodge against 0.1 bullets and yes dodge up to 3.9 power change. Also may stick to walls slightly more. I know that this helps against ram bots, but am curious if it helps elsewhere. I've also fixed the mess that was 1.67. When adding that many entries, mistakes will be made. With 1.69, I finally got 10% ahead of the nearest nano, an achievement in itself. I think I found 1 more byte in the aim code if I want to redo 1/2 the aim values. The typecast to short can be dropped if I change my negative aim values to 2*Pi - values as I'm normalizing my gun anyway. I'll do that if the intial movement change turns out decent and I want the slightly better dodging code back. Then I do another comb through for 1 more byte. Always 1 more byte :) I'm now also thining about PhoneBook, a micro bot based on the lessons this bot has taught me. I won't abuse string literals like I have with this bot as I'll have enough room to handle things more elegantly (at first!). I'm also going to make another pass through [[Infinity]] and [[DustBunny]], using my new tricks to save a ton of space. That may free up enough space for them to go on a new melee run. For fun, I've calculated what it would require to brute force the best possible bot with this technique and it would cost about (40^6 x 30 x 8 x 20 x 50 x 100) x numBots=800 x numSeasonsToGetGoodResult=10 or 7.86e20 battles run. Even at 1 battle per second, I don't think I have time to wait around for this result to appear. And this is with some culling already built in. Perhaps I'll check out JGAP or something for fun to see if a genetic algo comes up with better answers than what I've been doing. --[[User:Miked0801|Miked0801]] 22:59, 12 February 2010 (UTC)<br /> <br /> : Some rough calculation told me that even at 1000 battles/second, by the time the result appear, out sun will be White Dwarf for 2E10 year already ((7.86E20)/(86400*365*1000) - 5E9 approx. = 1.99E10, give or take leap year) --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 04:48, 13 February 2010 (UTC)<br /> <br /> Funny how taking out &quot;code improvments&quot; actually gained me between .25 and 1.0% APS in divisions. Now I'm sitting at 243 bytes with 6 bytes to spend on whatever. I also believe I may have figured out a cheap size way to get (averaged) lateral velocity segmentation in. If it works, I will be micro champion and will challenge for minis. Just need some time to see if it works - or I can go optimize some tables a bit to squeak out another 1.5% in micros and try to win that way. Either will work given some time. --[[User:Miked0801|Miked0801]] 08:16, 14 February 2010 (UTC)<br /> <br /> I've coded in average lateral velocity / distance segmenting on my local copy at the cost of only 2 bytes. I'm not happy with my data gathering method though. With simpler bots like el33tGangstar &lt;sp&gt; or [[Infinity]] or even [[spinbot]], I should be able to get a near 100% lock on rate with my gun and my test bot is currently not able to do this. I even added in a segment for acceleration/deceration/steady to see if perhaps that was the issue without luck thus far. Or am I being too perfect here? Amazingly enough, multiple segments isn't as easy as I thought it would be. Perhaps that's why there are so many different ways of doing this out there right now. If I can get my dataset cleaned up, I can test it against 10-20 bots and see how much of a difference it will make. It will fix my current weakness against multi-mode moving bots as well as make my data tables in general more efficient in space. I'll basically be trading 80% of my movement tables (which are mostly unused anyways) for additional aiming information which can be very useful. I can also explore segment size being controled via a more complex formula than e.distance() / CONSTANT to better pack my data into useful areas - with size cost being controlled. Perhaps something like a bell curve centered around 200ish distance. Perhaps even something like AmplitudeConstant * Math.sin(Math.min(e.getDistance * Constant, maxRange)). That costs around 27ish bytes so maybe I'll just stick with the original :) If I do get this to work, it means revisitng every stinking entry in the bot; AGAIN. Man that sucks --[[User:Miked0801|Miked0801]] 21:57, 16 February 2010 (UTC)<br /> <br /> It's been a while and I have been doing various experiments. I've now got my helper bot generating a profile based on acceleration, avg angular velocity, distance, and fire power. I've also calculated the math such that I have a very good idea if a particular GF bin or sets of bins actually hit the target or not. From that, I can compare the various fire power bins to get a points per tic calculation to determine what firepower is most effective at what range calculation. So, I now have a system to automate firepower at distance selection. Just that alone put into the current LBB framework would probably grab a full aps and perhaps more. But, I'll be adding an additional module to the test bot to iterate over the various movement profiles I've created. If it can alternate best movement check, best gun check, and iterate back and forth until both values agree, I've now automated most of the table creation process. Once that works, then I can use this new process to generate a set of tables for angular velocity vs distance vs firepower tables and perhaps even acceleration if I can find the code space. This of course is time consuming. Ambitious, but if successful, I'll have a very, very nice bot upgrade and a low labor path to adding all bots regardless of codesize catagory. I envision a time where adding a new bot is just a matter of running my test bot against it a few thousand times until the numbers stabilze. If I place the movement checks into an external xml or whatever table, then I have a way of adding new movement types at will without recompiling. A fully automated LBB table system. This of course could be used as a spring board for larger, more complex bots in the future. --[[User:Miked0801|Miked0801]] 18:07, 22 February 2010 (UTC)<br /> <br /> No work this last week - interest is waining and work is picking back up. I will make time in the near future to claim the micro crown though :) --[[User:Miked0801|Miked0801]] 19:15, 2 March 2010 (UTC)<br /> <br /> Work still going strong here. Interest renewing. I will get this bot to #1 micro some day when I have a few days to work on it... --[[User:Miked0801|Miked0801]] 18:57, 21 April 2010 (UTC)<br /> <br /> One work project complete, but another short timeline project started. Ugh. Still a few weeks at least until I can start thinking here again. I've got at least 5 new bots that would want to be added to my library. The there's finishing my last edit run on a new improved gun... --[[User:Miked0801|Miked0801]] 16:48, 8 June 2010 (UTC)<br /> <br /> Hooray, a new nano to the field that is strong! I look forward to seeing how far you can go Caligula! Still busy, busy at work, but still watching the action here --[[User:Miked0801|Miked0801]] 17:47, 7 September 2010 (UTC)<br /> <br /> Fighting the urge to play again over winter break :) --[[User:Miked0801|Miked0801]] 05:07, 31 December 2010 (UTC)<br /> <br /> Got lates bots and ran 2/3s of the testing suite needed to add their info. Man I wish I could automate this better. --[[User:Miked0801|Miked0801]] 15:48, 21 May 2011 (UTC)<br /> <br /> Ok, I've only got a few more outlyers to redo. Then I gotta figure out the google upload thingy. --[[User:Miked0801|Miked0801]] 06:03, 31 May 2011 (UTC)<br /> <br /> Nice updates. Back to #3 in Micro, but getting the last 2 bots will take forever with the current strings. So... I just figured out how to get averaged angular velocity segmenting combined with distance segmenting into its gun. Just got to create the helper bot to make the new aim tables and shrink the other tables by at least half so that the change is size neutral. I also could add psuedo acceleration to the segmenting as well, but that costs 10 more bytes I don't have yet. One thing at a time I guess. If this work as I expect, it will make LBB the micro champ and will put it top 5 in minis. That would be something. Heck, at that point, I could change the string table cheeziness into a file read like other other bots and make an official micro out of it with some space to spare. --[[User:Miked0801|Miked0801]] 05:16, 10 June 2011 (UTC)<br /> <br /> == LBB Cheeze Factor ==<br /> <br /> I added PEZ's [[LittleEvilBrother]], because it also had a String based GF gun, I believe. There was some discussion about whether or not it was cheesy to load data for a bot not capable of saving data. Consensus at the time was that it was cheesy, but judging by how much better [[LittleBlackBook]] does, it seems like a pretty cool strategy that has a lot of room for experimentation. Plus there's been nothing new in nano-land for years! --[[User:Alcatraz|Alcatraz]] 03:09, 26 June 2009 (UTC)<br /> <br /> : I'd be of the opinion that it is cheesy, but don't object to keeping it around, at least till something particularly new happens in nano-land :) --[[User:Rednaxela|Rednaxela]] 04:26, 26 June 2009 (UTC)<br /> <br /> :: It's extremely cheesy an exploitive of a loophole in the codesize tool. Yet, I'm having some real fun with it right now (and this game is supposed to be fun! :). I literally believe I can get this bot as a top 10 in the micro competition as a nano. That's something that hasn't been done since just after we decided on weight classes. Right now, I'm still crunching a rather exhasutive set of numbers for firepower and movement types. Once that's done, I'll grab the numbers and give it a test run to see where it stands. Good chance it will go in tonight. --[[User:Miked0801|Miked0801]] 05:15, 26 June 2009 (UTC)<br /> <br /> ::: Well, I wouldn't call it &quot;exploitive of a loophole in the codesize tool&quot; exactly (unless someone makes a highly capable interpereter within nano size), since such preloading of data specific to certain bots is also cheesy for megabots. I think what's cheesey most fundumentally, is when a bot that looks up the enemy on a preloaded table based on bot names regardless of codesize. --[[User:Rednaxela|Rednaxela]] 13:11, 26 June 2009 (UTC)<br /> <br /> ::: I for one don't like this though, but it is acceptable for me. Unless, like Rednaxela, someone make a good enough nano-size compiler and fit DrussGT into nano. I'll not object, but I do think that when you fully tuned this robot to the top and have no more idea, you should retire this robot. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 13:30, 26 June 2009 (UTC)<br /> <br /> ::: Of course I agree that preloading data is kinda cheesy, but I think everyone understands that LBB is of a different ilk than other NanoBots. It's cool seeing how far you can go with it. To be honest, I think even hand-tuned segmentations are similar to pre-loading: with a different rumble population, different tunings would surely work better. We all take the rumble population into account when we write our bots; pre-loading is just a more explicit way of doing so. --[[User:Voidious|Voidious]] 14:10, 26 June 2009 (UTC)<br /> <br /> ::: Yep, it's cool to see how far LBB can go indeed. It is true that we all build our bots in way that considers the rumble population, but I don't think pre-loading itself is the cheesy thing. For one thing, I wouldn't consider it cheesy at all, if a GF gun preloads with the average data of a bunch of rumble bots, until it's learned enough about the specific enemy (hint, hint). I think tying pre-loaded data to a specific bot name is where the 'cheese' begins, but more general pre-loaded data is simply prudant rather than cheesy. --[[User:Rednaxela|Rednaxela]] 14:34, 26 June 2009 (UTC)<br /> <br /> ::: Personally, I think the only issue here is that pre-loading is used to get around the size class limits. A bot that saves its own data is fine by me, whether it's general or specific -- the 200k limit restricts how much you can really store anyway. LBB is a novel concept, but it would be disappointing to see it inspire a new generation of string table nanos/micros/minis. Now if you could make a nano that ''generates'' its own string tables, that would be really cool. You still have a few bytes left, right? ;) --[[User:Darkcanuck|Darkcanuck]] 15:02, 26 June 2009 (UTC)<br /> <br /> == AceSurf ==<br /> <br /> I noticed you make not of AceSurf being a problem. One possible solution (if you can fit it into the codesize) that would probably work well, would be having a special code in your data that says &quot;Aim at the last GF it went to&quot;. I'm kind of thinking that would probably eat too much codesize... but I think that's probably the simplest thing that could be done with the likes of AceSurf, besides random targeting anyway. --[[User:Rednaxela|Rednaxela]] 16:00, 20 June 2009 (UTC)<br /> <br /> : I'm not too worried. This bot just hit the 1900 club - the first ever in nanoland to do this. This is with untuned tables for 1/2 the bots. I will take a closer look at ace.surf results though and possibly setup alternating guess factors at every 40 pixels. This has been the best way recently to smash wave bots as it is nearly the same as 2 different guess factors every few shots. Wow I proud of this bot. I might be able to get it to the 2000 club when all is said and done. It just needs another 1000 percentage basis points or so. Plus, right after this bot was released, I figured out a way to better hit stop'n'go's without reducing accuracy against simpler bots who just get stuck. Next release will be fun! --[[User:Miked0801|Miked0801]] 16:06, 20 June 2009 (UTC)<br /> <br /> :: IIRC, The club score is base on ELO, not Glicko-2. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 16:13, 20 June 2009 (UTC)<br /> ::: then [[Toorkild]] isn't in the 2k club. I was pretty sure it was the Glicko. But, it all may be mute. I just realized how few battles it has run - only about 1 per bot. I'll therefore wait a bit before posting anything further on that :) --[[User:Miked0801|Miked0801]] 16:17, 20 June 2009 (UTC)<br /> ::: We're in a weird position with the clubs because it was based on ELO on the old server. ELO on Darkcanuck's server is way lower than it was on the old server, and Glicko-2 is a bit higher -- at least in MegaBot and MiniBot 1v1. As a point of reference, before the old RR server hit a few months of non-stop upwards drift, Dookious was about 2130 and Komarious was about 2085 in mini (prolly a few points higher now). Nevertheless, it's still easy to compare your bot to the competition, arbitrary rating systems aside. =) --[[User:Voidious|Voidious]] 16:26, 20 June 2009 (UTC)<br /> :::: The new server originally matched the old one, but ELO has drifted steadily downwards in the past few months. Why, I don't know. In late 2008, Glicko2 and ELO were in the same range, but now they're quite different. Maybe it's all the recent activity, plus some long-standing bots were removed earlier this year too. In any case, ELO is a relative ranking system so it's the difference between the scores that matters, not the absolute values. But it does leave the ELO clubs in a funny position. --[[User:Darkcanuck|Darkcanuck]] 17:34, 20 June 2009 (UTC)<br /> <br /> <br /> == Fuatisha==<br /> Well, it's nice to see that my nano is giving you so much trouble! Would you happen to have any idea why LBB seems to be having more trouble with it than other adaptive movement nanos? Of course, I wouldn't just be trying to figure out the best things to tweak in it......--[[User:CrazyBassoonist|CrazyBassoonist]] 03:34, 14 February 2010 (UTC)<br /> <br /> It's a number of things:<br /> * It really doesn't have a weakness in its good at any distance I can exploit. [[Moebius]] had a weakness at 260. <br /> * It's movement is adaptive - my gun is not. Plus it has a Very flat movement profile.<br /> * It's gun is just really, really good.<br /> * The opening stop/go movement has a signifigantly different GF profile than its later movements meaning I have to give up hit percentage later to get it out of its opening gambit.<br /> Basically, it is a better overall fighting bot than [[NeophytePattern]] and [[Moebius]], but does worse against weaker bots. If you were to tune anything, tune agaist the masses and you'll probably get #2 (and help me!) :) --[[User:Miked0801|Miked0801]] 05:27, 14 February 2010 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=User_talk:Bwbaugh&diff=19499 2011-06-08T15:31:51Z

<p>Miked0801: Wow!!!</p> <hr /> <div>== RoboRumble ==<br /> <br /> '''Question: Number of Client Instances'''<br /> <br /> If I have computers that are multicore (some dual some quad), is there a way to safely run multiple instances of the RoboRumble client without causing skipped turns? Would I need to set the affinity of each instance to separate CPUs? I'm a bit new to this, and my parallel computing class doesn't start until the Fall. =) --[[User:Bwbaugh|bwbaugh]] 10:05, 8 June 2011 (UTC)<br /> <br /> Welcome to the wiki, glad you are contributing to the rumble =) If you're worried about causing skipped turns first open up robocode and reset the CPU constant, then close robocode and open up the config/robocode.properties file with notepad. Manually increase the CPU constant there to something you feel would account for anything like cache thrashing, possible external logins etc (I'd say just double it...) and save the file. Make sure you run each instance of roborumble from a different install, otherwise there will be issues with all of them saving to or uploading from the same file concurrently. Hope this helps! --[[User:Skilgannon|Skilgannon]] 10:28, 8 June 2011 (UTC)<br /> <br /> Personally, in addition to boosting the CPU constant, I prefer to run one fewer robocode instance than the number of CPUs on the system. This is because robocode seems to use some processor power outside it's handling it a separate thread than the robots run in (perhaps the Java GC? Perhaps part of the robocode engine itself? I'm not sure). About setting affinity, I doubt it would make much difference. Robocode is already alternating between running each robot, which I'd expect to limit how long-lived things are in the cpu cache, which I'd expect to mean that affinity probably wouldn't help much. That's just a guess though, it's not like I've tested. --[[User:Rednaxela|Rednaxela]] 13:57, 8 June 2011 (UTC)<br /> <br /> Agree with everything these guys said. About the affinity, I think this may depend on OS. I know on Mac, and I think on Linux, it will just work running one instance per core. I recall some people on Windows (XP days?) having to set affinity. FYI, [[RoboResearch]] is a great tool to leverage multiple cores for development. And yes, welcome and great to see you already contributing to the rumble. :-) Good luck! --[[User:Voidious|Voidious]] 14:33, 8 June 2011 (UTC)<br /> <br /> I personally used to run two RoboRumble clients (1v1 and melee) on Dual Core machine (Core 2 Duo P8400 2.26GHz) with about 1.1x increased cpu constants without trouble (I've checked the result on the server). I have also run two RoboRumble clients (1v1 and melee) on my Core 2 Quad 2.4GHz server without increased cpu constants without any trouble too. (but my server do esnot do anything other than consuming power when not explicitly used, it host my class' online judge system) --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 14:40, 8 June 2011 (UTC)<br /> <br /> Thank you all for the replies and information! I went ahead and configured 40 of my workstations to run 2 instances of RoboRumble each. Unfortunately, I noticed that after processing the battles, the upload process was much slower than it was during the past two days. In addition, the web interface for the rumble server was very slow to respond. So, it appears that the rumble server can't accept that many connections / uploads at once. I therefore reduced the number of stations running from 40 to 22, still running 2 instances each, and may reduce it further if it still seems to be overloading the rumble server. I wonder if there is a way to scale up the server to accept more simultaneous uploads... --[[User:Bwbaugh|bwbaugh]] 15:20, 8 June 2011 (UTC)<br /> <br /> Holy cow. In one or two nights, you've managed to contribute more power than just about everyone one else this year. Wow and thanks! --[[User:Miked0801|Miked0801]] 15:31, 8 June 2011 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=RoboRumble/Participants&diff=19485 2011-06-08T08:36:21Z

<p>Miked0801: new lbb</p> <hr /> <div>{{:RoboRumble/Navigation}}<br /> <br /> ----<br /> Just add your bot name ('''as appears in the Robocode selector after packaging''', so including versionnumber) and the RobocodeRepository id number separated by &quot;,&quot; (there must be no space after the comma).&lt;br&gt; <br /> Please, make sure your bot is not in the list before adding it, and delete the old version if you are adding a new one.<br /> &lt;br&gt;<br /> The list is in '''alphabetical''' order. Add your bot in the right slot.<br /> <br /> ----<br /> &lt;pre&gt;<br /> ab.DengerousRoBatra 1.3,http://www.robocoderepository.com/BotFiles/3664/ab.DengerousRoBatra_1.3.jar<br /> abc.Shadow 3.83c,http://robocode.aclsi.pt/abc.Shadow_3.83c.jar<br /> abc.tron3.Tron 3.11,http://www.robocoderepository.com/BotFiles/2205/abc.tron3.Tron_3.11.jar<br /> abc.Tron 2.02,http://www.robocoderepository.com/BotFiles/241/abc.Tron_2.02.jar<br /> abud.ThirdRobo 1.0,http://www.robocoderepository.com/BotFiles/2479/abud.ThirdRobo_1.0.jar<br /> ad.last.Bottom 1.0,http://www.robocoderepository.com/BotFiles/1876/ad.last.Bottom_1.0.jar<br /> ad.Quest 0.10,http://www.robocoderepository.com/BotFiles/1846/ad.Quest_0.10.jar<br /> adt.Ar1 2.1,http://www.robocoderepository.com/BotFiles/2254/adt.Ar1_2.1.jar<br /> adt.Ar2 1.0,http://www.robocoderepository.com/BotFiles/2303/adt.Ar2_1.0.jar<br /> ag.Gir 0.99,http://www.robocoderepository.com/BotFiles/3065/ag.Gir_0.99.jar<br /> agd.Mooserwirt2 2.7,http://www.glyndavies.org/robocode/agd.Mooserwirt2.jar<br /> ags.Glacier 0.2.7,http://rednaxela-robocode.dyndns.org/data/robots/ags.Glacier_0.2.7.jar<br /> ags.micro.Carpet 1.1,http://rednaxela-robocode.dyndns.org/data/robots/ags.micro.Carpet_1.1.jar<br /> ags.Midboss 1s,http://rednaxela-robocode.dyndns.org/data/robots/ags.Midboss_1s.jar<br /> ags.polished.PolishedRuby 1,http://rednaxela-robocode.dyndns.org/data/robots/ags.polished.PolishedRuby_1.jar<br /> ags.rougedc.RougeDC willow,http://rednaxela-robocode.dyndns.org/data/robots/ags.rougedc.RougeDC_willow.jar<br /> ahf.Acero 1.0,http://www.robocoderepository.com/BotFiles/2151/ahf.Acero_1.0.jar<br /> ahf.NanoAndrew .4,http://www.robocoderepository.com/BotFiles/2002/ahf.NanoAndrew_.4.jar<br /> ahf.r2d2.R2d2 0.86,http://www.robocoderepository.com/BotFiles/2035/ahf.r2d2.R2d2_0.86.jar<br /> ahr.ice.Ice 1.0,http://robocoderepository.com/BotFiles/3966/ahr.ice.Ice_1.0.jar<br /> ahr.ice.Ice 1.0.1,http://robocoderepository.com/BotFiles/3978/ahr.ice.Ice_1.0.1.jar<br /> AIR.iRobot 1.0,http://www.robocoderepository.com/BotFiles/3205/AIR.iRobot_1.0.jar<br /> ak.Fermat 2.0,http://www.robocoderepository.com/BotFiles/799/ak.Fermat_2.0.jar<br /> alex.Diabolo5 1.1,http://darkcanuck.net/rumble/robots/alex.Diabolo5_1.1.jar<br /> alk.lap.LoudAndProud 2.23,http://www.robocoderepository.com/BotFiles/3601/alk.lap.LoudAndProud_2.23.jar<br /> am.Miedzix 2.0,http://www.robocoderepository.com/BotFiles/3383/am.Miedzix_2.0.jar<br /> am.Miedzix 3.0,http://darkcanuck.net/rumble/robots/am.Miedzix_3.0.jar<br /> amarok.Rookie 1.1,http://www.robocoderepository.com/BotFiles/422/amarok.Rookie_1.1.jar<br /> amk.ChumbaMini 0.2,http://www.robocoderepository.com/BotFiles/2655/amk.ChumbaMini_0.2.jar<br /> amk.ChumbaWumba 0.3,http://www.robocoderepository.com/BotFiles/2646/amk.ChumbaWumba_0.3.jar<br /> amk.jointstrike.JointStrike 0.2,http://www.robocoderepository.com/BotFiles/2597/amk.jointstrike.JointStrike_0.2.jar<br /> amk.ShizzleStiX.ShizzleStiX 0.6,http://www.robocoderepository.com/BotFiles/2603/amk.ShizzleStiX.ShizzleStiX_0.6.jar<br /> amk.superstrike.SuperStrike 0.3,http://www.robocoderepository.com/BotFiles/2600/amk.superstrike.SuperStrike_0.3.jar<br /> amk.Punbot.Punbot 0.01,http://www.robocoderepository.com/BotFiles/2604/amk.Punbot.Punbot_0.01.jar<br /> ao.T100 0.9,http://www.robocoderepository.com/BotFiles/3385/ao.T100_0.9.jar<br /> ap.Frederick 1.1,http://darkcanuck.net/rumble/robots/ap.Frederick_1.1.jar<br /> apollokidd.ApolloKidd 0.9,http://www.robocoderepository.com/BotFiles/321/apollokidd.ApolloKidd_0.9.jar<br /> apv.Aspid 1.7,http://www.robocoderepository.com/BotFiles/1412/apv.Aspid_1.7.jar<br /> apv.AspidReloaded 0.6,http://www.robocoderepository.com/BotFiles/1985/apv.AspidReloaded_0.6.jar<br /> apv.LauLectrik 1.2,http://www.robocoderepository.com/BotFiles/1300/apv.LauLectrik_1.2.jar<br /> apv.MicroAspid 1.8,http://www.robocoderepository.com/BotFiles/2519/apv.MicroAspid_1.8.jar<br /> apv.NanoLauLectrik 1.0,http://www.robocoderepository.com/BotFiles/1399/apv.NanoLauLectrik_1.0.jar<br /> apv.NanoLauLectrikTheCannibal 1.1,http://www.robocoderepository.com/BotFiles/2147/apv.NanoLauLectrikTheCannibal_1.1.jar<br /> apv.ScruchiPu 1.0,http://www.robocoderepository.com/BotFiles/1367/apv.ScruchiPu_1.0.jar<br /> apv.test.Virus 0.6.1,http://www.robocoderepository.com/BotFiles/2645/apv.test.Virus_0.6.1.jar<br /> apv.TheBrainPi 0.5fix,http://darkcanuck.net/rumble/robots/apv.TheBrainPi_0.5fix.jar<br /> ar.horizon.Horizon 1.2.2,http://www.robocoderepository.com/BotFiles/3286/ar.horizon.Horizon_1.2.2.jar<br /> ar.QuantumChromodynamics 1.2.1,http://www.robocoderepository.com/BotFiles/3220/ar.QuantumChromodynamics_1.2.1.jar<br /> ar.TheoryOfEverything 1.2.1,http://www.robocoderepository.com/BotFiles/3221/ar.TheoryOfEverything_1.2.1.jar<br /> ara.Shera 0.88,http://www.robocoderepository.com/BotFiles/1050/ara.Shera_0.88.jar<br /> areb.Union 1.06,http://www.robocoderepository.com/BotFiles/2893/areb.Union_1.06.jar<br /> arthord.micro.Apoptygma 0.4,http://www.robocoderepository.com/BotFiles/1688/arthord.micro.Apoptygma_0.4.jar<br /> arthord.micro.Muffin 0.6.1,http://www.robocoderepository.com/BotFiles/1963/arthord.micro.Muffin_0.6.1.jar<br /> arthord.KostyaTszyu Beta2,http://www.robocoderepository.com/BotFiles/2322/arthord.KostyaTszyu_Beta2.jar<br /> arthord.MannyPacquiao Delta2,http://scoutery.awardspace.com/arthord.MannyPacquiao_Delta2.jar<br /> arthord.NanoSatan Mu,http://www.robocoderepository.com/BotFiles/2157/arthord.NanoSatan_Mu.jar<br /> arthord.NanoSatanMelee Beta,http://www.robocoderepository.com/BotFiles/2088/arthord.NanoSatanMelee_Beta.jar<br /> ary.micro.Weak 1.2,http://www.robocoderepository.com/BotFiles/3433/ary.micro.Weak_1.2.jar<br /> ary.mini.Nimi 1.0,http://www.robocoderepository.com/BotFiles/3397/ary.mini.Nimi_1.0.jar<br /> ary.nano.AceSurf 1.2,http://www.robocoderepository.com/BotFiles/3352/ary.nano.AceSurf_1.2.jar<br /> ary.nano.ColorNanoP 1.1,http://www.robocoderepository.com/BotFiles/3629/ary.nano.ColorNanoP_1.1.jar<br /> ary.Crisis 1.0,http://www.robocoderepository.com/BotFiles/3495/ary.Crisis_1.0.jar<br /> ary.Help 1.0,http://darkcanuck.net/rumble/robots/ary.Help_1.0.jar<br /> ary.FourWD 1.3d,http://darkcanuck.net/rumble/robots/ary.FourWD_1.3d.jar<br /> ary.SMG 1.01,http://ary-robocode.110mb.com/ary.SMG_1.01.jar<br /> as.xbots 1.0,http://darkcanuck.net/rumble/robots/as.xbots_1.0.jar<br /> asd.Cthulhu 1.2,http://darkcanuck.net/rumble/robots/asd.Cthulhu_1.2.jar<br /> asm.Statistas 0.1,http://www.robocoderepository.com/BotFiles/1989/asm.Statistas_0.1.jar<br /> aw.GreatWolf 2.0,https://sites.google.com/site/awusa94/robocode/aw.GreatWolf_2.0.jar<br /> awesomeness.Elite 1.0,http://robocoderepository.com/BotFiles/3597/awesomeness.Elite.jar<br /> awl.Locutus 1.0,3844<br /> axeBots.HataMoto 3.09,http://www.robocoderepository.com/BotFiles/1655/axeBots.HataMoto_3.09.jar<br /> axeBots.Musashi 2.18,http://www.robocoderepository.com/BotFiles/1759/axeBots.Musashi_2.18.jar<br /> axeBots.Okami 1.04,http://www.robocoderepository.com/BotFiles/2016/axeBots.Okami_1.04.jar<br /> axeBots.SilverSurfer 2.53.33fix,http://rednaxela-robocode.dyndns.org/data/robots/axeBots.SilverSurfer_2.53.33fix.jar<br /> ayk.WallHugger 1.0,https://sites.google.com/site/khanguyprojects/file-cabinet/ayk.WallHugger_1.0.jar<br /> baal.nano.N 1.42,http://webpages.charter.net/eleeleth/Robots/baal.nano.N_1.42.jar<br /> banshee.mini.Nexus6 0.2.0,http://www.robocoderepository.com/BotFiles/3467/banshee.mini.Nexus6_0.2.0.jar<br /> banshee.micro.Nexus6 0.3.0,http://www.robocoderepository.com/BotFiles/3473/banshee.micro.Nexus6_0.3.0.jar<br /> bayen.nano.Squirrel 0.2,http://www.freewebs.com/bayen/files/bayen.nano.Squirrel_0.2.jar<br /> bayen.nut.Squirrel 1.621,http://darkcanuck.net/rumble/robots/bayen.nut.Squirrel_1.621.jar<br /> bayen.UbaMicro 1.4,http://www.robocoderepository.com/BotFiles/2830/bayen.UbaMicro_1.4.jar<br /> bayen.UbaRamLT 1.0,http://www.robocoderepository.com/BotFiles/2868/bayen.UbaRamLT_1.0.jar<br /> bbo.RamboT 0.3,http://www.robocoderepository.com/BotFiles/2210/bbo.RamboT_0.3.jar<br /> bbo.TheRoof 1.4.3,http://www.robocoderepository.com/BotFiles/2179/bbo.TheRoof_1.4.3.jar<br /> Bemo.Sweet30 1.6.1,http://www.stg-volleyball.de/images/Bemo.Sweet30_1.6.1.jar<br /> benhorner.PureAggression 0.2.6,http://www.robocoderepository.com/BotFiles/3421/benhorner.PureAggression_0.2.6.jar<br /> bh.PencilRain 0.01,http://www.robocoderepository.com/BotFiles/3670/bh.PencilRain-0.01.jar<br /> bigpete.Stewie 1.0,http://www.robocoderepository.com/BotFiles/2927/bigpete.Stewie_1.0.jar<br /> bing2.Melody 1.3.1,http://www.ccs.neu.edu/home/bing/robocode/bing2.Melody_1.3.1.jar<br /> bjl.LoneDragon 0.5,http://www.robocoderepository.com/BotFiles/1929/bjl.LoneDragon_0.5.jar<br /> bndl.LostLion 1.2,http://www.robocoderepository.com/BotFiles/1033/bndl.LostLion_1.2.jar<br /> bons.NanoStalker 1.2,http://www.robocoderepository.com/BotFiles/1179/bons.NanoStalker_1.2.jar<br /> bp.Kuma 1.0,http://www.robocoderepository.com/BotFiles/3238/bp.Kuma_1.0.jar<br /> braaropolis.Abot 1.0,http://darkcanuck.net/rumble/robots/braaropolis.Abot_1.0.jar<br /> brainfade.Fallen 0.63,http://www.robocoderepository.com/BotFiles/2250/brainfade.Fallen_0.63.jar<br /> brainfade.melee.Dusk 0.44,http://www.robocoderepository.com/BotFiles/2518/brainfade.melee.Dusk_0.44.jar<br /> buba.Archivist 0.1,http://www.robocoderepository.com/BotFiles/3899/buba.Archivist_0.1.jar<br /> buba.Buba 0.3,http://www.robocoderepository.com/BotFiles/3896/buba.Buba_0.3.jar<br /> bvh.fnr.Fenrir 0.36l,http://www.robocoderepository.com/BotFiles/1428/bvh.fnr.Fenrir_0.36l.jar<br /> bvh.frg.Friga 0.112dev,http://darkcanuck.net/rumble/robots/bvh.frg.Friga_0.112dev.jar<br /> bvh.fry.Freya 0.82,http://darkcanuck.net/rumble/robots/bvh.fry.Freya_0.82.jar<br /> bvh.hdr.Hodur 0.4,http://www.robocoderepository.com/BotFiles/1954/bvh.hdr.Hodur_0.4.jar<br /> bvh.loki.Loki 0.5,http://www.robocoderepository.com/BotFiles/885/bvh.loki.Loki_0.5.jar<br /> bvh.micro.Freya 0.3,http://www.robocoderepository.com/BotFiles/2815/bvh.micro.Freya_0.3.jar<br /> bvh.micro.Svadilfari 0.2,http://www.robocoderepository.com/BotFiles/1086/bvh.micro.Svadilfari_0.2.jar<br /> bvh.mini.Fenrir 0.39,http://www.robocoderepository.com/BotFiles/1429/bvh.mini.Fenrir_0.39.jar<br /> bvh.mini.Freya 0.55,http://darkcanuck.net/rumble/robots/bvh.mini.Freya_0.55.jar<br /> bvh.mini.Mjolnir 0.3,http://www.robocoderepository.com/BotFiles/2220/bvh.mini.Mjolnir_0.3.jar<br /> bvh.mini.Wodan 0.50,http://www.robocoderepository.com/BotFiles/2064/bvh.mini.Wodan_0.50.jar<br /> bvh.tyr.Tyr 1.74,http://www.robocoderepository.com/BotFiles/886/bvh.tyr.Tyr_1.74.jar<br /> bwbaugh.nano.Tirunculus 0.0.0,http://files.brianbaugh.com/robocode/bwbaugh.nano.Tirunculus_0.0.0.jar<br /> bzdp.BoxCar 2.0,http://www.robocoderepository.com/BotFiles/3703/bzdp.BoxCar_2.0.jar<br /> bzdp.Pansy 2.1,http://www.robocoderepository.com/BotFiles/3726/bzdp.Pansy_2.1.jar<br /> caimano.Furia_Ceca 0.22,http://www.robocoderepository.com/BotFiles/1843/caimano.Furia_Ceca_0.22.jar<br /> cbot.agile.Nibbler 0.2,http://www.robocoderepository.com/BotFiles/1537/cbot.agile.Nibbler_0.2.jar<br /> cbot.cbot.CBot 0.8,http://www.robocoderepository.com/BotFiles/1375/cbot.cbot.CBot_0.8.jar<br /> cf.mini.Chiva 1.0,http://www.robocoderepository.com/BotFiles/2331/cf.mini.Chiva_1.0.jar<br /> cf.OldMan.OldManXP 0.1,http://www.robocoderepository.com/BotFiles/1968/cf.OldMan.OldManXP_0.1.jar<br /> cf.proto.Shiva 2.2,http://www.robocoderepository.com/BotFiles/2409/cf.proto.Shiva_2.2.jar<br /> cf.star.Star2 1.23,http://www.robocoderepository.com/BotFiles/2255/cf.star.Star2_1.23.jar<br /> ch.rhj.rbc.RHJ1 1.0,http://www.robocoderepository.com/BotFiles/1879/ch.rhj.rbc.RHJ1_1.0.jar<br /> CharlieN.Omega.Omega 1.03,http://www.robocoderepository.com/BotFiles/3503/CharlieN.Omega.Omega_1.03.jar<br /> chase.c.Wristwatch 1.0,http://file.csdgn.org/robocode/chase.c.Wristwatch_1.0.jar<br /> chase.pm.Pytko 1.0,http://file.csdgn.org/robocode/chase.pm.Pytko_1.0.jar<br /> chase.s2.Genesis 1.1,http://file.csdgn.org/robocode/chase.s2.Genesis_1.1.jar<br /> chase.s2.Seraphim 2.0.9,http://file.csdgn.org/robocode/chase.s2.Seraphim_2.0.9.jar<br /> chickenfuego.UrChicken2 1.0,http://www.robocoderepository.com/BotFiles/3422/chickenfuego.UrChicken2_1.0.jar<br /> cjk.Merkava 0.1.1,http://www.robocoderepository.com/BotFiles/2637/cjk.Merkava_0.1.1.jar<br /> cjk.Merkava 0.2.0,http://www.robocoderepository.com/BotFiles/2640/cjk.Merkava_0.2.0.jar<br /> cjk.Merkava 0.3.0,http://darkcanuck.net/rumble/robots/cjk.Merkava_0.3.0.jar<br /> cjm.chalk.Chalk 2.6.Be,http://scatterbright.com/robots/cjm.chalk.Chalk_2.6.Be.jar<br /> cjm.Charo 1.1,http://scatterbright.com/robots/cjm.Charo_1.1.jar<br /> cjm.Che 1.2,http://www.robocoderepository.com/BotFiles/2703/cjm.Che_1.2.jar<br /> cjm.Chomsky 1.5,http://scatterbright.com/robots/cjm.Chomsky_1.5.jar<br /> codemojo.nano.Woot 1.0,http://darkcanuck.net/rumble/robots/codemojo.nano.Woot_1.0.jar<br /> cs.ExclusionNano 1.1,http://file.csdgn.org/robocode/cs.ExclusionNano_1.1.jar<br /> csm.NthGeneration 0.04,http://www.robocoderepository.com/BotFiles/1214/csm.NthGeneration_0.04.jar<br /> csp.Eagle 3.30,http://www.robocoderepository.com/BotFiles/2436/csp.Eagle_3.30.jar<br /> css.Delitioner 0.11,http://darkcanuck.net/rumble/robots/css.Delitioner_0.11.jar<br /> cx.BlestPain 1.41,http://www.robocoderepository.com/BotFiles/1671/cx.BlestPain_1.41.jar<br /> cx.CigaretBH 1.03,http://www.robocoderepository.com/BotFiles/1414/cx.CigaretBH_1.03.jar<br /> cx.Lacrimas 1.36,http://www.robocoderepository.com/BotFiles/1820/cx.Lacrimas_1.36.jar<br /> cx.micro.Blur 0.2,http://www.robocoderepository.com/BotFiles/2447/cx.micro.Blur_0.2.jar<br /> cx.micro.Smoke 0.96,http://www.robocoderepository.com/BotFiles/1037/cx.micro.Smoke_0.96.jar<br /> cx.micro.Spark 0.6,http://www.robocoderepository.com/BotFiles/1320/cx.micro.Spark_0.6.jar<br /> cx.mini.BlackSwans 0.60,http://www.robocoderepository.com/BotFiles/1158/cx.mini.BlackSwans_0.60.jar<br /> cx.mini.Cigaret 1.31,http://www.robocoderepository.com/BotFiles/1152/cx.mini.Cigaret_1.31.jar<br /> cx.mini.Nimrod 0.55,http://www.robocoderepository.com/BotFiles/1236/cx.mini.Nimrod_0.55.jar<br /> cx.nano.Smog 2.6,http://www.robocoderepository.com/BotFiles/1036/cx.nano.Smog_2.6.jar<br /> cx.Princess 1.0,http://www.robocoderepository.com/BotFiles/1343/cx.Princess_1.0.jar<br /> da.NewBGank 1.4,http://www.robocoderepository.com/BotFiles/3312/da.NewBGank_1.4.jar<br /> dam.MogBot 2.9,http://www.robocoderepository.com/BotFiles/555/dam.MogBot_2.9.jar<br /> dans.Cinnamon 1.2,http://www.robocoderepository.com/BotFiles/1976/dans.Cinnamon_1.2.jar<br /> darkcanuck.Gaff 1.50,http://darkcanuck.net/rumble/robots/darkcanuck.Gaff_1.50.jar<br /> darkcanuck.Holden 1.13a,http://darkcanuck.net/rumble/robots/darkcanuck.Holden_1.13a.jar<br /> darkcanuck.Pris 0.88,http://darkcanuck.net/rumble/robots/darkcanuck.Pris_0.88.jar<br /> davidalves.Firebird 0.25,http://davidalves.net/robocode/robots/davidalves.Firebird_0.25.jar<br /> davidalves.Phoenix 1.02,http://davidalves.net/robocode/robots/davidalves.Phoenix_1.02.jar<br /> davidalves.PhoenixOS 1.1,http://davidalves.net/robocode/robots/davidalves.PhoenixOS_1.1.jar<br /> davidalves.net.Duelist 0.1.6src,http://www.robocoderepository.com/BotFiles/1000/davidalves.net.Duelist_0.1.6src.jar<br /> davidalves.net.DuelistMicro 1.22,http://www.robocoderepository.com/BotFiles/1144/davidalves.net.DuelistMicro_1.22.jar<br /> davidalves.net.DuelistMicroMkII 1.1,http://www.robocoderepository.com/BotFiles/1281/davidalves.net.DuelistMicroMkII_1.1.jar<br /> davidalves.net.DuelistMini 1.1,http://www.robocoderepository.com/BotFiles/1181/davidalves.net.DuelistMini_1.1.jar<br /> davidalves.net.DuelistNano 1.0,http://www.robocoderepository.com/BotFiles/1272/davidalves.net.DuelistNano_1.0.jar<br /> dcs.Eater_of_Worlds 1.1.3-A,http://www.robocoderepository.com/BotFiles/2578/dcs.Eater_of_Worlds_1.1.3-A.jar<br /> dcs.Eater_of_Worlds_Mini 1.0,http://www.robocoderepository.com/BotFiles/2850/dcs.Eater_of_Worlds_Mini_1.0.jar<br /> dcs.PM.Eater_of_Worlds_PM 1.2,http://www.robocoderepository.com/BotFiles/2856/dcs.PM.Eater_of_Worlds_PM_1.2.jar<br /> de.erdega.robocode.Polyphemos 0.4,http://darkcanuck.net/rumble/robots/de.erdega.robocode.Polyphemos_0.4.jar<br /> deewiant.Anomaly 0.2,http://www.iki.fi/~deewiant/files/deewiant.Anomaly_0.2.jar<br /> deith.Czolgzilla 0.11,http://www.robocoderepository.com/BotFiles/3256/deith.Czolgzilla_0.11.jar<br /> demetrix.ForceMajeure 0.75,http://ever-rage.narod.ru/robowiki/demetrix.ForceMajeure_0.75.jar<br /> demetrix.nano.Neutrino 0.27,http://ever-rage.narod.ru/robowiki/demetrix.nano.Neutrino_0.27.jar<br /> demetrix.nano.SledgeHammer 0.22,http://ever-rage.narod.ru/robowiki/demetrix.nano.SledgeHammer_0.22.jar<br /> deo.CloudBot 1.3,http://robocoderepository.com/BotFiles/3644/deo.CloudBot_1.3.jar<br /> deo.FlowerBot 1.0,http://robocoderepository.com/BotFiles/3683/deo.FlowerBot_1.0.jar<br /> deo.virtual.RainbowBot 1.0,http://robocoderepository.com/BotFiles/3694/deo.virtual.RainbowBot_1.0.jar<br /> dft.Calliope 5.6,http://www.robocoderepository.com/BotFiles/237/dft.Calliope_5.6.jar<br /> dft.Cyanide 1.90,http://darkcanuck.net/rumble/robots/dft.Cyanide_1.90.jar<br /> dft.Cyprus 3.0,http://www.robocoderepository.com/BotFiles/377/dft.Cyprus_3.0.jar<br /> dft.Freddie 1.32,http://darkcanuck.net/rumble/robots/dft.Freddie_1.32.jar<br /> dft.Guppy 1.0,http://darkcanuck.net/rumble/robots/dft.Guppy_1.0.jar<br /> dft.Immortal 1.40,http://darkcanuck.net/rumble/robots/dft.Immortal_1.40.jar<br /> dft.Krazy 1.5,http://www.robocoderepository.com/BotFiles/2099/dft.Krazy_1.5.jar<br /> dft.Virgin 1.25,http://www.robocoderepository.com/BotFiles/1447/dft.Virgin_1.25.jar<br /> dggp.haiku.gpBot_0 1.1,http://www.robocoderepository.com/BotFiles/3154/dggp.haiku.gpBot_0_1.1.jar<br /> dittman.BlindSquirl Retired,http://home.comcast.net/~kokyunage/robocode/ugluk/dittman.BlindSquirl_Retired.jar<br /> djc.Aardvark 0.3.6,http://www.robocoderepository.com/BotFiles/652/djc.Aardvark_0.3.6.jar<br /> djdjdj.NanoSkunk10 1.0,http://davidjoerg.com/robocode/djdjdj.NanoSkunk10_1.0.jar<br /> dk.stable.Gorgatron 1.1,http://www.robocoderepository.com/BotFiles/2112/dk.stable.Gorgatron_1.1.jar<br /> dks.MicroDanMK2 1.0,http://darkcanuck.net/rumble/robots/dks.MicroDanMK2_1.0.jar<br /> DM.Capriite 3.7.2,http://www.robocoderepository.com/BotFiles/2989/DM.Capriite_3.7.2.jar<br /> DM.Chicken 4.0,http://www.robocoderepository.com/BotFiles/3020/DM.Chicken_4.0.jar<br /> DM.Mijit .3,http://www.robocoderepository.com/BotFiles/3043/DM.Mijit_.3.jar<br /> dmp.micro.Aurora 1.41,http://www.robocoderepository.com/BotFiles/853/dmp.micro.Aurora_1.41.jar<br /> dmp.nano.Eve 3.41,http://www.robocoderepository.com/BotFiles/842/dmp.nano.Eve_3.41.jar<br /> donjezza.Jezza 1.0,http://www.robocoderepository.com/BotFiles/3385/donjezza.Jezza_1.0.jar<br /> donjezza.Muncho 1.0,http://www.robocoderepository.com/BotFiles/3384/donjezza.Muncho_1.0.jar<br /> drd.Dreadknoght 0.9,http://www.robocoderepository.com/BotFiles/3835/drd.Dreadknoght_0.9.jar<br /> drm.CobraBora 1.12,http://www.robocoderepository.com/BotFiles/1146/drm.CobraBora_1.12.jar<br /> drm.Magazine 0.39,http://www.robocoderepository.com/BotFiles/989/drm.Magazine_0.39.jar<br /> ds.OoV4 0.3b,http://www.robocoderepository.com/BotFiles/2851/ds.OoV4_0.3b.jar<br /> dsw.StaticD 1.0,http://darkcanuck.net/rumble/robots/dsw.StaticD_1.0.jar<br /> dsx724.VSAB_EP3a 1.0,http://darkcanuck.net/rumble/robots/dsx724.VSAB_EP3a_1.0.jar<br /> dsx724.VSAB_EP3_ATR 1.1,http://www.robocoderepository.com/BotFiles/3432/dsx724.VSAB_EP3_ATR_1.1.jar<br /> DTF.Kludgy 1.2b,http://www.robocoderepository.com/BotFiles/4041/DTF.Kludgy_1.2b.jar<br /> dukie.Ambassador 1.0,http://www.robocoderepository.com/BotFiles/2845/dukie.Ambassador_1.0.jar<br /> dummy.micro.HummingBird 2.14,http://www.robocoderepository.com/BotFiles/369/dummy.micro.HummingBird_2.14.jar<br /> dummy.micro.Sparrow 2.5,http://www.robocoderepository.com/BotFiles/484/dummy.micro.Sparrow_2.5.jar<br /> dummy.mini.Parakeet 2.40,http://www.robocoderepository.com/BotFiles/400/dummy.mini.Parakeet_2.40.jar<br /> dvogon.GangBang 1.0,http://www.robocoderepository.com/BotFiles/3193/dvogon.GangBang_1.0.jar<br /> dy.LevelOne 2.0,http://www.robocoderepository.com/BotFiles/3452/dy.LevelOne_2.0.jar<br /> dz.Caedo 1.4,http://www.robocoderepository.com/BotFiles/1044/dz.Caedo_1.4.jar<br /> dz.GalbaMicro 0.11,http://www.robocoderepository.com/BotFiles/2482/dz.GalbaMicro_0.11.jar<br /> dz.GalbaMini 0.121,http://darkcanuck.net/rumble/robots/dz.GalbaMini_0.121.jar<br /> dz.MostlyHarmlessNano 2.1,http://www.robocoderepository.com/BotFiles/2166/dz.MostlyHarmlessNano_2.1.jar<br /> dz.OthoMicro 0.12,http://www.robocoderepository.com/BotFiles/2198/dz.OthoMicro_0.12.jar<br /> dz.OthoMini 0.15,http://www.robocoderepository.com/BotFiles/2221/dz.OthoMini_0.15.jar<br /> eat.HumblePieLite 1.0,http://www.robocoderepository.com/BotFiles/1088/eat.HumblePieLite_1.0.jar<br /> ebo.Sparse 0.02,http://www.4geeks.de/files/ebo.Sparse_0.02.jar<br /> ebo.Tahoe 1.1.79,http://www.4geeks.de/files/ebo.Tahoe_1.1.79.jar<br /> EE.LittleBig 1.0,http://www.robocoderepository.com/BotFiles/4009/EE.LittleBig_1.0.jar<br /> EFD.AdvancedEFD 0.4.5a,http://sites.google.com/site/jannisbeese/robots/EFD.AdvancedEFD_0.4.5a.jar<br /> el.Attackr 0.1,http://darkcanuck.net/rumble/robots/el.Attackr_0.1.jar<br /> el.JumpShoot 0.2,http://www.robocoderepository.com/BotFiles/3360/el.JumpShoot_0.2.jar<br /> el33t.EL33tGangstarr2 2.0,http://www.robocoderepository.com/BotFiles/2069/el33t.EL33tGangstarr2_2.0.jar<br /> eld.Hmm 1.0,http://darkcanuck.net/rumble/robots/eld.Hmm_1.0.jar<br /> element.Earth 1.1,http://www.robocoderepository.com/BotFiles/3587/element.Earth_1.1.jar<br /> elloco.Flower 0.1r1,http://www.robocoderepository.com/BotFiles/3242/elloco.Flower_0.1r1.jar<br /> elloco.Kabuto 0.2r,http://www.robocoderepository.com/BotFiles/3229/elloco.Kabuto_0.2r.jar<br /> elvbot.ElverionBot 0.3,http://www.robocoderepository.com/BotFiles/3541/elvbot.ElverionBot_0.3.jar<br /> emp.Yngwie 1.11,http://www.robocoderepository.com/BotFiles/1928/emp.Yngwie_1.11.jar<br /> erdnis.Rover 0.3,http://www.free-games-fun.com/erdnis.Rover_0.3.jar<br /> eskimo.micro.Echo 0.1,http://robocoderepository.com/BotFiles/3969/eskimo.micro.Echo_0.1.jar<br /> et.Predator 1.8,http://www.robocoderepository.com/BotFiles/668/et.Predator_1.8.jar<br /> ethdsy.Malacka 2.4,http://www.robocoderepository.com/BotFiles/1159/ethdsy.Malacka_2.4.jar<br /> evd.X1 0.01,http://www.robocoderepository.com/BotFiles/3503/evd.X1_0.01.jar<br /> exauge.GateKeeper 1.1.121g,http://www.robocoderepository.com/BotFiles/3928/exauge.GateKeeper_1.1.121g.jar<br /> exauge.LemonDrop 1.6.130,http://www.robocoderepository.com/BotFiles/3911/exauge.LemonDrop_1.6.130.jar<br /> exauge.Leopard 1.1.019,http://www.robocoderepository.com/BotFiles/3917/exauge.Leopard_1.1.019.jar<br /> fala.robocode.FalaRobot 1.0,http://www.robocoderepository.com/BotFiles/3474/fala.robocode.FalaRobot_1.0.jar<br /> fcr.First 1.0,http://www.robocoderepository.com/BotFiles/3362/fcr.First_1.0.jar<br /> Fenix.FenixTrack 1.0,http://www.robocoderepository.com/BotFiles/1627/Fenix.FenixTrack_1.0.jar<br /> florent.FloatingTadpole 1.2.6,http://www.robocoderepository.com/BotFiles/2675/florent.FloatingTadpole_1.2.6.jar<br /> florent.small.LittleAngel 1.8,http://www.robocoderepository.com/BotFiles/2917/florent.small.LittleAngel_1.8.jar<br /> florent.test.Toad 0.14t,http://wesley3.free.fr/florent.test.Toad_0.14t.jar<br /> florent.XSeries.X2 0.17,http://wesley3.free.fr/florent.XSeries.X2_0.17.jar<br /> fm.claire 1.7,http://www.robocoderepository.com/BotFiles/2251/fm.claire_1.7.jar<br /> fm.mammillarias 1.3,http://www.robocoderepository.com/BotFiles/2238/fm.mammillarias_1.3.jar<br /> fnc.bandit.Bandit 5.2.0,http://www.robocoderepository.com/BotFiles/2155/fnc.bandit.Bandit_5.2.0.jar<br /> fnc.bandit2002.Bandit2002 4.0.2,http://www.robocoderepository.com/BotFiles/2202/fnc.bandit2002.Bandit2002_4.0.2.jar<br /> frag.FragBot 1.0,http://darkcanuck.net/rumble/robots/frag.FragBot_1.0.jar<br /> franzor.Lizt 1.3.1,http://pages.prodigy.net/franz1/house/franzor.Lizt_1.3.1.jar<br /> fromHell.CHCl3 0.0.1,http://fromhell.schreiende-stille.de/fromHell.CHCl3_0.0.1.jar<br /> fullsail.LaxativeTeaTwo 1.0,http://www.robocoderepository.com/BotFiles/3403/fullsail.LaxativeTeaTwo_1.0.jar<br /> fullsail.TimbotNoPrediction 1.0,http://darkcanuck.net/rumble/robots/fullsail.TimbotNoPrediction_1.0.jar<br /> fullsail.SweetTea 1.1,http://darkcanuck.net/rumble/robots/fullsail.SweetTea_1.1.jar<br /> fushi.PvP1.PvP1 2004-02-16,http://www.robocoderepository.com/BotFiles/2023/fushi.PvP1.PvP1_2004-02-16.jar<br /> fw.Number1 1.0b,http://www.dijitari.com/void/robocode/fw.Number1_1.0b.jar<br /> gadsky.Gadsky 1.01,http://www.robocoderepository.com/BotFiles/3595/gadsky.Gadsky_1.01.jar<br /> Gecko.ultimateGeckoBot 1.0,http://www.robocoderepository.com/BotFiles/4039/Gecko.ultimateGeckoBot_1.0.jar<br /> geep.mini.GPBotA 1.0,http://www.robocoderepository.com/BotFiles/2361/geep.mini.GPBotA_1.0.jar<br /> geep.mini.GPBotB 1.1,http://www.robocoderepository.com/BotFiles/2363/geep.mini.GPBotB_1.1.jar<br /> germ.TheMind .2,http://www.robocoderepository.com/BotFiles/2525/germ.TheMind_.2.jar<br /> gg.Squaraus 0.6,http://www.robocoderepository.com/BotFiles/1788/gg.Squaraus_0.6.jar<br /> gg.Wolverine 2.0,http://darkcanuck.net/rumble/robots/gg.Wolverine_2.0.jar<br /> gh.GresSuffurd 0.3.2,http://home.versatel.nl/gheijenk/robocode/jarfiles/gh.GresSuffurd_0.3.2.jar<br /> gh.GrubbmGrb 1.2.4,http://home.versatel.nl/gheijenk/robocode/jarfiles/gh.GrubbmGrb_1.2.4.jar<br /> gh.GrypRepetyf 0.13,http://www.robocoderepository.com/BotFiles/2650/gh.GrypRepetyf_0.13.jar<br /> gh.micro.Grinnik 0.7,http://www.robocoderepository.com/BotFiles/3208/gh.micro.Grinnik_0.7.jar<br /> gh.micro.GrubbmThree 0.9,http://www.robocoderepository.com/BotFiles/2444/gh.micro.GrubbmThree_0.9.jar<br /> gh.mini.Gruwel 0.9,http://www.robocoderepository.com/BotFiles/2511/gh.mini.Gruwel_0.9.jar<br /> gh.nano.Grofvuil 0.2,http://www.robocoderepository.com/BotFiles/2553/gh.nano.Grofvuil_0.2.jar<br /> gimp.GimpBot 0.1,http://www.robocoderepository.com/BotFiles/2434/gimp.GimpBot_0.1.jar<br /> gio.RealGioBot 1.0,http://www.robocoderepository.com/BotFiles/2521/gio.RealGioBot_1.0.jar<br /> gjr.Cephalosporin 0.2,http://www.robocoderepository.com/BotFiles/2240/gjr.Cephalosporin_0.2.jar<br /> gm.GaetanoA 2.15,http://www.robocoderepository.com/BotFiles/2188/gm.GaetanoA_2.15.jar<br /> goblin.Bender 2.4,http://www.robocoderepository.com/BotFiles/1871/goblin.Bender_2.4.jar<br /> grybgoofy.GoofyBot 0.10,http://www.robocoderepository.com/BotFiles/2196/grybgoofy.GoofyBot_0.10.jar<br /> gu.MicroScoob 1.3,http://www.robocoderepository.com/BotFiles/2086/gu.MicroScoob_1.3.jar<br /> gwah.GBotMarkIV 1.0,http://www.horula.ca/roborumble/participants/download.php?file=18<br /> gwah.GerryBotMkII 1.5.1,http://www.horula.ca/roborumble/participants/download.php?file=17<br /> hamilton.Hamilton 1.0,http://www.robocoderepository.com/BotFiles/1408/hamilton.Hamilton_1.0.jar<br /> hapiel.Spiral 0.1,http://robocoderepository.com/BotFiles/3997/hapiel.Spiral_0.1.jar<br /> hirataatsushi.Neo 1.6,http://www.robocoderepository.com/BotFiles/1081/hirataatsushi.Neo_1.6.jar<br /> hirataatsushi.Trinity 0.003,http://www.robocoderepository.com/BotFiles/1145/hirataatsushi.Trinity_0.003.jar<br /> homerbots.h1 1.0,http://www.robocoderepository.com/BotFiles/2999/homerbots.h1_1.0.jar<br /> hp.Athena 0.1,http://www.robocoderepository.com/BotFiles/3415/hp.Athena_0.1.jar<br /> hvilela.HVilela 0.9,http://henrique.vilela.googlepages.com/hvilela.HVilela_0.9.jar<br /> ins.MobyNano 0.8,http://www.robocoderepository.com/BotFiles/939/ins.MobyNano_0.8.jar<br /> intruder.PrairieWolf 2.61,http://darkcanuck.net/rumble/robots/intruder.PrairieWolf_2.61.jar<br /> ivor.prophet.Prophet 0.01,http://www.ivan.php5.sk/ivor.prophet.Prophet_0.01.jar<br /> is.fon.rs.FonDestroyer3084 1.0,http://www.robocoderepository.com/BotFiles/4047/is.fon.rs.FonDestroyer3084_1.0.jar<br /> jaara.LambdaBot 1.1,http://www.robocoderepository.com/BotFiles/3514/jaara.LambdaBot_1.1.jar<br /> jab.avk.ManuelGallegus 0.6,http://darkcanuck.net/rumble/robots/jab.avk.ManuelGallegus_0.6.jar<br /> jab.DiamondStealer 5,http://darkcanuck.net/rumble/robots/jab.DiamondStealers_5.jar<br /> jab.micro.Sanguijuela 0.8,http://darkcanuck.net/rumble/robots/jab.micro.Sanguijuela_0.8.jar<br /> janm.Jammy 1.0,http://www.robocoderepository.com/BotFiles/3543/janm.Jammy_1.0.jar<br /> jam.micro.RaikoMicro 1.44,http://www.robocoderepository.com/BotFiles/1983/jam.micro.RaikoMicro_1.44.jar<br /> jam.mini.Raiko 0.43,http://www.robocoderepository.com/BotFiles/1922/jam.mini.Raiko_0.43.jar<br /> jam.RaikoMX 0.32,http://www.robocoderepository.com/BotFiles/1961/jam.RaikoMX_0.32.jar<br /> japs.Serenity 1.0,http://www.robocoderepository.com/BotFiles/2217/japs.Serenity_1.0.jar<br /> japs.Sjonniebot 0.9.1,http://www.robocoderepository.com/BotFiles/2203/japs.Sjonniebot_0.9.1.jar<br /> jasolo.Sonda 0.55,http://www.robocoderepository.com/BotFiles/1534/jasolo.Sonda_0.55.jar<br /> jaw.Mouse 0.11,http://www.robocoderepository.com/BotFiles/2472/jaw.Mouse_0.11.jar<br /> jaw.KarenCain 0.11,http://www.robocoderepository.com/BotFiles/2474/jaw.KarenCain_0.11.jar<br /> jaybot.adv.bots.JayBot 2.0,http://darkcanuck.net/rumble/robots/jaybot.adv.bots.JayBot_2.0.jar<br /> jaybot.bots.Oddball 4.0,http://darkcanuck.net/rumble/robots/jaybot.bots.Oddball_4.0.jar<br /> jbot.Rabbit2 1.1,http://darkcanuck.net/rumble/robots/jbot.Rabbit2_1.1.jar<br /> jcs.AutoBot 4.2.1,http://www.robocoderepository.com/BotFiles/2616/jcs.AutoBot_4.2.1.jar<br /> jcs.Decepticon 2.5.3,http://www.robocoderepository.com/BotFiles/2620/jcs.Decepticon_2.5.3.jar<br /> jcs.Megatron 1.2,http://www.robocoderepository.com/BotFiles/2632/jcs.Megatron_1.2.jar<br /> jcs.Seth 1.8,http://darkcanuck.net/rumble/robots/jcs.Seth_1.8.jar<br /> jcw.ArcherOne 1.0,http://darkcanuck.net/rumble/robots/jcw.ArcherOne_1.0.jar<br /> jekl.DarkHallow .90.9,http://www.robocoderepository.com/BotFiles/2296/jekl.DarkHallow_.90.9.jar<br /> jekl.Jekyl .70,http://www.robocoderepository.com/BotFiles/1837/jekl.Jekyl_.70.jar<br /> jekl.mini.BlackPearl .91,http://www.robocoderepository.com/BotFiles/1875/jekl.mini.BlackPearl_.91.jar<br /> jep.nano.Hawkwing 0.4.1,http://www.robocoderepository.com/BotFiles/1561/jep.nano.Hawkwing_0.4.1.jar<br /> jep.nano.Hotspur 0.1,http://www.robocoderepository.com/BotFiles/1877/jep.nano.Hotspur_0.1.jar<br /> jep.Terrible 0.4.1,http://www.robocoderepository.com/BotFiles/1536/jep.Terrible_0.4.1.jar<br /> jeremyreeder.Vincent 2011.12.09,http://www.robocoderepository.com/BotFiles/3993/jeremyreeder.Vincent_2011.12.09.jar<br /> jf.Dodger 1.1,http://keenehs.dyndns.org:90/rumble/robots/jf.Dodger_1.1.jar<br /> jf.Dodger 1.3,http://keenehs.dyndns.org:90/rumble/robots/jf.Dodger_1.3.jar<br /> jgap.JGAP12584 1.0,http://www.robocoderepository.com/BotFiles/3383/jgap.JGAP12584_1.0.jar<br /> jgap.JGAP130166 1.0,http://www.robocoderepository.com/BotFiles/3371/jgap.JGAP130166_1.0.jar<br /> jgap.JGAP23423 1.0,http://www.robocoderepository.com/BotFiles/3378/jgap.JGAP23423_1.0.jar<br /> jgap.JGAP6139 1.0,http://www.robocoderepository.com/BotFiles/3372/jgap.JGAP6139_1.0.jar<br /> jgap.JGAP7247_2 1.0,http://www.robocoderepository.com/BotFiles/3382/jgap.JGAP7247_2_1.0.jar<br /> jgap.JGAP7958 1.0,http://www.robocoderepository.com/BotFiles/3373/jgap.JGAP7958_1.0.jar<br /> jje.BagPuss 1.2,http://darkcanuck.net/rumble/robots/jje.BagPuss_1.2.jar<br /> jk.mega.DrussGT 1.9.8,http://www.minifly.rchomepage.com/robocode/jk.mega.DrussGT_1.9.8.jar<br /> jk.micro.Toorkild 0.2.4b,http://www.minifly.rchomepage.com/robocode/jk.micro.Toorkild_0.2.4b.jar<br /> jk.mini.CunobelinDC 0.6,https://sites.google.com/site/jkflying/jk.mini.CunobelinDC_0.6.jar<br /> jk.precise.Wintermute 0.7,http://www.minifly.rchomepage.com/robocode/jk.precise.Wintermute_0.7.jar<br /> jmcd.BeoWulf 2.8,http://www.robocoderepository.com/BotFiles/1377/jmcd.BeoWulf_2.8.jar<br /> joe.ADinosaur 1.0,http://www.robocoderepository.com/BotFiles/2822/joe.ADinosaur_1.0.jar<br /> josago.Jorgito 0.16,http://www.robocoderepository.com/BotFiles/4000/josago.Jorgito_0.16.jar<br /> jp.Perpy 16.0,http://www.robocoderepository.com/BotFiles/3001/jp.Perpy_16.0.jar<br /> jp.SineWall 1.0,http://www.robocoderepository.com/BotFiles/2968/jp.SineWall_1.0.jar<br /> jrm.Test0 1.0,http://www.robocoderepository.com/BotFiles/3636/jrm.Test0_1.0.jar<br /> js.PinBall 1.6,http://www.robocoderepository.com/BotFiles/684/js.PinBall_1.6.jar<br /> jsal.Jsalbot 1.0,http://jeremybubs.googlepages.com/jsal.Jsalbot_1.0.jar<br /> jt.SpearmintCT Alpha,http://www.robocoderepository.com/BotFiles/2164/jt.SpearmintCT_Alpha.jar<br /> justin.DemonicRage 3.20,http://sites.google.com/site/justinsitehere/file-cabinet/justin.DemonicRage_3.20.jar<br /> jw.Booring 1.11,http://www.robocoderepository.com/BotFiles/1250/jw.Booring_1.11.jar<br /> jwst.DAD.DarkAndDarker 1.1,http://darkcanuck.net/rumble/robots/jwst.DAD.DarkAndDarker_1.1.jar<br /> kanishk.Fr0z3n 1.1,http://darkcanuck.net/rumble/robots/kanishk.Fr0z3n_1.1.jar<br /> kano.gamma.KanoGamma 1.8,http://www.robocoderepository.com/BotFiles/1098/kano.gamma.KanoGamma_1.8.jar<br /> kawam.kmBot9 1.0,http://www.robocoderepository.com/BotFiles/967/kawam.kmBot9_1.0.jar<br /> kawigi.f.FhqwhgadsMicro 1.0,http://www.robocoderepository.com/BotFiles/1673/kawigi.f.FhqwhgadsMicro_1.0.jar<br /> kawigi.micro.Shiz 1.1,http://www.robocoderepository.com/BotFiles/2007/kawigi.micro.Shiz_1.1.jar<br /> kawigi.mini.Coriantumr 1.1,http://www.robocoderepository.com/BotFiles/1988/kawigi.mini.Coriantumr_1.1.jar<br /> kawigi.mini.Fhqwhgads 1.1,http://www.robocoderepository.com/BotFiles/1604/kawigi.mini.Fhqwhgads_1.1.jar<br /> kawigi.nano.FunkyChicken 1.1,http://www.robocoderepository.com/BotFiles/1512/kawigi.nano.FunkyChicken_1.1.jar<br /> kawigi.nano.ThnikkaBot 0.9,http://www.robocoderepository.com/BotFiles/2059/kawigi.nano.ThnikkaBot_0.9.jar<br /> kawigi.robot.Girl 1.2,http://www.robocoderepository.com/BotFiles/2124/kawigi.robot.Girl_1.2.jar<br /> kawigi.sbf.Barracuda 1.0,http://www.robocoderepository.com/BotFiles/1535/kawigi.sbf.Barracuda_1.0.jar<br /> kawigi.sbf.FloodHT 0.9.2,http://www.robocoderepository.com/BotFiles/1552/kawigi.sbf.FloodHT_0.9.2.jar<br /> kawigi.sbf.FloodMicro 1.5,http://www.robocoderepository.com/BotFiles/1381/kawigi.sbf.FloodMicro_1.5.jar<br /> kawigi.sbf.FloodMini 1.4,http://www.robocoderepository.com/BotFiles/1462/kawigi.sbf.FloodMini_1.4.jar<br /> kawigi.sbf.FloodNano 1.2,http://www.robocoderepository.com/BotFiles/1421/kawigi.sbf.FloodNano_1.2.jar<br /> kawigi.sbf.FloodSonnet 0.9,http://www.robocoderepository.com/BotFiles/1779/kawigi.sbf.FloodSonnet_0.9.jar<br /> kawigi.sbf.Teancum 1.3,http://www.robocoderepository.com/BotFiles/1470/kawigi.sbf.Teancum_1.3.jar<br /> kawigi.spare.SpareParts 0.7.6nosnd,http://www.robocoderepository.com/BotFiles/1335/kawigi.spare.SpareParts_0.7.6nosnd.jar<br /> kc.micro.Needle 0.101,http://www.robocoderepository.com/BotFiles/3379/kc.micro.Needle_0.101.jar<br /> kc.micro.Thorn 1.252,http://sites.google.com/site/kevcsite/robocode/kc.micro.Thorn_1.252.jar<br /> kc.micro.WaveShark 0.31,http://www.robocoderepository.com/BotFiles/3822/kc.micro.WaveShark_0.31.jar<br /> kc.mini.Vyper 0.311,http://darkcanuck.net/rumble/robots/kc.mini.Vyper_0.311.jar<br /> kc.nano.Splinter 1.2,http://darkcanuck.net/rumble/robots/kc.nano.Splinter_1.2.jar<br /> kc.serpent.Hydra 0.21,http://darkcanuck.net/rumble/robots/kc.serpent.Hydra_0.21.jar<br /> kc.serpent.WaveSerpent 2.11,http://sites.google.com/site/kevcsite/robocode/kc.serpent.WaveSerpent_2.11.jar<br /> kcn.percept.PerceptBot 2.3,http://www.robocoderepository.com/BotFiles/1075/kcn.percept.PerceptBot_2.3.jar<br /> kcn.unnamed.Unnamed 1.21,http://www.robocoderepository.com/BotFiles/1969/kcn.unnamed.Unnamed_1.21.jar<br /> kenran.mega.Pantheist 1.1,http://sites.google.com/site/kenranbots/robocode/kenran.mega.Pantheist_1.1.jar<br /> kid.Gladiator .7.2,http://darkcanuck.net/rumble/robots/kid.Gladiator_.7.2.jar<br /> kid.Toa .0.5,http://rednaxela-robocode.dyndns.org/data/robot_archive/kid.Toa_.0.5.jar<br /> KiraNL.Chupacabra 0.5,http://sandbox-project.nl/robocode/KiraNL.Chupacabra_0.5.jar<br /> KiraNL.ChupaLite 0.4,http://sandbox-project.nl/robocode/KiraNL.ChupaLite_0.4.jar<br /> KiraNL.SpaceKees 0.1,http://sandbox-project.nl/robocode/KiraNL.SpaceKees_0.1.jar<br /> kinsen.melee.Angsaichmophobia 1.8c,http://sites.google.com/site/dcvqksyb/robocode/kinsen.melee.Angsaichmophobia_1.8c.jar<br /> kinsen.nano.Hoplomachy 1.6,http://sites.google.com/site/dcvqksyb/robocode/kinsen.nano.Hoplomachy_1.6.jar<br /> kinsen.nano.Quarrelet 1.0,http://sites.google.com/site/dcvqksyb/robocode/kinsen.nano.Quarrelet_1.0.jar<br /> kinsen.nano.Senticous 1.0,http://sites.google.com/site/dcvqksyb/robocode/kinsen.nano.Senticous_1.0.jar<br /> kjc.etc.Dharok 1.0,http://www.robocoderepository.com/BotFiles/3293/kjc.etc.Dharok_1.0.jar<br /> kjc.MailManX 2.0,http://www.robocoderepository.com/BotFiles/3288/kjc.MailManX_2.0.jar<br /> kjc.Karaykan 1.0,http://www.robocoderepository.com/BotFiles/3289/kjc.Karaykan_1.0.jar<br /> klein.GottesKrieger 1.1,http://www.robocoderepository.com/BotFiles/3258/klein.GottesKrieger_1.1.jar<br /> Krabb.fe4r.Fe4r 0.4,http://www.robocoderepository.com/BotFiles/2766/Krabb.fe4r.Fe4r_0.4.jar<br /> Krabb.sliNk.Garm 0.9u,http://designnj.de/roboking/Krabb.sliNk.Garm_0.9u.jar<br /> Krabb.krabby.Krabby 1.18b,http://darkcanuck.net/rumble/robots/Krabb.krabby.Krabby_1.18b.jar<br /> Krabb.krabby2.Krabby2 1.9o,http://darkcanuck.net/rumble/robots/Krabb.krabby2.Krabby2_1.9o.jar<br /> krillr.mini.JointStrike 2.0.0,http://darkcanuck.net/rumble/robots/krillr.mini.JointStrike_2.0.0.jar<br /> krillr.mega.Psyche 0.0.3,http://darkcanuck.net/rumble/robots/krillr.mega.Psyche_0.0.3.jar<br /> kronenthaler.Basilisk 1.0,http://www.robocoderepository.com/BotFiles/4051/kronenthaler.Basilisk_1.0.jar<br /> krzysiek.robbo2.Robbo 1.0.0,http://darkcanuck.net/rumble/robots/krzysiek.robbo2.Robbo_1.0.0.jar<br /> kurios.DOSexe .9a,http://www.kuriosly.com/roborumble/kurios.DOSexe_.9a.jar<br /> kurios.DOSexe .9b,http://www.kuriosly.com/roborumble/kurios.DOSexe_.9b.jar<br /> kvk.HebusLeTroll 0.41,http://www.robocoderepository.com/BotFiles/2125/kvk.HebusLeTroll_0.41.jar<br /> labg.Cataclysm 2.05,http://www.robocoderepository.com/BotFiles/2399/labg.Cataclysm_2.05.jar<br /> lancel.Lynx 1.09,http://www.robocoderepository.com/BotFiles/3992/lancel.Lynx_1.09.jar<br /> lazarecki.mega.PinkerStinker 0.7,http://www.robocoderepository.com/BotFiles/3838/lazarecki.mega.PinkerStinker_0.7.jar<br /> leb.ShootAnArrow 0.1,http://www.robocoderepository.com/BotFiles/2648/leb.ShootAnArrow_0.1.jar<br /> lechu.Ala 0.0.4,http://www.robocoderepository.com/BotFiles/3497/lechu.Ala_0.0.4.jar<br /> lechu.Lechu 1.1,http://www.robocoderepository.com/BotFiles/3480/lechu.Lechu_1.1.jar<br /> lion.Kresnanano 1.0,http://www.robocoderepository.com/BotFiles/2295/lion.Kresnanano_1.0.jar<br /> lk.nano.Avesnar 1.1,http://www.robocoderepository.com/BotFiles/1597/lk.nano.Avesnar_1.1.jar<br /> lorneswork.Predator 1.0,http://www.robocoderepository.com/BotFiles/2609/lorneswork.Predator_1.0.jar<br /> lrem.Spectre 0.4.4,http://www.robocoderepository.com/BotFiles/2253/lrem.Spectre_0.4.4.jar<br /> lrem.magic.TormentedAngel Antiquitie,http://maxnet.org.pl/~lrem/lrem.magic.TormentedAngel_Antiquitie.jar<br /> lrem.micro.MoggFanatic 0.2,http://www.robocoderepository.com/BotFiles/2639/lrem.micro.MoggFanatic_0.2.jar<br /> lrem.micro.FalseProphet Alpha,http://www.robocoderepository.com/BotFiles/2415/lrem.micro.FalseProphet_Alpha.jar<br /> lrem.quickhack.QuickHack 1.0,http://www.robocoderepository.com/BotFiles/2555/lrem.quickhack.QuickHack_1.0.jar<br /> lunchie.Lunchbox 0.93,http://darkcanuck.net/rumble/robots/lunchie.Lunchbox_0.93.jar<br /> lw.LuthersTest 0.1,http://darkcanuck.net/rumble/robots/lw.LuthersTest_0.1.jar<br /> m3thos.Eva00 1.1,http://darkcanuck.net/rumble/robots/m3thos.Eva00_1.1.jar<br /> m3thos.Eva02 0.7.1,http://darkcanuck.net/rumble/robots/m3thos.Eva02_0.7.1.jar<br /> m3thos.mini.Eva01 0.5.5,http://darkcanuck.net/rumble/robots/m3thos.mini.Eva01_0.5.5.jar<br /> ma.is.fon.rs.RobotA 0.01,http://www.robocoderepository.com/BotFiles/4048/ma.is.fon.rs.RobotA_0.01.jar<br /> madmath.Cow 0.1.1,http://www.robocoderepository.com/BotFiles/3476/madmath.Cow_0.1.1.jar<br /> marcinek.TopGun 1.3,http://www.robocoderepository.com/BotFiles/3458/marcinek.TopGun_1.3.jar<br /> marksteam.Phoenix 1.0,http://www.robocoderepository.com/BotFiles/2749/marksteam.Phoenix_1.0.jar<br /> matt.advanced.Katana 1.0,http://www.robocoderepository.com/BotFiles/2498/matt.advanced.Katana_1.0.jar<br /> matt.BlueMind 0.8.00,http://www.robocoderepository.com/BotFiles/2685/matt.BlueMind_0.8.00.jar<br /> matt.UnderDark3 2.4.34,http://www.robocoderepository.com/BotFiles/2485/matt.UnderDark3_2.4.34.jar<br /> matt.UnderDark4 0.4.00,http://www.robocoderepository.com/BotFiles/2644/matt.UnderDark4_0.4.00.jar<br /> mbh.Mbh 0.1,http://www.robocoderepository.com/BotFiles/3365/mbh.Mbh_0.1.jar<br /> mbro.BelajarBot 0.0.3,http://www.robocoderepository.com/BotFiles/2471/mbro.BelajarBot_0.0.3.jar<br /> mbro.Detektor3 0.1.1,http://www.robocoderepository.com/BotFiles/2478/mbro.Detektor3_0.1.1.jar<br /> mc.Messapia 0.1.8,http://www.robocoderepository.com/BotFiles/2223/mc.Messapia_0.1.8.jar<br /> mcb.Audace 1.3,http://www.robocoderepository.com/BotFiles/3424/mcb.Audace_1.3.jar<br /> md.November 1.0,http://www.robocoderepository.com/BotFiles/1004/md.November_1.0.jar<br /> md.Pasta 1.1,http://www.robocoderepository.com/BotFiles/1014/md.Pasta_1.1.jar<br /> md.VelociRaptor 1.3,http://www.robocoderepository.com/BotFiles/232/md.VelociRaptor_1.3.jar<br /> mdouet.BotKicker 2.0,http://www.robocoderepository.com/BotFiles/1478/mdouet.BotKicker_2.0.jar<br /> metal.small.MCool 1.21,http://www.robocoderepository.com/BotFiles/1698/metal.small.MCool_1.21.jar<br /> metal.small.dna2.MCoolDNA 1.5,http://www.robocoderepository.com/BotFiles/2354/metal.small.dna2.MCoolDNA_1.5.jar<br /> microtestbotpack.MicroTestBot 1.0,http://dl.dropbox.com/u/4547352/robocode/microtestbotpack.MicroTestBot_1.0.jar<br /> mk.Alpha 0.2.1,http://darkcanuck.net/rumble/robots/mk.Alpha_0.2.1.jar<br /> mladjo.AIR 0.7,http://www.robocoderepository.com/BotFiles/3187/mladjo.AIR_0.7.jar<br /> mladjo.GnuKlub 0.1,http://darkcanuck.net/rumble/robots/mladjo.GnuKlub_0.1.jar<br /> mladjo.Grrrrr 0.9,http://www.robocoderepository.com/BotFiles/3189/mladjo.Grrrrr_0.9.jar<br /> mladjo.iRobot 0.3,http://www.robocoderepository.com/BotFiles/3149/mladjo.iRobot_0.3.jar<br /> mladjo.Startko 1.0,http://www.robocoderepository.com/BotFiles/3186/mladjo.Startko_1.0.jar<br /> mld.DustBunny 3.8,http://www.robocoderepository.com/BotFiles/3650/mld.DustBunny_3.8.jar<br /> mld.Infinity 2.2,http://www.robocoderepository.com/BotFiles/3591/mld.Infinity_2.2.jar<br /> mld.LittleBlackBook 1.69e,https://sites.google.com/site/dorganrobocode/file-cabinet/mld.LittleBlackBook_1.69e.jar<br /> mld.Moebius 2.9.3,http://www.robocoderepository.com/BotFiles/3634/mld.Moebius_2.9.3.jar<br /> mld.Wisdom 1.0,http://www.robocoderepository.com/BotFiles/3640/mld.Wisdom_1.0.jar<br /> mmb.Roskilde 0.5,http://www.robocoderepository.com/BotFiles/3965/mmb.Roskilde_0.5.jar<br /> mme.NikeEnhanced 2.0,http://www.robocoderepository.com/BotFiles/2828/mme.NikeEnhanced_2.0.jar<br /> mn.Combat 1.0,http://www.robocoderepository.com/BotFiles/2351/mn.Combat_1.0.jar<br /> mn.WarMachine 1.1,http://www.robocoderepository.com/BotFiles/2574/mn.WarMachine_1.1.jar<br /> mnt.AHEB 0.6a,http://www.robocoderepository.com/BotFiles/2417/mnt.AHEB_0.6a.jar<br /> mnt.SurferBot 0.2.5,http://www.robocoderepository.com/BotFiles/2433/mnt.SurferBot_0.2.5.jar<br /> morbid.MorbidPriest 1.0,http://www.robocoderepository.com/BotFiles/1758/morbid.MorbidPriest_1.0.jar<br /> mrm.MightyMoose .2,http://darkcanuck.net/rumble/robots/mrm.MightyMoose_.2.jar<br /> ms.Ares 0.19,http://www.robocoderepository.com/BotFiles/730/ms.Ares_0.19.jar<br /> mue.Ascendant 1.2.27,http://mue.sonar-echo.de/robocode/mue.Ascendant_1.2.27.jar<br /> mue.Hyperion 0.8,http://www.robocoderepository.com/BotFiles/2224/mue.Hyperion_0.8.jar<br /> muf.CrazyKitten 0.9,http://www.robocoderepository.com/BotFiles/1946/muf.CrazyKitten_0.9.jar<br /> mwj.A1176183 1.0,http://robocode.rleach.id.au/mwj.A1176183_1.0.jar<br /> myl.micro.Avipes 1.00,http://www.robocoderepository.com/BotFiles/1347/myl.micro.Avipes_1.00.jar<br /> myl.micro.NekoNinja 1.30,http://www.robocoderepository.com/BotFiles/944/myl.micro.NekoNinja_1.30.jar<br /> myl.micro.Predator 1.50,http://www.robocoderepository.com/BotFiles/1097/myl.micro.Predator_1.50.jar<br /> myl.micro.Troodon 1.10,http://www.robocoderepository.com/BotFiles/1226/myl.micro.Troodon_1.10.jar<br /> myl.nano.Graviton 1.10,http://www.robocoderepository.com/BotFiles/770/myl.nano.Graviton_1.10.jar<br /> myl.nano.Kakuru 1.20,http://www.robocoderepository.com/BotFiles/1330/myl.nano.Kakuru_1.20.jar<br /> myl.nano.KomoriNinja 1.1,http://www.robocoderepository.com/BotFiles/978/myl.nano.KomoriNinja_1.1.jar<br /> mym.EdgeStalker 1.0,http://www.robocoderepository.com/BotFiles/3956/mym.EdgeStalker_1.0.jar<br /> mz.Adept 2.65,http://www.robocoderepository.com/BotFiles/2090/mz.Adept_2.65.jar<br /> mz.AdeptBSB 1.03,http://www.robocoderepository.com/BotFiles/2113/mz.AdeptBSB_1.03.jar<br /> mz.Movement 1.8,http://www.robocoderepository.com/BotFiles/2145/mz.Movement_1.8.jar<br /> mz.NanoDeath 2.56,http://www.robocoderepository.com/BotFiles/2010/mz.NanoDeath_2.56.jar<br /> mz.NanoGod 2.02,http://www.robocoderepository.com/BotFiles/1996/mz.NanoGod_2.02.jar<br /> nammyung.ModelT 0.23,http://www.robocoderepository.com/BotFiles/969/nammyung.ModelT_0.23.jar<br /> nanoskank.NanoSkank 1.0,http://darkcanuck.net/rumble/robots/nanoskank.NanoSkank_1.0.jar<br /> nat.BlackHole 2.0gamma,http://nat.robothai.net/robots/nat.BlackHole_2.0gamma.jar<br /> nat.micro.NP 1.34,http://nat.robothai.net/robots/nat.micro.NP_1.34.jar<br /> nat.micro.Reepicheep 0.1a,http://nat.robothai.net/robots/nat.micro.Reepicheep_0.1a.jar<br /> nat.nano.Ocnirp 1.73,http://nat.robothai.net/robots/nat.nano.Ocnirp_1.73.jar<br /> nat.nano.OcnirpPM 1.0,http://nat.robothai.net/robots/nat.nano.OcnirpPM_1.0.jar<br /> nat.nano.OcnirpSNG 1.0b,http://nat.robothai.net/robots/nat.nano.OcnirpSNG_1.0b.jar<br /> nat.Samekh 0.4,http://nat.robothai.net/robots/nat.Samekh_0.4.jar<br /> ncj.MoxieBot 1.0,http://www.robocoderepository.com/BotFiles/4003/ncj.MoxieBot_1.0.jar<br /> ndn.DyslexicMonkey 1.1,http://www.robocoderepository.com/BotFiles/1141/ndn.DyslexicMonkey_1.1.jar<br /> NDH.GuessFactor 1.0, http://www.robocoderepository.com/BotFiles/3949/NDH.GuessFactor_1.0.jar<br /> ne.Chimera 1.2,http://www.robocoderepository.com/BotFiles/3276/ne.Chimera_1.2.jar<br /> nexus.One 1.0,http://darkcanuck.net/rumble/robots/nexus.One_1.0.jar<br /> nexus.Prototype 1.0,http://darkcanuck.net/rumble/robots/nexus.Prototype_1.0.jar<br /> nic.Nicator 2.4,http://www.robocoderepository.com/BotFiles/193/nic.Nicator_2.4.jar<br /> nic.SnippetBot 1.0,http://www.robocoderepository.com/BotFiles/286/nic.SnippetBot_1.0.jar<br /> nkn.mini.Jskr0 0.1,http://www.robocoderepository.com/BotFiles/3852/nkn.mini.Jskr0_0.1.jar<br /> NG.LegatusLegionis 1.0,http://www.robocoderepository.com/BotFiles/3888/NG.LegatusLegionis_1.0.jar<br /> NG.LegatusLegionis 1.1,http://www.robocoderepository.com/BotFiles/3889/NG.LegatusLegionis_1.1.jar<br /> NG.LegatusLegionis 1.2,http://www.robocoderepository.com/BotFiles/4026/NG.LegatusLegionis_1.2.jar<br /> non.mega.NaN 0.1,http://www.robocoderepository.com/BotFiles/1960/non.mega.NaN_0.1.jar<br /> non.mega.NoName 0.0,http://www.robocoderepository.com/BotFiles/1957/non.mega.NoName_0.0.jar<br /> Noran.BitchingElk 0.054,http://www.robocoderepository.com/BotFiles/1855/Noran.BitchingElk_0.054.jar<br /> Noran.RandomTargeting 0.02,http://www.robocoderepository.com/BotFiles/1849/Noran.RandomTargeting_0.02.jar<br /> nova.Snow 1.0,http://www.robocoderepository.com/BotFiles/3623/nova.Snow_1.0.jar<br /> ntc.Cannon 1.12test,http://www.robocoderepository.com/BotFiles/3815/ntc.Cannon_1.12test.jar<br /> ntc.Evader 1.2,http://www.robocoderepository.com/BotFiles/3355/ntc.Evader_1.2.jar<br /> ntc.Knowledge 1.1,http://www.robocoderepository.com/BotFiles/3354/ntc.Knowledge_1.1.jar<br /> ntc.Lasers.Lasers 0.9,http://www.robocoderepository.com/BotFiles/3359/ntc.Lasers.Lasers_0.9.jar<br /> ntc.Plains 0.9,http://www.robocoderepository.com/BotFiles/3381/ntc.Plains_0.9.jar<br /> ntc.Swim 0.9,http://www.robocoderepository.com/BotFiles/3820/ntc.Swim_0.9.jar<br /> ntw.Sighup 1.5,http://darkcanuck.net/rumble/robots/ntw.Sighup_1.5.jar<br /> ntw.Sigsys 1.6,http://darkcanuck.net/rumble/robots/ntw.Sigsys_1.6.jar<br /> nz.jdc.micro.HedgehogGF 1.3,http://www.robocoderepository.com/BotFiles/3626/nz.jdc.micro.HedgehogGF_1.3.jar<br /> nz.jdc.micro.HedgehogP 1.2,http://www.robocoderepository.com/BotFiles/3622/nz.jdc.micro.HedgehogP_1.2.jar<br /> nz.jdc.nano.NeophytePattern 1.0,http://www.robocoderepository.com/BotFiles/3578/nz.jdc.nano.NeophytePattern_1.0.jar<br /> nz.jdc.nano.NeophytePRAL 1.2,http://www.robocoderepository.com/BotFiles/3568/nz.jdc.nano.NeophytePRAL_1.2.jar<br /> nz.jdc.nano.NeophyteSRAL 1.2,http://www.robocoderepository.com/BotFiles/3567/nz.jdc.nano.NeophyteSRAL_1.2.jar<br /> oa.weak.BotherBot 0.1,http://www.robocoderepository.com/BotFiles/2956/oa.weak.BotherBot_0.1.jar<br /> oa.weak.FlyMk1 0.1,http://www.robocoderepository.com/BotFiles/2958/oa.weak.FlyMk1_0.1.jar<br /> ola.Puffin 1.0,http://www.robocoderepository.com/BotFiles/3380/ola.Puffin_1.0.jar<br /> oog.melee.Capulet 1.1,https://sites.google.com/site/crazybassoon/oog.melee.Capulet_1.1.jar<br /> oog.melee.Mercutio 1.0,http://www.robocoderepository.com/BotFiles/3848/oog.melee.Mercutio_1.0.jar<br /> oog.micro.MagicD3 0.41,http://www.robocoderepository.com/BotFiles/3801/oog.micro.MagicD3_0.41.jar<br /> oog.micro.Maui 1.2,https://sites.google.com/site/crazybassoon/oog.micro.Maui_1.2.jar<br /> oog.micro.SavantMicro 1.0,http://www.robocoderepository.com/BotFiles/3958/oog.micro.SavantMicro_1.0.jar<br /> oog.mini.AlphaDragon 0.1,http://www.robocoderepository.com/BotFiles/4015/oog.mini.AlphaDragon_0.1.jar<br /> oog.nano.Caligula 1.15,http://www.robocoderepository.com/BotFiles/4022/oog.nano.Caligula_1.15.jar<br /> oog.nano.Fuatisha 1.1,http://www.robocoderepository.com/BotFiles/4045/oog.nano.Fuatisha_1.1.jar<br /> oog.nano.MagicD2 2.4,http://www.robocoderepository.com/BotFiles/3749/oog.nano.MagicD2_2.4.jar<br /> oog.nano.SavantVS 1.1,http://www.robocoderepository.com/BotFiles/3714/oog.nano.SavantVS_1.1.jar<br /> oog.nano.SavantWS 0.1,http://www.robocoderepository.com/BotFiles/3709/oog.nano.SavantWS_0.1.jar<br /> oog.PricklyPear 1.0.4,https://sites.google.com/site/crazybassoon/oog.PricklyPear_1.0.4.jar<br /> pa.Improved 1.1,http://darkcanuck.net/rumble/robots/pa.Improved_1.1.jar<br /> pak.JakeTheTestingRobot .1b,http://www.robocoderepository.com/BotFiles/3373/pak.JakeTheTestingRobot_.1b.jar<br /> pak.Dargon 1.0b,http://www.robocoderepository.com/BotFiles/3388/pak.Dargon_1.0b.jar<br /> pak.Dargon .2c,http://www.robocoderepository.com/BotFiles/3389/pak.Dargon_.2c.jar<br /> panzer.Panzer 0.2,http://www.robocoderepository.com/BotFiles/4008/panzer.Panzer_0.2.jar<br /> paolord.TheHulk 1.0,http://www.robocoderepository.com/BotFiles/3595/paolord.TheHulk_1.0.jar<br /> patson.PatsonTestBot 1.0,http://www.robocoderepository.com/BotFiles/3324/patson.PatsonTestBot_1.0.jar<br /> paulk.PaulV3 1.7,http://www.robocoderepository.com/BotFiles/3502/paulk.PaulV3_1.7.jar<br /> paulk.PaulV3 1.6,http://www.robocoderepository.com/BotFiles/3497/paulk.PaulV3_1.6.jar<br /> paulk.PaulV3 1.5,http://www.robocoderepository.com/BotFiles/3496/paulk.PaulV3_1.5.jar<br /> paulk.PaulV3 1.3,http://www.robocoderepository.com/BotFiles/3495/paulk.PaulV3_1.3.jar<br /> pb.Oscillator 1.0,http://www.robocoderepository.com/BotFiles/2070/pb.Oscillator_1.0.jar<br /> pe.mini.SandboxMini 1.2,http://www.robocoderepository.com/BotFiles/917/pe.mini.SandboxMini_1.2.jar<br /> pe.minimelee.SandboxMiniMelee 1.1,http://www.robocoderepository.com/BotFiles/934/pe.minimelee.SandboxMiniMelee_1.1.jar<br /> pe.SandboxDT 3.02,http://www.robocoderepository.com/BotFiles/793/pe.SandboxDT_3.02.jar<br /> pe.SandboxLump 1.52,http://www.robocoderepository.com/BotFiles/731/pe.SandboxLump_1.52.jar<br /> pedersen.Hubris 2.4,http://home.comcast.net/~kokyunage/robocode/hubris/pedersen.Hubris_2.4.jar<br /> pedersen.Ugluk 1.0,http://home.comcast.net/~kokyunage/robocode/ugluk/pedersen.Ugluk_1.0.jar<br /> pez.clean.Swiffer 0.2.9,http://www.robocoderepository.com/BotFiles/1883/pez.clean.Swiffer_0.2.9.jar<br /> pez.frankie.Frankie 0.9.6.1,http://www.robocoderepository.com/BotFiles/1565/pez.frankie.Frankie_0.9.6.1.jar<br /> pez.gloom.GloomyDark 0.9.2,http://www.robocoderepository.com/BotFiles/1741/pez.gloom.GloomyDark_0.9.2.jar<br /> pez.mako.Mako 1.5,http://www.robocoderepository.com/BotFiles/1317/pez.mako.Mako_1.5.jar<br /> pez.micro.Aristocles 0.3.7,http://www.robocoderepository.com/BotFiles/1923/pez.micro.Aristocles_0.3.7.jar<br /> pez.mini.ChironexFleckeri 0.5,http://www.robocoderepository.com/BotFiles/2513/pez.mini.ChironexFleckeri_0.5.jar<br /> pez.mini.Gouldingi 1.5,http://www.robocoderepository.com/BotFiles/1351/pez.mini.Gouldingi_1.5.jar<br /> pez.mini.Pugilist 2.4.18,http://darkcanuck.net/rumble/robots/pez.mini.Pugilist_2.4.18.jar<br /> pez.mini.Tityus 0.9.1,http://www.robocoderepository.com/BotFiles/1657/pez.mini.Tityus_0.9.1.jar<br /> pez.mini.VertiLeach 0.4.0,http://www.robocoderepository.com/BotFiles/1744/pez.mini.VertiLeach_0.4.0.jar<br /> pez.nano.Icarus 0.3,http://www.robocoderepository.com/BotFiles/2353/pez.nano.Icarus_0.3.jar<br /> pez.nano.LittleEvilBrother 0.1,http://www.robocoderepository.com/BotFiles/2056/pez.nano.LittleEvilBrother_0.1.jar<br /> pez.rumble.Ali 0.4.9,http://www.robocoderepository.com/BotFiles/2416/pez.rumble.Ali_0.4.9.jar<br /> pez.rumble.CassiusClay 2rho.01b,http://www.dijitari.com/void/robocode/pez.rumble.CassiusClay_2rho.01b.jar<br /> pfvicm.Sobieski 7.2.3b,http://www.robocoderepository.com/BotFiles/2911/pfvicm.Sobieski_7.2.3b.jar<br /> ph.micro.Pikeman 0.4.5,http://www.robocoderepository.com/BotFiles/2364/ph.micro.Pikeman_0.4.5.jar<br /> ph.mini.Archer 0.6.6,http://www.robocoderepository.com/BotFiles/2326/ph.mini.Archer_0.6.6.jar<br /> ph.musketeer.Musketeer 0.6,http://www.robocoderepository.com/BotFiles/2281/ph.musketeer.Musketeer_0.6.jar<br /> ph.Thinker 0.2.5,http://www.robocoderepository.com/BotFiles/2336/ph.Thinker_0.2.5.jar<br /> pi.Dark 10,http://darkcanuck.net/rumble/robots/pi.Dark_10.jar<br /> pl.Drum 0.1,http://darkcanuck.net/rumble/robots/pl.Drum_0.1.jar<br /> pl.Patton.GeneralPatton 1.54,http://darkcanuck.net/rumble/robots/pl.Patton.GeneralPatton_1.54.jar<br /> pla.Memnoch 0.5,http://www.robocoderepository.com/BotFiles/2211/pla.Memnoch_0.5.jar<br /> PK.Twardy 0.4.2,http://www.robocoderepository.com/BotFiles/3272/PK.Twardy_0.4.2.jar<br /> pkdeken.Paladin 1.0,http://www.robocoderepository.com/BotFiles/3556/pkdeken.Paladin_1.0.jar<br /> PkKillers.PkAssassin 1.0,http://www.robocoderepository.com/BotFiles/3485/PkKillers.PkAssassin_1.0.jar<br /> pmc.SniperBot 1.0,http://darkcanuck.net/rumble/robots/pmc.SniperBot_1.0.jar<br /> populations.TrainStoopidbot 0.01,http://www.robocoderepository.com/BotFiles/4052/populations.TrainStoopidbot_0.01.jar<br /> positive.Portia 1.26e,http://sites.google.com/site/robopositive/portia/positive.Portia_1.26e.jar<br /> povik.nano.Smilee 0.2.1,http://www.robocoderepository.com/BotFiles/3950/povik.nano.Smilee_0.2.1.jar<br /> projectx.ProjectNano 2.0,http://darkcanuck.net/rumble/robots/projectx.ProjectNano_2.0.jar<br /> projectx.TestNano 1.0,http://www.robocoderepository.com/BotFiles/3444/projectx.TestNano_1.0.jar<br /> pulsar.PulsarMax 0.8.9,http://www.robocoderepository.com/BotFiles/2227/pulsar.PulsarMax_0.8.9.jar<br /> pulsar.PulsarNano 0.2.4,http://www.robocoderepository.com/BotFiles/2335/pulsar.PulsarNano_0.2.4.jar<br /> pulsar.Nanis 0.3,http://www.robocoderepository.com/BotFiles/2560/pulsar.Nanis_0.3.jar<br /> qohnil.blot.BlotBot 3.61,http://www.robocoderepository.com/BotFiles/546/qohnil.blot.BlotBot_3.61.jar<br /> Queens_teamrobot.UltraRazor 1.0,http://www.robocoderepository.com/BotFiles/2108/Queens_teamrobot.UltraRazor_1.0.jar<br /> quietus.Invader 0.1,http://robocode.rleach.id.au/quietus.Invader_0.1.jar<br /> quietus.NarrowRadar 0.1,http://robocode.rleach.id.au/quietus.NarrowRadar_0.1.jar<br /> radnor.DoctorBob 1.42,http://www.robocoderepository.com/BotFiles/2133/radnor.DoctorBob_1.42.jar<br /> radnor.RamRod 1.0,http://www.robocoderepository.com/BotFiles/2085/radnor.RamRod_1.0.jar<br /> rampancy.Durandal 2.2d,http://stanford.edu/~mchunlum/robocode/rampancy.Durandal_2.2d.jar<br /> rampancy.micro.Epiphron 1.0,http://stanford.edu/~mchunlum/robocode/rampancy.micro.Epiphron_1.0.jar<br /> rapture.Rapture 2.13,http://www.robocoderepository.com/BotFiles/15/rapture.Rapture_2.13.jar<br /> ratosh.nano.Debo 1.36,http://www.robocoderepository.com/BotFiles/1702/ratosh.nano.Debo_1.36.jar<br /> ratosh.Nobo 0.21,http://www.robocoderepository.com/BotFiles/1612/ratosh.Nobo_0.21.jar<br /> ratosh.Wesco 1.4,http://www.robocoderepository.com/BotFiles/1914/ratosh.Wesco_1.4.jar<br /> rc.yoda.Yoda 1.0.6c.fix,http://rednaxela-robocode.dyndns.org/data/robots/rc.yoda.Yoda_1.0.6c.fix.jar<br /> rcb.Vanessa03 0,http://www.robocoderepository.com/BotFiles/1364/rcb.Vanessa03_0.jar<br /> rcp.Kuramatron 1.0,http://www.robocoderepository.com/BotFiles/3307/rcp.Kuramatron_1.0.jar<br /> rdt199.Warlord 0.73,http://www.robocoderepository.com/BotFiles/1130/rdt199.Warlord_0.73.jar<br /> reaper.Reaper 1.1,http://www.robocoderepository.com/BotFiles/3412/reaper.Reaper_1.1.jar<br /> repositorio.NanoStep 1.0,http://darkcanuck.net/rumble/robots/repositorio.NanoStep_1.0.jar<br /> rfj.Sunburn 1.1,http://www.robocoderepository.com/BotFiles/1060/rfj.Sunburn_1.1.jar<br /> rijteam.SmartDodge 1.1,http://www.robocoderepository.com/BotFiles/2959/rijteam.SmartDodge_1.1.jar<br /> robar.haiku.Spike 1.0,http://invitel.hu/artrog/robar.haiku.Spike_1.0.jar<br /> robar.micro.Gladius 1.15,http://invitel.hu/artrog/robar.micro.Gladius_1.15.jar<br /> robar.micro.Kirbyi 1.0,http://hunrobar.freeblog.hu/files/myrobots/robar.micro.Kirbyi_1.0.jar<br /> robar.micro.Topaz 0.25,http://invitel.hu/artrog/robar.micro.Topaz_0.25.jar<br /> robar.nano.Assertive 0.3,http://invitel.hu/artrog/robar.nano.Assertive_0.3.jar<br /> robar.nano.BlackWidow 1.3,http://www.robocoderepository.com/BotFiles/3574/robar.nano.BlackWidow_1.3.jar<br /> robar.nano.Breeze 0.3,http://hunrobar.freeblog.hu/files/myrobots/robar.nano.Breeze_0.3.jar<br /> robar.nano.Mosquito 1.1,http://hunrobar.freeblog.hu/files/myrobots/robar.nano.Mosquito_1.1.jar<br /> robar.nano.MosquitoPM 1.0,http://www.robocoderepository.com/BotFiles/3559/robar.nano.MosquitoPM_1.0.jar<br /> robar.nano.Prestige 1.0,http://www.robocoderepository.com/BotFiles/3507/robar.nano.Prestige_1.0.jar<br /> robar.nano.Pugio 1.49,http://www.robocoderepository.com/BotFiles/3710/robar.nano.Pugio_1.49.jar<br /> robar.nano.Scytodes 0.3,http://hunrobar.freeblog.hu/files/myrobots/robar.nano.Scytodes_0.3.jar<br /> robar.nano.Vespa 0.95,http://hunrobar.freeblog.hu/files/myrobots/robar.nano.Vespa_0.95.jar<br /> robo.PartsBot 1.1,http://darkcanuck.net/rumble/robots/robo.PartsBot_1.1.jar<br /> RobotMarco.MarcoV 0.1,http://www.robocoderepository.com/BotFiles/3941/RobotMarco.MarcoV_0.1.jar<br /> rsim.micro.uCatcher 0.1,http://sites.google.com/site/rsimander/robocode/rsim.micro.uCatcher_0.1.jar<br /> rsim.mini.BulletCatcher 0.4,http://www.robocoderepository.com/BotFiles/3737/rsim.mini.BulletCatcher_0.4.jar<br /> rsk1.RSK1 4.0,http://www.robocoderepository.com/BotFiles/3284/rsk1.RSK1_4.0.jar<br /> ruc.nano.Zealot 0.2,http://www.robocoderepository.com/BotFiles/1229/ruc.nano.Zealot_0.2.jar<br /> rus.vv.Dzhigit 1.1,http://www.robocoderepository.com/BotFiles/4002/rus.vv.Dzhigit1.1.jar<br /> rus.vv.Snezhok 1.1,http://www.robocoderepository.com/BotFiles/3998/rus.vv.Snezhok1.1.jar<br /> ry.LightningBug 1.0,http://www.robocoderepository.com/BotFiles/3472/ry.LightningBug_1.0.jar<br /> ry.VirtualGunExperiment 1.2.0,http://www.robocoderepository.com/BotFiles/3662/ry.VirtualGunExperiment_1.2.0.jar<br /> ry.Worst 1.0,http://www.robocoderepository.com/BotFiles/3645/ry.Worst_1.0.jar<br /> rz.Aleph 0.34,http://www.robocoderepository.com/BotFiles/1993/rz.Aleph_0.34.jar<br /> rz.Apollon 0.23,http://www.robocoderepository.com/BotFiles/2098/rz.Apollon_0.23.jar<br /> rz.Artist 0.2,http://www.robocoderepository.com/BotFiles/2156/rz.Artist_0.2.jar<br /> rz.GlowBlow 2.31,http://www.robocoderepository.com/BotFiles/1354/rz.GlowBlow_2.31.jar<br /> rz.GlowBlowAPM 1.0,http://www.robocoderepository.com/BotFiles/1382/rz.GlowBlowAPM_1.0.jar<br /> rz.GlowBlowMelee 1.4,http://www.robocoderepository.com/BotFiles/1436/rz.GlowBlowMelee_1.4.jar<br /> rz.HawkOnFire 0.1,http://www.robocoderepository.com/BotFiles/1575/rz.HawkOnFire_0.1.jar<br /> rz.SmallDevil 1.502,http://www.robocoderepository.com/BotFiles/1322/rz.SmallDevil_1.502.jar<br /> sadoner.killer 0.2,http://www.robocoderepository.com/BotFiles/4020/sadoner.killer_0.2.jar<br /> sam.ChipmunkDuelist 1.0,http://www.robocoderepository.com/BotFiles/3094/sam.ChipmunkDuelist_1.0.jar<br /> sam.Samspin 1.0,http://www.robocoderepository.com/BotFiles/2823/sam.Samspin_1.0.jar<br /> sanyi.mikrobi.Roberto 1.0,http://www.robocoderepository.com/BotFiles/3929/sanyi.mikrobi.Roberto_1.0.jar<br /> sch.Simone 0.3d,http://www.robocoderepository.com/BotFiles/374/sch.Simone_0.3d.jar<br /> serenity.moonlightBat 1.17,http://www.robocoderepository.com/BotFiles/2877/serenity.moonlightBat_1.17.jar<br /> serenity.nonSense 1.39,http://www.robocoderepository.com/BotFiles/3586/serenity.nonSense_1.39.jar<br /> serenity.serenityFire 1.29,http://www.robocoderepository.com/BotFiles/3071/serenity.serenityFire_1.29.jar<br /> sgp.JollyNinja 3.53,http://www.robocoderepository.com/BotFiles/183/sgp.JollyNinja_3.53.jar<br /> sgp.MadHatter 4.13,http://www.robocoderepository.com/BotFiles/156/sgp.MadHatter_4.13.jar<br /> sgp.nano.FurryLeech 1.0,http://www.robocoderepository.com/BotFiles/802/sgp.nano.FurryLeech_1.0.jar<br /> sgp.ShiningBeetle 1.1,http://www.robocoderepository.com/BotFiles/498/sgp.ShiningBeetle_1.1.jar<br /> sgp.SleepingGoat 1.1,http://www.robocoderepository.com/BotFiles/500/sgp.SleepingGoat_1.1.jar<br /> SHAM.WOW 1.4,http://darkcanuck.net/rumble/robots/SHAM.WOW_1.4.jar<br /> shinh.Entangled 0.3,http://www.robocoderepository.com/BotFiles/1070/shinh.Entangled_0.3.jar<br /> shrub.Silver v048,http://www.robocoderepository.com/BotFiles/449/shrub.Silver_v048.jar<br /> shrub.Vapour v159,http://www.robocoderepository.com/BotFiles/2654/shrub.Vapour_v159.jar<br /> shu.nitro.LENIN .T34,http://www.robocoderepository.com/BotFiles/1956/shu.nitro.LENIN_.T34.jar<br /> sigterm.Sigterm 1.0,http://darkcanuck.net/rumble/robots/sigterm.Sigterm_1.0.jar<br /> simonton.beta.LifelongObsession 0.5.1,http://www.robocoderepository.com/BotFiles/3195/simonton.beta.LifelongObsession_0.5.1.jar<br /> simonton.GFNano_D 3.1b,http://www.robocoderepository.com/BotFiles/3114/simonton.GFNano_D_3.1b.jar<br /> simonton.nano.WeekendObsession_S 1.7,http://www.robocoderepository.com/BotFiles/3117/simonton.nano.WeekendObsession_S_1.7.jar<br /> simonton.mega.SniperFrog 1.0.fix2,http://rednaxela-robocode.dyndns.org/data/robots/simonton.mega.SniperFrog_1.0.fix2.jar<br /> simonton.micro.GFMicro 1.0,http://darkcanuck.net/rumble/robots/simonton.micro.GFMicro_1.0.jar<br /> simonton.micro.WeeklongObsession 3.4.1,http://darkcanuck.net/rumble/robots/simonton.micro.WeeklongObsession_3.4.1.jar<br /> simonton.mini.WeeksOnEnd 1.10.4,http://darkcanuck.net/rumble/robots/simonton.mini.WeeksOnEnd_1.10.4.jar<br /> skm.butterfly 1.0,http://www.robocoderepository.com/BotFiles/3868/sean1.jar<br /> skm.Ryubot 1.0,http://www.robocoderepository.com/BotFiles/3594/skm.Ryubot_1.0.jar<br /> skm.PateranBotlock2 1.0,http://www.robocoderepository.com/BotFiles/3591/skm.PateranBotlock2_1.0.jar<br /> sL300.Mozart life,http://www.robocoderepository.com/BotFiles/1992/sL300.Mozart_life.jar<br /> sm.Devil 7.3,http://www.robocoderepository.com/BotFiles/1481/sm.Devil_7.3.jar<br /> sng.arco.Arco 0.0,http://www.robocoderepository.com/BotFiles/3279/sng.arco.Arco_0.0.jar<br /> sos.SOS 1.0,http://www.robocoderepository.com/BotFiles/3489/sos.SOS_1.0.jar<br /> spinnercat.CopyKat 1.2.3,http://www.robocoderepository.com/BotFiles/3818/spinnercat.CopyKat_1.2.3.jar<br /> spinnercat.Limit .01,http://www.robocoderepository.com/BotFiles/3659/spinnercat.Limit_.01.jar<br /> spinnercat.Kitten 1.6,http://www.robocoderepository.com/BotFiles/3819/spinnercat.Kitten_1.6.jar<br /> spinnercat.haiku.Refrigerator 1.1,http://www.robocoderepository.com/BotFiles/3688/spinnercat.haiku.Refrigerator_1.1.jar<br /> spinnercat.mega.Tardis 1.2,http://www.robocoderepository.com/BotFiles/3692/spinnercat.mega.Tardis_1.2.jar<br /> spinnercat.Robovirus 2.718,http://www.robocoderepository.com/BotFiles/3657/spinnercat.Robovirus_2.718.jar<br /> sqTank.waveSurfing.LionWWSVMvoid 0.01,http://www.robocoderepository.com/BotFiles/3436/sqTank.waveSurfing.LionWWSVMvoid_0.01.jar<br /> starpkg.StarViewerZ 1.26,http://www.robocoderepository.com/BotFiles/1931/starpkg.StarViewerZ_1.26.jar<br /> staticline.Whiskey 0.5.3,http://www.robocoderepository.com/BotFiles/3972/staticline.Whiskey_0.5.3.jar<br /> staticline.whiskey.Whiskey 0.6,http://rednaxela-robocode.dyndns.org/data/robot_archive/staticline.whiskey.Whiskey_0.6.jar<br /> stefw.Tigger 0.0.23,http://darkcanuck.net/rumble/robots/stefw.Tigger_0.0.23.jar<br /> stelo.Chord 1.0,http://darkcanuck.net/rumble/robots/stelo.Chord_1.0.jar<br /> stelo.FretNano 1.1,http://darkcanuck.net/rumble/robots/stelo.FretNano_1.1.jar<br /> stelo.Lifestealer 1.0,http://darkcanuck.net/rumble/robots/stelo.Lifestealer_1.0.jar<br /> stelo.MatchupMini 1.1,http://darkcanuck.net/rumble/robots/stelo.MatchupMini_1.1.jar<br /> stelo.MatchupMicro 1.2,http://darkcanuck.net/rumble/robots/stelo.MatchupMicro_1.2.jar<br /> stelo.MatchupAGF 1.1,http://darkcanuck.net/rumble/robots/stelo.MatchupAGF_1.1.jar<br /> stelo.MatchupWS 1.2c,http://darkcanuck.net/rumble/robots/stelo.MatchupWS_1.2c.jar<br /> stelo.Mirror 1.1,http://www.robocoderepository.com/BotFiles/3034/stelo.Mirror_1.1.jar<br /> stelo.MirrorMicro 1.1,http://darkcanuck.net/rumble/robots/stelo.MirrorMicro_1.1.jar<br /> stelo.MirrorNano 1.4,http://darkcanuck.net/rumble/robots/stelo.MirrorNano_1.4.jar<br /> stelo.MoojukNano 1.2,http://darkcanuck.net/rumble/robots/stelo.MoojukNano_1.2.jar<br /> stelo.PastFuture 2.1.9,http://www.robocoderepository.com/BotFiles/3910/stelo.PastFuture_2.1.9.jar<br /> stelo.PatternRobot 1.0,http://www.robocoderepository.com/BotFiles/2995/stelo.PatternRobot_1.0.jar<br /> stelo.PianistNano 1.3,http://darkcanuck.net/rumble/robots/stelo.PianistNano_1.3.jar<br /> stelo.RamTrackSurfer 1.2,http://darkcanuck.net/rumble/robots/stelo.RamTrackSurfer_1.2.jar<br /> stelo.Randomness 1.1,http://www.robocoderepository.com/BotFiles/3021/stelo.Randomness_1.1.jar<br /> stelo.Spread 0.2,http://www.robocoderepository.com/BotFiles/3922/stelo.Spread_0.2.jar<br /> stelo.SteloTestNano 1.0,http://darkcanuck.net/rumble/robots/stelo.SteloTestNano_1.0.jar<br /> stelo.UnfoolableNano 1.0,http://darkcanuck.net/rumble/robots/stelo.UnfoolableNano_1.0.jar<br /> stelo.UntouchableNano 1.4,http://darkcanuck.net/rumble/robots/stelo.UntouchableNano_1.4.jar<br /> step.nanoPri 1.0,http://www.robocoderepository.com/BotFiles/2996/step.nanoPri_1.0.jar<br /> step.NanoBidu 1.0,http://www.robocoderepository.com/BotFiles/3014/step.NanoBidu_1.0.jar<br /> stf.PanzerGeneral 0.1,http://www.robocoderepository.com/BotFiles/2233/stf.PanzerGeneral_0.1.jar<br /> stordy.StordyBot 1.0,http://sites.google.com/site/stordyrobo/Home/stordy.StordyBot_1.0.jar<br /> strider.Festis 1.2.1,http://www.robocoderepository.com/BotFiles/2355/strider.Festis_1.2.1.jar<br /> strider.Mer 1.1.0,http://www.robocoderepository.com/BotFiles/2360/strider.Mer_1.1.0.jar<br /> stuff.Vlad 0.1,http://www.robocoderepository.com/BotFiles/3701/stuff.Vlad_0.1.jar<br /> sul.NanoR2 1.32,http://www.robocoderepository.com/BotFiles/3348/sul.NanoR2_1.32.jar<br /> sul.Pinkbot 1.1,http://www.robocoderepository.com/BotFiles/3346/sul.Pinkbot_1.1.jar<br /> sul.Bicephal 1.2,http://www.robocoderepository.com/BotFiles/3343/sul.Bicephal_1.2.jar<br /> sul.BlueBot 1.0,http://www.robocoderepository.com/BotFiles/3347/sul.BlueBot_1.0.jar<br /> SuperSample.SuperCrazy 1.0,http://file.csdgn.org/robocode/SuperSample.SuperCrazy_1.0.jar<br /> syl.Centipede 0.5,http://www.robocoderepository.com/BotFiles/1254/syl.Centipede_0.5.jar<br /> synapse.Geomancy 15,http://sites.google.com/site/synapsebots/home/synapse.Geomancy_15.jar?attredirects=0<br /> synapse.rsim.GeomancyBS 0.11,http://robocoderepository.com/BotFiles/3758/synapse.rsim.GeomancyBS_0.11.jar<br /> synnalagma.NeuralPremier 0.51,http://www.robocoderepository.com/BotFiles/1557/synnalagma.NeuralPremier_0.51.jar<br /> synnalagma.test.MiniNeural 1.1,http://www.robocoderepository.com/BotFiles/1754/synnalagma.test.MiniNeural_1.1.jar<br /> tad.Dalek98 0.98,http://darkcanuck.net/rumble/robots/tad.Dalek98_0.98.jar<br /> takeBot.SpinSpiral 1.2,http://www.robocoderepository.com/BotFiles/312/takeBot.SpinSpiral_1.2.jar<br /> takeBot.SpiralCrash 1.0,http://www.robocoderepository.com/BotFiles/1013/takeBot.SpiralCrash_1.0.jar<br /> takeBot.WeavingWiggle 1.1,http://www.robocoderepository.com/BotFiles/1012/takeBot.WeavingWiggle_1.1.jar<br /> tango.Recrimpo 2.51,http://www.robocoderepository.com/BotFiles/2015/tango.Recrimpo_2.51.jar<br /> taqho.taqbot 1.0,http://www.robocoderepository.com/BotFiles/1316/taqho.taqbot_1.0.jar<br /> tcf.Drifter 29,http://www.7sun.com/robocode/robots/tcf.Drifter_29.jar<br /> tcf.Repat3 2,http://www.robocoderepository.com/BotFiles/3328/tcf.Repat3_2.jar<br /> techdude.kombat.FlamingKombat 1.5,http://www.robocoderepository.com/BotFiles/2810/techdude.kombat.FlamingKombat_1.5.jar<br /> techdude.Class2C.Class2C 0.1,http://www.robocoderepository.com/BotFiles/3078/techdude.Class2C.Class2C_0.1.jar<br /> test.Podgy 4.0,http://www.robocoderepository.com/BotFiles/3214/test.Podgy_4.0.jar<br /> test.Fuzzer 1.0.1,http://www.robocoderepository.com/BotFiles/3345/test.Fuzzer_1.0.1.jar<br /> testantiswapgun.AntiSwap 1.0,http://www.robocode.ilbello.com/asd.AntiSwap_1.0.jar<br /> throxbot.ThroxBot 0.1,http://www.robocoderepository.com/BotFiles/2548/throxbot.ThroxBot_0.1.jar<br /> tide.pear.Pear 0.62.1,http://www.robocoderepository.com/BotFiles/2393/tide.pear.Pear_0.62.1.jar<br /> timmit.micro.TimXJ 0.22,http://www.robocoderepository.com/BotFiles/1683/timmit.micro.TimXJ_0.22.jar<br /> timmit.mini.TimVA 0.43,http://www.robocoderepository.com/BotFiles/1681/timmit.mini.TimVA_0.43.jar<br /> timmit.nano.TimCat 0.13,http://www.robocoderepository.com/BotFiles/1600/timmit.nano.TimCat_0.13.jar<br /> timmit.nano.TimDog 0.33,http://www.robocoderepository.com/BotFiles/1602/timmit.nano.TimDog_0.33.jar<br /> timmit.TimmiT 0.22,http://www.robocoderepository.com/BotFiles/1468/timmit.TimmiT_0.22.jar<br /> TJ.Exupery 1.39,http://www.robocoderepository.com/BotFiles/3970/TJ.Exupery1.39.jar<br /> tjk.deBroglie 0.66,http://robocoderepository.com/BotFiles/3989/tjk.deBroglie_0.66.jar<br /> tlp.ThreeLeggedPig 1,http://pages.prodigy.net/franz1/house/tlp.ThreeLeggedPig_1.jar<br /> tm.Yuugao 1.0,http://www.robocoderepository.com/BotFiles/1056/tm.Yuugao_1.0.jar<br /> tobe.calypso.Calypso 4.1,http://www.robocoderepository.com/BotFiles/784/tobe.calypso.Calypso_4.1.jar<br /> tobe.Fusion 1.0,http://www.robocoderepository.com/BotFiles/649/tobe.Fusion_1.0.jar<br /> tobe.mini.Charon 0.9,http://www.robocoderepository.com/BotFiles/836/tobe.mini.Charon_0.9.jar<br /> tobe.Relativity 3.9,http://www.robocoderepository.com/BotFiles/360/tobe.Relativity_3.9.jar<br /> tobe.Saturn lambda,http://www.robocoderepository.com/BotFiles/685/tobe.Saturn_lambda.jar<br /> tornyil.bottomup.BottomUp 1.05,http://www.alpha-consulting.hu/robo/tornyil.bottomup.BottomUp_1.05.jar<br /> tornyil.Lajcsi2.Lajcsi2sm 1.0,http://www.alpha-consulting.hu/robo/tornyil.Lajcsi2.Lajcsi2sm_1.0.jar<br /> toz.Gnome 1.1,http://darkcanuck.net/rumble/robots/toz.Gnome_1.1.jar<br /> trab.Crusader 0.1.7,http://www.stud.ntnu.no/~grashei/bots/trab.Crusader_0.1.7.jar<br /> trab.nano.AinippeNano 1.3,http://www.stud.ntnu.no/~grashei/bots/trab.nano.AinippeNano_1.3.jar<br /> tw.Exterminator 1.0,http://www.robocoderepository.com/BotFiles/3607/tw.Exterminator_1.0.jar<br /> tzu.TheArtOfWar 1.2,http://darkcanuck.net/rumble/robots/tzu.TheArtOfWar_1.2.jar<br /> uccc.Dorito 1.12,http://www.devfluid.com/csc_w/images/e/e9/Uccc.Dorito_1.12.jar<br /> uccc.MilkyWay 1.01,http://www.devfluid.com/csc_w/images/a/a6/Uccc.MilkyWay_1.01.jar<br /> uccc.RingDing 1.12,http://www.devfluid.com/csc_w/images/5/5f/Uccc.RingDing_1.12.jar<br /> uccc.Scrapple 1.0,http://www.devfluid.com/csc_w/images/7/7a/Uccc.Scrapple_1.0.jar<br /> urdos.URDOS 1.3,http://darkcanuck.net/rumble/robots/urdos.URDOS_1.3.jar<br /> usa.nano.Nemo 2.0,http://www.robocoderepository.com/BotFiles/2045/usa.nano.Nemo_2.0.jar<br /> vic.Locke 0.7.5.5,http://www.robocoderepository.com/BotFiles/2115/vic.Locke_0.7.5.5.jar<br /> vft.Valkyrie 1.0,http://www.robocoderepository.com/BotFiles/3009/vft.Valkyrie_1.0.jar<br /> vft.Hrist 1.0,http://darkcanuck.net/rumble/robots/vft.Hrist_1.0.jar<br /> vjik.UnViolation 1.1,http://www.robocoderepository.com/BotFiles/3886/vjik.UnViolation_1.1.jar<br /> voidious.Diamond 1.5.38b,http://www.dijitari.com/void/robocode/voidious.Diamond_1.5.38b.jar<br /> voidious.Dookious 1.573c,http://www.dijitari.com/void/robocode/voidious.Dookious_1.573c.jar<br /> voidious.micro.Jen 1.11,http://www.dijitari.com/void/robocode/voidious.micro.Jen_1.11.jar<br /> voidious.mini.Komarious 1.88,http://www.dijitari.com/void/robocode/voidious.mini.Komarious_1.88.jar<br /> vuen.Fractal 0.55,http://www.robocoderepository.com/BotFiles/1579/vuen.Fractal_0.55.jar<br /> wcsv.Engineer.Engineer 0.5.4,http://darkcanuck.net/rumble/robots/wcsv.Engineer.Engineer_0.5.4.jar<br /> wcsv.PowerHouse.PowerHouse 1.7e3,http://darkcanuck.net/rumble/robots/wcsv.PowerHouse.PowerHouse_1.7e3.jar<br /> wcsv.mega.PowerHouse2 0.2,http://darkcanuck.net/rumble/robots/wcsv.mega.PowerHouse2_0.2.jar<br /> wcsv.Stampede 1.3.3,http://www.robocoderepository.com/BotFiles/2527/wcsv.Stampede_1.3.3.jar<br /> wcsv.Stampede2.Stampede2 1.1.0,http://www.robocoderepository.com/BotFiles/2714/wcsv.Stampede2.Stampede2_1.1.0.jar<br /> WdV.Lesserbee 0.01,http://www.robocoderepository.com/BotFiles/4046/WdV.Lesserbee_0.01.jar<br /> whind.Constitution 0.7.1,http://www.robocoderepository.com/BotFiles/2812/whind.Constitution_0.7.1.jar<br /> whind.Strength 0.6.4,http://whindgames.50webs.com/otherstuff/whind.Strength_0.6.4.jar<br /> whind.StrengthBee 0.6.4,http://whindgames.50webs.com/otherstuff/whind.StrengthBee_0.6.4.jar<br /> whind.Wisdom 0.5.1,http://www.robocoderepository.com/BotFiles/2742/whind.Wisdom_0.5.1.jar<br /> wiki.BasicGFSurfer 1.02,http://www.dijitari.com/void/robocode/wiki.BasicGFSurfer_1.02.jar<br /> wiki.mako.MakoHT 1.2.2.1,http://www.robocoderepository.com/BotFiles/1374/wiki.mako.MakoHT_1.2.2.1.jar<br /> wiki.mini.BlackDestroyer 0.9.0,http://www.robocoderepository.com/BotFiles/1927/wiki.mini.BlackDestroyer_0.9.0.jar<br /> wiki.mini.GouldingiHT 1.0,http://www.robocoderepository.com/BotFiles/1383/wiki.mini.GouldingiHT_1.0.jar<br /> wiki.mini.Griffon 0.1,http://www.robocoderepository.com/BotFiles/1774/wiki.mini.Griffon_0.1.jar<br /> wiki.mini.Sedan 1.0,http://www.robocoderepository.com/BotFiles/1676/wiki.mini.Sedan_1.0.jar<br /> wiki.nano.DevilFISH 1.0,http://www.robocoderepository.com/BotFiles/2235/wiki.nano.DevilFISH_1.0.jar<br /> wiki.nano.RaikoNano 1.1,http://www.robocoderepository.com/BotFiles/2163/wiki.nano.RaikoNano_1.1.jar<br /> wiki.WaveRammer 1.0,http://www.robocoderepository.com/BotFiles/3505/wiki.WaveRammer_1.0.jar<br /> wiki.Wolverine 2.1,http://darkcanuck.net/rumble/robots/wiki.Wolverine_2.1.jar<br /> wilson.Chameleon 0.91,http://www.robocoderepository.com/BotFiles/1608/wilson.Chameleon_0.91.jar<br /> winamp32.micro.MicroMacro 1.0,http://www.robocoderepository.com/BotFiles/2891/winamp32.micro.MicroMacro_1.0.jar<br /> wit.Chuliath 1.0,http://www.robocoderepository.com/BotFiles/2306/wit.Chuliath_1.0.jar<br /> wit.Deep7 2.0,http://www.robocoderepository.com/BotFiles/2313/wit.Deep7_2.0.jar<br /> xandercat.XanderCat 3.1,http://www.distantvisions.net/robocode/xandercat.XanderCat-3.1.jar<br /> xandercat.XanderCat 3.2,http://www.distantvisions.net/robocode/xandercat.XanderCat-3.2.jar<br /> xandercat.XanderCat 3.3,http://www.distantvisions.net/robocode/xandercat.XanderCat-3.3.jar<br /> xiongan.Xiongan 1.1,http://www.robocoderepository.com/BotFiles/3565/xiongan.Xiongan_1.1.jar<br /> yarghard.Y101 1.0,http://sliwa.ws/RoboCode/yarghard.Y101_1.0.jar<br /> yk.JahMicro 1.0,http://www.robocoderepository.com/BotFiles/3033/yk.JahMicro_1.0.jar<br /> yk.JahRoslav 1.1,http://www.robocoderepository.com/BotFiles/3032/yk.JahRoslav_1.1.jar<br /> zen.Lindada 0.2,http://www.robocoderepository.com/BotFiles/1679/zen.Lindada_0.2.jar<br /> zeze2.OperatorZeze 1.05,http://www.robocoderepository.com/BotFiles/3330/zeze2.OperatorZeze_1.05.jar<br /> zch.David 0.21,http://www.robocoderepository.com/BotFiles/3575/zch.David_0.21.jar<br /> zch.Hirkan 0.11,http://www.robocoderepository.com/BotFiles/1288/zch.Hirkan_0.11.jar<br /> zh.UnderDog 0.0.2,http://www.robocoderepository.com/BotFiles/3053/zh.UnderDog_0.0.2.jar<br /> zyx.mega.YersiniaPestis 3.0,http://darkcanuck.net/rumble/robots/zyx.mega.YersiniaPestis_3.0.jar<br /> zyx.micro.Ant 1.1,http://www.robocoderepository.com/BotFiles/3481/zyx.micro.Ant_1.1.jar<br /> zyx.nano.Ant 1.1,http://www.robocoderepository.com/BotFiles/3493/zyx.nano.Ant_1.1.jar<br /> zyx.nano.EscherichiaColi 1.0,http://darkcanuck.net/rumble/robots/zyx.nano.EscherichiaColi_1.0.jar<br /> zyx.nano.RedBull 1.0,http://darkcanuck.net/rumble/robots/zyx.nano.RedBull_1.0.jar<br /> &lt;/pre&gt;<br /> ----<br /> '''''No chatting on this page. Use the /ParticipantsChat page for that.'''''<br /> <br /> '''''Removed because the jarcontent/filename is not correct'''''&lt;br&gt;<br /> ''cberendt.Bot1 0.160''&lt;br&gt;<br /> ''dmsr.MiniR101 0.6''&lt;br&gt;<br /> ''henriquevilela.TieFighter 0.1,3224''&lt;br&gt;<br /> ''jgap.Aspirant_7980_gen7 1.0,3552''br&gt;<br /> ''jgap.Aspirant_13029_gen7 1.0,3553''&lt;br&gt;<br /> ''techdude.Carruthers 1.2.6''&lt;br&gt;<br /> ''uccc.Orbiter 1.0''&lt;br&gt;<br /> ''WhoAmI.WhoAmI 1.00''&lt;br&gt;<br /> <br /> '''''Removed until file corruption is resolved:'''''<br /> <br /> ''cas.CelsoKiller 1.0,3465''<br /> <br /> '''''Removed due to almost always giving '0' scores:'''''<br /> <br /> ''com.syncleus.robocode.Dreadnaught 0.1,3426''&lt;br&gt;<br /> ''lazarecki.PinkerStinker 0.1,http://www.robocoderepository.com/BotFiles/3824/lazarecki.PinkerStinker_0.1.jar''<br /> <br /> '''''Removed because it's incorrectly packaged:'''''<br /> <br /> ''Indesh.Indesh 1.1,http://jakobserlier.250free.com/Indesh.jar''<br /> <br /> '''''Removed due to 1.6.1.4 incompatibility'''''<br /> <br /> ''extra.LightSauce 0.01,http://www.robocoderepository.com/BotFiles/4031/extra.LightSauce_0.01.jar''&lt;br&gt;<br /> ''extra.Sauce .01,http://robocoderepository.com/BotFiles/4029/extra.Sauce_.01.jar''<br /> <br /> <br /> <br /> ----<br /> <br /> '''''Removed due to WontFix issues in Robocode 1.7+:'''''&lt;br&gt;<br /> ''* Hviela: ([[http://sourceforge.net/tracker/?func=detail&amp;aid=2953268&amp;group_id=37202&amp;atid=419486 SF #2953268]])''&lt;br&gt;<br /> '': hvilela.HVilela 0.9.3,http://henrique.vilela.googlepages.com/hvilela.HVilela_0.9.3.jar''&lt;br&gt;<br /> ''* Barney (Tries to write files without using RobocodeOutputStream. Robocode 1.7 punishes for that more harshly which will give 0 scores)&lt;br&gt;<br /> '': Homer.Barney 1.0,http://www.robocoderepository.com/BotFiles/1932/Homer.Barney_1.0.jar&lt;br&gt;</div>

Miked0801 http://robowiki.net/w/index.php?title=User_talk:Miked0801&diff=19438 2011-06-04T07:38:26Z

<p>Miked0801: </p> <hr /> <div>Hey! Do you have to remove the &quot;Inactive Authors&quot; category now? =) --[[User:Voidious|Voidious]] 17:31, 28 April 2009 (UTC)<br /> <br /> Lol - I think I already did. Gotta upload an Infinty page now that I fixed a minor bug with him.<br /> <br /> Hey man, I happened to randomly notice that an old version of BrokenSword is appearing in the melee rumble. Did you point your client at the new [[RoboRumble/Participants/Melee]] page? Actually I don't know how that would happen anyway, unless it uses the last participants list it saw if it can't find the list. Or maybe you just had some cached / unuploaded results from the last time you ran it? --[[User:Voidious|Voidious]] 20:06, 28 April 2009 (UTC)<br /> <br /> Good call. Just fixed that. Sorry for the out of date files being added. I'm running the new link now. Someone's going to have to clean up my mess on that one. --[[User:Miked0801|Miked0801]]<br /> <br /> ----<br /> <br /> Just to let you know, I've noticed you signing with &lt;nowiki&gt;--[[User:Miked0801|Miked0801]] or --[[User:Miked0801]]&lt;/nowiki&gt;. Just to let you know, on the new wiki you can simply sign with &lt;nowiki&gt;--~~~~&lt;/nowiki&gt; (or the signature button if you have js enabled), and it'll automatically turn it to a complete signature including timestamp even. Just a tip :) --[[User:Rednaxela|Rednaxela]] 17:01, 29 April 2009 (UTC)<br /> <br /> : Yep, someone else let me know that too. :) --[[User:Miked0801|Miked0801]] 20:36, 29 April 2009 (UTC)<br /> <br /> Oh hey, speaking of code shrinking, I just thought I'd point out the new &quot;Rules&quot; class if you hadn't seen it. I resisted using it for the longest time to ensure compatibility with old Robocodes, but it's been in there for a while and we now have a way of filtering out old clients anyway. So now I'm compiling with Jikes and Robocode 1.4.9, so I can use Rules but still compile with Jikes. --[[User:Voidious|Voidious]] 14:21, 7 May 2009 (UTC)<br /> <br /> Alright, what is this rules class you speak of? --[[User:Miked0801|Miked0801]] 17:54, 7 May 2009 (UTC)<br /> <br /> The [http://robocode.sourceforge.net/docs/robocode/robocode/Rules.html robocode.Rules] class can be used to calculate the max turn rate, bullet power, bullet damage and so on. It is the one use by game engine, and it is now public. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 18:12, 7 May 2009 (UTC)<br /> <br /> (edit conflict) It's a utilities class that provides methods for a bunch of basic stuff, like bullet speed, damage, turn rate, etc. [http://robocode.sourceforge.net/docs/robocode/robocode/Rules.html Rules class in Robocode API]. It's definitely an unfair advantage over legacy bots, but that's your decision to grapple with. =) --[[User:Voidious|Voidious]] 18:16, 7 May 2009 (UTC)<br /> <br /> I checked it out and none of its functions would have use in [[DustBunny]] nor [[Infinity]], though bullet speed would become useful for linear leading if I stored my firepower instead of just calculating in place. --[[User:Miked0801|Miked0801]] 20:33, 7 May 2009 (UTC)<br /> <br /> ----<br /> <br /> Your client seems to be uploading 1-on-1 results for retired bots? stelo.PastFuture 1.0, for example. This is easy to fix but if there is a bigger problem going on... --[[User:Darkcanuck|Darkcanuck]] 03:55, 8 May 2009 (UTC)<br /> <br /> Perhaps I've got the wrong page pointed at (again) for rumble. I'll check when I get home. --[[User:Miked0801|Miked0801]] 20:27, 8 May 2009 (UTC)<br /> <br /> ----<br /> <br /> Hi, it's good to see a 'veteran' coming back and working on nanos. :D I have been on rest since the beginning of April, but now I think I should do something to get back the top 3 rank. ;) --[[User:Robar|HUNRobar]] 16:02, 13 May 2009 (UTC)<br /> :First Place in Melee and 1v1 are sooo close. I got back into this again because I've got some late night hours free with a newborn - just like last time I got into the fun. Come on, just 1% in each. There's gotta be something I can tweak to get that right? :) --[[User:Miked0801|Miked0801]] 18:49, 13 May 2009 (UTC)<br /> <br /> Just watch out because I'm going to make an update on my top bots. :) See Pugio 1.3 for example. ;) --[[User:Robar|HUNRobar]] 19:13, 13 May 2009 (UTC)<br /> : Wow, nice update. Game on! --[[User:Miked0801|Miked0801]] 20:28, 13 May 2009 (UTC)<br /> <br /> Are we allowed to use:<br /> Vector&lt;Double&gt; vect = new Vector&lt;Double&gt;();<br /> <br /> type things and set the &quot;-source 1.5&quot; flag for our bots? If so, that will save some codesize for me.<br /> <br /> Yep, Robocode has required Java 5 for a while now, so that should be fine. I use generics in [[Diamond]] and it definitely ran fine in my 1.5.4 RoboRumble clients, which is the oldest version allowed for the rumble. So that saves code size, eh? Hmm, thanks for the info... =) --[[User:Voidious|Voidious]] 01:12, 27 May 2009 (UTC)<br /> <br /> : Oh yeah, but I forgot, Jikes only supports Java 1.4, that's why I never used generics in my MiniBots. But I'll definitely compare it to normal javac with generics now that I know this. --[[User:Voidious|Voidious]] 01:15, 27 May 2009 (UTC)<br /> : Sorry for triple post, but what makes you say it will save you code size? I tried changing Komarious to use generics for its one collection, and it had no effect on code size. --[[User:Voidious|Voidious]] 01:23, 27 May 2009 (UTC)<br /> <br /> :: Lol, I just realized I never ran codesize on my micro with generics in place. Doh! Well, generics look cleaner if anything else :) --[[User:Miked0801|Miked0801]] 02:25, 27 May 2009 (UTC)<br /> <br /> ::: Generic only available in source, it will ease out at compile time and every casting will come back (try decompile the generic-ize class and see) The generic only to check the type sefty. This is from java specification. And because the codesize library check the byte code, not the not the source code so this has no effect. And this is not require Java 5 to run since it isn't in the byte code, ad long as you only use the classes from the target version.<br /> <br /> ----<br /> <br /> While scanning my local harddrive, I found a newer version of Radnor.DoctorBob (1.50). Any objections to me entering this into the fray and seeing how well it does in tandem with 1.42?<br /> : And removed. Failed experiment there.<br /> <br /> ----<br /> Does Kawigi's old floodGrapher stuff still work with the latest versions of Java for anyone else? I get tons of Javax.Swing exceptions when I try to view a graph. It looks like swing has be deprecrated. Is this so?<br /> : I've never tried FloodGrapher, but I'm almost certain swing is not deprecated, even in Java 7 beta versions, but may something changed that requires old code to work properly. --[[User:Zyx|zyx]] 02:05, 9 June 2009 (UTC)<br /> <br /> I use FloodGrapher myself. I think you are running Windows Vista then, because if you are running it as normal user, it will throw a lot of exceptions and generate NaN hit rate. You need to run it as administrator. I run with both Java 5 and Java 6 and it all work. If you are loading result from FloodGrapger saved file (not FloodMini saved file), you will need to add robocode.jar to classpath yourself. Andway, I bet PEZ's TGrapgher (aka FloodGrapher 1.0) is much more easier to use. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 02:44, 9 June 2009 (UTC)<br /> : I'm using XP Sp2 and while the program opens fine, it fails with all sorts of Swing exceptions for classes not found. No biggie as I got Pez's utility to work. Anyone know exactly what his FirePower/Distance values are that he decided to use A-E on? I'm guess 160 for the distance, but the rest is a guess.<br /> : Also, if you had to choose just 1 method of segmentation for guess factoring (against Nanos of course) do you think that distance would be the best one? My initial results seem to point at this, but was just wondering. Anyways, I'll have my first GF Nano done here shortly. --[[User:Miked0801|Miked0801]] 22:57, 9 June 2009 (UTC)<br /> <br /> : I don't know anything about PEZ's utility, but personally, I would definitely recommend lateral velocity over distance, and probably even absolute velocity over distance (seeing as code size is such an issue here and lateral is so expensive). But by all means, go with what your testing shows is best. =) --[[User:Voidious|Voidious]] 02:38, 10 June 2009 (UTC)<br /> <br /> : It seem to run fine with my old XP Sp3 (and Sp2 too before upgrade) Can you post the actual (partial?) exceptions? For the segmentation, I think lateral velocity is much important. Because many bots will be hit at the same GF at every segment (taking distance into account for flattener). &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 13:24, 10 June 2009 (UTC)<br /> <br /> ---<br /> I took a glance on your new nano. It's fascinating! Ok, it loses against some of my bots decently, but it scores awesomely against others. It scored 68% against nanolaulektrik!<br /> I'm looking forward to see the final rank. ;) --[[User:Robar|HUNRobar]] 21:33, 14 June 2009 (UTC)<br /> : Thanks. I had some inspiration from the 200k max conversation and went to town. I need to change RoboGrapher a bit to output a string per bot in the rumble to save me time (and accuracy in typing). That will help him out in other size catagories. I also, ideally, would average enemy velocity over a few ticks and add that to the guess factor velocity to be able to target true dodge, stop and go bots. That of course costs bytes :). My random movement code needs some tuning as well. But overall, I'm very pleased with this bot. I will put a hard limit of no more than 200k on the string though just to be fair. Maybe less. This bot would probably do ok in melee as well. I'll investigate that soon. I have to admit I was tempted to release no source until I had it tuned, but that wouldn't be fair. --[[User:Miked0801|Miked0801]] 22:22, 14 June 2009 (UTC)<br /> <br /> Is there any good way to get at the battle results from within a robot or are those classes restricted? --[[User:Miked0801|Miked0801]] 02:21, 16 June 2009 (UTC)<br /> <br /> : No, those classes are restricted unless you use -DNOSECURITY=true. I believe that in one-on-one, you can simulate the score calculator in your robot. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 02:55, 16 June 2009 (UTC)<br /> <br /> :: Just saw this go by in the recent changes... You can get scores and stuff from the Robot.onBattleEnded(BattleEndedEvent) method (also accessible from AdvancedRobots). The BattleEndedEvent has a method getResults() which returns a [[http://robocode.sourceforge.net/docs/robocode/ BattleResults]] object which contains fields you can access for all the columns of the results that pop up at the end of a battle. Not certain this is what you are looking for. --[[User:BenHorner|BenHorner]] 03:18, 16 June 2009 (UTC)<br /> ::: Either of these will work for me. Thanks. Expect my next blackbook update sometime tomorrow. My testbot is built and running through all the nanos now. --[[User:Miked0801|Miked0801]] 03:22, 16 June 2009 (UTC)<br /> :::: You must use my method since Skilgannon still ran 1.5.4 client... &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 03:24, 16 June 2009 (UTC)<br /> ::::: No I must not - it's for my local statistical gatherer only. That said, I'm using Excel and RoboResearch this time around to manage all my data. --[[User:Miked0801|Miked0801]] 05:31, 16 June 2009 (UTC)<br /> ::: There's a BattleEndedEvent? Interesting... --[[User:Darkcanuck|Darkcanuck]] 04:30, 16 June 2009 (UTC)<br /> ::: Interesting indeed... I'd personally suggest we try to phase out 1.5.4 asap... ;) --[[User:Rednaxela|Rednaxela]] 04:39, 16 June 2009 (UTC)<br /> :::: Darkcanuck, I think you should move on 1.7.1.3 instead =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 07:01, 16 June 2009 (UTC)<br /> :::: Yes, if 1.7.1.3 comes through with no rumble bugs, we could probably roll forward. Actually, with 1.6.1.4 so active, is there any reason to keep 1.5.4 or 1.6.0 alive? --[[User:Darkcanuck|Darkcanuck]] 07:16, 16 June 2009 (UTC)<br /> ::::: No, no reason to keep 1.5.4 or 1.6.0. At least, not in my opinion :) --[[User:Rednaxela|Rednaxela]] 13:26, 16 June 2009 (UTC)<br /> I added all the repository bots to my 1.7.1.3 install and it froze building the database, I'll file a bug this evening. --[[User:Skilgannon|Skilgannon]] 08:29, 16 June 2009 (UTC)<br /> <br /> Does anyone have a better site to upload bots to than the robocoderepository? Seems like it's down quite a bit. --[[User:Miked0801|Miked0801]] 02:28, 27 January 2010 (UTC)<br /> <br /> I personally use my university web space, but I hear [http://sites.google.com google sites] works fairly well and some others around here have recommended it. --[[User:Rednaxela|Rednaxela]] 03:10, 27 January 2010 (UTC)<br /> <br /> I reccommend Google Site too, buT i personally use my own web hosting. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 05:23, 27 January 2010 (UTC)<br /> <br /> ----<br /> Booted up my test suite. All still in order. Started with new bots. We'll see if I can get an update in by end of week... --[[User:Miked0801|Miked0801]] 04:34, 16 May 2011 (UTC)<br /> <br /> And updated. A bit late. I don't have local copies of extra.sauce or extra.lightsauce though. Considering they appear to be competing for worst in division, I'd be willing to vot efor them removed if someone doesn't have a local copy I could get a hold of... --[[User:Miked0801|Miked0801]] 07:38, 4 June 2011 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=User_talk:Miked0801&diff=19437 2011-06-04T07:38:00Z

<p>Miked0801: extra.sauce bots missing from my local suite. May effect rankings...</p> <hr /> <div>Hey! Do you have to remove the &quot;Inactive Authors&quot; category now? =) --[[User:Voidious|Voidious]] 17:31, 28 April 2009 (UTC)<br /> <br /> Lol - I think I already did. Gotta upload an Infinty page now that I fixed a minor bug with him.<br /> <br /> Hey man, I happened to randomly notice that an old version of BrokenSword is appearing in the melee rumble. Did you point your client at the new [[RoboRumble/Participants/Melee]] page? Actually I don't know how that would happen anyway, unless it uses the last participants list it saw if it can't find the list. Or maybe you just had some cached / unuploaded results from the last time you ran it? --[[User:Voidious|Voidious]] 20:06, 28 April 2009 (UTC)<br /> <br /> Good call. Just fixed that. Sorry for the out of date files being added. I'm running the new link now. Someone's going to have to clean up my mess on that one. --[[User:Miked0801|Miked0801]]<br /> <br /> ----<br /> <br /> Just to let you know, I've noticed you signing with &lt;nowiki&gt;--[[User:Miked0801|Miked0801]] or --[[User:Miked0801]]&lt;/nowiki&gt;. Just to let you know, on the new wiki you can simply sign with &lt;nowiki&gt;--~~~~&lt;/nowiki&gt; (or the signature button if you have js enabled), and it'll automatically turn it to a complete signature including timestamp even. Just a tip :) --[[User:Rednaxela|Rednaxela]] 17:01, 29 April 2009 (UTC)<br /> <br /> : Yep, someone else let me know that too. :) --[[User:Miked0801|Miked0801]] 20:36, 29 April 2009 (UTC)<br /> <br /> Oh hey, speaking of code shrinking, I just thought I'd point out the new &quot;Rules&quot; class if you hadn't seen it. I resisted using it for the longest time to ensure compatibility with old Robocodes, but it's been in there for a while and we now have a way of filtering out old clients anyway. So now I'm compiling with Jikes and Robocode 1.4.9, so I can use Rules but still compile with Jikes. --[[User:Voidious|Voidious]] 14:21, 7 May 2009 (UTC)<br /> <br /> Alright, what is this rules class you speak of? --[[User:Miked0801|Miked0801]] 17:54, 7 May 2009 (UTC)<br /> <br /> The [http://robocode.sourceforge.net/docs/robocode/robocode/Rules.html robocode.Rules] class can be used to calculate the max turn rate, bullet power, bullet damage and so on. It is the one use by game engine, and it is now public. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 18:12, 7 May 2009 (UTC)<br /> <br /> (edit conflict) It's a utilities class that provides methods for a bunch of basic stuff, like bullet speed, damage, turn rate, etc. [http://robocode.sourceforge.net/docs/robocode/robocode/Rules.html Rules class in Robocode API]. It's definitely an unfair advantage over legacy bots, but that's your decision to grapple with. =) --[[User:Voidious|Voidious]] 18:16, 7 May 2009 (UTC)<br /> <br /> I checked it out and none of its functions would have use in [[DustBunny]] nor [[Infinity]], though bullet speed would become useful for linear leading if I stored my firepower instead of just calculating in place. --[[User:Miked0801|Miked0801]] 20:33, 7 May 2009 (UTC)<br /> <br /> ----<br /> <br /> Your client seems to be uploading 1-on-1 results for retired bots? stelo.PastFuture 1.0, for example. This is easy to fix but if there is a bigger problem going on... --[[User:Darkcanuck|Darkcanuck]] 03:55, 8 May 2009 (UTC)<br /> <br /> Perhaps I've got the wrong page pointed at (again) for rumble. I'll check when I get home. --[[User:Miked0801|Miked0801]] 20:27, 8 May 2009 (UTC)<br /> <br /> ----<br /> <br /> Hi, it's good to see a 'veteran' coming back and working on nanos. :D I have been on rest since the beginning of April, but now I think I should do something to get back the top 3 rank. ;) --[[User:Robar|HUNRobar]] 16:02, 13 May 2009 (UTC)<br /> :First Place in Melee and 1v1 are sooo close. I got back into this again because I've got some late night hours free with a newborn - just like last time I got into the fun. Come on, just 1% in each. There's gotta be something I can tweak to get that right? :) --[[User:Miked0801|Miked0801]] 18:49, 13 May 2009 (UTC)<br /> <br /> Just watch out because I'm going to make an update on my top bots. :) See Pugio 1.3 for example. ;) --[[User:Robar|HUNRobar]] 19:13, 13 May 2009 (UTC)<br /> : Wow, nice update. Game on! --[[User:Miked0801|Miked0801]] 20:28, 13 May 2009 (UTC)<br /> <br /> Are we allowed to use:<br /> Vector&lt;Double&gt; vect = new Vector&lt;Double&gt;();<br /> <br /> type things and set the &quot;-source 1.5&quot; flag for our bots? If so, that will save some codesize for me.<br /> <br /> Yep, Robocode has required Java 5 for a while now, so that should be fine. I use generics in [[Diamond]] and it definitely ran fine in my 1.5.4 RoboRumble clients, which is the oldest version allowed for the rumble. So that saves code size, eh? Hmm, thanks for the info... =) --[[User:Voidious|Voidious]] 01:12, 27 May 2009 (UTC)<br /> <br /> : Oh yeah, but I forgot, Jikes only supports Java 1.4, that's why I never used generics in my MiniBots. But I'll definitely compare it to normal javac with generics now that I know this. --[[User:Voidious|Voidious]] 01:15, 27 May 2009 (UTC)<br /> : Sorry for triple post, but what makes you say it will save you code size? I tried changing Komarious to use generics for its one collection, and it had no effect on code size. --[[User:Voidious|Voidious]] 01:23, 27 May 2009 (UTC)<br /> <br /> :: Lol, I just realized I never ran codesize on my micro with generics in place. Doh! Well, generics look cleaner if anything else :) --[[User:Miked0801|Miked0801]] 02:25, 27 May 2009 (UTC)<br /> <br /> ::: Generic only available in source, it will ease out at compile time and every casting will come back (try decompile the generic-ize class and see) The generic only to check the type sefty. This is from java specification. And because the codesize library check the byte code, not the not the source code so this has no effect. And this is not require Java 5 to run since it isn't in the byte code, ad long as you only use the classes from the target version.<br /> <br /> ----<br /> <br /> While scanning my local harddrive, I found a newer version of Radnor.DoctorBob (1.50). Any objections to me entering this into the fray and seeing how well it does in tandem with 1.42?<br /> : And removed. Failed experiment there.<br /> <br /> ----<br /> Does Kawigi's old floodGrapher stuff still work with the latest versions of Java for anyone else? I get tons of Javax.Swing exceptions when I try to view a graph. It looks like swing has be deprecrated. Is this so?<br /> : I've never tried FloodGrapher, but I'm almost certain swing is not deprecated, even in Java 7 beta versions, but may something changed that requires old code to work properly. --[[User:Zyx|zyx]] 02:05, 9 June 2009 (UTC)<br /> <br /> I use FloodGrapher myself. I think you are running Windows Vista then, because if you are running it as normal user, it will throw a lot of exceptions and generate NaN hit rate. You need to run it as administrator. I run with both Java 5 and Java 6 and it all work. If you are loading result from FloodGrapger saved file (not FloodMini saved file), you will need to add robocode.jar to classpath yourself. Andway, I bet PEZ's TGrapgher (aka FloodGrapher 1.0) is much more easier to use. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 02:44, 9 June 2009 (UTC)<br /> : I'm using XP Sp2 and while the program opens fine, it fails with all sorts of Swing exceptions for classes not found. No biggie as I got Pez's utility to work. Anyone know exactly what his FirePower/Distance values are that he decided to use A-E on? I'm guess 160 for the distance, but the rest is a guess.<br /> : Also, if you had to choose just 1 method of segmentation for guess factoring (against Nanos of course) do you think that distance would be the best one? My initial results seem to point at this, but was just wondering. Anyways, I'll have my first GF Nano done here shortly. --[[User:Miked0801|Miked0801]] 22:57, 9 June 2009 (UTC)<br /> <br /> : I don't know anything about PEZ's utility, but personally, I would definitely recommend lateral velocity over distance, and probably even absolute velocity over distance (seeing as code size is such an issue here and lateral is so expensive). But by all means, go with what your testing shows is best. =) --[[User:Voidious|Voidious]] 02:38, 10 June 2009 (UTC)<br /> <br /> : It seem to run fine with my old XP Sp3 (and Sp2 too before upgrade) Can you post the actual (partial?) exceptions? For the segmentation, I think lateral velocity is much important. Because many bots will be hit at the same GF at every segment (taking distance into account for flattener). &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 13:24, 10 June 2009 (UTC)<br /> <br /> ---<br /> I took a glance on your new nano. It's fascinating! Ok, it loses against some of my bots decently, but it scores awesomely against others. It scored 68% against nanolaulektrik!<br /> I'm looking forward to see the final rank. ;) --[[User:Robar|HUNRobar]] 21:33, 14 June 2009 (UTC)<br /> : Thanks. I had some inspiration from the 200k max conversation and went to town. I need to change RoboGrapher a bit to output a string per bot in the rumble to save me time (and accuracy in typing). That will help him out in other size catagories. I also, ideally, would average enemy velocity over a few ticks and add that to the guess factor velocity to be able to target true dodge, stop and go bots. That of course costs bytes :). My random movement code needs some tuning as well. But overall, I'm very pleased with this bot. I will put a hard limit of no more than 200k on the string though just to be fair. Maybe less. This bot would probably do ok in melee as well. I'll investigate that soon. I have to admit I was tempted to release no source until I had it tuned, but that wouldn't be fair. --[[User:Miked0801|Miked0801]] 22:22, 14 June 2009 (UTC)<br /> <br /> Is there any good way to get at the battle results from within a robot or are those classes restricted? --[[User:Miked0801|Miked0801]] 02:21, 16 June 2009 (UTC)<br /> <br /> : No, those classes are restricted unless you use -DNOSECURITY=true. I believe that in one-on-one, you can simulate the score calculator in your robot. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 02:55, 16 June 2009 (UTC)<br /> <br /> :: Just saw this go by in the recent changes... You can get scores and stuff from the Robot.onBattleEnded(BattleEndedEvent) method (also accessible from AdvancedRobots). The BattleEndedEvent has a method getResults() which returns a [[http://robocode.sourceforge.net/docs/robocode/ BattleResults]] object which contains fields you can access for all the columns of the results that pop up at the end of a battle. Not certain this is what you are looking for. --[[User:BenHorner|BenHorner]] 03:18, 16 June 2009 (UTC)<br /> ::: Either of these will work for me. Thanks. Expect my next blackbook update sometime tomorrow. My testbot is built and running through all the nanos now. --[[User:Miked0801|Miked0801]] 03:22, 16 June 2009 (UTC)<br /> :::: You must use my method since Skilgannon still ran 1.5.4 client... &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 03:24, 16 June 2009 (UTC)<br /> ::::: No I must not - it's for my local statistical gatherer only. That said, I'm using Excel and RoboResearch this time around to manage all my data. --[[User:Miked0801|Miked0801]] 05:31, 16 June 2009 (UTC)<br /> ::: There's a BattleEndedEvent? Interesting... --[[User:Darkcanuck|Darkcanuck]] 04:30, 16 June 2009 (UTC)<br /> ::: Interesting indeed... I'd personally suggest we try to phase out 1.5.4 asap... ;) --[[User:Rednaxela|Rednaxela]] 04:39, 16 June 2009 (UTC)<br /> :::: Darkcanuck, I think you should move on 1.7.1.3 instead =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 07:01, 16 June 2009 (UTC)<br /> :::: Yes, if 1.7.1.3 comes through with no rumble bugs, we could probably roll forward. Actually, with 1.6.1.4 so active, is there any reason to keep 1.5.4 or 1.6.0 alive? --[[User:Darkcanuck|Darkcanuck]] 07:16, 16 June 2009 (UTC)<br /> ::::: No, no reason to keep 1.5.4 or 1.6.0. At least, not in my opinion :) --[[User:Rednaxela|Rednaxela]] 13:26, 16 June 2009 (UTC)<br /> I added all the repository bots to my 1.7.1.3 install and it froze building the database, I'll file a bug this evening. --[[User:Skilgannon|Skilgannon]] 08:29, 16 June 2009 (UTC)<br /> <br /> Does anyone have a better site to upload bots to than the robocoderepository? Seems like it's down quite a bit. --[[User:Miked0801|Miked0801]] 02:28, 27 January 2010 (UTC)<br /> <br /> I personally use my university web space, but I hear [http://sites.google.com google sites] works fairly well and some others around here have recommended it. --[[User:Rednaxela|Rednaxela]] 03:10, 27 January 2010 (UTC)<br /> <br /> I reccommend Google Site too, buT i personally use my own web hosting. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 05:23, 27 January 2010 (UTC)<br /> <br /> ----<br /> Booted up my test suite. All still in order. Started with new bots. We'll see if I can get an update in by end of week... --[[User:Miked0801|Miked0801]] 04:34, 16 May 2011 (UTC)<br /> <br /> And updated. A bit late. I don't have local copies of extra.sauce or extra.lightsauce though. Considering they appear to be competing for worst in division, I'd be willing to vot efor them removed if someone doesn't have a local copy I could get a hold of</div>

Miked0801 http://robowiki.net/w/index.php?title=RoboRumble/Participants&diff=19436 2011-06-04T05:03:26Z

<p>Miked0801: Removed old version. New version appears to dl fine.</p> <hr /> <div>{{:RoboRumble/Navigation}}<br /> <br /> ----<br /> Just add your bot name ('''as appears in the Robocode selector after packaging''', so including versionnumber) and the RobocodeRepository id number separated by &quot;,&quot; (there must be no space after the comma).&lt;br&gt; <br /> Please, make sure your bot is not in the list before adding it, and delete the old version if you are adding a new one.<br /> &lt;br&gt;<br /> The list is in '''alphabetical''' order. Add your bot in the right slot.<br /> <br /> ----<br /> &lt;pre&gt;<br /> ab.DengerousRoBatra 1.3,http://www.robocoderepository.com/BotFiles/3664/ab.DengerousRoBatra_1.3.jar<br /> abc.Shadow 3.83c,http://robocode.aclsi.pt/abc.Shadow_3.83c.jar<br /> abc.tron3.Tron 3.11,http://www.robocoderepository.com/BotFiles/2205/abc.tron3.Tron_3.11.jar<br /> abc.Tron 2.02,http://www.robocoderepository.com/BotFiles/241/abc.Tron_2.02.jar<br /> abud.ThirdRobo 1.0,http://www.robocoderepository.com/BotFiles/2479/abud.ThirdRobo_1.0.jar<br /> ad.last.Bottom 1.0,http://www.robocoderepository.com/BotFiles/1876/ad.last.Bottom_1.0.jar<br /> ad.Quest 0.10,http://www.robocoderepository.com/BotFiles/1846/ad.Quest_0.10.jar<br /> adt.Ar1 2.1,http://www.robocoderepository.com/BotFiles/2254/adt.Ar1_2.1.jar<br /> adt.Ar2 1.0,http://www.robocoderepository.com/BotFiles/2303/adt.Ar2_1.0.jar<br /> ag.Gir 0.99,http://www.robocoderepository.com/BotFiles/3065/ag.Gir_0.99.jar<br /> agd.Mooserwirt2 2.7,http://www.glyndavies.org/robocode/agd.Mooserwirt2.jar<br /> ags.Glacier 0.2.7,http://rednaxela-robocode.dyndns.org/data/robots/ags.Glacier_0.2.7.jar<br /> ags.micro.Carpet 1.1,http://rednaxela-robocode.dyndns.org/data/robots/ags.micro.Carpet_1.1.jar<br /> ags.Midboss 1s,http://rednaxela-robocode.dyndns.org/data/robots/ags.Midboss_1s.jar<br /> ags.polished.PolishedRuby 1,http://rednaxela-robocode.dyndns.org/data/robots/ags.polished.PolishedRuby_1.jar<br /> ags.rougedc.RougeDC willow,http://rednaxela-robocode.dyndns.org/data/robots/ags.rougedc.RougeDC_willow.jar<br /> ahf.Acero 1.0,http://www.robocoderepository.com/BotFiles/2151/ahf.Acero_1.0.jar<br /> ahf.NanoAndrew .4,http://www.robocoderepository.com/BotFiles/2002/ahf.NanoAndrew_.4.jar<br /> ahf.r2d2.R2d2 0.86,http://www.robocoderepository.com/BotFiles/2035/ahf.r2d2.R2d2_0.86.jar<br /> ahr.ice.Ice 1.0,http://robocoderepository.com/BotFiles/3966/ahr.ice.Ice_1.0.jar<br /> ahr.ice.Ice 1.0.1,http://robocoderepository.com/BotFiles/3978/ahr.ice.Ice_1.0.1.jar<br /> AIR.iRobot 1.0,http://www.robocoderepository.com/BotFiles/3205/AIR.iRobot_1.0.jar<br /> ak.Fermat 2.0,http://www.robocoderepository.com/BotFiles/799/ak.Fermat_2.0.jar<br /> alex.Diabolo5 1.1,http://darkcanuck.net/rumble/robots/alex.Diabolo5_1.1.jar<br /> alk.lap.LoudAndProud 2.23,http://www.robocoderepository.com/BotFiles/3601/alk.lap.LoudAndProud_2.23.jar<br /> am.Miedzix 2.0,http://www.robocoderepository.com/BotFiles/3383/am.Miedzix_2.0.jar<br /> am.Miedzix 3.0,http://darkcanuck.net/rumble/robots/am.Miedzix_3.0.jar<br /> amarok.Rookie 1.1,http://www.robocoderepository.com/BotFiles/422/amarok.Rookie_1.1.jar<br /> amk.ChumbaMini 0.2,http://www.robocoderepository.com/BotFiles/2655/amk.ChumbaMini_0.2.jar<br /> amk.ChumbaWumba 0.3,http://www.robocoderepository.com/BotFiles/2646/amk.ChumbaWumba_0.3.jar<br /> amk.jointstrike.JointStrike 0.2,http://www.robocoderepository.com/BotFiles/2597/amk.jointstrike.JointStrike_0.2.jar<br /> amk.ShizzleStiX.ShizzleStiX 0.6,http://www.robocoderepository.com/BotFiles/2603/amk.ShizzleStiX.ShizzleStiX_0.6.jar<br /> amk.superstrike.SuperStrike 0.3,http://www.robocoderepository.com/BotFiles/2600/amk.superstrike.SuperStrike_0.3.jar<br /> amk.Punbot.Punbot 0.01,http://www.robocoderepository.com/BotFiles/2604/amk.Punbot.Punbot_0.01.jar<br /> ao.T100 0.9,http://www.robocoderepository.com/BotFiles/3385/ao.T100_0.9.jar<br /> ap.Frederick 1.1,http://darkcanuck.net/rumble/robots/ap.Frederick_1.1.jar<br /> apollokidd.ApolloKidd 0.9,http://www.robocoderepository.com/BotFiles/321/apollokidd.ApolloKidd_0.9.jar<br /> apv.Aspid 1.7,http://www.robocoderepository.com/BotFiles/1412/apv.Aspid_1.7.jar<br /> apv.AspidReloaded 0.6,http://www.robocoderepository.com/BotFiles/1985/apv.AspidReloaded_0.6.jar<br /> apv.LauLectrik 1.2,http://www.robocoderepository.com/BotFiles/1300/apv.LauLectrik_1.2.jar<br /> apv.MicroAspid 1.8,http://www.robocoderepository.com/BotFiles/2519/apv.MicroAspid_1.8.jar<br /> apv.NanoLauLectrik 1.0,http://www.robocoderepository.com/BotFiles/1399/apv.NanoLauLectrik_1.0.jar<br /> apv.NanoLauLectrikTheCannibal 1.1,http://www.robocoderepository.com/BotFiles/2147/apv.NanoLauLectrikTheCannibal_1.1.jar<br /> apv.ScruchiPu 1.0,http://www.robocoderepository.com/BotFiles/1367/apv.ScruchiPu_1.0.jar<br /> apv.test.Virus 0.6.1,http://www.robocoderepository.com/BotFiles/2645/apv.test.Virus_0.6.1.jar<br /> apv.TheBrainPi 0.5fix,http://darkcanuck.net/rumble/robots/apv.TheBrainPi_0.5fix.jar<br /> ar.horizon.Horizon 1.2.2,http://www.robocoderepository.com/BotFiles/3286/ar.horizon.Horizon_1.2.2.jar<br /> ar.QuantumChromodynamics 1.2.1,http://www.robocoderepository.com/BotFiles/3220/ar.QuantumChromodynamics_1.2.1.jar<br /> ar.TheoryOfEverything 1.2.1,http://www.robocoderepository.com/BotFiles/3221/ar.TheoryOfEverything_1.2.1.jar<br /> ara.Shera 0.88,http://www.robocoderepository.com/BotFiles/1050/ara.Shera_0.88.jar<br /> areb.Union 1.06,http://www.robocoderepository.com/BotFiles/2893/areb.Union_1.06.jar<br /> arthord.micro.Apoptygma 0.4,http://www.robocoderepository.com/BotFiles/1688/arthord.micro.Apoptygma_0.4.jar<br /> arthord.micro.Muffin 0.6.1,http://www.robocoderepository.com/BotFiles/1963/arthord.micro.Muffin_0.6.1.jar<br /> arthord.KostyaTszyu Beta2,http://www.robocoderepository.com/BotFiles/2322/arthord.KostyaTszyu_Beta2.jar<br /> arthord.MannyPacquiao Delta2,http://scoutery.awardspace.com/arthord.MannyPacquiao_Delta2.jar<br /> arthord.NanoSatan Mu,http://www.robocoderepository.com/BotFiles/2157/arthord.NanoSatan_Mu.jar<br /> arthord.NanoSatanMelee Beta,http://www.robocoderepository.com/BotFiles/2088/arthord.NanoSatanMelee_Beta.jar<br /> ary.micro.Weak 1.2,http://www.robocoderepository.com/BotFiles/3433/ary.micro.Weak_1.2.jar<br /> ary.mini.Nimi 1.0,http://www.robocoderepository.com/BotFiles/3397/ary.mini.Nimi_1.0.jar<br /> ary.nano.AceSurf 1.2,http://www.robocoderepository.com/BotFiles/3352/ary.nano.AceSurf_1.2.jar<br /> ary.nano.ColorNanoP 1.1,http://www.robocoderepository.com/BotFiles/3629/ary.nano.ColorNanoP_1.1.jar<br /> ary.Crisis 1.0,http://www.robocoderepository.com/BotFiles/3495/ary.Crisis_1.0.jar<br /> ary.Help 1.0,http://darkcanuck.net/rumble/robots/ary.Help_1.0.jar<br /> ary.FourWD 1.3d,http://darkcanuck.net/rumble/robots/ary.FourWD_1.3d.jar<br /> ary.SMG 1.01,http://ary-robocode.110mb.com/ary.SMG_1.01.jar<br /> as.xbots 1.0,http://darkcanuck.net/rumble/robots/as.xbots_1.0.jar<br /> asd.Cthulhu 1.2,http://darkcanuck.net/rumble/robots/asd.Cthulhu_1.2.jar<br /> asm.Statistas 0.1,http://www.robocoderepository.com/BotFiles/1989/asm.Statistas_0.1.jar<br /> aw.GreatWolf 2.0,https://sites.google.com/site/awusa94/robocode/aw.GreatWolf_2.0.jar<br /> awesomeness.Elite 1.0,http://robocoderepository.com/BotFiles/3597/awesomeness.Elite.jar<br /> awl.Locutus 1.0,3844<br /> axeBots.HataMoto 3.09,http://www.robocoderepository.com/BotFiles/1655/axeBots.HataMoto_3.09.jar<br /> axeBots.Musashi 2.18,http://www.robocoderepository.com/BotFiles/1759/axeBots.Musashi_2.18.jar<br /> axeBots.Okami 1.04,http://www.robocoderepository.com/BotFiles/2016/axeBots.Okami_1.04.jar<br /> axeBots.SilverSurfer 2.53.33fix,http://rednaxela-robocode.dyndns.org/data/robots/axeBots.SilverSurfer_2.53.33fix.jar<br /> ayk.WallHugger 1.0,https://sites.google.com/site/khanguyprojects/file-cabinet/ayk.WallHugger_1.0.jar<br /> baal.nano.N 1.42,http://webpages.charter.net/eleeleth/Robots/baal.nano.N_1.42.jar<br /> banshee.mini.Nexus6 0.2.0,http://www.robocoderepository.com/BotFiles/3467/banshee.mini.Nexus6_0.2.0.jar<br /> banshee.micro.Nexus6 0.3.0,http://www.robocoderepository.com/BotFiles/3473/banshee.micro.Nexus6_0.3.0.jar<br /> bayen.nano.Squirrel 0.2,http://www.freewebs.com/bayen/files/bayen.nano.Squirrel_0.2.jar<br /> bayen.nut.Squirrel 1.621,http://darkcanuck.net/rumble/robots/bayen.nut.Squirrel_1.621.jar<br /> bayen.UbaMicro 1.4,http://www.robocoderepository.com/BotFiles/2830/bayen.UbaMicro_1.4.jar<br /> bayen.UbaRamLT 1.0,http://www.robocoderepository.com/BotFiles/2868/bayen.UbaRamLT_1.0.jar<br /> bbo.RamboT 0.3,http://www.robocoderepository.com/BotFiles/2210/bbo.RamboT_0.3.jar<br /> bbo.TheRoof 1.4.3,http://www.robocoderepository.com/BotFiles/2179/bbo.TheRoof_1.4.3.jar<br /> Bemo.Sweet30 1.6.1,http://www.stg-volleyball.de/images/Bemo.Sweet30_1.6.1.jar<br /> benhorner.PureAggression 0.2.6,http://www.robocoderepository.com/BotFiles/3421/benhorner.PureAggression_0.2.6.jar<br /> bh.PencilRain 0.01,http://www.robocoderepository.com/BotFiles/3670/bh.PencilRain-0.01.jar<br /> bigpete.Stewie 1.0,http://www.robocoderepository.com/BotFiles/2927/bigpete.Stewie_1.0.jar<br /> bing2.Melody 1.3.1,http://www.ccs.neu.edu/home/bing/robocode/bing2.Melody_1.3.1.jar<br /> bjl.LoneDragon 0.5,http://www.robocoderepository.com/BotFiles/1929/bjl.LoneDragon_0.5.jar<br /> bndl.LostLion 1.2,http://www.robocoderepository.com/BotFiles/1033/bndl.LostLion_1.2.jar<br /> bons.NanoStalker 1.2,http://www.robocoderepository.com/BotFiles/1179/bons.NanoStalker_1.2.jar<br /> bp.Kuma 1.0,http://www.robocoderepository.com/BotFiles/3238/bp.Kuma_1.0.jar<br /> braaropolis.Abot 1.0,http://darkcanuck.net/rumble/robots/braaropolis.Abot_1.0.jar<br /> brainfade.Fallen 0.63,http://www.robocoderepository.com/BotFiles/2250/brainfade.Fallen_0.63.jar<br /> brainfade.melee.Dusk 0.44,http://www.robocoderepository.com/BotFiles/2518/brainfade.melee.Dusk_0.44.jar<br /> buba.Archivist 0.1,http://www.robocoderepository.com/BotFiles/3899/buba.Archivist_0.1.jar<br /> buba.Buba 0.3,http://www.robocoderepository.com/BotFiles/3896/buba.Buba_0.3.jar<br /> bvh.fnr.Fenrir 0.36l,http://www.robocoderepository.com/BotFiles/1428/bvh.fnr.Fenrir_0.36l.jar<br /> bvh.frg.Friga 0.112dev,http://darkcanuck.net/rumble/robots/bvh.frg.Friga_0.112dev.jar<br /> bvh.fry.Freya 0.82,http://darkcanuck.net/rumble/robots/bvh.fry.Freya_0.82.jar<br /> bvh.hdr.Hodur 0.4,http://www.robocoderepository.com/BotFiles/1954/bvh.hdr.Hodur_0.4.jar<br /> bvh.loki.Loki 0.5,http://www.robocoderepository.com/BotFiles/885/bvh.loki.Loki_0.5.jar<br /> bvh.micro.Freya 0.3,http://www.robocoderepository.com/BotFiles/2815/bvh.micro.Freya_0.3.jar<br /> bvh.micro.Svadilfari 0.2,http://www.robocoderepository.com/BotFiles/1086/bvh.micro.Svadilfari_0.2.jar<br /> bvh.mini.Fenrir 0.39,http://www.robocoderepository.com/BotFiles/1429/bvh.mini.Fenrir_0.39.jar<br /> bvh.mini.Freya 0.55,http://darkcanuck.net/rumble/robots/bvh.mini.Freya_0.55.jar<br /> bvh.mini.Mjolnir 0.3,http://www.robocoderepository.com/BotFiles/2220/bvh.mini.Mjolnir_0.3.jar<br /> bvh.mini.Wodan 0.50,http://www.robocoderepository.com/BotFiles/2064/bvh.mini.Wodan_0.50.jar<br /> bvh.tyr.Tyr 1.74,http://www.robocoderepository.com/BotFiles/886/bvh.tyr.Tyr_1.74.jar<br /> bzdp.BoxCar 2.0,http://www.robocoderepository.com/BotFiles/3703/bzdp.BoxCar_2.0.jar<br /> bzdp.Pansy 2.1,http://www.robocoderepository.com/BotFiles/3726/bzdp.Pansy_2.1.jar<br /> caimano.Furia_Ceca 0.22,http://www.robocoderepository.com/BotFiles/1843/caimano.Furia_Ceca_0.22.jar<br /> cbot.agile.Nibbler 0.2,http://www.robocoderepository.com/BotFiles/1537/cbot.agile.Nibbler_0.2.jar<br /> cbot.cbot.CBot 0.8,http://www.robocoderepository.com/BotFiles/1375/cbot.cbot.CBot_0.8.jar<br /> cf.mini.Chiva 1.0,http://www.robocoderepository.com/BotFiles/2331/cf.mini.Chiva_1.0.jar<br /> cf.OldMan.OldManXP 0.1,http://www.robocoderepository.com/BotFiles/1968/cf.OldMan.OldManXP_0.1.jar<br /> cf.proto.Shiva 2.2,http://www.robocoderepository.com/BotFiles/2409/cf.proto.Shiva_2.2.jar<br /> cf.star.Star2 1.23,http://www.robocoderepository.com/BotFiles/2255/cf.star.Star2_1.23.jar<br /> ch.rhj.rbc.RHJ1 1.0,http://www.robocoderepository.com/BotFiles/1879/ch.rhj.rbc.RHJ1_1.0.jar<br /> CharlieN.Omega.Omega 1.03,http://www.robocoderepository.com/BotFiles/3503/CharlieN.Omega.Omega_1.03.jar<br /> chase.c.Wristwatch 1.0,http://file.csdgn.org/robocode/chase.c.Wristwatch_1.0.jar<br /> chase.pm.Pytko 1.0,http://file.csdgn.org/robocode/chase.pm.Pytko_1.0.jar<br /> chase.s2.Genesis 1.1,http://file.csdgn.org/robocode/chase.s2.Genesis_1.1.jar<br /> chase.s2.Seraphim 2.0.9,http://file.csdgn.org/robocode/chase.s2.Seraphim_2.0.9.jar<br /> chickenfuego.UrChicken2 1.0,http://www.robocoderepository.com/BotFiles/3422/chickenfuego.UrChicken2_1.0.jar<br /> cjk.Merkava 0.1.1,http://www.robocoderepository.com/BotFiles/2637/cjk.Merkava_0.1.1.jar<br /> cjk.Merkava 0.2.0,http://www.robocoderepository.com/BotFiles/2640/cjk.Merkava_0.2.0.jar<br /> cjk.Merkava 0.3.0,http://darkcanuck.net/rumble/robots/cjk.Merkava_0.3.0.jar<br /> cjm.chalk.Chalk 2.6.Be,http://scatterbright.com/robots/cjm.chalk.Chalk_2.6.Be.jar<br /> cjm.Charo 1.1,http://scatterbright.com/robots/cjm.Charo_1.1.jar<br /> cjm.Che 1.2,http://www.robocoderepository.com/BotFiles/2703/cjm.Che_1.2.jar<br /> cjm.Chomsky 1.5,http://scatterbright.com/robots/cjm.Chomsky_1.5.jar<br /> codemojo.nano.Woot 1.0,http://darkcanuck.net/rumble/robots/codemojo.nano.Woot_1.0.jar<br /> cs.ExclusionNano 1.1,http://file.csdgn.org/robocode/cs.ExclusionNano_1.1.jar<br /> csm.NthGeneration 0.04,http://www.robocoderepository.com/BotFiles/1214/csm.NthGeneration_0.04.jar<br /> csp.Eagle 3.30,http://www.robocoderepository.com/BotFiles/2436/csp.Eagle_3.30.jar<br /> css.Delitioner 0.11,http://darkcanuck.net/rumble/robots/css.Delitioner_0.11.jar<br /> cx.BlestPain 1.41,http://www.robocoderepository.com/BotFiles/1671/cx.BlestPain_1.41.jar<br /> cx.CigaretBH 1.03,http://www.robocoderepository.com/BotFiles/1414/cx.CigaretBH_1.03.jar<br /> cx.Lacrimas 1.36,http://www.robocoderepository.com/BotFiles/1820/cx.Lacrimas_1.36.jar<br /> cx.micro.Blur 0.2,http://www.robocoderepository.com/BotFiles/2447/cx.micro.Blur_0.2.jar<br /> cx.micro.Smoke 0.96,http://www.robocoderepository.com/BotFiles/1037/cx.micro.Smoke_0.96.jar<br /> cx.micro.Spark 0.6,http://www.robocoderepository.com/BotFiles/1320/cx.micro.Spark_0.6.jar<br /> cx.mini.BlackSwans 0.60,http://www.robocoderepository.com/BotFiles/1158/cx.mini.BlackSwans_0.60.jar<br /> cx.mini.Cigaret 1.31,http://www.robocoderepository.com/BotFiles/1152/cx.mini.Cigaret_1.31.jar<br /> cx.mini.Nimrod 0.55,http://www.robocoderepository.com/BotFiles/1236/cx.mini.Nimrod_0.55.jar<br /> cx.nano.Smog 2.6,http://www.robocoderepository.com/BotFiles/1036/cx.nano.Smog_2.6.jar<br /> cx.Princess 1.0,http://www.robocoderepository.com/BotFiles/1343/cx.Princess_1.0.jar<br /> da.NewBGank 1.4,http://www.robocoderepository.com/BotFiles/3312/da.NewBGank_1.4.jar<br /> dam.MogBot 2.9,http://www.robocoderepository.com/BotFiles/555/dam.MogBot_2.9.jar<br /> dans.Cinnamon 1.2,http://www.robocoderepository.com/BotFiles/1976/dans.Cinnamon_1.2.jar<br /> darkcanuck.Gaff 1.50,http://darkcanuck.net/rumble/robots/darkcanuck.Gaff_1.50.jar<br /> darkcanuck.Holden 1.13a,http://darkcanuck.net/rumble/robots/darkcanuck.Holden_1.13a.jar<br /> darkcanuck.Pris 0.88,http://darkcanuck.net/rumble/robots/darkcanuck.Pris_0.88.jar<br /> davidalves.Firebird 0.25,http://davidalves.net/robocode/robots/davidalves.Firebird_0.25.jar<br /> davidalves.Phoenix 1.02,http://davidalves.net/robocode/robots/davidalves.Phoenix_1.02.jar<br /> davidalves.PhoenixOS 1.1,http://davidalves.net/robocode/robots/davidalves.PhoenixOS_1.1.jar<br /> davidalves.net.Duelist 0.1.6src,http://www.robocoderepository.com/BotFiles/1000/davidalves.net.Duelist_0.1.6src.jar<br /> davidalves.net.DuelistMicro 1.22,http://www.robocoderepository.com/BotFiles/1144/davidalves.net.DuelistMicro_1.22.jar<br /> davidalves.net.DuelistMicroMkII 1.1,http://www.robocoderepository.com/BotFiles/1281/davidalves.net.DuelistMicroMkII_1.1.jar<br /> davidalves.net.DuelistMini 1.1,http://www.robocoderepository.com/BotFiles/1181/davidalves.net.DuelistMini_1.1.jar<br /> davidalves.net.DuelistNano 1.0,http://www.robocoderepository.com/BotFiles/1272/davidalves.net.DuelistNano_1.0.jar<br /> dcs.Eater_of_Worlds 1.1.3-A,http://www.robocoderepository.com/BotFiles/2578/dcs.Eater_of_Worlds_1.1.3-A.jar<br /> dcs.Eater_of_Worlds_Mini 1.0,http://www.robocoderepository.com/BotFiles/2850/dcs.Eater_of_Worlds_Mini_1.0.jar<br /> dcs.PM.Eater_of_Worlds_PM 1.2,http://www.robocoderepository.com/BotFiles/2856/dcs.PM.Eater_of_Worlds_PM_1.2.jar<br /> de.erdega.robocode.Polyphemos 0.4,http://darkcanuck.net/rumble/robots/de.erdega.robocode.Polyphemos_0.4.jar<br /> deewiant.Anomaly 0.2,http://www.iki.fi/~deewiant/files/deewiant.Anomaly_0.2.jar<br /> deith.Czolgzilla 0.11,http://www.robocoderepository.com/BotFiles/3256/deith.Czolgzilla_0.11.jar<br /> demetrix.ForceMajeure 0.75,http://ever-rage.narod.ru/robowiki/demetrix.ForceMajeure_0.75.jar<br /> demetrix.nano.Neutrino 0.27,http://ever-rage.narod.ru/robowiki/demetrix.nano.Neutrino_0.27.jar<br /> demetrix.nano.SledgeHammer 0.22,http://ever-rage.narod.ru/robowiki/demetrix.nano.SledgeHammer_0.22.jar<br /> deo.CloudBot 1.3,http://robocoderepository.com/BotFiles/3644/deo.CloudBot_1.3.jar<br /> deo.FlowerBot 1.0,http://robocoderepository.com/BotFiles/3683/deo.FlowerBot_1.0.jar<br /> deo.virtual.RainbowBot 1.0,http://robocoderepository.com/BotFiles/3694/deo.virtual.RainbowBot_1.0.jar<br /> dft.Calliope 5.6,http://www.robocoderepository.com/BotFiles/237/dft.Calliope_5.6.jar<br /> dft.Cyanide 1.90,http://darkcanuck.net/rumble/robots/dft.Cyanide_1.90.jar<br /> dft.Cyprus 3.0,http://www.robocoderepository.com/BotFiles/377/dft.Cyprus_3.0.jar<br /> dft.Freddie 1.32,http://darkcanuck.net/rumble/robots/dft.Freddie_1.32.jar<br /> dft.Guppy 1.0,http://darkcanuck.net/rumble/robots/dft.Guppy_1.0.jar<br /> dft.Immortal 1.40,http://darkcanuck.net/rumble/robots/dft.Immortal_1.40.jar<br /> dft.Krazy 1.5,http://www.robocoderepository.com/BotFiles/2099/dft.Krazy_1.5.jar<br /> dft.Virgin 1.25,http://www.robocoderepository.com/BotFiles/1447/dft.Virgin_1.25.jar<br /> dggp.haiku.gpBot_0 1.1,http://www.robocoderepository.com/BotFiles/3154/dggp.haiku.gpBot_0_1.1.jar<br /> dittman.BlindSquirl Retired,http://home.comcast.net/~kokyunage/robocode/ugluk/dittman.BlindSquirl_Retired.jar<br /> djc.Aardvark 0.3.6,http://www.robocoderepository.com/BotFiles/652/djc.Aardvark_0.3.6.jar<br /> djdjdj.NanoSkunk10 1.0,http://davidjoerg.com/robocode/djdjdj.NanoSkunk10_1.0.jar<br /> dk.stable.Gorgatron 1.1,http://www.robocoderepository.com/BotFiles/2112/dk.stable.Gorgatron_1.1.jar<br /> dks.MicroDanMK2 1.0,http://darkcanuck.net/rumble/robots/dks.MicroDanMK2_1.0.jar<br /> DM.Capriite 3.7.2,http://www.robocoderepository.com/BotFiles/2989/DM.Capriite_3.7.2.jar<br /> DM.Chicken 4.0,http://www.robocoderepository.com/BotFiles/3020/DM.Chicken_4.0.jar<br /> DM.Mijit .3,http://www.robocoderepository.com/BotFiles/3043/DM.Mijit_.3.jar<br /> dmp.micro.Aurora 1.41,http://www.robocoderepository.com/BotFiles/853/dmp.micro.Aurora_1.41.jar<br /> dmp.nano.Eve 3.41,http://www.robocoderepository.com/BotFiles/842/dmp.nano.Eve_3.41.jar<br /> donjezza.Jezza 1.0,http://www.robocoderepository.com/BotFiles/3385/donjezza.Jezza_1.0.jar<br /> donjezza.Muncho 1.0,http://www.robocoderepository.com/BotFiles/3384/donjezza.Muncho_1.0.jar<br /> drd.Dreadknoght 0.9,http://www.robocoderepository.com/BotFiles/3835/drd.Dreadknoght_0.9.jar<br /> drm.CobraBora 1.12,http://www.robocoderepository.com/BotFiles/1146/drm.CobraBora_1.12.jar<br /> drm.Magazine 0.39,http://www.robocoderepository.com/BotFiles/989/drm.Magazine_0.39.jar<br /> ds.OoV4 0.3b,http://www.robocoderepository.com/BotFiles/2851/ds.OoV4_0.3b.jar<br /> dsw.StaticD 1.0,http://darkcanuck.net/rumble/robots/dsw.StaticD_1.0.jar<br /> dsx724.VSAB_EP3a 1.0,http://darkcanuck.net/rumble/robots/dsx724.VSAB_EP3a_1.0.jar<br /> dsx724.VSAB_EP3_ATR 1.1,http://www.robocoderepository.com/BotFiles/3432/dsx724.VSAB_EP3_ATR_1.1.jar<br /> DTF.Kludgy 1.2b,http://www.robocoderepository.com/BotFiles/4041/DTF.Kludgy_1.2b.jar<br /> dukie.Ambassador 1.0,http://www.robocoderepository.com/BotFiles/2845/dukie.Ambassador_1.0.jar<br /> dummy.micro.HummingBird 2.14,http://www.robocoderepository.com/BotFiles/369/dummy.micro.HummingBird_2.14.jar<br /> dummy.micro.Sparrow 2.5,http://www.robocoderepository.com/BotFiles/484/dummy.micro.Sparrow_2.5.jar<br /> dummy.mini.Parakeet 2.40,http://www.robocoderepository.com/BotFiles/400/dummy.mini.Parakeet_2.40.jar<br /> dvogon.GangBang 1.0,http://www.robocoderepository.com/BotFiles/3193/dvogon.GangBang_1.0.jar<br /> dy.LevelOne 2.0,http://www.robocoderepository.com/BotFiles/3452/dy.LevelOne_2.0.jar<br /> dz.Caedo 1.4,http://www.robocoderepository.com/BotFiles/1044/dz.Caedo_1.4.jar<br /> dz.GalbaMicro 0.11,http://www.robocoderepository.com/BotFiles/2482/dz.GalbaMicro_0.11.jar<br /> dz.GalbaMini 0.121,http://darkcanuck.net/rumble/robots/dz.GalbaMini_0.121.jar<br /> dz.MostlyHarmlessNano 2.1,http://www.robocoderepository.com/BotFiles/2166/dz.MostlyHarmlessNano_2.1.jar<br /> dz.OthoMicro 0.12,http://www.robocoderepository.com/BotFiles/2198/dz.OthoMicro_0.12.jar<br /> dz.OthoMini 0.15,http://www.robocoderepository.com/BotFiles/2221/dz.OthoMini_0.15.jar<br /> eat.HumblePieLite 1.0,http://www.robocoderepository.com/BotFiles/1088/eat.HumblePieLite_1.0.jar<br /> ebo.Sparse 0.02,http://www.4geeks.de/files/ebo.Sparse_0.02.jar<br /> ebo.Tahoe 1.1.79,http://www.4geeks.de/files/ebo.Tahoe_1.1.79.jar<br /> EE.LittleBig 1.0,http://www.robocoderepository.com/BotFiles/4009/EE.LittleBig_1.0.jar<br /> EFD.AdvancedEFD 0.4.5a,http://sites.google.com/site/jannisbeese/robots/EFD.AdvancedEFD_0.4.5a.jar<br /> el.Attackr 0.1,http://darkcanuck.net/rumble/robots/el.Attackr_0.1.jar<br /> el.JumpShoot 0.2,http://www.robocoderepository.com/BotFiles/3360/el.JumpShoot_0.2.jar<br /> el33t.EL33tGangstarr2 2.0,http://www.robocoderepository.com/BotFiles/2069/el33t.EL33tGangstarr2_2.0.jar<br /> eld.Hmm 1.0,http://darkcanuck.net/rumble/robots/eld.Hmm_1.0.jar<br /> element.Earth 1.1,http://www.robocoderepository.com/BotFiles/3587/element.Earth_1.1.jar<br /> elloco.Flower 0.1r1,http://www.robocoderepository.com/BotFiles/3242/elloco.Flower_0.1r1.jar<br /> elloco.Kabuto 0.2r,http://www.robocoderepository.com/BotFiles/3229/elloco.Kabuto_0.2r.jar<br /> elvbot.ElverionBot 0.3,http://www.robocoderepository.com/BotFiles/3541/elvbot.ElverionBot_0.3.jar<br /> emp.Yngwie 1.11,http://www.robocoderepository.com/BotFiles/1928/emp.Yngwie_1.11.jar<br /> erdnis.Rover 0.3,http://www.free-games-fun.com/erdnis.Rover_0.3.jar<br /> eskimo.micro.Echo 0.1,http://robocoderepository.com/BotFiles/3969/eskimo.micro.Echo_0.1.jar<br /> et.Predator 1.8,http://www.robocoderepository.com/BotFiles/668/et.Predator_1.8.jar<br /> ethdsy.Malacka 2.4,http://www.robocoderepository.com/BotFiles/1159/ethdsy.Malacka_2.4.jar<br /> evd.X1 0.01,http://www.robocoderepository.com/BotFiles/3503/evd.X1_0.01.jar<br /> exauge.GateKeeper 1.1.121g,http://www.robocoderepository.com/BotFiles/3928/exauge.GateKeeper_1.1.121g.jar<br /> exauge.LemonDrop 1.6.130,http://www.robocoderepository.com/BotFiles/3911/exauge.LemonDrop_1.6.130.jar<br /> exauge.Leopard 1.1.019,http://www.robocoderepository.com/BotFiles/3917/exauge.Leopard_1.1.019.jar<br /> extra.LightSauce 0.01,http://www.robocoderepository.com/BotFiles/4031/extra.LightSauce_0.01.jar<br /> extra.Sauce .01,http://robocoderepository.com/BotFiles/4029/extra.Sauce_.01.jar<br /> fala.robocode.FalaRobot 1.0,http://www.robocoderepository.com/BotFiles/3474/fala.robocode.FalaRobot_1.0.jar<br /> fcr.First 1.0,http://www.robocoderepository.com/BotFiles/3362/fcr.First_1.0.jar<br /> Fenix.FenixTrack 1.0,http://www.robocoderepository.com/BotFiles/1627/Fenix.FenixTrack_1.0.jar<br /> florent.FloatingTadpole 1.2.6,http://www.robocoderepository.com/BotFiles/2675/florent.FloatingTadpole_1.2.6.jar<br /> florent.small.LittleAngel 1.8,http://www.robocoderepository.com/BotFiles/2917/florent.small.LittleAngel_1.8.jar<br /> florent.test.Toad 0.14t,http://wesley3.free.fr/florent.test.Toad_0.14t.jar<br /> florent.XSeries.X2 0.17,http://wesley3.free.fr/florent.XSeries.X2_0.17.jar<br /> fm.claire 1.7,http://www.robocoderepository.com/BotFiles/2251/fm.claire_1.7.jar<br /> fm.mammillarias 1.3,http://www.robocoderepository.com/BotFiles/2238/fm.mammillarias_1.3.jar<br /> fnc.bandit.Bandit 5.2.0,http://www.robocoderepository.com/BotFiles/2155/fnc.bandit.Bandit_5.2.0.jar<br /> fnc.bandit2002.Bandit2002 4.0.2,http://www.robocoderepository.com/BotFiles/2202/fnc.bandit2002.Bandit2002_4.0.2.jar<br /> frag.FragBot 1.0,http://darkcanuck.net/rumble/robots/frag.FragBot_1.0.jar<br /> franzor.Lizt 1.3.1,http://pages.prodigy.net/franz1/house/franzor.Lizt_1.3.1.jar<br /> fromHell.CHCl3 0.0.1,http://fromhell.schreiende-stille.de/fromHell.CHCl3_0.0.1.jar<br /> fullsail.LaxativeTeaTwo 1.0,http://www.robocoderepository.com/BotFiles/3403/fullsail.LaxativeTeaTwo_1.0.jar<br /> fullsail.TimbotNoPrediction 1.0,http://darkcanuck.net/rumble/robots/fullsail.TimbotNoPrediction_1.0.jar<br /> fullsail.SweetTea 1.1,http://darkcanuck.net/rumble/robots/fullsail.SweetTea_1.1.jar<br /> fushi.PvP1.PvP1 2004-02-16,http://www.robocoderepository.com/BotFiles/2023/fushi.PvP1.PvP1_2004-02-16.jar<br /> fw.Number1 1.0b,http://www.dijitari.com/void/robocode/fw.Number1_1.0b.jar<br /> gadsky.Gadsky 1.01,http://www.robocoderepository.com/BotFiles/3595/gadsky.Gadsky_1.01.jar<br /> Gecko.ultimateGeckoBot 1.0,http://www.robocoderepository.com/BotFiles/4039/Gecko.ultimateGeckoBot_1.0.jar<br /> geep.mini.GPBotA 1.0,http://www.robocoderepository.com/BotFiles/2361/geep.mini.GPBotA_1.0.jar<br /> geep.mini.GPBotB 1.1,http://www.robocoderepository.com/BotFiles/2363/geep.mini.GPBotB_1.1.jar<br /> germ.TheMind .2,http://www.robocoderepository.com/BotFiles/2525/germ.TheMind_.2.jar<br /> gg.Squaraus 0.6,http://www.robocoderepository.com/BotFiles/1788/gg.Squaraus_0.6.jar<br /> gg.Wolverine 2.0,http://darkcanuck.net/rumble/robots/gg.Wolverine_2.0.jar<br /> gh.GresSuffurd 0.3.2,http://home.versatel.nl/gheijenk/robocode/jarfiles/gh.GresSuffurd_0.3.2.jar<br /> gh.GrubbmGrb 1.2.4,http://home.versatel.nl/gheijenk/robocode/jarfiles/gh.GrubbmGrb_1.2.4.jar<br /> gh.GrypRepetyf 0.13,http://www.robocoderepository.com/BotFiles/2650/gh.GrypRepetyf_0.13.jar<br /> gh.micro.Grinnik 0.7,http://www.robocoderepository.com/BotFiles/3208/gh.micro.Grinnik_0.7.jar<br /> gh.micro.GrubbmThree 0.9,http://www.robocoderepository.com/BotFiles/2444/gh.micro.GrubbmThree_0.9.jar<br /> gh.mini.Gruwel 0.9,http://www.robocoderepository.com/BotFiles/2511/gh.mini.Gruwel_0.9.jar<br /> gh.nano.Grofvuil 0.2,http://www.robocoderepository.com/BotFiles/2553/gh.nano.Grofvuil_0.2.jar<br /> gimp.GimpBot 0.1,http://www.robocoderepository.com/BotFiles/2434/gimp.GimpBot_0.1.jar<br /> gio.RealGioBot 1.0,http://www.robocoderepository.com/BotFiles/2521/gio.RealGioBot_1.0.jar<br /> gjr.Cephalosporin 0.2,http://www.robocoderepository.com/BotFiles/2240/gjr.Cephalosporin_0.2.jar<br /> gm.GaetanoA 2.15,http://www.robocoderepository.com/BotFiles/2188/gm.GaetanoA_2.15.jar<br /> goblin.Bender 2.4,http://www.robocoderepository.com/BotFiles/1871/goblin.Bender_2.4.jar<br /> grybgoofy.GoofyBot 0.10,http://www.robocoderepository.com/BotFiles/2196/grybgoofy.GoofyBot_0.10.jar<br /> gu.MicroScoob 1.3,http://www.robocoderepository.com/BotFiles/2086/gu.MicroScoob_1.3.jar<br /> gwah.GBotMarkIV 1.0,http://www.horula.ca/roborumble/participants/download.php?file=18<br /> gwah.GerryBotMkII 1.5.1,http://www.horula.ca/roborumble/participants/download.php?file=17<br /> hamilton.Hamilton 1.0,http://www.robocoderepository.com/BotFiles/1408/hamilton.Hamilton_1.0.jar<br /> hapiel.Spiral 0.1,http://robocoderepository.com/BotFiles/3997/hapiel.Spiral_0.1.jar<br /> hirataatsushi.Neo 1.6,http://www.robocoderepository.com/BotFiles/1081/hirataatsushi.Neo_1.6.jar<br /> hirataatsushi.Trinity 0.003,http://www.robocoderepository.com/BotFiles/1145/hirataatsushi.Trinity_0.003.jar<br /> homerbots.h1 1.0,http://www.robocoderepository.com/BotFiles/2999/homerbots.h1_1.0.jar<br /> hp.Athena 0.1,http://www.robocoderepository.com/BotFiles/3415/hp.Athena_0.1.jar<br /> hvilela.HVilela 0.9,http://henrique.vilela.googlepages.com/hvilela.HVilela_0.9.jar<br /> ins.MobyNano 0.8,http://www.robocoderepository.com/BotFiles/939/ins.MobyNano_0.8.jar<br /> intruder.PrairieWolf 2.61,http://darkcanuck.net/rumble/robots/intruder.PrairieWolf_2.61.jar<br /> ivor.prophet.Prophet 0.01,http://www.ivan.php5.sk/ivor.prophet.Prophet_0.01.jar<br /> is.fon.rs.FonDestroyer3084 1.0,http://www.robocoderepository.com/BotFiles/4047/is.fon.rs.FonDestroyer3084_1.0.jar<br /> jaara.LambdaBot 1.1,http://www.robocoderepository.com/BotFiles/3514/jaara.LambdaBot_1.1.jar<br /> jab.avk.ManuelGallegus 0.6,http://darkcanuck.net/rumble/robots/jab.avk.ManuelGallegus_0.6.jar<br /> jab.DiamondStealer 5,http://darkcanuck.net/rumble/robots/jab.DiamondStealers_5.jar<br /> jab.micro.Sanguijuela 0.8,http://darkcanuck.net/rumble/robots/jab.micro.Sanguijuela_0.8.jar<br /> janm.Jammy 1.0,http://www.robocoderepository.com/BotFiles/3543/janm.Jammy_1.0.jar<br /> jam.micro.RaikoMicro 1.44,http://www.robocoderepository.com/BotFiles/1983/jam.micro.RaikoMicro_1.44.jar<br /> jam.mini.Raiko 0.43,http://www.robocoderepository.com/BotFiles/1922/jam.mini.Raiko_0.43.jar<br /> jam.RaikoMX 0.32,http://www.robocoderepository.com/BotFiles/1961/jam.RaikoMX_0.32.jar<br /> japs.Serenity 1.0,http://www.robocoderepository.com/BotFiles/2217/japs.Serenity_1.0.jar<br /> japs.Sjonniebot 0.9.1,http://www.robocoderepository.com/BotFiles/2203/japs.Sjonniebot_0.9.1.jar<br /> jasolo.Sonda 0.55,http://www.robocoderepository.com/BotFiles/1534/jasolo.Sonda_0.55.jar<br /> jaw.Mouse 0.11,http://www.robocoderepository.com/BotFiles/2472/jaw.Mouse_0.11.jar<br /> jaw.KarenCain 0.11,http://www.robocoderepository.com/BotFiles/2474/jaw.KarenCain_0.11.jar<br /> jaybot.adv.bots.JayBot 2.0,http://darkcanuck.net/rumble/robots/jaybot.adv.bots.JayBot_2.0.jar<br /> jaybot.bots.Oddball 4.0,http://darkcanuck.net/rumble/robots/jaybot.bots.Oddball_4.0.jar<br /> jbot.Rabbit2 1.1,http://darkcanuck.net/rumble/robots/jbot.Rabbit2_1.1.jar<br /> jcs.AutoBot 4.2.1,http://www.robocoderepository.com/BotFiles/2616/jcs.AutoBot_4.2.1.jar<br /> jcs.Decepticon 2.5.3,http://www.robocoderepository.com/BotFiles/2620/jcs.Decepticon_2.5.3.jar<br /> jcs.Megatron 1.2,http://www.robocoderepository.com/BotFiles/2632/jcs.Megatron_1.2.jar<br /> jcs.Seth 1.8,http://darkcanuck.net/rumble/robots/jcs.Seth_1.8.jar<br /> jcw.ArcherOne 1.0,http://darkcanuck.net/rumble/robots/jcw.ArcherOne_1.0.jar<br /> jekl.DarkHallow .90.9,http://www.robocoderepository.com/BotFiles/2296/jekl.DarkHallow_.90.9.jar<br /> jekl.Jekyl .70,http://www.robocoderepository.com/BotFiles/1837/jekl.Jekyl_.70.jar<br /> jekl.mini.BlackPearl .91,http://www.robocoderepository.com/BotFiles/1875/jekl.mini.BlackPearl_.91.jar<br /> jep.nano.Hawkwing 0.4.1,http://www.robocoderepository.com/BotFiles/1561/jep.nano.Hawkwing_0.4.1.jar<br /> jep.nano.Hotspur 0.1,http://www.robocoderepository.com/BotFiles/1877/jep.nano.Hotspur_0.1.jar<br /> jep.Terrible 0.4.1,http://www.robocoderepository.com/BotFiles/1536/jep.Terrible_0.4.1.jar<br /> jeremyreeder.Vincent 2011.12.09,http://www.robocoderepository.com/BotFiles/3993/jeremyreeder.Vincent_2011.12.09.jar<br /> jf.Dodger 1.1,http://keenehs.dyndns.org:90/rumble/robots/jf.Dodger_1.1.jar<br /> jf.Dodger 1.3,http://keenehs.dyndns.org:90/rumble/robots/jf.Dodger_1.3.jar<br /> jgap.JGAP12584 1.0,http://www.robocoderepository.com/BotFiles/3383/jgap.JGAP12584_1.0.jar<br /> jgap.JGAP130166 1.0,http://www.robocoderepository.com/BotFiles/3371/jgap.JGAP130166_1.0.jar<br /> jgap.JGAP23423 1.0,http://www.robocoderepository.com/BotFiles/3378/jgap.JGAP23423_1.0.jar<br /> jgap.JGAP6139 1.0,http://www.robocoderepository.com/BotFiles/3372/jgap.JGAP6139_1.0.jar<br /> jgap.JGAP7247_2 1.0,http://www.robocoderepository.com/BotFiles/3382/jgap.JGAP7247_2_1.0.jar<br /> jgap.JGAP7958 1.0,http://www.robocoderepository.com/BotFiles/3373/jgap.JGAP7958_1.0.jar<br /> jje.BagPuss 1.2,http://darkcanuck.net/rumble/robots/jje.BagPuss_1.2.jar<br /> jk.mega.DrussGT 1.9.8,http://www.minifly.rchomepage.com/robocode/jk.mega.DrussGT_1.9.8.jar<br /> jk.micro.Toorkild 0.2.4b,http://www.minifly.rchomepage.com/robocode/jk.micro.Toorkild_0.2.4b.jar<br /> jk.mini.CunobelinDC 0.6,https://sites.google.com/site/jkflying/jk.mini.CunobelinDC_0.6.jar<br /> jk.precise.Wintermute 0.7,http://www.minifly.rchomepage.com/robocode/jk.precise.Wintermute_0.7.jar<br /> jmcd.BeoWulf 2.8,http://www.robocoderepository.com/BotFiles/1377/jmcd.BeoWulf_2.8.jar<br /> joe.ADinosaur 1.0,http://www.robocoderepository.com/BotFiles/2822/joe.ADinosaur_1.0.jar<br /> josago.Jorgito 0.16,http://www.robocoderepository.com/BotFiles/4000/josago.Jorgito_0.16.jar<br /> jp.Perpy 16.0,http://www.robocoderepository.com/BotFiles/3001/jp.Perpy_16.0.jar<br /> jp.SineWall 1.0,http://www.robocoderepository.com/BotFiles/2968/jp.SineWall_1.0.jar<br /> jrm.Test0 1.0,http://www.robocoderepository.com/BotFiles/3636/jrm.Test0_1.0.jar<br /> js.PinBall 1.6,http://www.robocoderepository.com/BotFiles/684/js.PinBall_1.6.jar<br /> jsal.Jsalbot 1.0,http://jeremybubs.googlepages.com/jsal.Jsalbot_1.0.jar<br /> jt.SpearmintCT Alpha,http://www.robocoderepository.com/BotFiles/2164/jt.SpearmintCT_Alpha.jar<br /> justin.DemonicRage 3.20,http://sites.google.com/site/justinsitehere/file-cabinet/justin.DemonicRage_3.20.jar<br /> jw.Booring 1.11,http://www.robocoderepository.com/BotFiles/1250/jw.Booring_1.11.jar<br /> jwst.DAD.DarkAndDarker 1.1,http://darkcanuck.net/rumble/robots/jwst.DAD.DarkAndDarker_1.1.jar<br /> kanishk.Fr0z3n 1.1,http://darkcanuck.net/rumble/robots/kanishk.Fr0z3n_1.1.jar<br /> kano.gamma.KanoGamma 1.8,http://www.robocoderepository.com/BotFiles/1098/kano.gamma.KanoGamma_1.8.jar<br /> kawam.kmBot9 1.0,http://www.robocoderepository.com/BotFiles/967/kawam.kmBot9_1.0.jar<br /> kawigi.f.FhqwhgadsMicro 1.0,http://www.robocoderepository.com/BotFiles/1673/kawigi.f.FhqwhgadsMicro_1.0.jar<br /> kawigi.micro.Shiz 1.1,http://www.robocoderepository.com/BotFiles/2007/kawigi.micro.Shiz_1.1.jar<br /> kawigi.mini.Coriantumr 1.1,http://www.robocoderepository.com/BotFiles/1988/kawigi.mini.Coriantumr_1.1.jar<br /> kawigi.mini.Fhqwhgads 1.1,http://www.robocoderepository.com/BotFiles/1604/kawigi.mini.Fhqwhgads_1.1.jar<br /> kawigi.nano.FunkyChicken 1.1,http://www.robocoderepository.com/BotFiles/1512/kawigi.nano.FunkyChicken_1.1.jar<br /> kawigi.nano.ThnikkaBot 0.9,http://www.robocoderepository.com/BotFiles/2059/kawigi.nano.ThnikkaBot_0.9.jar<br /> kawigi.robot.Girl 1.2,http://www.robocoderepository.com/BotFiles/2124/kawigi.robot.Girl_1.2.jar<br /> kawigi.sbf.Barracuda 1.0,http://www.robocoderepository.com/BotFiles/1535/kawigi.sbf.Barracuda_1.0.jar<br /> kawigi.sbf.FloodHT 0.9.2,http://www.robocoderepository.com/BotFiles/1552/kawigi.sbf.FloodHT_0.9.2.jar<br /> kawigi.sbf.FloodMicro 1.5,http://www.robocoderepository.com/BotFiles/1381/kawigi.sbf.FloodMicro_1.5.jar<br /> kawigi.sbf.FloodMini 1.4,http://www.robocoderepository.com/BotFiles/1462/kawigi.sbf.FloodMini_1.4.jar<br /> kawigi.sbf.FloodNano 1.2,http://www.robocoderepository.com/BotFiles/1421/kawigi.sbf.FloodNano_1.2.jar<br /> kawigi.sbf.FloodSonnet 0.9,http://www.robocoderepository.com/BotFiles/1779/kawigi.sbf.FloodSonnet_0.9.jar<br /> kawigi.sbf.Teancum 1.3,http://www.robocoderepository.com/BotFiles/1470/kawigi.sbf.Teancum_1.3.jar<br /> kawigi.spare.SpareParts 0.7.6nosnd,http://www.robocoderepository.com/BotFiles/1335/kawigi.spare.SpareParts_0.7.6nosnd.jar<br /> kc.micro.Needle 0.101,http://www.robocoderepository.com/BotFiles/3379/kc.micro.Needle_0.101.jar<br /> kc.micro.Thorn 1.252,http://sites.google.com/site/kevcsite/robocode/kc.micro.Thorn_1.252.jar<br /> kc.micro.WaveShark 0.31,http://www.robocoderepository.com/BotFiles/3822/kc.micro.WaveShark_0.31.jar<br /> kc.mini.Vyper 0.311,http://darkcanuck.net/rumble/robots/kc.mini.Vyper_0.311.jar<br /> kc.nano.Splinter 1.2,http://darkcanuck.net/rumble/robots/kc.nano.Splinter_1.2.jar<br /> kc.serpent.Hydra 0.21,http://darkcanuck.net/rumble/robots/kc.serpent.Hydra_0.21.jar<br /> kc.serpent.WaveSerpent 2.11,http://sites.google.com/site/kevcsite/robocode/kc.serpent.WaveSerpent_2.11.jar<br /> kcn.percept.PerceptBot 2.3,http://www.robocoderepository.com/BotFiles/1075/kcn.percept.PerceptBot_2.3.jar<br /> kcn.unnamed.Unnamed 1.21,http://www.robocoderepository.com/BotFiles/1969/kcn.unnamed.Unnamed_1.21.jar<br /> kenran.mega.Pantheist 1.1,http://sites.google.com/site/kenranbots/robocode/kenran.mega.Pantheist_1.1.jar<br /> kid.Gladiator .7.2,http://darkcanuck.net/rumble/robots/kid.Gladiator_.7.2.jar<br /> kid.Toa .0.5,http://rednaxela-robocode.dyndns.org/data/robot_archive/kid.Toa_.0.5.jar<br /> KiraNL.Chupacabra 0.5,http://sandbox-project.nl/robocode/KiraNL.Chupacabra_0.5.jar<br /> KiraNL.ChupaLite 0.4,http://sandbox-project.nl/robocode/KiraNL.ChupaLite_0.4.jar<br /> KiraNL.SpaceKees 0.1,http://sandbox-project.nl/robocode/KiraNL.SpaceKees_0.1.jar<br /> kinsen.melee.Angsaichmophobia 1.8c,http://sites.google.com/site/dcvqksyb/robocode/kinsen.melee.Angsaichmophobia_1.8c.jar<br /> kinsen.nano.Hoplomachy 1.6,http://sites.google.com/site/dcvqksyb/robocode/kinsen.nano.Hoplomachy_1.6.jar<br /> kinsen.nano.Quarrelet 1.0,http://sites.google.com/site/dcvqksyb/robocode/kinsen.nano.Quarrelet_1.0.jar<br /> kinsen.nano.Senticous 1.0,http://sites.google.com/site/dcvqksyb/robocode/kinsen.nano.Senticous_1.0.jar<br /> kjc.etc.Dharok 1.0,http://www.robocoderepository.com/BotFiles/3293/kjc.etc.Dharok_1.0.jar<br /> kjc.MailManX 2.0,http://www.robocoderepository.com/BotFiles/3288/kjc.MailManX_2.0.jar<br /> kjc.Karaykan 1.0,http://www.robocoderepository.com/BotFiles/3289/kjc.Karaykan_1.0.jar<br /> klein.GottesKrieger 1.1,http://www.robocoderepository.com/BotFiles/3258/klein.GottesKrieger_1.1.jar<br /> Krabb.fe4r.Fe4r 0.4,http://www.robocoderepository.com/BotFiles/2766/Krabb.fe4r.Fe4r_0.4.jar<br /> Krabb.sliNk.Garm 0.9u,http://designnj.de/roboking/Krabb.sliNk.Garm_0.9u.jar<br /> Krabb.krabby.Krabby 1.18b,http://darkcanuck.net/rumble/robots/Krabb.krabby.Krabby_1.18b.jar<br /> Krabb.krabby2.Krabby2 1.9o,http://darkcanuck.net/rumble/robots/Krabb.krabby2.Krabby2_1.9o.jar<br /> krillr.mini.JointStrike 2.0.0,http://darkcanuck.net/rumble/robots/krillr.mini.JointStrike_2.0.0.jar<br /> krillr.mega.Psyche 0.0.3,http://darkcanuck.net/rumble/robots/krillr.mega.Psyche_0.0.3.jar<br /> kronenthaler.Basilisk 1.0,http://www.robocoderepository.com/BotFiles/4051/kronenthaler.Basilisk_1.0.jar<br /> krzysiek.robbo2.Robbo 1.0.0,http://darkcanuck.net/rumble/robots/krzysiek.robbo2.Robbo_1.0.0.jar<br /> kurios.DOSexe .9a,http://www.kuriosly.com/roborumble/kurios.DOSexe_.9a.jar<br /> kurios.DOSexe .9b,http://www.kuriosly.com/roborumble/kurios.DOSexe_.9b.jar<br /> kvk.HebusLeTroll 0.41,http://www.robocoderepository.com/BotFiles/2125/kvk.HebusLeTroll_0.41.jar<br /> labg.Cataclysm 2.05,http://www.robocoderepository.com/BotFiles/2399/labg.Cataclysm_2.05.jar<br /> lancel.Lynx 1.09,http://www.robocoderepository.com/BotFiles/3992/lancel.Lynx_1.09.jar<br /> lazarecki.mega.PinkerStinker 0.7,http://www.robocoderepository.com/BotFiles/3838/lazarecki.mega.PinkerStinker_0.7.jar<br /> leb.ShootAnArrow 0.1,http://www.robocoderepository.com/BotFiles/2648/leb.ShootAnArrow_0.1.jar<br /> lechu.Ala 0.0.4,http://www.robocoderepository.com/BotFiles/3497/lechu.Ala_0.0.4.jar<br /> lechu.Lechu 1.1,http://www.robocoderepository.com/BotFiles/3480/lechu.Lechu_1.1.jar<br /> lion.Kresnanano 1.0,http://www.robocoderepository.com/BotFiles/2295/lion.Kresnanano_1.0.jar<br /> lk.nano.Avesnar 1.1,http://www.robocoderepository.com/BotFiles/1597/lk.nano.Avesnar_1.1.jar<br /> lorneswork.Predator 1.0,http://www.robocoderepository.com/BotFiles/2609/lorneswork.Predator_1.0.jar<br /> lrem.Spectre 0.4.4,http://www.robocoderepository.com/BotFiles/2253/lrem.Spectre_0.4.4.jar<br /> lrem.magic.TormentedAngel Antiquitie,http://maxnet.org.pl/~lrem/lrem.magic.TormentedAngel_Antiquitie.jar<br /> lrem.micro.MoggFanatic 0.2,http://www.robocoderepository.com/BotFiles/2639/lrem.micro.MoggFanatic_0.2.jar<br /> lrem.micro.FalseProphet Alpha,http://www.robocoderepository.com/BotFiles/2415/lrem.micro.FalseProphet_Alpha.jar<br /> lrem.quickhack.QuickHack 1.0,http://www.robocoderepository.com/BotFiles/2555/lrem.quickhack.QuickHack_1.0.jar<br /> lunchie.Lunchbox 0.93,http://darkcanuck.net/rumble/robots/lunchie.Lunchbox_0.93.jar<br /> lw.LuthersTest 0.1,http://darkcanuck.net/rumble/robots/lw.LuthersTest_0.1.jar<br /> m3thos.Eva00 1.1,http://darkcanuck.net/rumble/robots/m3thos.Eva00_1.1.jar<br /> m3thos.Eva02 0.7.1,http://darkcanuck.net/rumble/robots/m3thos.Eva02_0.7.1.jar<br /> m3thos.mini.Eva01 0.5.5,http://darkcanuck.net/rumble/robots/m3thos.mini.Eva01_0.5.5.jar<br /> ma.is.fon.rs.RobotA 0.01,http://www.robocoderepository.com/BotFiles/4048/ma.is.fon.rs.RobotA_0.01.jar<br /> madmath.Cow 0.1.1,http://www.robocoderepository.com/BotFiles/3476/madmath.Cow_0.1.1.jar<br /> marcinek.TopGun 1.3,http://www.robocoderepository.com/BotFiles/3458/marcinek.TopGun_1.3.jar<br /> marksteam.Phoenix 1.0,http://www.robocoderepository.com/BotFiles/2749/marksteam.Phoenix_1.0.jar<br /> matt.advanced.Katana 1.0,http://www.robocoderepository.com/BotFiles/2498/matt.advanced.Katana_1.0.jar<br /> matt.BlueMind 0.8.00,http://www.robocoderepository.com/BotFiles/2685/matt.BlueMind_0.8.00.jar<br /> matt.UnderDark3 2.4.34,http://www.robocoderepository.com/BotFiles/2485/matt.UnderDark3_2.4.34.jar<br /> matt.UnderDark4 0.4.00,http://www.robocoderepository.com/BotFiles/2644/matt.UnderDark4_0.4.00.jar<br /> mbh.Mbh 0.1,http://www.robocoderepository.com/BotFiles/3365/mbh.Mbh_0.1.jar<br /> mbro.BelajarBot 0.0.3,http://www.robocoderepository.com/BotFiles/2471/mbro.BelajarBot_0.0.3.jar<br /> mbro.Detektor3 0.1.1,http://www.robocoderepository.com/BotFiles/2478/mbro.Detektor3_0.1.1.jar<br /> mc.Messapia 0.1.8,http://www.robocoderepository.com/BotFiles/2223/mc.Messapia_0.1.8.jar<br /> mcb.Audace 1.3,http://www.robocoderepository.com/BotFiles/3424/mcb.Audace_1.3.jar<br /> md.November 1.0,http://www.robocoderepository.com/BotFiles/1004/md.November_1.0.jar<br /> md.Pasta 1.1,http://www.robocoderepository.com/BotFiles/1014/md.Pasta_1.1.jar<br /> md.VelociRaptor 1.3,http://www.robocoderepository.com/BotFiles/232/md.VelociRaptor_1.3.jar<br /> mdouet.BotKicker 2.0,http://www.robocoderepository.com/BotFiles/1478/mdouet.BotKicker_2.0.jar<br /> metal.small.MCool 1.21,http://www.robocoderepository.com/BotFiles/1698/metal.small.MCool_1.21.jar<br /> metal.small.dna2.MCoolDNA 1.5,http://www.robocoderepository.com/BotFiles/2354/metal.small.dna2.MCoolDNA_1.5.jar<br /> microtestbotpack.MicroTestBot 1.0,http://dl.dropbox.com/u/4547352/robocode/microtestbotpack.MicroTestBot_1.0.jar<br /> mk.Alpha 0.2.1,http://darkcanuck.net/rumble/robots/mk.Alpha_0.2.1.jar<br /> mladjo.AIR 0.7,http://www.robocoderepository.com/BotFiles/3187/mladjo.AIR_0.7.jar<br /> mladjo.GnuKlub 0.1,http://darkcanuck.net/rumble/robots/mladjo.GnuKlub_0.1.jar<br /> mladjo.Grrrrr 0.9,http://www.robocoderepository.com/BotFiles/3189/mladjo.Grrrrr_0.9.jar<br /> mladjo.iRobot 0.3,http://www.robocoderepository.com/BotFiles/3149/mladjo.iRobot_0.3.jar<br /> mladjo.Startko 1.0,http://www.robocoderepository.com/BotFiles/3186/mladjo.Startko_1.0.jar<br /> mld.DustBunny 3.8,http://www.robocoderepository.com/BotFiles/3650/mld.DustBunny_3.8.jar<br /> mld.Infinity 2.2,http://www.robocoderepository.com/BotFiles/3591/mld.Infinity_2.2.jar<br /> mld.LittleBlackBook 1.69d,https://sites.google.com/site/dorganrobocode/file-cabinet/mld.LittleBlackBook_1.69d.jar<br /> mld.Moebius 2.9.3,http://www.robocoderepository.com/BotFiles/3634/mld.Moebius_2.9.3.jar<br /> mld.Wisdom 1.0,http://www.robocoderepository.com/BotFiles/3640/mld.Wisdom_1.0.jar<br /> mmb.Roskilde 0.5,http://www.robocoderepository.com/BotFiles/3965/mmb.Roskilde_0.5.jar<br /> mme.NikeEnhanced 2.0,http://www.robocoderepository.com/BotFiles/2828/mme.NikeEnhanced_2.0.jar<br /> mn.Combat 1.0,http://www.robocoderepository.com/BotFiles/2351/mn.Combat_1.0.jar<br /> mn.WarMachine 1.1,http://www.robocoderepository.com/BotFiles/2574/mn.WarMachine_1.1.jar<br /> mnt.AHEB 0.6a,http://www.robocoderepository.com/BotFiles/2417/mnt.AHEB_0.6a.jar<br /> mnt.SurferBot 0.2.5,http://www.robocoderepository.com/BotFiles/2433/mnt.SurferBot_0.2.5.jar<br /> morbid.MorbidPriest 1.0,http://www.robocoderepository.com/BotFiles/1758/morbid.MorbidPriest_1.0.jar<br /> mrm.MightyMoose .2,http://darkcanuck.net/rumble/robots/mrm.MightyMoose_.2.jar<br /> ms.Ares 0.19,http://www.robocoderepository.com/BotFiles/730/ms.Ares_0.19.jar<br /> mue.Ascendant 1.2.27,http://mue.sonar-echo.de/robocode/mue.Ascendant_1.2.27.jar<br /> mue.Hyperion 0.8,http://www.robocoderepository.com/BotFiles/2224/mue.Hyperion_0.8.jar<br /> muf.CrazyKitten 0.9,http://www.robocoderepository.com/BotFiles/1946/muf.CrazyKitten_0.9.jar<br /> mwj.A1176183 1.0,http://robocode.rleach.id.au/mwj.A1176183_1.0.jar<br /> myl.micro.Avipes 1.00,http://www.robocoderepository.com/BotFiles/1347/myl.micro.Avipes_1.00.jar<br /> myl.micro.NekoNinja 1.30,http://www.robocoderepository.com/BotFiles/944/myl.micro.NekoNinja_1.30.jar<br /> myl.micro.Predator 1.50,http://www.robocoderepository.com/BotFiles/1097/myl.micro.Predator_1.50.jar<br /> myl.micro.Troodon 1.10,http://www.robocoderepository.com/BotFiles/1226/myl.micro.Troodon_1.10.jar<br /> myl.nano.Graviton 1.10,http://www.robocoderepository.com/BotFiles/770/myl.nano.Graviton_1.10.jar<br /> myl.nano.Kakuru 1.20,http://www.robocoderepository.com/BotFiles/1330/myl.nano.Kakuru_1.20.jar<br /> myl.nano.KomoriNinja 1.1,http://www.robocoderepository.com/BotFiles/978/myl.nano.KomoriNinja_1.1.jar<br /> mym.EdgeStalker 1.0,http://www.robocoderepository.com/BotFiles/3956/mym.EdgeStalker_1.0.jar<br /> mz.Adept 2.65,http://www.robocoderepository.com/BotFiles/2090/mz.Adept_2.65.jar<br /> mz.AdeptBSB 1.03,http://www.robocoderepository.com/BotFiles/2113/mz.AdeptBSB_1.03.jar<br /> mz.Movement 1.8,http://www.robocoderepository.com/BotFiles/2145/mz.Movement_1.8.jar<br /> mz.NanoDeath 2.56,http://www.robocoderepository.com/BotFiles/2010/mz.NanoDeath_2.56.jar<br /> mz.NanoGod 2.02,http://www.robocoderepository.com/BotFiles/1996/mz.NanoGod_2.02.jar<br /> nammyung.ModelT 0.23,http://www.robocoderepository.com/BotFiles/969/nammyung.ModelT_0.23.jar<br /> nanoskank.NanoSkank 1.0,http://darkcanuck.net/rumble/robots/nanoskank.NanoSkank_1.0.jar<br /> nat.BlackHole 2.0gamma,http://nat.robothai.net/robots/nat.BlackHole_2.0gamma.jar<br /> nat.micro.NP 1.34,http://nat.robothai.net/robots/nat.micro.NP_1.34.jar<br /> nat.micro.Reepicheep 0.1a,http://nat.robothai.net/robots/nat.micro.Reepicheep_0.1a.jar<br /> nat.nano.Ocnirp 1.73,http://nat.robothai.net/robots/nat.nano.Ocnirp_1.73.jar<br /> nat.nano.OcnirpPM 1.0,http://nat.robothai.net/robots/nat.nano.OcnirpPM_1.0.jar<br /> nat.nano.OcnirpSNG 1.0b,http://nat.robothai.net/robots/nat.nano.OcnirpSNG_1.0b.jar<br /> nat.Samekh 0.4,http://nat.robothai.net/robots/nat.Samekh_0.4.jar<br /> ncj.MoxieBot 1.0,http://www.robocoderepository.com/BotFiles/4003/ncj.MoxieBot_1.0.jar<br /> ndn.DyslexicMonkey 1.1,http://www.robocoderepository.com/BotFiles/1141/ndn.DyslexicMonkey_1.1.jar<br /> NDH.GuessFactor 1.0, http://www.robocoderepository.com/BotFiles/3949/NDH.GuessFactor_1.0.jar<br /> ne.Chimera 1.2,http://www.robocoderepository.com/BotFiles/3276/ne.Chimera_1.2.jar<br /> nexus.One 1.0,http://darkcanuck.net/rumble/robots/nexus.One_1.0.jar<br /> nexus.Prototype 1.0,http://darkcanuck.net/rumble/robots/nexus.Prototype_1.0.jar<br /> nic.Nicator 2.4,http://www.robocoderepository.com/BotFiles/193/nic.Nicator_2.4.jar<br /> nic.SnippetBot 1.0,http://www.robocoderepository.com/BotFiles/286/nic.SnippetBot_1.0.jar<br /> nkn.mini.Jskr0 0.1,http://www.robocoderepository.com/BotFiles/3852/nkn.mini.Jskr0_0.1.jar<br /> NG.LegatusLegionis 1.0,http://www.robocoderepository.com/BotFiles/3888/NG.LegatusLegionis_1.0.jar<br /> NG.LegatusLegionis 1.1,http://www.robocoderepository.com/BotFiles/3889/NG.LegatusLegionis_1.1.jar<br /> NG.LegatusLegionis 1.2,http://www.robocoderepository.com/BotFiles/4026/NG.LegatusLegionis_1.2.jar<br /> non.mega.NaN 0.1,http://www.robocoderepository.com/BotFiles/1960/non.mega.NaN_0.1.jar<br /> non.mega.NoName 0.0,http://www.robocoderepository.com/BotFiles/1957/non.mega.NoName_0.0.jar<br /> Noran.BitchingElk 0.054,http://www.robocoderepository.com/BotFiles/1855/Noran.BitchingElk_0.054.jar<br /> Noran.RandomTargeting 0.02,http://www.robocoderepository.com/BotFiles/1849/Noran.RandomTargeting_0.02.jar<br /> nova.Snow 1.0,http://www.robocoderepository.com/BotFiles/3623/nova.Snow_1.0.jar<br /> ntc.Cannon 1.12test,http://www.robocoderepository.com/BotFiles/3815/ntc.Cannon_1.12test.jar<br /> ntc.Evader 1.2,http://www.robocoderepository.com/BotFiles/3355/ntc.Evader_1.2.jar<br /> ntc.Knowledge 1.1,http://www.robocoderepository.com/BotFiles/3354/ntc.Knowledge_1.1.jar<br /> ntc.Lasers.Lasers 0.9,http://www.robocoderepository.com/BotFiles/3359/ntc.Lasers.Lasers_0.9.jar<br /> ntc.Plains 0.9,http://www.robocoderepository.com/BotFiles/3381/ntc.Plains_0.9.jar<br /> ntc.Swim 0.9,http://www.robocoderepository.com/BotFiles/3820/ntc.Swim_0.9.jar<br /> ntw.Sighup 1.5,http://darkcanuck.net/rumble/robots/ntw.Sighup_1.5.jar<br /> ntw.Sigsys 1.6,http://darkcanuck.net/rumble/robots/ntw.Sigsys_1.6.jar<br /> nz.jdc.micro.HedgehogGF 1.3,http://www.robocoderepository.com/BotFiles/3626/nz.jdc.micro.HedgehogGF_1.3.jar<br /> nz.jdc.micro.HedgehogP 1.2,http://www.robocoderepository.com/BotFiles/3622/nz.jdc.micro.HedgehogP_1.2.jar<br /> nz.jdc.nano.NeophytePattern 1.0,http://www.robocoderepository.com/BotFiles/3578/nz.jdc.nano.NeophytePattern_1.0.jar<br /> nz.jdc.nano.NeophytePRAL 1.2,http://www.robocoderepository.com/BotFiles/3568/nz.jdc.nano.NeophytePRAL_1.2.jar<br /> nz.jdc.nano.NeophyteSRAL 1.2,http://www.robocoderepository.com/BotFiles/3567/nz.jdc.nano.NeophyteSRAL_1.2.jar<br /> oa.weak.BotherBot 0.1,http://www.robocoderepository.com/BotFiles/2956/oa.weak.BotherBot_0.1.jar<br /> oa.weak.FlyMk1 0.1,http://www.robocoderepository.com/BotFiles/2958/oa.weak.FlyMk1_0.1.jar<br /> ola.Puffin 1.0,http://www.robocoderepository.com/BotFiles/3380/ola.Puffin_1.0.jar<br /> oog.melee.Capulet 1.1,https://sites.google.com/site/crazybassoon/oog.melee.Capulet_1.1.jar<br /> oog.melee.Mercutio 1.0,http://www.robocoderepository.com/BotFiles/3848/oog.melee.Mercutio_1.0.jar<br /> oog.micro.MagicD3 0.41,http://www.robocoderepository.com/BotFiles/3801/oog.micro.MagicD3_0.41.jar<br /> oog.micro.Maui 1.2,https://sites.google.com/site/crazybassoon/oog.micro.Maui_1.2.jar<br /> oog.micro.SavantMicro 1.0,http://www.robocoderepository.com/BotFiles/3958/oog.micro.SavantMicro_1.0.jar<br /> oog.mini.AlphaDragon 0.1,http://www.robocoderepository.com/BotFiles/4015/oog.mini.AlphaDragon_0.1.jar<br /> oog.nano.Caligula 1.15,http://www.robocoderepository.com/BotFiles/4022/oog.nano.Caligula_1.15.jar<br /> oog.nano.Fuatisha 1.1,http://www.robocoderepository.com/BotFiles/4045/oog.nano.Fuatisha_1.1.jar<br /> oog.nano.MagicD2 2.4,http://www.robocoderepository.com/BotFiles/3749/oog.nano.MagicD2_2.4.jar<br /> oog.nano.SavantVS 1.1,http://www.robocoderepository.com/BotFiles/3714/oog.nano.SavantVS_1.1.jar<br /> oog.nano.SavantWS 0.1,http://www.robocoderepository.com/BotFiles/3709/oog.nano.SavantWS_0.1.jar<br /> oog.PricklyPear 1.0.4,https://sites.google.com/site/crazybassoon/oog.PricklyPear_1.0.4.jar<br /> pa.Improved 1.1,http://darkcanuck.net/rumble/robots/pa.Improved_1.1.jar<br /> pak.JakeTheTestingRobot .1b,http://www.robocoderepository.com/BotFiles/3373/pak.JakeTheTestingRobot_.1b.jar<br /> pak.Dargon 1.0b,http://www.robocoderepository.com/BotFiles/3388/pak.Dargon_1.0b.jar<br /> pak.Dargon .2c,http://www.robocoderepository.com/BotFiles/3389/pak.Dargon_.2c.jar<br /> panzer.Panzer 0.2,http://www.robocoderepository.com/BotFiles/4008/panzer.Panzer_0.2.jar<br /> paolord.TheHulk 1.0,http://www.robocoderepository.com/BotFiles/3595/paolord.TheHulk_1.0.jar<br /> patson.PatsonTestBot 1.0,http://www.robocoderepository.com/BotFiles/3324/patson.PatsonTestBot_1.0.jar<br /> paulk.PaulV3 1.7,http://www.robocoderepository.com/BotFiles/3502/paulk.PaulV3_1.7.jar<br /> paulk.PaulV3 1.6,http://www.robocoderepository.com/BotFiles/3497/paulk.PaulV3_1.6.jar<br /> paulk.PaulV3 1.5,http://www.robocoderepository.com/BotFiles/3496/paulk.PaulV3_1.5.jar<br /> paulk.PaulV3 1.3,http://www.robocoderepository.com/BotFiles/3495/paulk.PaulV3_1.3.jar<br /> pb.Oscillator 1.0,http://www.robocoderepository.com/BotFiles/2070/pb.Oscillator_1.0.jar<br /> pe.mini.SandboxMini 1.2,http://www.robocoderepository.com/BotFiles/917/pe.mini.SandboxMini_1.2.jar<br /> pe.minimelee.SandboxMiniMelee 1.1,http://www.robocoderepository.com/BotFiles/934/pe.minimelee.SandboxMiniMelee_1.1.jar<br /> pe.SandboxDT 3.02,http://www.robocoderepository.com/BotFiles/793/pe.SandboxDT_3.02.jar<br /> pe.SandboxLump 1.52,http://www.robocoderepository.com/BotFiles/731/pe.SandboxLump_1.52.jar<br /> pedersen.Hubris 2.4,http://home.comcast.net/~kokyunage/robocode/hubris/pedersen.Hubris_2.4.jar<br /> pedersen.Ugluk 1.0,http://home.comcast.net/~kokyunage/robocode/ugluk/pedersen.Ugluk_1.0.jar<br /> pez.clean.Swiffer 0.2.9,http://www.robocoderepository.com/BotFiles/1883/pez.clean.Swiffer_0.2.9.jar<br /> pez.frankie.Frankie 0.9.6.1,http://www.robocoderepository.com/BotFiles/1565/pez.frankie.Frankie_0.9.6.1.jar<br /> pez.gloom.GloomyDark 0.9.2,http://www.robocoderepository.com/BotFiles/1741/pez.gloom.GloomyDark_0.9.2.jar<br /> pez.mako.Mako 1.5,http://www.robocoderepository.com/BotFiles/1317/pez.mako.Mako_1.5.jar<br /> pez.micro.Aristocles 0.3.7,http://www.robocoderepository.com/BotFiles/1923/pez.micro.Aristocles_0.3.7.jar<br /> pez.mini.ChironexFleckeri 0.5,http://www.robocoderepository.com/BotFiles/2513/pez.mini.ChironexFleckeri_0.5.jar<br /> pez.mini.Gouldingi 1.5,http://www.robocoderepository.com/BotFiles/1351/pez.mini.Gouldingi_1.5.jar<br /> pez.mini.Pugilist 2.4.18,http://darkcanuck.net/rumble/robots/pez.mini.Pugilist_2.4.18.jar<br /> pez.mini.Tityus 0.9.1,http://www.robocoderepository.com/BotFiles/1657/pez.mini.Tityus_0.9.1.jar<br /> pez.mini.VertiLeach 0.4.0,http://www.robocoderepository.com/BotFiles/1744/pez.mini.VertiLeach_0.4.0.jar<br /> pez.nano.Icarus 0.3,http://www.robocoderepository.com/BotFiles/2353/pez.nano.Icarus_0.3.jar<br /> pez.nano.LittleEvilBrother 0.1,http://www.robocoderepository.com/BotFiles/2056/pez.nano.LittleEvilBrother_0.1.jar<br /> pez.rumble.Ali 0.4.9,http://www.robocoderepository.com/BotFiles/2416/pez.rumble.Ali_0.4.9.jar<br /> pez.rumble.CassiusClay 2rho.01b,http://www.dijitari.com/void/robocode/pez.rumble.CassiusClay_2rho.01b.jar<br /> pfvicm.Sobieski 7.2.3b,http://www.robocoderepository.com/BotFiles/2911/pfvicm.Sobieski_7.2.3b.jar<br /> ph.micro.Pikeman 0.4.5,http://www.robocoderepository.com/BotFiles/2364/ph.micro.Pikeman_0.4.5.jar<br /> ph.mini.Archer 0.6.6,http://www.robocoderepository.com/BotFiles/2326/ph.mini.Archer_0.6.6.jar<br /> ph.musketeer.Musketeer 0.6,http://www.robocoderepository.com/BotFiles/2281/ph.musketeer.Musketeer_0.6.jar<br /> ph.Thinker 0.2.5,http://www.robocoderepository.com/BotFiles/2336/ph.Thinker_0.2.5.jar<br /> pi.Dark 10,http://darkcanuck.net/rumble/robots/pi.Dark_10.jar<br /> pl.Drum 0.1,http://darkcanuck.net/rumble/robots/pl.Drum_0.1.jar<br /> pl.Patton.GeneralPatton 1.54,http://darkcanuck.net/rumble/robots/pl.Patton.GeneralPatton_1.54.jar<br /> pla.Memnoch 0.5,http://www.robocoderepository.com/BotFiles/2211/pla.Memnoch_0.5.jar<br /> PK.Twardy 0.4.2,http://www.robocoderepository.com/BotFiles/3272/PK.Twardy_0.4.2.jar<br /> pkdeken.Paladin 1.0,http://www.robocoderepository.com/BotFiles/3556/pkdeken.Paladin_1.0.jar<br /> PkKillers.PkAssassin 1.0,http://www.robocoderepository.com/BotFiles/3485/PkKillers.PkAssassin_1.0.jar<br /> pmc.SniperBot 1.0,http://darkcanuck.net/rumble/robots/pmc.SniperBot_1.0.jar<br /> populations.TrainStoopidbot 0.01,http://www.robocoderepository.com/BotFiles/4052/populations.TrainStoopidbot_0.01.jar<br /> positive.Portia 1.26e,http://sites.google.com/site/robopositive/portia/positive.Portia_1.26e.jar<br /> povik.nano.Smilee 0.2.1,http://www.robocoderepository.com/BotFiles/3950/povik.nano.Smilee_0.2.1.jar<br /> projectx.ProjectNano 2.0,http://darkcanuck.net/rumble/robots/projectx.ProjectNano_2.0.jar<br /> projectx.TestNano 1.0,http://www.robocoderepository.com/BotFiles/3444/projectx.TestNano_1.0.jar<br /> pulsar.PulsarMax 0.8.9,http://www.robocoderepository.com/BotFiles/2227/pulsar.PulsarMax_0.8.9.jar<br /> pulsar.PulsarNano 0.2.4,http://www.robocoderepository.com/BotFiles/2335/pulsar.PulsarNano_0.2.4.jar<br /> pulsar.Nanis 0.3,http://www.robocoderepository.com/BotFiles/2560/pulsar.Nanis_0.3.jar<br /> qohnil.blot.BlotBot 3.61,http://www.robocoderepository.com/BotFiles/546/qohnil.blot.BlotBot_3.61.jar<br /> Queens_teamrobot.UltraRazor 1.0,http://www.robocoderepository.com/BotFiles/2108/Queens_teamrobot.UltraRazor_1.0.jar<br /> quietus.Invader 0.1,http://robocode.rleach.id.au/quietus.Invader_0.1.jar<br /> quietus.NarrowRadar 0.1,http://robocode.rleach.id.au/quietus.NarrowRadar_0.1.jar<br /> radnor.DoctorBob 1.42,http://www.robocoderepository.com/BotFiles/2133/radnor.DoctorBob_1.42.jar<br /> radnor.RamRod 1.0,http://www.robocoderepository.com/BotFiles/2085/radnor.RamRod_1.0.jar<br /> rampancy.Durandal 2.2d,http://stanford.edu/~mchunlum/robocode/rampancy.Durandal_2.2d.jar<br /> rampancy.micro.Epiphron 1.0,http://stanford.edu/~mchunlum/robocode/rampancy.micro.Epiphron_1.0.jar<br /> rapture.Rapture 2.13,http://www.robocoderepository.com/BotFiles/15/rapture.Rapture_2.13.jar<br /> ratosh.nano.Debo 1.36,http://www.robocoderepository.com/BotFiles/1702/ratosh.nano.Debo_1.36.jar<br /> ratosh.Nobo 0.21,http://www.robocoderepository.com/BotFiles/1612/ratosh.Nobo_0.21.jar<br /> ratosh.Wesco 1.4,http://www.robocoderepository.com/BotFiles/1914/ratosh.Wesco_1.4.jar<br /> rc.yoda.Yoda 1.0.6c.fix,http://rednaxela-robocode.dyndns.org/data/robots/rc.yoda.Yoda_1.0.6c.fix.jar<br /> rcb.Vanessa03 0,http://www.robocoderepository.com/BotFiles/1364/rcb.Vanessa03_0.jar<br /> rcp.Kuramatron 1.0,http://www.robocoderepository.com/BotFiles/3307/rcp.Kuramatron_1.0.jar<br /> rdt199.Warlord 0.73,http://www.robocoderepository.com/BotFiles/1130/rdt199.Warlord_0.73.jar<br /> reaper.Reaper 1.1,http://www.robocoderepository.com/BotFiles/3412/reaper.Reaper_1.1.jar<br /> repositorio.NanoStep 1.0,http://darkcanuck.net/rumble/robots/repositorio.NanoStep_1.0.jar<br /> rfj.Sunburn 1.1,http://www.robocoderepository.com/BotFiles/1060/rfj.Sunburn_1.1.jar<br /> rijteam.SmartDodge 1.1,http://www.robocoderepository.com/BotFiles/2959/rijteam.SmartDodge_1.1.jar<br /> robar.haiku.Spike 1.0,http://invitel.hu/artrog/robar.haiku.Spike_1.0.jar<br /> robar.micro.Gladius 1.15,http://invitel.hu/artrog/robar.micro.Gladius_1.15.jar<br /> robar.micro.Kirbyi 1.0,http://hunrobar.freeblog.hu/files/myrobots/robar.micro.Kirbyi_1.0.jar<br /> robar.micro.Topaz 0.25,http://invitel.hu/artrog/robar.micro.Topaz_0.25.jar<br /> robar.nano.Assertive 0.3,http://invitel.hu/artrog/robar.nano.Assertive_0.3.jar<br /> robar.nano.BlackWidow 1.3,http://www.robocoderepository.com/BotFiles/3574/robar.nano.BlackWidow_1.3.jar<br /> robar.nano.Breeze 0.3,http://hunrobar.freeblog.hu/files/myrobots/robar.nano.Breeze_0.3.jar<br /> robar.nano.Mosquito 1.1,http://hunrobar.freeblog.hu/files/myrobots/robar.nano.Mosquito_1.1.jar<br /> robar.nano.MosquitoPM 1.0,http://www.robocoderepository.com/BotFiles/3559/robar.nano.MosquitoPM_1.0.jar<br /> robar.nano.Prestige 1.0,http://www.robocoderepository.com/BotFiles/3507/robar.nano.Prestige_1.0.jar<br /> robar.nano.Pugio 1.49,http://www.robocoderepository.com/BotFiles/3710/robar.nano.Pugio_1.49.jar<br /> robar.nano.Scytodes 0.3,http://hunrobar.freeblog.hu/files/myrobots/robar.nano.Scytodes_0.3.jar<br /> robar.nano.Vespa 0.95,http://hunrobar.freeblog.hu/files/myrobots/robar.nano.Vespa_0.95.jar<br /> robo.PartsBot 1.1,http://darkcanuck.net/rumble/robots/robo.PartsBot_1.1.jar<br /> RobotMarco.MarcoV 0.1,http://www.robocoderepository.com/BotFiles/3941/RobotMarco.MarcoV_0.1.jar<br /> rsim.micro.uCatcher 0.1,http://sites.google.com/site/rsimander/robocode/rsim.micro.uCatcher_0.1.jar<br /> rsim.mini.BulletCatcher 0.4,http://www.robocoderepository.com/BotFiles/3737/rsim.mini.BulletCatcher_0.4.jar<br /> rsk1.RSK1 4.0,http://www.robocoderepository.com/BotFiles/3284/rsk1.RSK1_4.0.jar<br /> ruc.nano.Zealot 0.2,http://www.robocoderepository.com/BotFiles/1229/ruc.nano.Zealot_0.2.jar<br /> rus.vv.Dzhigit 1.1,http://www.robocoderepository.com/BotFiles/4002/rus.vv.Dzhigit1.1.jar<br /> rus.vv.Snezhok 1.1,http://www.robocoderepository.com/BotFiles/3998/rus.vv.Snezhok1.1.jar<br /> ry.LightningBug 1.0,http://www.robocoderepository.com/BotFiles/3472/ry.LightningBug_1.0.jar<br /> ry.VirtualGunExperiment 1.2.0,http://www.robocoderepository.com/BotFiles/3662/ry.VirtualGunExperiment_1.2.0.jar<br /> ry.Worst 1.0,http://www.robocoderepository.com/BotFiles/3645/ry.Worst_1.0.jar<br /> rz.Aleph 0.34,http://www.robocoderepository.com/BotFiles/1993/rz.Aleph_0.34.jar<br /> rz.Apollon 0.23,http://www.robocoderepository.com/BotFiles/2098/rz.Apollon_0.23.jar<br /> rz.Artist 0.2,http://www.robocoderepository.com/BotFiles/2156/rz.Artist_0.2.jar<br /> rz.GlowBlow 2.31,http://www.robocoderepository.com/BotFiles/1354/rz.GlowBlow_2.31.jar<br /> rz.GlowBlowAPM 1.0,http://www.robocoderepository.com/BotFiles/1382/rz.GlowBlowAPM_1.0.jar<br /> rz.GlowBlowMelee 1.4,http://www.robocoderepository.com/BotFiles/1436/rz.GlowBlowMelee_1.4.jar<br /> rz.HawkOnFire 0.1,http://www.robocoderepository.com/BotFiles/1575/rz.HawkOnFire_0.1.jar<br /> rz.SmallDevil 1.502,http://www.robocoderepository.com/BotFiles/1322/rz.SmallDevil_1.502.jar<br /> sadoner.killer 0.2,http://www.robocoderepository.com/BotFiles/4020/sadoner.killer_0.2.jar<br /> sam.ChipmunkDuelist 1.0,http://www.robocoderepository.com/BotFiles/3094/sam.ChipmunkDuelist_1.0.jar<br /> sam.Samspin 1.0,http://www.robocoderepository.com/BotFiles/2823/sam.Samspin_1.0.jar<br /> sanyi.mikrobi.Roberto 1.0,http://www.robocoderepository.com/BotFiles/3929/sanyi.mikrobi.Roberto_1.0.jar<br /> sch.Simone 0.3d,http://www.robocoderepository.com/BotFiles/374/sch.Simone_0.3d.jar<br /> serenity.moonlightBat 1.17,http://www.robocoderepository.com/BotFiles/2877/serenity.moonlightBat_1.17.jar<br /> serenity.nonSense 1.39,http://www.robocoderepository.com/BotFiles/3586/serenity.nonSense_1.39.jar<br /> serenity.serenityFire 1.29,http://www.robocoderepository.com/BotFiles/3071/serenity.serenityFire_1.29.jar<br /> sgp.JollyNinja 3.53,http://www.robocoderepository.com/BotFiles/183/sgp.JollyNinja_3.53.jar<br /> sgp.MadHatter 4.13,http://www.robocoderepository.com/BotFiles/156/sgp.MadHatter_4.13.jar<br /> sgp.nano.FurryLeech 1.0,http://www.robocoderepository.com/BotFiles/802/sgp.nano.FurryLeech_1.0.jar<br /> sgp.ShiningBeetle 1.1,http://www.robocoderepository.com/BotFiles/498/sgp.ShiningBeetle_1.1.jar<br /> sgp.SleepingGoat 1.1,http://www.robocoderepository.com/BotFiles/500/sgp.SleepingGoat_1.1.jar<br /> SHAM.WOW 1.4,http://darkcanuck.net/rumble/robots/SHAM.WOW_1.4.jar<br /> shinh.Entangled 0.3,http://www.robocoderepository.com/BotFiles/1070/shinh.Entangled_0.3.jar<br /> shrub.Silver v048,http://www.robocoderepository.com/BotFiles/449/shrub.Silver_v048.jar<br /> shrub.Vapour v159,http://www.robocoderepository.com/BotFiles/2654/shrub.Vapour_v159.jar<br /> shu.nitro.LENIN .T34,http://www.robocoderepository.com/BotFiles/1956/shu.nitro.LENIN_.T34.jar<br /> sigterm.Sigterm 1.0,http://darkcanuck.net/rumble/robots/sigterm.Sigterm_1.0.jar<br /> simonton.beta.LifelongObsession 0.5.1,http://www.robocoderepository.com/BotFiles/3195/simonton.beta.LifelongObsession_0.5.1.jar<br /> simonton.GFNano_D 3.1b,http://www.robocoderepository.com/BotFiles/3114/simonton.GFNano_D_3.1b.jar<br /> simonton.nano.WeekendObsession_S 1.7,http://www.robocoderepository.com/BotFiles/3117/simonton.nano.WeekendObsession_S_1.7.jar<br /> simonton.mega.SniperFrog 1.0.fix2,http://rednaxela-robocode.dyndns.org/data/robots/simonton.mega.SniperFrog_1.0.fix2.jar<br /> simonton.micro.GFMicro 1.0,http://darkcanuck.net/rumble/robots/simonton.micro.GFMicro_1.0.jar<br /> simonton.micro.WeeklongObsession 3.4.1,http://darkcanuck.net/rumble/robots/simonton.micro.WeeklongObsession_3.4.1.jar<br /> simonton.mini.WeeksOnEnd 1.10.4,http://darkcanuck.net/rumble/robots/simonton.mini.WeeksOnEnd_1.10.4.jar<br /> skm.butterfly 1.0,http://www.robocoderepository.com/BotFiles/3868/sean1.jar<br /> skm.Ryubot 1.0,http://www.robocoderepository.com/BotFiles/3594/skm.Ryubot_1.0.jar<br /> skm.PateranBotlock2 1.0,http://www.robocoderepository.com/BotFiles/3591/skm.PateranBotlock2_1.0.jar<br /> sL300.Mozart life,http://www.robocoderepository.com/BotFiles/1992/sL300.Mozart_life.jar<br /> sm.Devil 7.3,http://www.robocoderepository.com/BotFiles/1481/sm.Devil_7.3.jar<br /> sng.arco.Arco 0.0,http://www.robocoderepository.com/BotFiles/3279/sng.arco.Arco_0.0.jar<br /> sos.SOS 1.0,http://www.robocoderepository.com/BotFiles/3489/sos.SOS_1.0.jar<br /> spinnercat.CopyKat 1.2.3,http://www.robocoderepository.com/BotFiles/3818/spinnercat.CopyKat_1.2.3.jar<br /> spinnercat.Limit .01,http://www.robocoderepository.com/BotFiles/3659/spinnercat.Limit_.01.jar<br /> spinnercat.Kitten 1.6,http://www.robocoderepository.com/BotFiles/3819/spinnercat.Kitten_1.6.jar<br /> spinnercat.haiku.Refrigerator 1.1,http://www.robocoderepository.com/BotFiles/3688/spinnercat.haiku.Refrigerator_1.1.jar<br /> spinnercat.mega.Tardis 1.2,http://www.robocoderepository.com/BotFiles/3692/spinnercat.mega.Tardis_1.2.jar<br /> spinnercat.Robovirus 2.718,http://www.robocoderepository.com/BotFiles/3657/spinnercat.Robovirus_2.718.jar<br /> sqTank.waveSurfing.LionWWSVMvoid 0.01,http://www.robocoderepository.com/BotFiles/3436/sqTank.waveSurfing.LionWWSVMvoid_0.01.jar<br /> starpkg.StarViewerZ 1.26,http://www.robocoderepository.com/BotFiles/1931/starpkg.StarViewerZ_1.26.jar<br /> staticline.Whiskey 0.5.3,http://www.robocoderepository.com/BotFiles/3972/staticline.Whiskey_0.5.3.jar<br /> staticline.whiskey.Whiskey 0.6,http://rednaxela-robocode.dyndns.org/data/robot_archive/staticline.whiskey.Whiskey_0.6.jar<br /> stefw.Tigger 0.0.23,http://darkcanuck.net/rumble/robots/stefw.Tigger_0.0.23.jar<br /> stelo.Chord 1.0,http://darkcanuck.net/rumble/robots/stelo.Chord_1.0.jar<br /> stelo.FretNano 1.1,http://darkcanuck.net/rumble/robots/stelo.FretNano_1.1.jar<br /> stelo.Lifestealer 1.0,http://darkcanuck.net/rumble/robots/stelo.Lifestealer_1.0.jar<br /> stelo.MatchupMini 1.1,http://darkcanuck.net/rumble/robots/stelo.MatchupMini_1.1.jar<br /> stelo.MatchupMicro 1.2,http://darkcanuck.net/rumble/robots/stelo.MatchupMicro_1.2.jar<br /> stelo.MatchupAGF 1.1,http://darkcanuck.net/rumble/robots/stelo.MatchupAGF_1.1.jar<br /> stelo.MatchupWS 1.2c,http://darkcanuck.net/rumble/robots/stelo.MatchupWS_1.2c.jar<br /> stelo.Mirror 1.1,http://www.robocoderepository.com/BotFiles/3034/stelo.Mirror_1.1.jar<br /> stelo.MirrorMicro 1.1,http://darkcanuck.net/rumble/robots/stelo.MirrorMicro_1.1.jar<br /> stelo.MirrorNano 1.4,http://darkcanuck.net/rumble/robots/stelo.MirrorNano_1.4.jar<br /> stelo.MoojukNano 1.2,http://darkcanuck.net/rumble/robots/stelo.MoojukNano_1.2.jar<br /> stelo.PastFuture 2.1.9,http://www.robocoderepository.com/BotFiles/3910/stelo.PastFuture_2.1.9.jar<br /> stelo.PatternRobot 1.0,http://www.robocoderepository.com/BotFiles/2995/stelo.PatternRobot_1.0.jar<br /> stelo.PianistNano 1.3,http://darkcanuck.net/rumble/robots/stelo.PianistNano_1.3.jar<br /> stelo.RamTrackSurfer 1.2,http://darkcanuck.net/rumble/robots/stelo.RamTrackSurfer_1.2.jar<br /> stelo.Randomness 1.1,http://www.robocoderepository.com/BotFiles/3021/stelo.Randomness_1.1.jar<br /> stelo.Spread 0.2,http://www.robocoderepository.com/BotFiles/3922/stelo.Spread_0.2.jar<br /> stelo.SteloTestNano 1.0,http://darkcanuck.net/rumble/robots/stelo.SteloTestNano_1.0.jar<br /> stelo.UnfoolableNano 1.0,http://darkcanuck.net/rumble/robots/stelo.UnfoolableNano_1.0.jar<br /> stelo.UntouchableNano 1.4,http://darkcanuck.net/rumble/robots/stelo.UntouchableNano_1.4.jar<br /> step.nanoPri 1.0,http://www.robocoderepository.com/BotFiles/2996/step.nanoPri_1.0.jar<br /> step.NanoBidu 1.0,http://www.robocoderepository.com/BotFiles/3014/step.NanoBidu_1.0.jar<br /> stf.PanzerGeneral 0.1,http://www.robocoderepository.com/BotFiles/2233/stf.PanzerGeneral_0.1.jar<br /> stordy.StordyBot 1.0,http://sites.google.com/site/stordyrobo/Home/stordy.StordyBot_1.0.jar<br /> strider.Festis 1.2.1,http://www.robocoderepository.com/BotFiles/2355/strider.Festis_1.2.1.jar<br /> strider.Mer 1.1.0,http://www.robocoderepository.com/BotFiles/2360/strider.Mer_1.1.0.jar<br /> stuff.Vlad 0.1,http://www.robocoderepository.com/BotFiles/3701/stuff.Vlad_0.1.jar<br /> sul.NanoR2 1.32,http://www.robocoderepository.com/BotFiles/3348/sul.NanoR2_1.32.jar<br /> sul.Pinkbot 1.1,http://www.robocoderepository.com/BotFiles/3346/sul.Pinkbot_1.1.jar<br /> sul.Bicephal 1.2,http://www.robocoderepository.com/BotFiles/3343/sul.Bicephal_1.2.jar<br /> sul.BlueBot 1.0,http://www.robocoderepository.com/BotFiles/3347/sul.BlueBot_1.0.jar<br /> SuperSample.SuperCrazy 1.0,http://file.csdgn.org/robocode/SuperSample.SuperCrazy_1.0.jar<br /> syl.Centipede 0.5,http://www.robocoderepository.com/BotFiles/1254/syl.Centipede_0.5.jar<br /> synapse.Geomancy 15,http://sites.google.com/site/synapsebots/home/synapse.Geomancy_15.jar?attredirects=0<br /> synapse.rsim.GeomancyBS 0.11,http://robocoderepository.com/BotFiles/3758/synapse.rsim.GeomancyBS_0.11.jar<br /> synnalagma.NeuralPremier 0.51,http://www.robocoderepository.com/BotFiles/1557/synnalagma.NeuralPremier_0.51.jar<br /> synnalagma.test.MiniNeural 1.1,http://www.robocoderepository.com/BotFiles/1754/synnalagma.test.MiniNeural_1.1.jar<br /> tad.Dalek98 0.98,http://darkcanuck.net/rumble/robots/tad.Dalek98_0.98.jar<br /> takeBot.SpinSpiral 1.2,http://www.robocoderepository.com/BotFiles/312/takeBot.SpinSpiral_1.2.jar<br /> takeBot.SpiralCrash 1.0,http://www.robocoderepository.com/BotFiles/1013/takeBot.SpiralCrash_1.0.jar<br /> takeBot.WeavingWiggle 1.1,http://www.robocoderepository.com/BotFiles/1012/takeBot.WeavingWiggle_1.1.jar<br /> tango.Recrimpo 2.51,http://www.robocoderepository.com/BotFiles/2015/tango.Recrimpo_2.51.jar<br /> taqho.taqbot 1.0,http://www.robocoderepository.com/BotFiles/1316/taqho.taqbot_1.0.jar<br /> tcf.Drifter 29,http://www.7sun.com/robocode/robots/tcf.Drifter_29.jar<br /> tcf.Repat3 2,http://www.robocoderepository.com/BotFiles/3328/tcf.Repat3_2.jar<br /> techdude.kombat.FlamingKombat 1.5,http://www.robocoderepository.com/BotFiles/2810/techdude.kombat.FlamingKombat_1.5.jar<br /> techdude.Class2C.Class2C 0.1,http://www.robocoderepository.com/BotFiles/3078/techdude.Class2C.Class2C_0.1.jar<br /> test.Podgy 4.0,http://www.robocoderepository.com/BotFiles/3214/test.Podgy_4.0.jar<br /> test.Fuzzer 1.0.1,http://www.robocoderepository.com/BotFiles/3345/test.Fuzzer_1.0.1.jar<br /> testantiswapgun.AntiSwap 1.0,http://www.robocode.ilbello.com/asd.AntiSwap_1.0.jar<br /> throxbot.ThroxBot 0.1,http://www.robocoderepository.com/BotFiles/2548/throxbot.ThroxBot_0.1.jar<br /> tide.pear.Pear 0.62.1,http://www.robocoderepository.com/BotFiles/2393/tide.pear.Pear_0.62.1.jar<br /> timmit.micro.TimXJ 0.22,http://www.robocoderepository.com/BotFiles/1683/timmit.micro.TimXJ_0.22.jar<br /> timmit.mini.TimVA 0.43,http://www.robocoderepository.com/BotFiles/1681/timmit.mini.TimVA_0.43.jar<br /> timmit.nano.TimCat 0.13,http://www.robocoderepository.com/BotFiles/1600/timmit.nano.TimCat_0.13.jar<br /> timmit.nano.TimDog 0.33,http://www.robocoderepository.com/BotFiles/1602/timmit.nano.TimDog_0.33.jar<br /> timmit.TimmiT 0.22,http://www.robocoderepository.com/BotFiles/1468/timmit.TimmiT_0.22.jar<br /> TJ.Exupery 1.39,http://www.robocoderepository.com/BotFiles/3970/TJ.Exupery1.39.jar<br /> tjk.deBroglie 0.66,http://robocoderepository.com/BotFiles/3989/tjk.deBroglie_0.66.jar<br /> tlp.ThreeLeggedPig 1,http://pages.prodigy.net/franz1/house/tlp.ThreeLeggedPig_1.jar<br /> tm.Yuugao 1.0,http://www.robocoderepository.com/BotFiles/1056/tm.Yuugao_1.0.jar<br /> tobe.calypso.Calypso 4.1,http://www.robocoderepository.com/BotFiles/784/tobe.calypso.Calypso_4.1.jar<br /> tobe.Fusion 1.0,http://www.robocoderepository.com/BotFiles/649/tobe.Fusion_1.0.jar<br /> tobe.mini.Charon 0.9,http://www.robocoderepository.com/BotFiles/836/tobe.mini.Charon_0.9.jar<br /> tobe.Relativity 3.9,http://www.robocoderepository.com/BotFiles/360/tobe.Relativity_3.9.jar<br /> tobe.Saturn lambda,http://www.robocoderepository.com/BotFiles/685/tobe.Saturn_lambda.jar<br /> tornyil.bottomup.BottomUp 1.05,http://www.alpha-consulting.hu/robo/tornyil.bottomup.BottomUp_1.05.jar<br /> tornyil.Lajcsi2.Lajcsi2sm 1.0,http://www.alpha-consulting.hu/robo/tornyil.Lajcsi2.Lajcsi2sm_1.0.jar<br /> toz.Gnome 1.1,http://darkcanuck.net/rumble/robots/toz.Gnome_1.1.jar<br /> trab.Crusader 0.1.7,http://www.stud.ntnu.no/~grashei/bots/trab.Crusader_0.1.7.jar<br /> trab.nano.AinippeNano 1.3,http://www.stud.ntnu.no/~grashei/bots/trab.nano.AinippeNano_1.3.jar<br /> tw.Exterminator 1.0,http://www.robocoderepository.com/BotFiles/3607/tw.Exterminator_1.0.jar<br /> tzu.TheArtOfWar 1.2,http://darkcanuck.net/rumble/robots/tzu.TheArtOfWar_1.2.jar<br /> uccc.Dorito 1.12,http://www.devfluid.com/csc_w/images/e/e9/Uccc.Dorito_1.12.jar<br /> uccc.MilkyWay 1.01,http://www.devfluid.com/csc_w/images/a/a6/Uccc.MilkyWay_1.01.jar<br /> uccc.RingDing 1.12,http://www.devfluid.com/csc_w/images/5/5f/Uccc.RingDing_1.12.jar<br /> uccc.Scrapple 1.0,http://www.devfluid.com/csc_w/images/7/7a/Uccc.Scrapple_1.0.jar<br /> urdos.URDOS 1.3,http://darkcanuck.net/rumble/robots/urdos.URDOS_1.3.jar<br /> usa.nano.Nemo 2.0,http://www.robocoderepository.com/BotFiles/2045/usa.nano.Nemo_2.0.jar<br /> vic.Locke 0.7.5.5,http://www.robocoderepository.com/BotFiles/2115/vic.Locke_0.7.5.5.jar<br /> vft.Valkyrie 1.0,http://www.robocoderepository.com/BotFiles/3009/vft.Valkyrie_1.0.jar<br /> vft.Hrist 1.0,http://darkcanuck.net/rumble/robots/vft.Hrist_1.0.jar<br /> vjik.UnViolation 1.1,http://www.robocoderepository.com/BotFiles/3886/vjik.UnViolation_1.1.jar<br /> voidious.Diamond 1.5.38b,http://www.dijitari.com/void/robocode/voidious.Diamond_1.5.38b.jar<br /> voidious.Dookious 1.573c,http://www.dijitari.com/void/robocode/voidious.Dookious_1.573c.jar<br /> voidious.micro.Jen 1.11,http://www.dijitari.com/void/robocode/voidious.micro.Jen_1.11.jar<br /> voidious.mini.Komarious 1.88,http://www.dijitari.com/void/robocode/voidious.mini.Komarious_1.88.jar<br /> vuen.Fractal 0.55,http://www.robocoderepository.com/BotFiles/1579/vuen.Fractal_0.55.jar<br /> wcsv.Engineer.Engineer 0.5.4,http://darkcanuck.net/rumble/robots/wcsv.Engineer.Engineer_0.5.4.jar<br /> wcsv.PowerHouse.PowerHouse 1.7e3,http://darkcanuck.net/rumble/robots/wcsv.PowerHouse.PowerHouse_1.7e3.jar<br /> wcsv.mega.PowerHouse2 0.2,http://darkcanuck.net/rumble/robots/wcsv.mega.PowerHouse2_0.2.jar<br /> wcsv.Stampede 1.3.3,http://www.robocoderepository.com/BotFiles/2527/wcsv.Stampede_1.3.3.jar<br /> wcsv.Stampede2.Stampede2 1.1.0,http://www.robocoderepository.com/BotFiles/2714/wcsv.Stampede2.Stampede2_1.1.0.jar<br /> WdV.Lesserbee 0.01,http://www.robocoderepository.com/BotFiles/4046/WdV.Lesserbee_0.01.jar<br /> whind.Constitution 0.7.1,http://www.robocoderepository.com/BotFiles/2812/whind.Constitution_0.7.1.jar<br /> whind.Strength 0.6.4,http://whindgames.50webs.com/otherstuff/whind.Strength_0.6.4.jar<br /> whind.StrengthBee 0.6.4,http://whindgames.50webs.com/otherstuff/whind.StrengthBee_0.6.4.jar<br /> whind.Wisdom 0.5.1,http://www.robocoderepository.com/BotFiles/2742/whind.Wisdom_0.5.1.jar<br /> wiki.BasicGFSurfer 1.02,http://www.dijitari.com/void/robocode/wiki.BasicGFSurfer_1.02.jar<br /> wiki.mako.MakoHT 1.2.2.1,http://www.robocoderepository.com/BotFiles/1374/wiki.mako.MakoHT_1.2.2.1.jar<br /> wiki.mini.BlackDestroyer 0.9.0,http://www.robocoderepository.com/BotFiles/1927/wiki.mini.BlackDestroyer_0.9.0.jar<br /> wiki.mini.GouldingiHT 1.0,http://www.robocoderepository.com/BotFiles/1383/wiki.mini.GouldingiHT_1.0.jar<br /> wiki.mini.Griffon 0.1,http://www.robocoderepository.com/BotFiles/1774/wiki.mini.Griffon_0.1.jar<br /> wiki.mini.Sedan 1.0,http://www.robocoderepository.com/BotFiles/1676/wiki.mini.Sedan_1.0.jar<br /> wiki.nano.DevilFISH 1.0,http://www.robocoderepository.com/BotFiles/2235/wiki.nano.DevilFISH_1.0.jar<br /> wiki.nano.RaikoNano 1.1,http://www.robocoderepository.com/BotFiles/2163/wiki.nano.RaikoNano_1.1.jar<br /> wiki.WaveRammer 1.0,http://www.robocoderepository.com/BotFiles/3505/wiki.WaveRammer_1.0.jar<br /> wiki.Wolverine 2.1,http://darkcanuck.net/rumble/robots/wiki.Wolverine_2.1.jar<br /> wilson.Chameleon 0.91,http://www.robocoderepository.com/BotFiles/1608/wilson.Chameleon_0.91.jar<br /> winamp32.micro.MicroMacro 1.0,http://www.robocoderepository.com/BotFiles/2891/winamp32.micro.MicroMacro_1.0.jar<br /> wit.Chuliath 1.0,http://www.robocoderepository.com/BotFiles/2306/wit.Chuliath_1.0.jar<br /> wit.Deep7 2.0,http://www.robocoderepository.com/BotFiles/2313/wit.Deep7_2.0.jar<br /> xandercat.XanderCat 2.1,http://www.distantvisions.net/robocode/xandercat.XanderCat-2.1.jar<br /> xandercat.XanderCat 3.0,http://www.distantvisions.net/robocode/xandercat.XanderCat-3.0.jar<br /> xiongan.Xiongan 1.1,http://www.robocoderepository.com/BotFiles/3565/xiongan.Xiongan_1.1.jar<br /> yarghard.Y101 1.0,http://sliwa.ws/RoboCode/yarghard.Y101_1.0.jar<br /> yk.JahMicro 1.0,http://www.robocoderepository.com/BotFiles/3033/yk.JahMicro_1.0.jar<br /> yk.JahRoslav 1.1,http://www.robocoderepository.com/BotFiles/3032/yk.JahRoslav_1.1.jar<br /> zen.Lindada 0.2,http://www.robocoderepository.com/BotFiles/1679/zen.Lindada_0.2.jar<br /> zeze2.OperatorZeze 1.05,http://www.robocoderepository.com/BotFiles/3330/zeze2.OperatorZeze_1.05.jar<br /> zch.David 0.21,http://www.robocoderepository.com/BotFiles/3575/zch.David_0.21.jar<br /> zch.Hirkan 0.11,http://www.robocoderepository.com/BotFiles/1288/zch.Hirkan_0.11.jar<br /> zh.UnderDog 0.0.2,http://www.robocoderepository.com/BotFiles/3053/zh.UnderDog_0.0.2.jar<br /> zyx.mega.YersiniaPestis 3.0,http://darkcanuck.net/rumble/robots/zyx.mega.YersiniaPestis_3.0.jar<br /> zyx.micro.Ant 1.1,http://www.robocoderepository.com/BotFiles/3481/zyx.micro.Ant_1.1.jar<br /> zyx.nano.Ant 1.1,http://www.robocoderepository.com/BotFiles/3493/zyx.nano.Ant_1.1.jar<br /> zyx.nano.EscherichiaColi 1.0,http://darkcanuck.net/rumble/robots/zyx.nano.EscherichiaColi_1.0.jar<br /> zyx.nano.RedBull 1.0,http://darkcanuck.net/rumble/robots/zyx.nano.RedBull_1.0.jar<br /> &lt;/pre&gt;<br /> ----<br /> '''''No chatting on this page. Use the /ParticipantsChat page for that.'''''<br /> <br /> '''''Removed because the jarcontent/filename is not correct'''''&lt;br&gt;<br /> ''cberendt.Bot1 0.160''&lt;br&gt;<br /> ''dmsr.MiniR101 0.6''&lt;br&gt;<br /> ''henriquevilela.TieFighter 0.1,3224''&lt;br&gt;<br /> ''jgap.Aspirant_7980_gen7 1.0,3552''br&gt;<br /> ''jgap.Aspirant_13029_gen7 1.0,3553''&lt;br&gt;<br /> ''techdude.Carruthers 1.2.6''&lt;br&gt;<br /> ''uccc.Orbiter 1.0''&lt;br&gt;<br /> ''WhoAmI.WhoAmI 1.00''&lt;br&gt;<br /> <br /> '''''Removed until file corruption is resolved:'''''<br /> <br /> ''cas.CelsoKiller 1.0,3465''<br /> <br /> '''''Removed due to almost always giving '0' scores:'''''<br /> <br /> ''com.syncleus.robocode.Dreadnaught 0.1,3426''&lt;br&gt;<br /> ''lazarecki.PinkerStinker 0.1,http://www.robocoderepository.com/BotFiles/3824/lazarecki.PinkerStinker_0.1.jar''<br /> <br /> '''''Removed because it's incorrectly packaged:'''''<br /> <br /> ''Indesh.Indesh 1.1,http://jakobserlier.250free.com/Indesh.jar''<br /> <br /> <br /> ----<br /> <br /> '''''Removed due to WontFix issues in Robocode 1.7+:'''''&lt;br&gt;<br /> ''* Hviela: ([[http://sourceforge.net/tracker/?func=detail&amp;aid=2953268&amp;group_id=37202&amp;atid=419486 SF #2953268]])''&lt;br&gt;<br /> '': hvilela.HVilela 0.9.3,http://henrique.vilela.googlepages.com/hvilela.HVilela_0.9.3.jar''&lt;br&gt;<br /> ''* Barney (Tries to write files without using RobocodeOutputStream. Robocode 1.7 punishes for that more harshly which will give 0 scores)&lt;br&gt;<br /> '': Homer.Barney 1.0,http://www.robocoderepository.com/BotFiles/1932/Homer.Barney_1.0.jar&lt;br&gt;</div>

Miked0801 http://robowiki.net/w/index.php?title=RoboRumble/Participants&diff=19435 2011-06-04T04:55:54Z

<p>Miked0801: 2nd try</p> <hr /> <div>{{:RoboRumble/Navigation}}<br /> <br /> ----<br /> Just add your bot name ('''as appears in the Robocode selector after packaging''', so including versionnumber) and the RobocodeRepository id number separated by &quot;,&quot; (there must be no space after the comma).&lt;br&gt; <br /> Please, make sure your bot is not in the list before adding it, and delete the old version if you are adding a new one.<br /> &lt;br&gt;<br /> The list is in '''alphabetical''' order. Add your bot in the right slot.<br /> <br /> ----<br /> &lt;pre&gt;<br /> ab.DengerousRoBatra 1.3,http://www.robocoderepository.com/BotFiles/3664/ab.DengerousRoBatra_1.3.jar<br /> abc.Shadow 3.83c,http://robocode.aclsi.pt/abc.Shadow_3.83c.jar<br /> abc.tron3.Tron 3.11,http://www.robocoderepository.com/BotFiles/2205/abc.tron3.Tron_3.11.jar<br /> abc.Tron 2.02,http://www.robocoderepository.com/BotFiles/241/abc.Tron_2.02.jar<br /> abud.ThirdRobo 1.0,http://www.robocoderepository.com/BotFiles/2479/abud.ThirdRobo_1.0.jar<br /> ad.last.Bottom 1.0,http://www.robocoderepository.com/BotFiles/1876/ad.last.Bottom_1.0.jar<br /> ad.Quest 0.10,http://www.robocoderepository.com/BotFiles/1846/ad.Quest_0.10.jar<br /> adt.Ar1 2.1,http://www.robocoderepository.com/BotFiles/2254/adt.Ar1_2.1.jar<br /> adt.Ar2 1.0,http://www.robocoderepository.com/BotFiles/2303/adt.Ar2_1.0.jar<br /> ag.Gir 0.99,http://www.robocoderepository.com/BotFiles/3065/ag.Gir_0.99.jar<br /> agd.Mooserwirt2 2.7,http://www.glyndavies.org/robocode/agd.Mooserwirt2.jar<br /> ags.Glacier 0.2.7,http://rednaxela-robocode.dyndns.org/data/robots/ags.Glacier_0.2.7.jar<br /> ags.micro.Carpet 1.1,http://rednaxela-robocode.dyndns.org/data/robots/ags.micro.Carpet_1.1.jar<br /> ags.Midboss 1s,http://rednaxela-robocode.dyndns.org/data/robots/ags.Midboss_1s.jar<br /> ags.polished.PolishedRuby 1,http://rednaxela-robocode.dyndns.org/data/robots/ags.polished.PolishedRuby_1.jar<br /> ags.rougedc.RougeDC willow,http://rednaxela-robocode.dyndns.org/data/robots/ags.rougedc.RougeDC_willow.jar<br /> ahf.Acero 1.0,http://www.robocoderepository.com/BotFiles/2151/ahf.Acero_1.0.jar<br /> ahf.NanoAndrew .4,http://www.robocoderepository.com/BotFiles/2002/ahf.NanoAndrew_.4.jar<br /> ahf.r2d2.R2d2 0.86,http://www.robocoderepository.com/BotFiles/2035/ahf.r2d2.R2d2_0.86.jar<br /> ahr.ice.Ice 1.0,http://robocoderepository.com/BotFiles/3966/ahr.ice.Ice_1.0.jar<br /> ahr.ice.Ice 1.0.1,http://robocoderepository.com/BotFiles/3978/ahr.ice.Ice_1.0.1.jar<br /> AIR.iRobot 1.0,http://www.robocoderepository.com/BotFiles/3205/AIR.iRobot_1.0.jar<br /> ak.Fermat 2.0,http://www.robocoderepository.com/BotFiles/799/ak.Fermat_2.0.jar<br /> alex.Diabolo5 1.1,http://darkcanuck.net/rumble/robots/alex.Diabolo5_1.1.jar<br /> alk.lap.LoudAndProud 2.23,http://www.robocoderepository.com/BotFiles/3601/alk.lap.LoudAndProud_2.23.jar<br /> am.Miedzix 2.0,http://www.robocoderepository.com/BotFiles/3383/am.Miedzix_2.0.jar<br /> am.Miedzix 3.0,http://darkcanuck.net/rumble/robots/am.Miedzix_3.0.jar<br /> amarok.Rookie 1.1,http://www.robocoderepository.com/BotFiles/422/amarok.Rookie_1.1.jar<br /> amk.ChumbaMini 0.2,http://www.robocoderepository.com/BotFiles/2655/amk.ChumbaMini_0.2.jar<br /> amk.ChumbaWumba 0.3,http://www.robocoderepository.com/BotFiles/2646/amk.ChumbaWumba_0.3.jar<br /> amk.jointstrike.JointStrike 0.2,http://www.robocoderepository.com/BotFiles/2597/amk.jointstrike.JointStrike_0.2.jar<br /> amk.ShizzleStiX.ShizzleStiX 0.6,http://www.robocoderepository.com/BotFiles/2603/amk.ShizzleStiX.ShizzleStiX_0.6.jar<br /> amk.superstrike.SuperStrike 0.3,http://www.robocoderepository.com/BotFiles/2600/amk.superstrike.SuperStrike_0.3.jar<br /> amk.Punbot.Punbot 0.01,http://www.robocoderepository.com/BotFiles/2604/amk.Punbot.Punbot_0.01.jar<br /> ao.T100 0.9,http://www.robocoderepository.com/BotFiles/3385/ao.T100_0.9.jar<br /> ap.Frederick 1.1,http://darkcanuck.net/rumble/robots/ap.Frederick_1.1.jar<br /> apollokidd.ApolloKidd 0.9,http://www.robocoderepository.com/BotFiles/321/apollokidd.ApolloKidd_0.9.jar<br /> apv.Aspid 1.7,http://www.robocoderepository.com/BotFiles/1412/apv.Aspid_1.7.jar<br /> apv.AspidReloaded 0.6,http://www.robocoderepository.com/BotFiles/1985/apv.AspidReloaded_0.6.jar<br /> apv.LauLectrik 1.2,http://www.robocoderepository.com/BotFiles/1300/apv.LauLectrik_1.2.jar<br /> apv.MicroAspid 1.8,http://www.robocoderepository.com/BotFiles/2519/apv.MicroAspid_1.8.jar<br /> apv.NanoLauLectrik 1.0,http://www.robocoderepository.com/BotFiles/1399/apv.NanoLauLectrik_1.0.jar<br /> apv.NanoLauLectrikTheCannibal 1.1,http://www.robocoderepository.com/BotFiles/2147/apv.NanoLauLectrikTheCannibal_1.1.jar<br /> apv.ScruchiPu 1.0,http://www.robocoderepository.com/BotFiles/1367/apv.ScruchiPu_1.0.jar<br /> apv.test.Virus 0.6.1,http://www.robocoderepository.com/BotFiles/2645/apv.test.Virus_0.6.1.jar<br /> apv.TheBrainPi 0.5fix,http://darkcanuck.net/rumble/robots/apv.TheBrainPi_0.5fix.jar<br /> ar.horizon.Horizon 1.2.2,http://www.robocoderepository.com/BotFiles/3286/ar.horizon.Horizon_1.2.2.jar<br /> ar.QuantumChromodynamics 1.2.1,http://www.robocoderepository.com/BotFiles/3220/ar.QuantumChromodynamics_1.2.1.jar<br /> ar.TheoryOfEverything 1.2.1,http://www.robocoderepository.com/BotFiles/3221/ar.TheoryOfEverything_1.2.1.jar<br /> ara.Shera 0.88,http://www.robocoderepository.com/BotFiles/1050/ara.Shera_0.88.jar<br /> areb.Union 1.06,http://www.robocoderepository.com/BotFiles/2893/areb.Union_1.06.jar<br /> arthord.micro.Apoptygma 0.4,http://www.robocoderepository.com/BotFiles/1688/arthord.micro.Apoptygma_0.4.jar<br /> arthord.micro.Muffin 0.6.1,http://www.robocoderepository.com/BotFiles/1963/arthord.micro.Muffin_0.6.1.jar<br /> arthord.KostyaTszyu Beta2,http://www.robocoderepository.com/BotFiles/2322/arthord.KostyaTszyu_Beta2.jar<br /> arthord.MannyPacquiao Delta2,http://scoutery.awardspace.com/arthord.MannyPacquiao_Delta2.jar<br /> arthord.NanoSatan Mu,http://www.robocoderepository.com/BotFiles/2157/arthord.NanoSatan_Mu.jar<br /> arthord.NanoSatanMelee Beta,http://www.robocoderepository.com/BotFiles/2088/arthord.NanoSatanMelee_Beta.jar<br /> ary.micro.Weak 1.2,http://www.robocoderepository.com/BotFiles/3433/ary.micro.Weak_1.2.jar<br /> ary.mini.Nimi 1.0,http://www.robocoderepository.com/BotFiles/3397/ary.mini.Nimi_1.0.jar<br /> ary.nano.AceSurf 1.2,http://www.robocoderepository.com/BotFiles/3352/ary.nano.AceSurf_1.2.jar<br /> ary.nano.ColorNanoP 1.1,http://www.robocoderepository.com/BotFiles/3629/ary.nano.ColorNanoP_1.1.jar<br /> ary.Crisis 1.0,http://www.robocoderepository.com/BotFiles/3495/ary.Crisis_1.0.jar<br /> ary.Help 1.0,http://darkcanuck.net/rumble/robots/ary.Help_1.0.jar<br /> ary.FourWD 1.3d,http://darkcanuck.net/rumble/robots/ary.FourWD_1.3d.jar<br /> ary.SMG 1.01,http://ary-robocode.110mb.com/ary.SMG_1.01.jar<br /> as.xbots 1.0,http://darkcanuck.net/rumble/robots/as.xbots_1.0.jar<br /> asd.Cthulhu 1.2,http://darkcanuck.net/rumble/robots/asd.Cthulhu_1.2.jar<br /> asm.Statistas 0.1,http://www.robocoderepository.com/BotFiles/1989/asm.Statistas_0.1.jar<br /> aw.GreatWolf 2.0,https://sites.google.com/site/awusa94/robocode/aw.GreatWolf_2.0.jar<br /> awesomeness.Elite 1.0,http://robocoderepository.com/BotFiles/3597/awesomeness.Elite.jar<br /> awl.Locutus 1.0,3844<br /> axeBots.HataMoto 3.09,http://www.robocoderepository.com/BotFiles/1655/axeBots.HataMoto_3.09.jar<br /> axeBots.Musashi 2.18,http://www.robocoderepository.com/BotFiles/1759/axeBots.Musashi_2.18.jar<br /> axeBots.Okami 1.04,http://www.robocoderepository.com/BotFiles/2016/axeBots.Okami_1.04.jar<br /> axeBots.SilverSurfer 2.53.33fix,http://rednaxela-robocode.dyndns.org/data/robots/axeBots.SilverSurfer_2.53.33fix.jar<br /> ayk.WallHugger 1.0,https://sites.google.com/site/khanguyprojects/file-cabinet/ayk.WallHugger_1.0.jar<br /> baal.nano.N 1.42,http://webpages.charter.net/eleeleth/Robots/baal.nano.N_1.42.jar<br /> banshee.mini.Nexus6 0.2.0,http://www.robocoderepository.com/BotFiles/3467/banshee.mini.Nexus6_0.2.0.jar<br /> banshee.micro.Nexus6 0.3.0,http://www.robocoderepository.com/BotFiles/3473/banshee.micro.Nexus6_0.3.0.jar<br /> bayen.nano.Squirrel 0.2,http://www.freewebs.com/bayen/files/bayen.nano.Squirrel_0.2.jar<br /> bayen.nut.Squirrel 1.621,http://darkcanuck.net/rumble/robots/bayen.nut.Squirrel_1.621.jar<br /> bayen.UbaMicro 1.4,http://www.robocoderepository.com/BotFiles/2830/bayen.UbaMicro_1.4.jar<br /> bayen.UbaRamLT 1.0,http://www.robocoderepository.com/BotFiles/2868/bayen.UbaRamLT_1.0.jar<br /> bbo.RamboT 0.3,http://www.robocoderepository.com/BotFiles/2210/bbo.RamboT_0.3.jar<br /> bbo.TheRoof 1.4.3,http://www.robocoderepository.com/BotFiles/2179/bbo.TheRoof_1.4.3.jar<br /> Bemo.Sweet30 1.6.1,http://www.stg-volleyball.de/images/Bemo.Sweet30_1.6.1.jar<br /> benhorner.PureAggression 0.2.6,http://www.robocoderepository.com/BotFiles/3421/benhorner.PureAggression_0.2.6.jar<br /> bh.PencilRain 0.01,http://www.robocoderepository.com/BotFiles/3670/bh.PencilRain-0.01.jar<br /> bigpete.Stewie 1.0,http://www.robocoderepository.com/BotFiles/2927/bigpete.Stewie_1.0.jar<br /> bing2.Melody 1.3.1,http://www.ccs.neu.edu/home/bing/robocode/bing2.Melody_1.3.1.jar<br /> bjl.LoneDragon 0.5,http://www.robocoderepository.com/BotFiles/1929/bjl.LoneDragon_0.5.jar<br /> bndl.LostLion 1.2,http://www.robocoderepository.com/BotFiles/1033/bndl.LostLion_1.2.jar<br /> bons.NanoStalker 1.2,http://www.robocoderepository.com/BotFiles/1179/bons.NanoStalker_1.2.jar<br /> bp.Kuma 1.0,http://www.robocoderepository.com/BotFiles/3238/bp.Kuma_1.0.jar<br /> braaropolis.Abot 1.0,http://darkcanuck.net/rumble/robots/braaropolis.Abot_1.0.jar<br /> brainfade.Fallen 0.63,http://www.robocoderepository.com/BotFiles/2250/brainfade.Fallen_0.63.jar<br /> brainfade.melee.Dusk 0.44,http://www.robocoderepository.com/BotFiles/2518/brainfade.melee.Dusk_0.44.jar<br /> buba.Archivist 0.1,http://www.robocoderepository.com/BotFiles/3899/buba.Archivist_0.1.jar<br /> buba.Buba 0.3,http://www.robocoderepository.com/BotFiles/3896/buba.Buba_0.3.jar<br /> bvh.fnr.Fenrir 0.36l,http://www.robocoderepository.com/BotFiles/1428/bvh.fnr.Fenrir_0.36l.jar<br /> bvh.frg.Friga 0.112dev,http://darkcanuck.net/rumble/robots/bvh.frg.Friga_0.112dev.jar<br /> bvh.fry.Freya 0.82,http://darkcanuck.net/rumble/robots/bvh.fry.Freya_0.82.jar<br /> bvh.hdr.Hodur 0.4,http://www.robocoderepository.com/BotFiles/1954/bvh.hdr.Hodur_0.4.jar<br /> bvh.loki.Loki 0.5,http://www.robocoderepository.com/BotFiles/885/bvh.loki.Loki_0.5.jar<br /> bvh.micro.Freya 0.3,http://www.robocoderepository.com/BotFiles/2815/bvh.micro.Freya_0.3.jar<br /> bvh.micro.Svadilfari 0.2,http://www.robocoderepository.com/BotFiles/1086/bvh.micro.Svadilfari_0.2.jar<br /> bvh.mini.Fenrir 0.39,http://www.robocoderepository.com/BotFiles/1429/bvh.mini.Fenrir_0.39.jar<br /> bvh.mini.Freya 0.55,http://darkcanuck.net/rumble/robots/bvh.mini.Freya_0.55.jar<br /> bvh.mini.Mjolnir 0.3,http://www.robocoderepository.com/BotFiles/2220/bvh.mini.Mjolnir_0.3.jar<br /> bvh.mini.Wodan 0.50,http://www.robocoderepository.com/BotFiles/2064/bvh.mini.Wodan_0.50.jar<br /> bvh.tyr.Tyr 1.74,http://www.robocoderepository.com/BotFiles/886/bvh.tyr.Tyr_1.74.jar<br /> bzdp.BoxCar 2.0,http://www.robocoderepository.com/BotFiles/3703/bzdp.BoxCar_2.0.jar<br /> bzdp.Pansy 2.1,http://www.robocoderepository.com/BotFiles/3726/bzdp.Pansy_2.1.jar<br /> caimano.Furia_Ceca 0.22,http://www.robocoderepository.com/BotFiles/1843/caimano.Furia_Ceca_0.22.jar<br /> cbot.agile.Nibbler 0.2,http://www.robocoderepository.com/BotFiles/1537/cbot.agile.Nibbler_0.2.jar<br /> cbot.cbot.CBot 0.8,http://www.robocoderepository.com/BotFiles/1375/cbot.cbot.CBot_0.8.jar<br /> cf.mini.Chiva 1.0,http://www.robocoderepository.com/BotFiles/2331/cf.mini.Chiva_1.0.jar<br /> cf.OldMan.OldManXP 0.1,http://www.robocoderepository.com/BotFiles/1968/cf.OldMan.OldManXP_0.1.jar<br /> cf.proto.Shiva 2.2,http://www.robocoderepository.com/BotFiles/2409/cf.proto.Shiva_2.2.jar<br /> cf.star.Star2 1.23,http://www.robocoderepository.com/BotFiles/2255/cf.star.Star2_1.23.jar<br /> ch.rhj.rbc.RHJ1 1.0,http://www.robocoderepository.com/BotFiles/1879/ch.rhj.rbc.RHJ1_1.0.jar<br /> CharlieN.Omega.Omega 1.03,http://www.robocoderepository.com/BotFiles/3503/CharlieN.Omega.Omega_1.03.jar<br /> chase.c.Wristwatch 1.0,http://file.csdgn.org/robocode/chase.c.Wristwatch_1.0.jar<br /> chase.pm.Pytko 1.0,http://file.csdgn.org/robocode/chase.pm.Pytko_1.0.jar<br /> chase.s2.Genesis 1.1,http://file.csdgn.org/robocode/chase.s2.Genesis_1.1.jar<br /> chase.s2.Seraphim 2.0.9,http://file.csdgn.org/robocode/chase.s2.Seraphim_2.0.9.jar<br /> chickenfuego.UrChicken2 1.0,http://www.robocoderepository.com/BotFiles/3422/chickenfuego.UrChicken2_1.0.jar<br /> cjk.Merkava 0.1.1,http://www.robocoderepository.com/BotFiles/2637/cjk.Merkava_0.1.1.jar<br /> cjk.Merkava 0.2.0,http://www.robocoderepository.com/BotFiles/2640/cjk.Merkava_0.2.0.jar<br /> cjk.Merkava 0.3.0,http://darkcanuck.net/rumble/robots/cjk.Merkava_0.3.0.jar<br /> cjm.chalk.Chalk 2.6.Be,http://scatterbright.com/robots/cjm.chalk.Chalk_2.6.Be.jar<br /> cjm.Charo 1.1,http://scatterbright.com/robots/cjm.Charo_1.1.jar<br /> cjm.Che 1.2,http://www.robocoderepository.com/BotFiles/2703/cjm.Che_1.2.jar<br /> cjm.Chomsky 1.5,http://scatterbright.com/robots/cjm.Chomsky_1.5.jar<br /> codemojo.nano.Woot 1.0,http://darkcanuck.net/rumble/robots/codemojo.nano.Woot_1.0.jar<br /> cs.ExclusionNano 1.1,http://file.csdgn.org/robocode/cs.ExclusionNano_1.1.jar<br /> csm.NthGeneration 0.04,http://www.robocoderepository.com/BotFiles/1214/csm.NthGeneration_0.04.jar<br /> csp.Eagle 3.30,http://www.robocoderepository.com/BotFiles/2436/csp.Eagle_3.30.jar<br /> css.Delitioner 0.11,http://darkcanuck.net/rumble/robots/css.Delitioner_0.11.jar<br /> cx.BlestPain 1.41,http://www.robocoderepository.com/BotFiles/1671/cx.BlestPain_1.41.jar<br /> cx.CigaretBH 1.03,http://www.robocoderepository.com/BotFiles/1414/cx.CigaretBH_1.03.jar<br /> cx.Lacrimas 1.36,http://www.robocoderepository.com/BotFiles/1820/cx.Lacrimas_1.36.jar<br /> cx.micro.Blur 0.2,http://www.robocoderepository.com/BotFiles/2447/cx.micro.Blur_0.2.jar<br /> cx.micro.Smoke 0.96,http://www.robocoderepository.com/BotFiles/1037/cx.micro.Smoke_0.96.jar<br /> cx.micro.Spark 0.6,http://www.robocoderepository.com/BotFiles/1320/cx.micro.Spark_0.6.jar<br /> cx.mini.BlackSwans 0.60,http://www.robocoderepository.com/BotFiles/1158/cx.mini.BlackSwans_0.60.jar<br /> cx.mini.Cigaret 1.31,http://www.robocoderepository.com/BotFiles/1152/cx.mini.Cigaret_1.31.jar<br /> cx.mini.Nimrod 0.55,http://www.robocoderepository.com/BotFiles/1236/cx.mini.Nimrod_0.55.jar<br /> cx.nano.Smog 2.6,http://www.robocoderepository.com/BotFiles/1036/cx.nano.Smog_2.6.jar<br /> cx.Princess 1.0,http://www.robocoderepository.com/BotFiles/1343/cx.Princess_1.0.jar<br /> da.NewBGank 1.4,http://www.robocoderepository.com/BotFiles/3312/da.NewBGank_1.4.jar<br /> dam.MogBot 2.9,http://www.robocoderepository.com/BotFiles/555/dam.MogBot_2.9.jar<br /> dans.Cinnamon 1.2,http://www.robocoderepository.com/BotFiles/1976/dans.Cinnamon_1.2.jar<br /> darkcanuck.Gaff 1.50,http://darkcanuck.net/rumble/robots/darkcanuck.Gaff_1.50.jar<br /> darkcanuck.Holden 1.13a,http://darkcanuck.net/rumble/robots/darkcanuck.Holden_1.13a.jar<br /> darkcanuck.Pris 0.88,http://darkcanuck.net/rumble/robots/darkcanuck.Pris_0.88.jar<br /> davidalves.Firebird 0.25,http://davidalves.net/robocode/robots/davidalves.Firebird_0.25.jar<br /> davidalves.Phoenix 1.02,http://davidalves.net/robocode/robots/davidalves.Phoenix_1.02.jar<br /> davidalves.PhoenixOS 1.1,http://davidalves.net/robocode/robots/davidalves.PhoenixOS_1.1.jar<br /> davidalves.net.Duelist 0.1.6src,http://www.robocoderepository.com/BotFiles/1000/davidalves.net.Duelist_0.1.6src.jar<br /> davidalves.net.DuelistMicro 1.22,http://www.robocoderepository.com/BotFiles/1144/davidalves.net.DuelistMicro_1.22.jar<br /> davidalves.net.DuelistMicroMkII 1.1,http://www.robocoderepository.com/BotFiles/1281/davidalves.net.DuelistMicroMkII_1.1.jar<br /> davidalves.net.DuelistMini 1.1,http://www.robocoderepository.com/BotFiles/1181/davidalves.net.DuelistMini_1.1.jar<br /> davidalves.net.DuelistNano 1.0,http://www.robocoderepository.com/BotFiles/1272/davidalves.net.DuelistNano_1.0.jar<br /> dcs.Eater_of_Worlds 1.1.3-A,http://www.robocoderepository.com/BotFiles/2578/dcs.Eater_of_Worlds_1.1.3-A.jar<br /> dcs.Eater_of_Worlds_Mini 1.0,http://www.robocoderepository.com/BotFiles/2850/dcs.Eater_of_Worlds_Mini_1.0.jar<br /> dcs.PM.Eater_of_Worlds_PM 1.2,http://www.robocoderepository.com/BotFiles/2856/dcs.PM.Eater_of_Worlds_PM_1.2.jar<br /> de.erdega.robocode.Polyphemos 0.4,http://darkcanuck.net/rumble/robots/de.erdega.robocode.Polyphemos_0.4.jar<br /> deewiant.Anomaly 0.2,http://www.iki.fi/~deewiant/files/deewiant.Anomaly_0.2.jar<br /> deith.Czolgzilla 0.11,http://www.robocoderepository.com/BotFiles/3256/deith.Czolgzilla_0.11.jar<br /> demetrix.ForceMajeure 0.75,http://ever-rage.narod.ru/robowiki/demetrix.ForceMajeure_0.75.jar<br /> demetrix.nano.Neutrino 0.27,http://ever-rage.narod.ru/robowiki/demetrix.nano.Neutrino_0.27.jar<br /> demetrix.nano.SledgeHammer 0.22,http://ever-rage.narod.ru/robowiki/demetrix.nano.SledgeHammer_0.22.jar<br /> deo.CloudBot 1.3,http://robocoderepository.com/BotFiles/3644/deo.CloudBot_1.3.jar<br /> deo.FlowerBot 1.0,http://robocoderepository.com/BotFiles/3683/deo.FlowerBot_1.0.jar<br /> deo.virtual.RainbowBot 1.0,http://robocoderepository.com/BotFiles/3694/deo.virtual.RainbowBot_1.0.jar<br /> dft.Calliope 5.6,http://www.robocoderepository.com/BotFiles/237/dft.Calliope_5.6.jar<br /> dft.Cyanide 1.90,http://darkcanuck.net/rumble/robots/dft.Cyanide_1.90.jar<br /> dft.Cyprus 3.0,http://www.robocoderepository.com/BotFiles/377/dft.Cyprus_3.0.jar<br /> dft.Freddie 1.32,http://darkcanuck.net/rumble/robots/dft.Freddie_1.32.jar<br /> dft.Guppy 1.0,http://darkcanuck.net/rumble/robots/dft.Guppy_1.0.jar<br /> dft.Immortal 1.40,http://darkcanuck.net/rumble/robots/dft.Immortal_1.40.jar<br /> dft.Krazy 1.5,http://www.robocoderepository.com/BotFiles/2099/dft.Krazy_1.5.jar<br /> dft.Virgin 1.25,http://www.robocoderepository.com/BotFiles/1447/dft.Virgin_1.25.jar<br /> dggp.haiku.gpBot_0 1.1,http://www.robocoderepository.com/BotFiles/3154/dggp.haiku.gpBot_0_1.1.jar<br /> dittman.BlindSquirl Retired,http://home.comcast.net/~kokyunage/robocode/ugluk/dittman.BlindSquirl_Retired.jar<br /> djc.Aardvark 0.3.6,http://www.robocoderepository.com/BotFiles/652/djc.Aardvark_0.3.6.jar<br /> djdjdj.NanoSkunk10 1.0,http://davidjoerg.com/robocode/djdjdj.NanoSkunk10_1.0.jar<br /> dk.stable.Gorgatron 1.1,http://www.robocoderepository.com/BotFiles/2112/dk.stable.Gorgatron_1.1.jar<br /> dks.MicroDanMK2 1.0,http://darkcanuck.net/rumble/robots/dks.MicroDanMK2_1.0.jar<br /> DM.Capriite 3.7.2,http://www.robocoderepository.com/BotFiles/2989/DM.Capriite_3.7.2.jar<br /> DM.Chicken 4.0,http://www.robocoderepository.com/BotFiles/3020/DM.Chicken_4.0.jar<br /> DM.Mijit .3,http://www.robocoderepository.com/BotFiles/3043/DM.Mijit_.3.jar<br /> dmp.micro.Aurora 1.41,http://www.robocoderepository.com/BotFiles/853/dmp.micro.Aurora_1.41.jar<br /> dmp.nano.Eve 3.41,http://www.robocoderepository.com/BotFiles/842/dmp.nano.Eve_3.41.jar<br /> donjezza.Jezza 1.0,http://www.robocoderepository.com/BotFiles/3385/donjezza.Jezza_1.0.jar<br /> donjezza.Muncho 1.0,http://www.robocoderepository.com/BotFiles/3384/donjezza.Muncho_1.0.jar<br /> drd.Dreadknoght 0.9,http://www.robocoderepository.com/BotFiles/3835/drd.Dreadknoght_0.9.jar<br /> drm.CobraBora 1.12,http://www.robocoderepository.com/BotFiles/1146/drm.CobraBora_1.12.jar<br /> drm.Magazine 0.39,http://www.robocoderepository.com/BotFiles/989/drm.Magazine_0.39.jar<br /> ds.OoV4 0.3b,http://www.robocoderepository.com/BotFiles/2851/ds.OoV4_0.3b.jar<br /> dsw.StaticD 1.0,http://darkcanuck.net/rumble/robots/dsw.StaticD_1.0.jar<br /> dsx724.VSAB_EP3a 1.0,http://darkcanuck.net/rumble/robots/dsx724.VSAB_EP3a_1.0.jar<br /> dsx724.VSAB_EP3_ATR 1.1,http://www.robocoderepository.com/BotFiles/3432/dsx724.VSAB_EP3_ATR_1.1.jar<br /> DTF.Kludgy 1.2b,http://www.robocoderepository.com/BotFiles/4041/DTF.Kludgy_1.2b.jar<br /> dukie.Ambassador 1.0,http://www.robocoderepository.com/BotFiles/2845/dukie.Ambassador_1.0.jar<br /> dummy.micro.HummingBird 2.14,http://www.robocoderepository.com/BotFiles/369/dummy.micro.HummingBird_2.14.jar<br /> dummy.micro.Sparrow 2.5,http://www.robocoderepository.com/BotFiles/484/dummy.micro.Sparrow_2.5.jar<br /> dummy.mini.Parakeet 2.40,http://www.robocoderepository.com/BotFiles/400/dummy.mini.Parakeet_2.40.jar<br /> dvogon.GangBang 1.0,http://www.robocoderepository.com/BotFiles/3193/dvogon.GangBang_1.0.jar<br /> dy.LevelOne 2.0,http://www.robocoderepository.com/BotFiles/3452/dy.LevelOne_2.0.jar<br /> dz.Caedo 1.4,http://www.robocoderepository.com/BotFiles/1044/dz.Caedo_1.4.jar<br /> dz.GalbaMicro 0.11,http://www.robocoderepository.com/BotFiles/2482/dz.GalbaMicro_0.11.jar<br /> dz.GalbaMini 0.121,http://darkcanuck.net/rumble/robots/dz.GalbaMini_0.121.jar<br /> dz.MostlyHarmlessNano 2.1,http://www.robocoderepository.com/BotFiles/2166/dz.MostlyHarmlessNano_2.1.jar<br /> dz.OthoMicro 0.12,http://www.robocoderepository.com/BotFiles/2198/dz.OthoMicro_0.12.jar<br /> dz.OthoMini 0.15,http://www.robocoderepository.com/BotFiles/2221/dz.OthoMini_0.15.jar<br /> eat.HumblePieLite 1.0,http://www.robocoderepository.com/BotFiles/1088/eat.HumblePieLite_1.0.jar<br /> ebo.Sparse 0.02,http://www.4geeks.de/files/ebo.Sparse_0.02.jar<br /> ebo.Tahoe 1.1.79,http://www.4geeks.de/files/ebo.Tahoe_1.1.79.jar<br /> EE.LittleBig 1.0,http://www.robocoderepository.com/BotFiles/4009/EE.LittleBig_1.0.jar<br /> EFD.AdvancedEFD 0.4.5a,http://sites.google.com/site/jannisbeese/robots/EFD.AdvancedEFD_0.4.5a.jar<br /> el.Attackr 0.1,http://darkcanuck.net/rumble/robots/el.Attackr_0.1.jar<br /> el.JumpShoot 0.2,http://www.robocoderepository.com/BotFiles/3360/el.JumpShoot_0.2.jar<br /> el33t.EL33tGangstarr2 2.0,http://www.robocoderepository.com/BotFiles/2069/el33t.EL33tGangstarr2_2.0.jar<br /> eld.Hmm 1.0,http://darkcanuck.net/rumble/robots/eld.Hmm_1.0.jar<br /> element.Earth 1.1,http://www.robocoderepository.com/BotFiles/3587/element.Earth_1.1.jar<br /> elloco.Flower 0.1r1,http://www.robocoderepository.com/BotFiles/3242/elloco.Flower_0.1r1.jar<br /> elloco.Kabuto 0.2r,http://www.robocoderepository.com/BotFiles/3229/elloco.Kabuto_0.2r.jar<br /> elvbot.ElverionBot 0.3,http://www.robocoderepository.com/BotFiles/3541/elvbot.ElverionBot_0.3.jar<br /> emp.Yngwie 1.11,http://www.robocoderepository.com/BotFiles/1928/emp.Yngwie_1.11.jar<br /> erdnis.Rover 0.3,http://www.free-games-fun.com/erdnis.Rover_0.3.jar<br /> eskimo.micro.Echo 0.1,http://robocoderepository.com/BotFiles/3969/eskimo.micro.Echo_0.1.jar<br /> et.Predator 1.8,http://www.robocoderepository.com/BotFiles/668/et.Predator_1.8.jar<br /> ethdsy.Malacka 2.4,http://www.robocoderepository.com/BotFiles/1159/ethdsy.Malacka_2.4.jar<br /> evd.X1 0.01,http://www.robocoderepository.com/BotFiles/3503/evd.X1_0.01.jar<br /> exauge.GateKeeper 1.1.121g,http://www.robocoderepository.com/BotFiles/3928/exauge.GateKeeper_1.1.121g.jar<br /> exauge.LemonDrop 1.6.130,http://www.robocoderepository.com/BotFiles/3911/exauge.LemonDrop_1.6.130.jar<br /> exauge.Leopard 1.1.019,http://www.robocoderepository.com/BotFiles/3917/exauge.Leopard_1.1.019.jar<br /> extra.LightSauce 0.01,http://www.robocoderepository.com/BotFiles/4031/extra.LightSauce_0.01.jar<br /> extra.Sauce .01,http://robocoderepository.com/BotFiles/4029/extra.Sauce_.01.jar<br /> fala.robocode.FalaRobot 1.0,http://www.robocoderepository.com/BotFiles/3474/fala.robocode.FalaRobot_1.0.jar<br /> fcr.First 1.0,http://www.robocoderepository.com/BotFiles/3362/fcr.First_1.0.jar<br /> Fenix.FenixTrack 1.0,http://www.robocoderepository.com/BotFiles/1627/Fenix.FenixTrack_1.0.jar<br /> florent.FloatingTadpole 1.2.6,http://www.robocoderepository.com/BotFiles/2675/florent.FloatingTadpole_1.2.6.jar<br /> florent.small.LittleAngel 1.8,http://www.robocoderepository.com/BotFiles/2917/florent.small.LittleAngel_1.8.jar<br /> florent.test.Toad 0.14t,http://wesley3.free.fr/florent.test.Toad_0.14t.jar<br /> florent.XSeries.X2 0.17,http://wesley3.free.fr/florent.XSeries.X2_0.17.jar<br /> fm.claire 1.7,http://www.robocoderepository.com/BotFiles/2251/fm.claire_1.7.jar<br /> fm.mammillarias 1.3,http://www.robocoderepository.com/BotFiles/2238/fm.mammillarias_1.3.jar<br /> fnc.bandit.Bandit 5.2.0,http://www.robocoderepository.com/BotFiles/2155/fnc.bandit.Bandit_5.2.0.jar<br /> fnc.bandit2002.Bandit2002 4.0.2,http://www.robocoderepository.com/BotFiles/2202/fnc.bandit2002.Bandit2002_4.0.2.jar<br /> frag.FragBot 1.0,http://darkcanuck.net/rumble/robots/frag.FragBot_1.0.jar<br /> franzor.Lizt 1.3.1,http://pages.prodigy.net/franz1/house/franzor.Lizt_1.3.1.jar<br /> fromHell.CHCl3 0.0.1,http://fromhell.schreiende-stille.de/fromHell.CHCl3_0.0.1.jar<br /> fullsail.LaxativeTeaTwo 1.0,http://www.robocoderepository.com/BotFiles/3403/fullsail.LaxativeTeaTwo_1.0.jar<br /> fullsail.TimbotNoPrediction 1.0,http://darkcanuck.net/rumble/robots/fullsail.TimbotNoPrediction_1.0.jar<br /> fullsail.SweetTea 1.1,http://darkcanuck.net/rumble/robots/fullsail.SweetTea_1.1.jar<br /> fushi.PvP1.PvP1 2004-02-16,http://www.robocoderepository.com/BotFiles/2023/fushi.PvP1.PvP1_2004-02-16.jar<br /> fw.Number1 1.0b,http://www.dijitari.com/void/robocode/fw.Number1_1.0b.jar<br /> gadsky.Gadsky 1.01,http://www.robocoderepository.com/BotFiles/3595/gadsky.Gadsky_1.01.jar<br /> Gecko.ultimateGeckoBot 1.0,http://www.robocoderepository.com/BotFiles/4039/Gecko.ultimateGeckoBot_1.0.jar<br /> geep.mini.GPBotA 1.0,http://www.robocoderepository.com/BotFiles/2361/geep.mini.GPBotA_1.0.jar<br /> geep.mini.GPBotB 1.1,http://www.robocoderepository.com/BotFiles/2363/geep.mini.GPBotB_1.1.jar<br /> germ.TheMind .2,http://www.robocoderepository.com/BotFiles/2525/germ.TheMind_.2.jar<br /> gg.Squaraus 0.6,http://www.robocoderepository.com/BotFiles/1788/gg.Squaraus_0.6.jar<br /> gg.Wolverine 2.0,http://darkcanuck.net/rumble/robots/gg.Wolverine_2.0.jar<br /> gh.GresSuffurd 0.3.2,http://home.versatel.nl/gheijenk/robocode/jarfiles/gh.GresSuffurd_0.3.2.jar<br /> gh.GrubbmGrb 1.2.4,http://home.versatel.nl/gheijenk/robocode/jarfiles/gh.GrubbmGrb_1.2.4.jar<br /> gh.GrypRepetyf 0.13,http://www.robocoderepository.com/BotFiles/2650/gh.GrypRepetyf_0.13.jar<br /> gh.micro.Grinnik 0.7,http://www.robocoderepository.com/BotFiles/3208/gh.micro.Grinnik_0.7.jar<br /> gh.micro.GrubbmThree 0.9,http://www.robocoderepository.com/BotFiles/2444/gh.micro.GrubbmThree_0.9.jar<br /> gh.mini.Gruwel 0.9,http://www.robocoderepository.com/BotFiles/2511/gh.mini.Gruwel_0.9.jar<br /> gh.nano.Grofvuil 0.2,http://www.robocoderepository.com/BotFiles/2553/gh.nano.Grofvuil_0.2.jar<br /> gimp.GimpBot 0.1,http://www.robocoderepository.com/BotFiles/2434/gimp.GimpBot_0.1.jar<br /> gio.RealGioBot 1.0,http://www.robocoderepository.com/BotFiles/2521/gio.RealGioBot_1.0.jar<br /> gjr.Cephalosporin 0.2,http://www.robocoderepository.com/BotFiles/2240/gjr.Cephalosporin_0.2.jar<br /> gm.GaetanoA 2.15,http://www.robocoderepository.com/BotFiles/2188/gm.GaetanoA_2.15.jar<br /> goblin.Bender 2.4,http://www.robocoderepository.com/BotFiles/1871/goblin.Bender_2.4.jar<br /> grybgoofy.GoofyBot 0.10,http://www.robocoderepository.com/BotFiles/2196/grybgoofy.GoofyBot_0.10.jar<br /> gu.MicroScoob 1.3,http://www.robocoderepository.com/BotFiles/2086/gu.MicroScoob_1.3.jar<br /> gwah.GBotMarkIV 1.0,http://www.horula.ca/roborumble/participants/download.php?file=18<br /> gwah.GerryBotMkII 1.5.1,http://www.horula.ca/roborumble/participants/download.php?file=17<br /> hamilton.Hamilton 1.0,http://www.robocoderepository.com/BotFiles/1408/hamilton.Hamilton_1.0.jar<br /> hapiel.Spiral 0.1,http://robocoderepository.com/BotFiles/3997/hapiel.Spiral_0.1.jar<br /> hirataatsushi.Neo 1.6,http://www.robocoderepository.com/BotFiles/1081/hirataatsushi.Neo_1.6.jar<br /> hirataatsushi.Trinity 0.003,http://www.robocoderepository.com/BotFiles/1145/hirataatsushi.Trinity_0.003.jar<br /> homerbots.h1 1.0,http://www.robocoderepository.com/BotFiles/2999/homerbots.h1_1.0.jar<br /> hp.Athena 0.1,http://www.robocoderepository.com/BotFiles/3415/hp.Athena_0.1.jar<br /> hvilela.HVilela 0.9,http://henrique.vilela.googlepages.com/hvilela.HVilela_0.9.jar<br /> ins.MobyNano 0.8,http://www.robocoderepository.com/BotFiles/939/ins.MobyNano_0.8.jar<br /> intruder.PrairieWolf 2.61,http://darkcanuck.net/rumble/robots/intruder.PrairieWolf_2.61.jar<br /> ivor.prophet.Prophet 0.01,http://www.ivan.php5.sk/ivor.prophet.Prophet_0.01.jar<br /> is.fon.rs.FonDestroyer3084 1.0,http://www.robocoderepository.com/BotFiles/4047/is.fon.rs.FonDestroyer3084_1.0.jar<br /> jaara.LambdaBot 1.1,http://www.robocoderepository.com/BotFiles/3514/jaara.LambdaBot_1.1.jar<br /> jab.avk.ManuelGallegus 0.6,http://darkcanuck.net/rumble/robots/jab.avk.ManuelGallegus_0.6.jar<br /> jab.DiamondStealer 5,http://darkcanuck.net/rumble/robots/jab.DiamondStealers_5.jar<br /> jab.micro.Sanguijuela 0.8,http://darkcanuck.net/rumble/robots/jab.micro.Sanguijuela_0.8.jar<br /> janm.Jammy 1.0,http://www.robocoderepository.com/BotFiles/3543/janm.Jammy_1.0.jar<br /> jam.micro.RaikoMicro 1.44,http://www.robocoderepository.com/BotFiles/1983/jam.micro.RaikoMicro_1.44.jar<br /> jam.mini.Raiko 0.43,http://www.robocoderepository.com/BotFiles/1922/jam.mini.Raiko_0.43.jar<br /> jam.RaikoMX 0.32,http://www.robocoderepository.com/BotFiles/1961/jam.RaikoMX_0.32.jar<br /> japs.Serenity 1.0,http://www.robocoderepository.com/BotFiles/2217/japs.Serenity_1.0.jar<br /> japs.Sjonniebot 0.9.1,http://www.robocoderepository.com/BotFiles/2203/japs.Sjonniebot_0.9.1.jar<br /> jasolo.Sonda 0.55,http://www.robocoderepository.com/BotFiles/1534/jasolo.Sonda_0.55.jar<br /> jaw.Mouse 0.11,http://www.robocoderepository.com/BotFiles/2472/jaw.Mouse_0.11.jar<br /> jaw.KarenCain 0.11,http://www.robocoderepository.com/BotFiles/2474/jaw.KarenCain_0.11.jar<br /> jaybot.adv.bots.JayBot 2.0,http://darkcanuck.net/rumble/robots/jaybot.adv.bots.JayBot_2.0.jar<br /> jaybot.bots.Oddball 4.0,http://darkcanuck.net/rumble/robots/jaybot.bots.Oddball_4.0.jar<br /> jbot.Rabbit2 1.1,http://darkcanuck.net/rumble/robots/jbot.Rabbit2_1.1.jar<br /> jcs.AutoBot 4.2.1,http://www.robocoderepository.com/BotFiles/2616/jcs.AutoBot_4.2.1.jar<br /> jcs.Decepticon 2.5.3,http://www.robocoderepository.com/BotFiles/2620/jcs.Decepticon_2.5.3.jar<br /> jcs.Megatron 1.2,http://www.robocoderepository.com/BotFiles/2632/jcs.Megatron_1.2.jar<br /> jcs.Seth 1.8,http://darkcanuck.net/rumble/robots/jcs.Seth_1.8.jar<br /> jcw.ArcherOne 1.0,http://darkcanuck.net/rumble/robots/jcw.ArcherOne_1.0.jar<br /> jekl.DarkHallow .90.9,http://www.robocoderepository.com/BotFiles/2296/jekl.DarkHallow_.90.9.jar<br /> jekl.Jekyl .70,http://www.robocoderepository.com/BotFiles/1837/jekl.Jekyl_.70.jar<br /> jekl.mini.BlackPearl .91,http://www.robocoderepository.com/BotFiles/1875/jekl.mini.BlackPearl_.91.jar<br /> jep.nano.Hawkwing 0.4.1,http://www.robocoderepository.com/BotFiles/1561/jep.nano.Hawkwing_0.4.1.jar<br /> jep.nano.Hotspur 0.1,http://www.robocoderepository.com/BotFiles/1877/jep.nano.Hotspur_0.1.jar<br /> jep.Terrible 0.4.1,http://www.robocoderepository.com/BotFiles/1536/jep.Terrible_0.4.1.jar<br /> jeremyreeder.Vincent 2011.12.09,http://www.robocoderepository.com/BotFiles/3993/jeremyreeder.Vincent_2011.12.09.jar<br /> jf.Dodger 1.1,http://keenehs.dyndns.org:90/rumble/robots/jf.Dodger_1.1.jar<br /> jf.Dodger 1.3,http://keenehs.dyndns.org:90/rumble/robots/jf.Dodger_1.3.jar<br /> jgap.JGAP12584 1.0,http://www.robocoderepository.com/BotFiles/3383/jgap.JGAP12584_1.0.jar<br /> jgap.JGAP130166 1.0,http://www.robocoderepository.com/BotFiles/3371/jgap.JGAP130166_1.0.jar<br /> jgap.JGAP23423 1.0,http://www.robocoderepository.com/BotFiles/3378/jgap.JGAP23423_1.0.jar<br /> jgap.JGAP6139 1.0,http://www.robocoderepository.com/BotFiles/3372/jgap.JGAP6139_1.0.jar<br /> jgap.JGAP7247_2 1.0,http://www.robocoderepository.com/BotFiles/3382/jgap.JGAP7247_2_1.0.jar<br /> jgap.JGAP7958 1.0,http://www.robocoderepository.com/BotFiles/3373/jgap.JGAP7958_1.0.jar<br /> jje.BagPuss 1.2,http://darkcanuck.net/rumble/robots/jje.BagPuss_1.2.jar<br /> jk.mega.DrussGT 1.9.8,http://www.minifly.rchomepage.com/robocode/jk.mega.DrussGT_1.9.8.jar<br /> jk.micro.Toorkild 0.2.4b,http://www.minifly.rchomepage.com/robocode/jk.micro.Toorkild_0.2.4b.jar<br /> jk.mini.CunobelinDC 0.6,https://sites.google.com/site/jkflying/jk.mini.CunobelinDC_0.6.jar<br /> jk.precise.Wintermute 0.7,http://www.minifly.rchomepage.com/robocode/jk.precise.Wintermute_0.7.jar<br /> jmcd.BeoWulf 2.8,http://www.robocoderepository.com/BotFiles/1377/jmcd.BeoWulf_2.8.jar<br /> joe.ADinosaur 1.0,http://www.robocoderepository.com/BotFiles/2822/joe.ADinosaur_1.0.jar<br /> josago.Jorgito 0.16,http://www.robocoderepository.com/BotFiles/4000/josago.Jorgito_0.16.jar<br /> jp.Perpy 16.0,http://www.robocoderepository.com/BotFiles/3001/jp.Perpy_16.0.jar<br /> jp.SineWall 1.0,http://www.robocoderepository.com/BotFiles/2968/jp.SineWall_1.0.jar<br /> jrm.Test0 1.0,http://www.robocoderepository.com/BotFiles/3636/jrm.Test0_1.0.jar<br /> js.PinBall 1.6,http://www.robocoderepository.com/BotFiles/684/js.PinBall_1.6.jar<br /> jsal.Jsalbot 1.0,http://jeremybubs.googlepages.com/jsal.Jsalbot_1.0.jar<br /> jt.SpearmintCT Alpha,http://www.robocoderepository.com/BotFiles/2164/jt.SpearmintCT_Alpha.jar<br /> justin.DemonicRage 3.20,http://sites.google.com/site/justinsitehere/file-cabinet/justin.DemonicRage_3.20.jar<br /> jw.Booring 1.11,http://www.robocoderepository.com/BotFiles/1250/jw.Booring_1.11.jar<br /> jwst.DAD.DarkAndDarker 1.1,http://darkcanuck.net/rumble/robots/jwst.DAD.DarkAndDarker_1.1.jar<br /> kanishk.Fr0z3n 1.1,http://darkcanuck.net/rumble/robots/kanishk.Fr0z3n_1.1.jar<br /> kano.gamma.KanoGamma 1.8,http://www.robocoderepository.com/BotFiles/1098/kano.gamma.KanoGamma_1.8.jar<br /> kawam.kmBot9 1.0,http://www.robocoderepository.com/BotFiles/967/kawam.kmBot9_1.0.jar<br /> kawigi.f.FhqwhgadsMicro 1.0,http://www.robocoderepository.com/BotFiles/1673/kawigi.f.FhqwhgadsMicro_1.0.jar<br /> kawigi.micro.Shiz 1.1,http://www.robocoderepository.com/BotFiles/2007/kawigi.micro.Shiz_1.1.jar<br /> kawigi.mini.Coriantumr 1.1,http://www.robocoderepository.com/BotFiles/1988/kawigi.mini.Coriantumr_1.1.jar<br /> kawigi.mini.Fhqwhgads 1.1,http://www.robocoderepository.com/BotFiles/1604/kawigi.mini.Fhqwhgads_1.1.jar<br /> kawigi.nano.FunkyChicken 1.1,http://www.robocoderepository.com/BotFiles/1512/kawigi.nano.FunkyChicken_1.1.jar<br /> kawigi.nano.ThnikkaBot 0.9,http://www.robocoderepository.com/BotFiles/2059/kawigi.nano.ThnikkaBot_0.9.jar<br /> kawigi.robot.Girl 1.2,http://www.robocoderepository.com/BotFiles/2124/kawigi.robot.Girl_1.2.jar<br /> kawigi.sbf.Barracuda 1.0,http://www.robocoderepository.com/BotFiles/1535/kawigi.sbf.Barracuda_1.0.jar<br /> kawigi.sbf.FloodHT 0.9.2,http://www.robocoderepository.com/BotFiles/1552/kawigi.sbf.FloodHT_0.9.2.jar<br /> kawigi.sbf.FloodMicro 1.5,http://www.robocoderepository.com/BotFiles/1381/kawigi.sbf.FloodMicro_1.5.jar<br /> kawigi.sbf.FloodMini 1.4,http://www.robocoderepository.com/BotFiles/1462/kawigi.sbf.FloodMini_1.4.jar<br /> kawigi.sbf.FloodNano 1.2,http://www.robocoderepository.com/BotFiles/1421/kawigi.sbf.FloodNano_1.2.jar<br /> kawigi.sbf.FloodSonnet 0.9,http://www.robocoderepository.com/BotFiles/1779/kawigi.sbf.FloodSonnet_0.9.jar<br /> kawigi.sbf.Teancum 1.3,http://www.robocoderepository.com/BotFiles/1470/kawigi.sbf.Teancum_1.3.jar<br /> kawigi.spare.SpareParts 0.7.6nosnd,http://www.robocoderepository.com/BotFiles/1335/kawigi.spare.SpareParts_0.7.6nosnd.jar<br /> kc.micro.Needle 0.101,http://www.robocoderepository.com/BotFiles/3379/kc.micro.Needle_0.101.jar<br /> kc.micro.Thorn 1.252,http://sites.google.com/site/kevcsite/robocode/kc.micro.Thorn_1.252.jar<br /> kc.micro.WaveShark 0.31,http://www.robocoderepository.com/BotFiles/3822/kc.micro.WaveShark_0.31.jar<br /> kc.mini.Vyper 0.311,http://darkcanuck.net/rumble/robots/kc.mini.Vyper_0.311.jar<br /> kc.nano.Splinter 1.2,http://darkcanuck.net/rumble/robots/kc.nano.Splinter_1.2.jar<br /> kc.serpent.Hydra 0.21,http://darkcanuck.net/rumble/robots/kc.serpent.Hydra_0.21.jar<br /> kc.serpent.WaveSerpent 2.11,http://sites.google.com/site/kevcsite/robocode/kc.serpent.WaveSerpent_2.11.jar<br /> kcn.percept.PerceptBot 2.3,http://www.robocoderepository.com/BotFiles/1075/kcn.percept.PerceptBot_2.3.jar<br /> kcn.unnamed.Unnamed 1.21,http://www.robocoderepository.com/BotFiles/1969/kcn.unnamed.Unnamed_1.21.jar<br /> kenran.mega.Pantheist 1.1,http://sites.google.com/site/kenranbots/robocode/kenran.mega.Pantheist_1.1.jar<br /> kid.Gladiator .7.2,http://darkcanuck.net/rumble/robots/kid.Gladiator_.7.2.jar<br /> kid.Toa .0.5,http://rednaxela-robocode.dyndns.org/data/robot_archive/kid.Toa_.0.5.jar<br /> KiraNL.Chupacabra 0.5,http://sandbox-project.nl/robocode/KiraNL.Chupacabra_0.5.jar<br /> KiraNL.ChupaLite 0.4,http://sandbox-project.nl/robocode/KiraNL.ChupaLite_0.4.jar<br /> KiraNL.SpaceKees 0.1,http://sandbox-project.nl/robocode/KiraNL.SpaceKees_0.1.jar<br /> kinsen.melee.Angsaichmophobia 1.8c,http://sites.google.com/site/dcvqksyb/robocode/kinsen.melee.Angsaichmophobia_1.8c.jar<br /> kinsen.nano.Hoplomachy 1.6,http://sites.google.com/site/dcvqksyb/robocode/kinsen.nano.Hoplomachy_1.6.jar<br /> kinsen.nano.Quarrelet 1.0,http://sites.google.com/site/dcvqksyb/robocode/kinsen.nano.Quarrelet_1.0.jar<br /> kinsen.nano.Senticous 1.0,http://sites.google.com/site/dcvqksyb/robocode/kinsen.nano.Senticous_1.0.jar<br /> kjc.etc.Dharok 1.0,http://www.robocoderepository.com/BotFiles/3293/kjc.etc.Dharok_1.0.jar<br /> kjc.MailManX 2.0,http://www.robocoderepository.com/BotFiles/3288/kjc.MailManX_2.0.jar<br /> kjc.Karaykan 1.0,http://www.robocoderepository.com/BotFiles/3289/kjc.Karaykan_1.0.jar<br /> klein.GottesKrieger 1.1,http://www.robocoderepository.com/BotFiles/3258/klein.GottesKrieger_1.1.jar<br /> Krabb.fe4r.Fe4r 0.4,http://www.robocoderepository.com/BotFiles/2766/Krabb.fe4r.Fe4r_0.4.jar<br /> Krabb.sliNk.Garm 0.9u,http://designnj.de/roboking/Krabb.sliNk.Garm_0.9u.jar<br /> Krabb.krabby.Krabby 1.18b,http://darkcanuck.net/rumble/robots/Krabb.krabby.Krabby_1.18b.jar<br /> Krabb.krabby2.Krabby2 1.9o,http://darkcanuck.net/rumble/robots/Krabb.krabby2.Krabby2_1.9o.jar<br /> krillr.mini.JointStrike 2.0.0,http://darkcanuck.net/rumble/robots/krillr.mini.JointStrike_2.0.0.jar<br /> krillr.mega.Psyche 0.0.3,http://darkcanuck.net/rumble/robots/krillr.mega.Psyche_0.0.3.jar<br /> kronenthaler.Basilisk 1.0,http://www.robocoderepository.com/BotFiles/4051/kronenthaler.Basilisk_1.0.jar<br /> krzysiek.robbo2.Robbo 1.0.0,http://darkcanuck.net/rumble/robots/krzysiek.robbo2.Robbo_1.0.0.jar<br /> kurios.DOSexe .9a,http://www.kuriosly.com/roborumble/kurios.DOSexe_.9a.jar<br /> kurios.DOSexe .9b,http://www.kuriosly.com/roborumble/kurios.DOSexe_.9b.jar<br /> kvk.HebusLeTroll 0.41,http://www.robocoderepository.com/BotFiles/2125/kvk.HebusLeTroll_0.41.jar<br /> labg.Cataclysm 2.05,http://www.robocoderepository.com/BotFiles/2399/labg.Cataclysm_2.05.jar<br /> lancel.Lynx 1.09,http://www.robocoderepository.com/BotFiles/3992/lancel.Lynx_1.09.jar<br /> lazarecki.mega.PinkerStinker 0.7,http://www.robocoderepository.com/BotFiles/3838/lazarecki.mega.PinkerStinker_0.7.jar<br /> leb.ShootAnArrow 0.1,http://www.robocoderepository.com/BotFiles/2648/leb.ShootAnArrow_0.1.jar<br /> lechu.Ala 0.0.4,http://www.robocoderepository.com/BotFiles/3497/lechu.Ala_0.0.4.jar<br /> lechu.Lechu 1.1,http://www.robocoderepository.com/BotFiles/3480/lechu.Lechu_1.1.jar<br /> lion.Kresnanano 1.0,http://www.robocoderepository.com/BotFiles/2295/lion.Kresnanano_1.0.jar<br /> lk.nano.Avesnar 1.1,http://www.robocoderepository.com/BotFiles/1597/lk.nano.Avesnar_1.1.jar<br /> lorneswork.Predator 1.0,http://www.robocoderepository.com/BotFiles/2609/lorneswork.Predator_1.0.jar<br /> lrem.Spectre 0.4.4,http://www.robocoderepository.com/BotFiles/2253/lrem.Spectre_0.4.4.jar<br /> lrem.magic.TormentedAngel Antiquitie,http://maxnet.org.pl/~lrem/lrem.magic.TormentedAngel_Antiquitie.jar<br /> lrem.micro.MoggFanatic 0.2,http://www.robocoderepository.com/BotFiles/2639/lrem.micro.MoggFanatic_0.2.jar<br /> lrem.micro.FalseProphet Alpha,http://www.robocoderepository.com/BotFiles/2415/lrem.micro.FalseProphet_Alpha.jar<br /> lrem.quickhack.QuickHack 1.0,http://www.robocoderepository.com/BotFiles/2555/lrem.quickhack.QuickHack_1.0.jar<br /> lunchie.Lunchbox 0.93,http://darkcanuck.net/rumble/robots/lunchie.Lunchbox_0.93.jar<br /> lw.LuthersTest 0.1,http://darkcanuck.net/rumble/robots/lw.LuthersTest_0.1.jar<br /> m3thos.Eva00 1.1,http://darkcanuck.net/rumble/robots/m3thos.Eva00_1.1.jar<br /> m3thos.Eva02 0.7.1,http://darkcanuck.net/rumble/robots/m3thos.Eva02_0.7.1.jar<br /> m3thos.mini.Eva01 0.5.5,http://darkcanuck.net/rumble/robots/m3thos.mini.Eva01_0.5.5.jar<br /> ma.is.fon.rs.RobotA 0.01,http://www.robocoderepository.com/BotFiles/4048/ma.is.fon.rs.RobotA_0.01.jar<br /> madmath.Cow 0.1.1,http://www.robocoderepository.com/BotFiles/3476/madmath.Cow_0.1.1.jar<br /> marcinek.TopGun 1.3,http://www.robocoderepository.com/BotFiles/3458/marcinek.TopGun_1.3.jar<br /> marksteam.Phoenix 1.0,http://www.robocoderepository.com/BotFiles/2749/marksteam.Phoenix_1.0.jar<br /> matt.advanced.Katana 1.0,http://www.robocoderepository.com/BotFiles/2498/matt.advanced.Katana_1.0.jar<br /> matt.BlueMind 0.8.00,http://www.robocoderepository.com/BotFiles/2685/matt.BlueMind_0.8.00.jar<br /> matt.UnderDark3 2.4.34,http://www.robocoderepository.com/BotFiles/2485/matt.UnderDark3_2.4.34.jar<br /> matt.UnderDark4 0.4.00,http://www.robocoderepository.com/BotFiles/2644/matt.UnderDark4_0.4.00.jar<br /> mbh.Mbh 0.1,http://www.robocoderepository.com/BotFiles/3365/mbh.Mbh_0.1.jar<br /> mbro.BelajarBot 0.0.3,http://www.robocoderepository.com/BotFiles/2471/mbro.BelajarBot_0.0.3.jar<br /> mbro.Detektor3 0.1.1,http://www.robocoderepository.com/BotFiles/2478/mbro.Detektor3_0.1.1.jar<br /> mc.Messapia 0.1.8,http://www.robocoderepository.com/BotFiles/2223/mc.Messapia_0.1.8.jar<br /> mcb.Audace 1.3,http://www.robocoderepository.com/BotFiles/3424/mcb.Audace_1.3.jar<br /> md.November 1.0,http://www.robocoderepository.com/BotFiles/1004/md.November_1.0.jar<br /> md.Pasta 1.1,http://www.robocoderepository.com/BotFiles/1014/md.Pasta_1.1.jar<br /> md.VelociRaptor 1.3,http://www.robocoderepository.com/BotFiles/232/md.VelociRaptor_1.3.jar<br /> mdouet.BotKicker 2.0,http://www.robocoderepository.com/BotFiles/1478/mdouet.BotKicker_2.0.jar<br /> metal.small.MCool 1.21,http://www.robocoderepository.com/BotFiles/1698/metal.small.MCool_1.21.jar<br /> metal.small.dna2.MCoolDNA 1.5,http://www.robocoderepository.com/BotFiles/2354/metal.small.dna2.MCoolDNA_1.5.jar<br /> microtestbotpack.MicroTestBot 1.0,http://dl.dropbox.com/u/4547352/robocode/microtestbotpack.MicroTestBot_1.0.jar<br /> mk.Alpha 0.2.1,http://darkcanuck.net/rumble/robots/mk.Alpha_0.2.1.jar<br /> mladjo.AIR 0.7,http://www.robocoderepository.com/BotFiles/3187/mladjo.AIR_0.7.jar<br /> mladjo.GnuKlub 0.1,http://darkcanuck.net/rumble/robots/mladjo.GnuKlub_0.1.jar<br /> mladjo.Grrrrr 0.9,http://www.robocoderepository.com/BotFiles/3189/mladjo.Grrrrr_0.9.jar<br /> mladjo.iRobot 0.3,http://www.robocoderepository.com/BotFiles/3149/mladjo.iRobot_0.3.jar<br /> mladjo.Startko 1.0,http://www.robocoderepository.com/BotFiles/3186/mladjo.Startko_1.0.jar<br /> mld.DustBunny 3.8,http://www.robocoderepository.com/BotFiles/3650/mld.DustBunny_3.8.jar<br /> mld.Infinity 2.2,http://www.robocoderepository.com/BotFiles/3591/mld.Infinity_2.2.jar<br /> mld.LittleBlackBook 1.69c,http://www.robocoderepository.com/BotFiles/3873/mld.LittleBlackBook_1.69c.jar<br /> mld.LittleBlackBook 1.69d,https://sites.google.com/site/dorganrobocode/file-cabinet/mld.LittleBlackBook_1.69d.jar<br /> mld.Moebius 2.9.3,http://www.robocoderepository.com/BotFiles/3634/mld.Moebius_2.9.3.jar<br /> mld.Wisdom 1.0,http://www.robocoderepository.com/BotFiles/3640/mld.Wisdom_1.0.jar<br /> mmb.Roskilde 0.5,http://www.robocoderepository.com/BotFiles/3965/mmb.Roskilde_0.5.jar<br /> mme.NikeEnhanced 2.0,http://www.robocoderepository.com/BotFiles/2828/mme.NikeEnhanced_2.0.jar<br /> mn.Combat 1.0,http://www.robocoderepository.com/BotFiles/2351/mn.Combat_1.0.jar<br /> mn.WarMachine 1.1,http://www.robocoderepository.com/BotFiles/2574/mn.WarMachine_1.1.jar<br /> mnt.AHEB 0.6a,http://www.robocoderepository.com/BotFiles/2417/mnt.AHEB_0.6a.jar<br /> mnt.SurferBot 0.2.5,http://www.robocoderepository.com/BotFiles/2433/mnt.SurferBot_0.2.5.jar<br /> morbid.MorbidPriest 1.0,http://www.robocoderepository.com/BotFiles/1758/morbid.MorbidPriest_1.0.jar<br /> mrm.MightyMoose .2,http://darkcanuck.net/rumble/robots/mrm.MightyMoose_.2.jar<br /> ms.Ares 0.19,http://www.robocoderepository.com/BotFiles/730/ms.Ares_0.19.jar<br /> mue.Ascendant 1.2.27,http://mue.sonar-echo.de/robocode/mue.Ascendant_1.2.27.jar<br /> mue.Hyperion 0.8,http://www.robocoderepository.com/BotFiles/2224/mue.Hyperion_0.8.jar<br /> muf.CrazyKitten 0.9,http://www.robocoderepository.com/BotFiles/1946/muf.CrazyKitten_0.9.jar<br /> mwj.A1176183 1.0,http://robocode.rleach.id.au/mwj.A1176183_1.0.jar<br /> myl.micro.Avipes 1.00,http://www.robocoderepository.com/BotFiles/1347/myl.micro.Avipes_1.00.jar<br /> myl.micro.NekoNinja 1.30,http://www.robocoderepository.com/BotFiles/944/myl.micro.NekoNinja_1.30.jar<br /> myl.micro.Predator 1.50,http://www.robocoderepository.com/BotFiles/1097/myl.micro.Predator_1.50.jar<br /> myl.micro.Troodon 1.10,http://www.robocoderepository.com/BotFiles/1226/myl.micro.Troodon_1.10.jar<br /> myl.nano.Graviton 1.10,http://www.robocoderepository.com/BotFiles/770/myl.nano.Graviton_1.10.jar<br /> myl.nano.Kakuru 1.20,http://www.robocoderepository.com/BotFiles/1330/myl.nano.Kakuru_1.20.jar<br /> myl.nano.KomoriNinja 1.1,http://www.robocoderepository.com/BotFiles/978/myl.nano.KomoriNinja_1.1.jar<br /> mym.EdgeStalker 1.0,http://www.robocoderepository.com/BotFiles/3956/mym.EdgeStalker_1.0.jar<br /> mz.Adept 2.65,http://www.robocoderepository.com/BotFiles/2090/mz.Adept_2.65.jar<br /> mz.AdeptBSB 1.03,http://www.robocoderepository.com/BotFiles/2113/mz.AdeptBSB_1.03.jar<br /> mz.Movement 1.8,http://www.robocoderepository.com/BotFiles/2145/mz.Movement_1.8.jar<br /> mz.NanoDeath 2.56,http://www.robocoderepository.com/BotFiles/2010/mz.NanoDeath_2.56.jar<br /> mz.NanoGod 2.02,http://www.robocoderepository.com/BotFiles/1996/mz.NanoGod_2.02.jar<br /> nammyung.ModelT 0.23,http://www.robocoderepository.com/BotFiles/969/nammyung.ModelT_0.23.jar<br /> nanoskank.NanoSkank 1.0,http://darkcanuck.net/rumble/robots/nanoskank.NanoSkank_1.0.jar<br /> nat.BlackHole 2.0gamma,http://nat.robothai.net/robots/nat.BlackHole_2.0gamma.jar<br /> nat.micro.NP 1.34,http://nat.robothai.net/robots/nat.micro.NP_1.34.jar<br /> nat.micro.Reepicheep 0.1a,http://nat.robothai.net/robots/nat.micro.Reepicheep_0.1a.jar<br /> nat.nano.Ocnirp 1.73,http://nat.robothai.net/robots/nat.nano.Ocnirp_1.73.jar<br /> nat.nano.OcnirpPM 1.0,http://nat.robothai.net/robots/nat.nano.OcnirpPM_1.0.jar<br /> nat.nano.OcnirpSNG 1.0b,http://nat.robothai.net/robots/nat.nano.OcnirpSNG_1.0b.jar<br /> nat.Samekh 0.4,http://nat.robothai.net/robots/nat.Samekh_0.4.jar<br /> ncj.MoxieBot 1.0,http://www.robocoderepository.com/BotFiles/4003/ncj.MoxieBot_1.0.jar<br /> ndn.DyslexicMonkey 1.1,http://www.robocoderepository.com/BotFiles/1141/ndn.DyslexicMonkey_1.1.jar<br /> NDH.GuessFactor 1.0, http://www.robocoderepository.com/BotFiles/3949/NDH.GuessFactor_1.0.jar<br /> ne.Chimera 1.2,http://www.robocoderepository.com/BotFiles/3276/ne.Chimera_1.2.jar<br /> nexus.One 1.0,http://darkcanuck.net/rumble/robots/nexus.One_1.0.jar<br /> nexus.Prototype 1.0,http://darkcanuck.net/rumble/robots/nexus.Prototype_1.0.jar<br /> nic.Nicator 2.4,http://www.robocoderepository.com/BotFiles/193/nic.Nicator_2.4.jar<br /> nic.SnippetBot 1.0,http://www.robocoderepository.com/BotFiles/286/nic.SnippetBot_1.0.jar<br /> nkn.mini.Jskr0 0.1,http://www.robocoderepository.com/BotFiles/3852/nkn.mini.Jskr0_0.1.jar<br /> NG.LegatusLegionis 1.0,http://www.robocoderepository.com/BotFiles/3888/NG.LegatusLegionis_1.0.jar<br /> NG.LegatusLegionis 1.1,http://www.robocoderepository.com/BotFiles/3889/NG.LegatusLegionis_1.1.jar<br /> NG.LegatusLegionis 1.2,http://www.robocoderepository.com/BotFiles/4026/NG.LegatusLegionis_1.2.jar<br /> non.mega.NaN 0.1,http://www.robocoderepository.com/BotFiles/1960/non.mega.NaN_0.1.jar<br /> non.mega.NoName 0.0,http://www.robocoderepository.com/BotFiles/1957/non.mega.NoName_0.0.jar<br /> Noran.BitchingElk 0.054,http://www.robocoderepository.com/BotFiles/1855/Noran.BitchingElk_0.054.jar<br /> Noran.RandomTargeting 0.02,http://www.robocoderepository.com/BotFiles/1849/Noran.RandomTargeting_0.02.jar<br /> nova.Snow 1.0,http://www.robocoderepository.com/BotFiles/3623/nova.Snow_1.0.jar<br /> ntc.Cannon 1.12test,http://www.robocoderepository.com/BotFiles/3815/ntc.Cannon_1.12test.jar<br /> ntc.Evader 1.2,http://www.robocoderepository.com/BotFiles/3355/ntc.Evader_1.2.jar<br /> ntc.Knowledge 1.1,http://www.robocoderepository.com/BotFiles/3354/ntc.Knowledge_1.1.jar<br /> ntc.Lasers.Lasers 0.9,http://www.robocoderepository.com/BotFiles/3359/ntc.Lasers.Lasers_0.9.jar<br /> ntc.Plains 0.9,http://www.robocoderepository.com/BotFiles/3381/ntc.Plains_0.9.jar<br /> ntc.Swim 0.9,http://www.robocoderepository.com/BotFiles/3820/ntc.Swim_0.9.jar<br /> ntw.Sighup 1.5,http://darkcanuck.net/rumble/robots/ntw.Sighup_1.5.jar<br /> ntw.Sigsys 1.6,http://darkcanuck.net/rumble/robots/ntw.Sigsys_1.6.jar<br /> nz.jdc.micro.HedgehogGF 1.3,http://www.robocoderepository.com/BotFiles/3626/nz.jdc.micro.HedgehogGF_1.3.jar<br /> nz.jdc.micro.HedgehogP 1.2,http://www.robocoderepository.com/BotFiles/3622/nz.jdc.micro.HedgehogP_1.2.jar<br /> nz.jdc.nano.NeophytePattern 1.0,http://www.robocoderepository.com/BotFiles/3578/nz.jdc.nano.NeophytePattern_1.0.jar<br /> nz.jdc.nano.NeophytePRAL 1.2,http://www.robocoderepository.com/BotFiles/3568/nz.jdc.nano.NeophytePRAL_1.2.jar<br /> nz.jdc.nano.NeophyteSRAL 1.2,http://www.robocoderepository.com/BotFiles/3567/nz.jdc.nano.NeophyteSRAL_1.2.jar<br /> oa.weak.BotherBot 0.1,http://www.robocoderepository.com/BotFiles/2956/oa.weak.BotherBot_0.1.jar<br /> oa.weak.FlyMk1 0.1,http://www.robocoderepository.com/BotFiles/2958/oa.weak.FlyMk1_0.1.jar<br /> ola.Puffin 1.0,http://www.robocoderepository.com/BotFiles/3380/ola.Puffin_1.0.jar<br /> oog.melee.Capulet 1.1,https://sites.google.com/site/crazybassoon/oog.melee.Capulet_1.1.jar<br /> oog.melee.Mercutio 1.0,http://www.robocoderepository.com/BotFiles/3848/oog.melee.Mercutio_1.0.jar<br /> oog.micro.MagicD3 0.41,http://www.robocoderepository.com/BotFiles/3801/oog.micro.MagicD3_0.41.jar<br /> oog.micro.Maui 1.2,https://sites.google.com/site/crazybassoon/oog.micro.Maui_1.2.jar<br /> oog.micro.SavantMicro 1.0,http://www.robocoderepository.com/BotFiles/3958/oog.micro.SavantMicro_1.0.jar<br /> oog.mini.AlphaDragon 0.1,http://www.robocoderepository.com/BotFiles/4015/oog.mini.AlphaDragon_0.1.jar<br /> oog.nano.Caligula 1.15,http://www.robocoderepository.com/BotFiles/4022/oog.nano.Caligula_1.15.jar<br /> oog.nano.Fuatisha 1.1,http://www.robocoderepository.com/BotFiles/4045/oog.nano.Fuatisha_1.1.jar<br /> oog.nano.MagicD2 2.4,http://www.robocoderepository.com/BotFiles/3749/oog.nano.MagicD2_2.4.jar<br /> oog.nano.SavantVS 1.1,http://www.robocoderepository.com/BotFiles/3714/oog.nano.SavantVS_1.1.jar<br /> oog.nano.SavantWS 0.1,http://www.robocoderepository.com/BotFiles/3709/oog.nano.SavantWS_0.1.jar<br /> oog.PricklyPear 1.0.4,https://sites.google.com/site/crazybassoon/oog.PricklyPear_1.0.4.jar<br /> pa.Improved 1.1,http://darkcanuck.net/rumble/robots/pa.Improved_1.1.jar<br /> pak.JakeTheTestingRobot .1b,http://www.robocoderepository.com/BotFiles/3373/pak.JakeTheTestingRobot_.1b.jar<br /> pak.Dargon 1.0b,http://www.robocoderepository.com/BotFiles/3388/pak.Dargon_1.0b.jar<br /> pak.Dargon .2c,http://www.robocoderepository.com/BotFiles/3389/pak.Dargon_.2c.jar<br /> panzer.Panzer 0.2,http://www.robocoderepository.com/BotFiles/4008/panzer.Panzer_0.2.jar<br /> paolord.TheHulk 1.0,http://www.robocoderepository.com/BotFiles/3595/paolord.TheHulk_1.0.jar<br /> patson.PatsonTestBot 1.0,http://www.robocoderepository.com/BotFiles/3324/patson.PatsonTestBot_1.0.jar<br /> paulk.PaulV3 1.7,http://www.robocoderepository.com/BotFiles/3502/paulk.PaulV3_1.7.jar<br /> paulk.PaulV3 1.6,http://www.robocoderepository.com/BotFiles/3497/paulk.PaulV3_1.6.jar<br /> paulk.PaulV3 1.5,http://www.robocoderepository.com/BotFiles/3496/paulk.PaulV3_1.5.jar<br /> paulk.PaulV3 1.3,http://www.robocoderepository.com/BotFiles/3495/paulk.PaulV3_1.3.jar<br /> pb.Oscillator 1.0,http://www.robocoderepository.com/BotFiles/2070/pb.Oscillator_1.0.jar<br /> pe.mini.SandboxMini 1.2,http://www.robocoderepository.com/BotFiles/917/pe.mini.SandboxMini_1.2.jar<br /> pe.minimelee.SandboxMiniMelee 1.1,http://www.robocoderepository.com/BotFiles/934/pe.minimelee.SandboxMiniMelee_1.1.jar<br /> pe.SandboxDT 3.02,http://www.robocoderepository.com/BotFiles/793/pe.SandboxDT_3.02.jar<br /> pe.SandboxLump 1.52,http://www.robocoderepository.com/BotFiles/731/pe.SandboxLump_1.52.jar<br /> pedersen.Hubris 2.4,http://home.comcast.net/~kokyunage/robocode/hubris/pedersen.Hubris_2.4.jar<br /> pedersen.Ugluk 1.0,http://home.comcast.net/~kokyunage/robocode/ugluk/pedersen.Ugluk_1.0.jar<br /> pez.clean.Swiffer 0.2.9,http://www.robocoderepository.com/BotFiles/1883/pez.clean.Swiffer_0.2.9.jar<br /> pez.frankie.Frankie 0.9.6.1,http://www.robocoderepository.com/BotFiles/1565/pez.frankie.Frankie_0.9.6.1.jar<br /> pez.gloom.GloomyDark 0.9.2,http://www.robocoderepository.com/BotFiles/1741/pez.gloom.GloomyDark_0.9.2.jar<br /> pez.mako.Mako 1.5,http://www.robocoderepository.com/BotFiles/1317/pez.mako.Mako_1.5.jar<br /> pez.micro.Aristocles 0.3.7,http://www.robocoderepository.com/BotFiles/1923/pez.micro.Aristocles_0.3.7.jar<br /> pez.mini.ChironexFleckeri 0.5,http://www.robocoderepository.com/BotFiles/2513/pez.mini.ChironexFleckeri_0.5.jar<br /> pez.mini.Gouldingi 1.5,http://www.robocoderepository.com/BotFiles/1351/pez.mini.Gouldingi_1.5.jar<br /> pez.mini.Pugilist 2.4.18,http://darkcanuck.net/rumble/robots/pez.mini.Pugilist_2.4.18.jar<br /> pez.mini.Tityus 0.9.1,http://www.robocoderepository.com/BotFiles/1657/pez.mini.Tityus_0.9.1.jar<br /> pez.mini.VertiLeach 0.4.0,http://www.robocoderepository.com/BotFiles/1744/pez.mini.VertiLeach_0.4.0.jar<br /> pez.nano.Icarus 0.3,http://www.robocoderepository.com/BotFiles/2353/pez.nano.Icarus_0.3.jar<br /> pez.nano.LittleEvilBrother 0.1,http://www.robocoderepository.com/BotFiles/2056/pez.nano.LittleEvilBrother_0.1.jar<br /> pez.rumble.Ali 0.4.9,http://www.robocoderepository.com/BotFiles/2416/pez.rumble.Ali_0.4.9.jar<br /> pez.rumble.CassiusClay 2rho.01b,http://www.dijitari.com/void/robocode/pez.rumble.CassiusClay_2rho.01b.jar<br /> pfvicm.Sobieski 7.2.3b,http://www.robocoderepository.com/BotFiles/2911/pfvicm.Sobieski_7.2.3b.jar<br /> ph.micro.Pikeman 0.4.5,http://www.robocoderepository.com/BotFiles/2364/ph.micro.Pikeman_0.4.5.jar<br /> ph.mini.Archer 0.6.6,http://www.robocoderepository.com/BotFiles/2326/ph.mini.Archer_0.6.6.jar<br /> ph.musketeer.Musketeer 0.6,http://www.robocoderepository.com/BotFiles/2281/ph.musketeer.Musketeer_0.6.jar<br /> ph.Thinker 0.2.5,http://www.robocoderepository.com/BotFiles/2336/ph.Thinker_0.2.5.jar<br /> pi.Dark 10,http://darkcanuck.net/rumble/robots/pi.Dark_10.jar<br /> pl.Drum 0.1,http://darkcanuck.net/rumble/robots/pl.Drum_0.1.jar<br /> pl.Patton.GeneralPatton 1.54,http://darkcanuck.net/rumble/robots/pl.Patton.GeneralPatton_1.54.jar<br /> pla.Memnoch 0.5,http://www.robocoderepository.com/BotFiles/2211/pla.Memnoch_0.5.jar<br /> PK.Twardy 0.4.2,http://www.robocoderepository.com/BotFiles/3272/PK.Twardy_0.4.2.jar<br /> pkdeken.Paladin 1.0,http://www.robocoderepository.com/BotFiles/3556/pkdeken.Paladin_1.0.jar<br /> PkKillers.PkAssassin 1.0,http://www.robocoderepository.com/BotFiles/3485/PkKillers.PkAssassin_1.0.jar<br /> pmc.SniperBot 1.0,http://darkcanuck.net/rumble/robots/pmc.SniperBot_1.0.jar<br /> populations.TrainStoopidbot 0.01,http://www.robocoderepository.com/BotFiles/4052/populations.TrainStoopidbot_0.01.jar<br /> positive.Portia 1.26e,http://sites.google.com/site/robopositive/portia/positive.Portia_1.26e.jar<br /> povik.nano.Smilee 0.2.1,http://www.robocoderepository.com/BotFiles/3950/povik.nano.Smilee_0.2.1.jar<br /> projectx.ProjectNano 2.0,http://darkcanuck.net/rumble/robots/projectx.ProjectNano_2.0.jar<br /> projectx.TestNano 1.0,http://www.robocoderepository.com/BotFiles/3444/projectx.TestNano_1.0.jar<br /> pulsar.PulsarMax 0.8.9,http://www.robocoderepository.com/BotFiles/2227/pulsar.PulsarMax_0.8.9.jar<br /> pulsar.PulsarNano 0.2.4,http://www.robocoderepository.com/BotFiles/2335/pulsar.PulsarNano_0.2.4.jar<br /> pulsar.Nanis 0.3,http://www.robocoderepository.com/BotFiles/2560/pulsar.Nanis_0.3.jar<br /> qohnil.blot.BlotBot 3.61,http://www.robocoderepository.com/BotFiles/546/qohnil.blot.BlotBot_3.61.jar<br /> Queens_teamrobot.UltraRazor 1.0,http://www.robocoderepository.com/BotFiles/2108/Queens_teamrobot.UltraRazor_1.0.jar<br /> quietus.Invader 0.1,http://robocode.rleach.id.au/quietus.Invader_0.1.jar<br /> quietus.NarrowRadar 0.1,http://robocode.rleach.id.au/quietus.NarrowRadar_0.1.jar<br /> radnor.DoctorBob 1.42,http://www.robocoderepository.com/BotFiles/2133/radnor.DoctorBob_1.42.jar<br /> radnor.RamRod 1.0,http://www.robocoderepository.com/BotFiles/2085/radnor.RamRod_1.0.jar<br /> rampancy.Durandal 2.2d,http://stanford.edu/~mchunlum/robocode/rampancy.Durandal_2.2d.jar<br /> rampancy.micro.Epiphron 1.0,http://stanford.edu/~mchunlum/robocode/rampancy.micro.Epiphron_1.0.jar<br /> rapture.Rapture 2.13,http://www.robocoderepository.com/BotFiles/15/rapture.Rapture_2.13.jar<br /> ratosh.nano.Debo 1.36,http://www.robocoderepository.com/BotFiles/1702/ratosh.nano.Debo_1.36.jar<br /> ratosh.Nobo 0.21,http://www.robocoderepository.com/BotFiles/1612/ratosh.Nobo_0.21.jar<br /> ratosh.Wesco 1.4,http://www.robocoderepository.com/BotFiles/1914/ratosh.Wesco_1.4.jar<br /> rc.yoda.Yoda 1.0.6c.fix,http://rednaxela-robocode.dyndns.org/data/robots/rc.yoda.Yoda_1.0.6c.fix.jar<br /> rcb.Vanessa03 0,http://www.robocoderepository.com/BotFiles/1364/rcb.Vanessa03_0.jar<br /> rcp.Kuramatron 1.0,http://www.robocoderepository.com/BotFiles/3307/rcp.Kuramatron_1.0.jar<br /> rdt199.Warlord 0.73,http://www.robocoderepository.com/BotFiles/1130/rdt199.Warlord_0.73.jar<br /> reaper.Reaper 1.1,http://www.robocoderepository.com/BotFiles/3412/reaper.Reaper_1.1.jar<br /> repositorio.NanoStep 1.0,http://darkcanuck.net/rumble/robots/repositorio.NanoStep_1.0.jar<br /> rfj.Sunburn 1.1,http://www.robocoderepository.com/BotFiles/1060/rfj.Sunburn_1.1.jar<br /> rijteam.SmartDodge 1.1,http://www.robocoderepository.com/BotFiles/2959/rijteam.SmartDodge_1.1.jar<br /> robar.haiku.Spike 1.0,http://invitel.hu/artrog/robar.haiku.Spike_1.0.jar<br /> robar.micro.Gladius 1.15,http://invitel.hu/artrog/robar.micro.Gladius_1.15.jar<br /> robar.micro.Kirbyi 1.0,http://hunrobar.freeblog.hu/files/myrobots/robar.micro.Kirbyi_1.0.jar<br /> robar.micro.Topaz 0.25,http://invitel.hu/artrog/robar.micro.Topaz_0.25.jar<br /> robar.nano.Assertive 0.3,http://invitel.hu/artrog/robar.nano.Assertive_0.3.jar<br /> robar.nano.BlackWidow 1.3,http://www.robocoderepository.com/BotFiles/3574/robar.nano.BlackWidow_1.3.jar<br /> robar.nano.Breeze 0.3,http://hunrobar.freeblog.hu/files/myrobots/robar.nano.Breeze_0.3.jar<br /> robar.nano.Mosquito 1.1,http://hunrobar.freeblog.hu/files/myrobots/robar.nano.Mosquito_1.1.jar<br /> robar.nano.MosquitoPM 1.0,http://www.robocoderepository.com/BotFiles/3559/robar.nano.MosquitoPM_1.0.jar<br /> robar.nano.Prestige 1.0,http://www.robocoderepository.com/BotFiles/3507/robar.nano.Prestige_1.0.jar<br /> robar.nano.Pugio 1.49,http://www.robocoderepository.com/BotFiles/3710/robar.nano.Pugio_1.49.jar<br /> robar.nano.Scytodes 0.3,http://hunrobar.freeblog.hu/files/myrobots/robar.nano.Scytodes_0.3.jar<br /> robar.nano.Vespa 0.95,http://hunrobar.freeblog.hu/files/myrobots/robar.nano.Vespa_0.95.jar<br /> robo.PartsBot 1.1,http://darkcanuck.net/rumble/robots/robo.PartsBot_1.1.jar<br /> RobotMarco.MarcoV 0.1,http://www.robocoderepository.com/BotFiles/3941/RobotMarco.MarcoV_0.1.jar<br /> rsim.micro.uCatcher 0.1,http://sites.google.com/site/rsimander/robocode/rsim.micro.uCatcher_0.1.jar<br /> rsim.mini.BulletCatcher 0.4,http://www.robocoderepository.com/BotFiles/3737/rsim.mini.BulletCatcher_0.4.jar<br /> rsk1.RSK1 4.0,http://www.robocoderepository.com/BotFiles/3284/rsk1.RSK1_4.0.jar<br /> ruc.nano.Zealot 0.2,http://www.robocoderepository.com/BotFiles/1229/ruc.nano.Zealot_0.2.jar<br /> rus.vv.Dzhigit 1.1,http://www.robocoderepository.com/BotFiles/4002/rus.vv.Dzhigit1.1.jar<br /> rus.vv.Snezhok 1.1,http://www.robocoderepository.com/BotFiles/3998/rus.vv.Snezhok1.1.jar<br /> ry.LightningBug 1.0,http://www.robocoderepository.com/BotFiles/3472/ry.LightningBug_1.0.jar<br /> ry.VirtualGunExperiment 1.2.0,http://www.robocoderepository.com/BotFiles/3662/ry.VirtualGunExperiment_1.2.0.jar<br /> ry.Worst 1.0,http://www.robocoderepository.com/BotFiles/3645/ry.Worst_1.0.jar<br /> rz.Aleph 0.34,http://www.robocoderepository.com/BotFiles/1993/rz.Aleph_0.34.jar<br /> rz.Apollon 0.23,http://www.robocoderepository.com/BotFiles/2098/rz.Apollon_0.23.jar<br /> rz.Artist 0.2,http://www.robocoderepository.com/BotFiles/2156/rz.Artist_0.2.jar<br /> rz.GlowBlow 2.31,http://www.robocoderepository.com/BotFiles/1354/rz.GlowBlow_2.31.jar<br /> rz.GlowBlowAPM 1.0,http://www.robocoderepository.com/BotFiles/1382/rz.GlowBlowAPM_1.0.jar<br /> rz.GlowBlowMelee 1.4,http://www.robocoderepository.com/BotFiles/1436/rz.GlowBlowMelee_1.4.jar<br /> rz.HawkOnFire 0.1,http://www.robocoderepository.com/BotFiles/1575/rz.HawkOnFire_0.1.jar<br /> rz.SmallDevil 1.502,http://www.robocoderepository.com/BotFiles/1322/rz.SmallDevil_1.502.jar<br /> sadoner.killer 0.2,http://www.robocoderepository.com/BotFiles/4020/sadoner.killer_0.2.jar<br /> sam.ChipmunkDuelist 1.0,http://www.robocoderepository.com/BotFiles/3094/sam.ChipmunkDuelist_1.0.jar<br /> sam.Samspin 1.0,http://www.robocoderepository.com/BotFiles/2823/sam.Samspin_1.0.jar<br /> sanyi.mikrobi.Roberto 1.0,http://www.robocoderepository.com/BotFiles/3929/sanyi.mikrobi.Roberto_1.0.jar<br /> sch.Simone 0.3d,http://www.robocoderepository.com/BotFiles/374/sch.Simone_0.3d.jar<br /> serenity.moonlightBat 1.17,http://www.robocoderepository.com/BotFiles/2877/serenity.moonlightBat_1.17.jar<br /> serenity.nonSense 1.39,http://www.robocoderepository.com/BotFiles/3586/serenity.nonSense_1.39.jar<br /> serenity.serenityFire 1.29,http://www.robocoderepository.com/BotFiles/3071/serenity.serenityFire_1.29.jar<br /> sgp.JollyNinja 3.53,http://www.robocoderepository.com/BotFiles/183/sgp.JollyNinja_3.53.jar<br /> sgp.MadHatter 4.13,http://www.robocoderepository.com/BotFiles/156/sgp.MadHatter_4.13.jar<br /> sgp.nano.FurryLeech 1.0,http://www.robocoderepository.com/BotFiles/802/sgp.nano.FurryLeech_1.0.jar<br /> sgp.ShiningBeetle 1.1,http://www.robocoderepository.com/BotFiles/498/sgp.ShiningBeetle_1.1.jar<br /> sgp.SleepingGoat 1.1,http://www.robocoderepository.com/BotFiles/500/sgp.SleepingGoat_1.1.jar<br /> SHAM.WOW 1.4,http://darkcanuck.net/rumble/robots/SHAM.WOW_1.4.jar<br /> shinh.Entangled 0.3,http://www.robocoderepository.com/BotFiles/1070/shinh.Entangled_0.3.jar<br /> shrub.Silver v048,http://www.robocoderepository.com/BotFiles/449/shrub.Silver_v048.jar<br /> shrub.Vapour v159,http://www.robocoderepository.com/BotFiles/2654/shrub.Vapour_v159.jar<br /> shu.nitro.LENIN .T34,http://www.robocoderepository.com/BotFiles/1956/shu.nitro.LENIN_.T34.jar<br /> sigterm.Sigterm 1.0,http://darkcanuck.net/rumble/robots/sigterm.Sigterm_1.0.jar<br /> simonton.beta.LifelongObsession 0.5.1,http://www.robocoderepository.com/BotFiles/3195/simonton.beta.LifelongObsession_0.5.1.jar<br /> simonton.GFNano_D 3.1b,http://www.robocoderepository.com/BotFiles/3114/simonton.GFNano_D_3.1b.jar<br /> simonton.nano.WeekendObsession_S 1.7,http://www.robocoderepository.com/BotFiles/3117/simonton.nano.WeekendObsession_S_1.7.jar<br /> simonton.mega.SniperFrog 1.0.fix2,http://rednaxela-robocode.dyndns.org/data/robots/simonton.mega.SniperFrog_1.0.fix2.jar<br /> simonton.micro.GFMicro 1.0,http://darkcanuck.net/rumble/robots/simonton.micro.GFMicro_1.0.jar<br /> simonton.micro.WeeklongObsession 3.4.1,http://darkcanuck.net/rumble/robots/simonton.micro.WeeklongObsession_3.4.1.jar<br /> simonton.mini.WeeksOnEnd 1.10.4,http://darkcanuck.net/rumble/robots/simonton.mini.WeeksOnEnd_1.10.4.jar<br /> skm.butterfly 1.0,http://www.robocoderepository.com/BotFiles/3868/sean1.jar<br /> skm.Ryubot 1.0,http://www.robocoderepository.com/BotFiles/3594/skm.Ryubot_1.0.jar<br /> skm.PateranBotlock2 1.0,http://www.robocoderepository.com/BotFiles/3591/skm.PateranBotlock2_1.0.jar<br /> sL300.Mozart life,http://www.robocoderepository.com/BotFiles/1992/sL300.Mozart_life.jar<br /> sm.Devil 7.3,http://www.robocoderepository.com/BotFiles/1481/sm.Devil_7.3.jar<br /> sng.arco.Arco 0.0,http://www.robocoderepository.com/BotFiles/3279/sng.arco.Arco_0.0.jar<br /> sos.SOS 1.0,http://www.robocoderepository.com/BotFiles/3489/sos.SOS_1.0.jar<br /> spinnercat.CopyKat 1.2.3,http://www.robocoderepository.com/BotFiles/3818/spinnercat.CopyKat_1.2.3.jar<br /> spinnercat.Limit .01,http://www.robocoderepository.com/BotFiles/3659/spinnercat.Limit_.01.jar<br /> spinnercat.Kitten 1.6,http://www.robocoderepository.com/BotFiles/3819/spinnercat.Kitten_1.6.jar<br /> spinnercat.haiku.Refrigerator 1.1,http://www.robocoderepository.com/BotFiles/3688/spinnercat.haiku.Refrigerator_1.1.jar<br /> spinnercat.mega.Tardis 1.2,http://www.robocoderepository.com/BotFiles/3692/spinnercat.mega.Tardis_1.2.jar<br /> spinnercat.Robovirus 2.718,http://www.robocoderepository.com/BotFiles/3657/spinnercat.Robovirus_2.718.jar<br /> sqTank.waveSurfing.LionWWSVMvoid 0.01,http://www.robocoderepository.com/BotFiles/3436/sqTank.waveSurfing.LionWWSVMvoid_0.01.jar<br /> starpkg.StarViewerZ 1.26,http://www.robocoderepository.com/BotFiles/1931/starpkg.StarViewerZ_1.26.jar<br /> staticline.Whiskey 0.5.3,http://www.robocoderepository.com/BotFiles/3972/staticline.Whiskey_0.5.3.jar<br /> staticline.whiskey.Whiskey 0.6,http://rednaxela-robocode.dyndns.org/data/robot_archive/staticline.whiskey.Whiskey_0.6.jar<br /> stefw.Tigger 0.0.23,http://darkcanuck.net/rumble/robots/stefw.Tigger_0.0.23.jar<br /> stelo.Chord 1.0,http://darkcanuck.net/rumble/robots/stelo.Chord_1.0.jar<br /> stelo.FretNano 1.1,http://darkcanuck.net/rumble/robots/stelo.FretNano_1.1.jar<br /> stelo.Lifestealer 1.0,http://darkcanuck.net/rumble/robots/stelo.Lifestealer_1.0.jar<br /> stelo.MatchupMini 1.1,http://darkcanuck.net/rumble/robots/stelo.MatchupMini_1.1.jar<br /> stelo.MatchupMicro 1.2,http://darkcanuck.net/rumble/robots/stelo.MatchupMicro_1.2.jar<br /> stelo.MatchupAGF 1.1,http://darkcanuck.net/rumble/robots/stelo.MatchupAGF_1.1.jar<br /> stelo.MatchupWS 1.2c,http://darkcanuck.net/rumble/robots/stelo.MatchupWS_1.2c.jar<br /> stelo.Mirror 1.1,http://www.robocoderepository.com/BotFiles/3034/stelo.Mirror_1.1.jar<br /> stelo.MirrorMicro 1.1,http://darkcanuck.net/rumble/robots/stelo.MirrorMicro_1.1.jar<br /> stelo.MirrorNano 1.4,http://darkcanuck.net/rumble/robots/stelo.MirrorNano_1.4.jar<br /> stelo.MoojukNano 1.2,http://darkcanuck.net/rumble/robots/stelo.MoojukNano_1.2.jar<br /> stelo.PastFuture 2.1.9,http://www.robocoderepository.com/BotFiles/3910/stelo.PastFuture_2.1.9.jar<br /> stelo.PatternRobot 1.0,http://www.robocoderepository.com/BotFiles/2995/stelo.PatternRobot_1.0.jar<br /> stelo.PianistNano 1.3,http://darkcanuck.net/rumble/robots/stelo.PianistNano_1.3.jar<br /> stelo.RamTrackSurfer 1.2,http://darkcanuck.net/rumble/robots/stelo.RamTrackSurfer_1.2.jar<br /> stelo.Randomness 1.1,http://www.robocoderepository.com/BotFiles/3021/stelo.Randomness_1.1.jar<br /> stelo.Spread 0.2,http://www.robocoderepository.com/BotFiles/3922/stelo.Spread_0.2.jar<br /> stelo.SteloTestNano 1.0,http://darkcanuck.net/rumble/robots/stelo.SteloTestNano_1.0.jar<br /> stelo.UnfoolableNano 1.0,http://darkcanuck.net/rumble/robots/stelo.UnfoolableNano_1.0.jar<br /> stelo.UntouchableNano 1.4,http://darkcanuck.net/rumble/robots/stelo.UntouchableNano_1.4.jar<br /> step.nanoPri 1.0,http://www.robocoderepository.com/BotFiles/2996/step.nanoPri_1.0.jar<br /> step.NanoBidu 1.0,http://www.robocoderepository.com/BotFiles/3014/step.NanoBidu_1.0.jar<br /> stf.PanzerGeneral 0.1,http://www.robocoderepository.com/BotFiles/2233/stf.PanzerGeneral_0.1.jar<br /> stordy.StordyBot 1.0,http://sites.google.com/site/stordyrobo/Home/stordy.StordyBot_1.0.jar<br /> strider.Festis 1.2.1,http://www.robocoderepository.com/BotFiles/2355/strider.Festis_1.2.1.jar<br /> strider.Mer 1.1.0,http://www.robocoderepository.com/BotFiles/2360/strider.Mer_1.1.0.jar<br /> stuff.Vlad 0.1,http://www.robocoderepository.com/BotFiles/3701/stuff.Vlad_0.1.jar<br /> sul.NanoR2 1.32,http://www.robocoderepository.com/BotFiles/3348/sul.NanoR2_1.32.jar<br /> sul.Pinkbot 1.1,http://www.robocoderepository.com/BotFiles/3346/sul.Pinkbot_1.1.jar<br /> sul.Bicephal 1.2,http://www.robocoderepository.com/BotFiles/3343/sul.Bicephal_1.2.jar<br /> sul.BlueBot 1.0,http://www.robocoderepository.com/BotFiles/3347/sul.BlueBot_1.0.jar<br /> SuperSample.SuperCrazy 1.0,http://file.csdgn.org/robocode/SuperSample.SuperCrazy_1.0.jar<br /> syl.Centipede 0.5,http://www.robocoderepository.com/BotFiles/1254/syl.Centipede_0.5.jar<br /> synapse.Geomancy 15,http://sites.google.com/site/synapsebots/home/synapse.Geomancy_15.jar?attredirects=0<br /> synapse.rsim.GeomancyBS 0.11,http://robocoderepository.com/BotFiles/3758/synapse.rsim.GeomancyBS_0.11.jar<br /> synnalagma.NeuralPremier 0.51,http://www.robocoderepository.com/BotFiles/1557/synnalagma.NeuralPremier_0.51.jar<br /> synnalagma.test.MiniNeural 1.1,http://www.robocoderepository.com/BotFiles/1754/synnalagma.test.MiniNeural_1.1.jar<br /> tad.Dalek98 0.98,http://darkcanuck.net/rumble/robots/tad.Dalek98_0.98.jar<br /> takeBot.SpinSpiral 1.2,http://www.robocoderepository.com/BotFiles/312/takeBot.SpinSpiral_1.2.jar<br /> takeBot.SpiralCrash 1.0,http://www.robocoderepository.com/BotFiles/1013/takeBot.SpiralCrash_1.0.jar<br /> takeBot.WeavingWiggle 1.1,http://www.robocoderepository.com/BotFiles/1012/takeBot.WeavingWiggle_1.1.jar<br /> tango.Recrimpo 2.51,http://www.robocoderepository.com/BotFiles/2015/tango.Recrimpo_2.51.jar<br /> taqho.taqbot 1.0,http://www.robocoderepository.com/BotFiles/1316/taqho.taqbot_1.0.jar<br /> tcf.Drifter 29,http://www.7sun.com/robocode/robots/tcf.Drifter_29.jar<br /> tcf.Repat3 2,http://www.robocoderepository.com/BotFiles/3328/tcf.Repat3_2.jar<br /> techdude.kombat.FlamingKombat 1.5,http://www.robocoderepository.com/BotFiles/2810/techdude.kombat.FlamingKombat_1.5.jar<br /> techdude.Class2C.Class2C 0.1,http://www.robocoderepository.com/BotFiles/3078/techdude.Class2C.Class2C_0.1.jar<br /> test.Podgy 4.0,http://www.robocoderepository.com/BotFiles/3214/test.Podgy_4.0.jar<br /> test.Fuzzer 1.0.1,http://www.robocoderepository.com/BotFiles/3345/test.Fuzzer_1.0.1.jar<br /> testantiswapgun.AntiSwap 1.0,http://www.robocode.ilbello.com/asd.AntiSwap_1.0.jar<br /> throxbot.ThroxBot 0.1,http://www.robocoderepository.com/BotFiles/2548/throxbot.ThroxBot_0.1.jar<br /> tide.pear.Pear 0.62.1,http://www.robocoderepository.com/BotFiles/2393/tide.pear.Pear_0.62.1.jar<br /> timmit.micro.TimXJ 0.22,http://www.robocoderepository.com/BotFiles/1683/timmit.micro.TimXJ_0.22.jar<br /> timmit.mini.TimVA 0.43,http://www.robocoderepository.com/BotFiles/1681/timmit.mini.TimVA_0.43.jar<br /> timmit.nano.TimCat 0.13,http://www.robocoderepository.com/BotFiles/1600/timmit.nano.TimCat_0.13.jar<br /> timmit.nano.TimDog 0.33,http://www.robocoderepository.com/BotFiles/1602/timmit.nano.TimDog_0.33.jar<br /> timmit.TimmiT 0.22,http://www.robocoderepository.com/BotFiles/1468/timmit.TimmiT_0.22.jar<br /> TJ.Exupery 1.39,http://www.robocoderepository.com/BotFiles/3970/TJ.Exupery1.39.jar<br /> tjk.deBroglie 0.66,http://robocoderepository.com/BotFiles/3989/tjk.deBroglie_0.66.jar<br /> tlp.ThreeLeggedPig 1,http://pages.prodigy.net/franz1/house/tlp.ThreeLeggedPig_1.jar<br /> tm.Yuugao 1.0,http://www.robocoderepository.com/BotFiles/1056/tm.Yuugao_1.0.jar<br /> tobe.calypso.Calypso 4.1,http://www.robocoderepository.com/BotFiles/784/tobe.calypso.Calypso_4.1.jar<br /> tobe.Fusion 1.0,http://www.robocoderepository.com/BotFiles/649/tobe.Fusion_1.0.jar<br /> tobe.mini.Charon 0.9,http://www.robocoderepository.com/BotFiles/836/tobe.mini.Charon_0.9.jar<br /> tobe.Relativity 3.9,http://www.robocoderepository.com/BotFiles/360/tobe.Relativity_3.9.jar<br /> tobe.Saturn lambda,http://www.robocoderepository.com/BotFiles/685/tobe.Saturn_lambda.jar<br /> tornyil.bottomup.BottomUp 1.05,http://www.alpha-consulting.hu/robo/tornyil.bottomup.BottomUp_1.05.jar<br /> tornyil.Lajcsi2.Lajcsi2sm 1.0,http://www.alpha-consulting.hu/robo/tornyil.Lajcsi2.Lajcsi2sm_1.0.jar<br /> toz.Gnome 1.1,http://darkcanuck.net/rumble/robots/toz.Gnome_1.1.jar<br /> trab.Crusader 0.1.7,http://www.stud.ntnu.no/~grashei/bots/trab.Crusader_0.1.7.jar<br /> trab.nano.AinippeNano 1.3,http://www.stud.ntnu.no/~grashei/bots/trab.nano.AinippeNano_1.3.jar<br /> tw.Exterminator 1.0,http://www.robocoderepository.com/BotFiles/3607/tw.Exterminator_1.0.jar<br /> tzu.TheArtOfWar 1.2,http://darkcanuck.net/rumble/robots/tzu.TheArtOfWar_1.2.jar<br /> uccc.Dorito 1.12,http://www.devfluid.com/csc_w/images/e/e9/Uccc.Dorito_1.12.jar<br /> uccc.MilkyWay 1.01,http://www.devfluid.com/csc_w/images/a/a6/Uccc.MilkyWay_1.01.jar<br /> uccc.RingDing 1.12,http://www.devfluid.com/csc_w/images/5/5f/Uccc.RingDing_1.12.jar<br /> uccc.Scrapple 1.0,http://www.devfluid.com/csc_w/images/7/7a/Uccc.Scrapple_1.0.jar<br /> urdos.URDOS 1.3,http://darkcanuck.net/rumble/robots/urdos.URDOS_1.3.jar<br /> usa.nano.Nemo 2.0,http://www.robocoderepository.com/BotFiles/2045/usa.nano.Nemo_2.0.jar<br /> vic.Locke 0.7.5.5,http://www.robocoderepository.com/BotFiles/2115/vic.Locke_0.7.5.5.jar<br /> vft.Valkyrie 1.0,http://www.robocoderepository.com/BotFiles/3009/vft.Valkyrie_1.0.jar<br /> vft.Hrist 1.0,http://darkcanuck.net/rumble/robots/vft.Hrist_1.0.jar<br /> vjik.UnViolation 1.1,http://www.robocoderepository.com/BotFiles/3886/vjik.UnViolation_1.1.jar<br /> voidious.Diamond 1.5.38b,http://www.dijitari.com/void/robocode/voidious.Diamond_1.5.38b.jar<br /> voidious.Dookious 1.573c,http://www.dijitari.com/void/robocode/voidious.Dookious_1.573c.jar<br /> voidious.micro.Jen 1.11,http://www.dijitari.com/void/robocode/voidious.micro.Jen_1.11.jar<br /> voidious.mini.Komarious 1.88,http://www.dijitari.com/void/robocode/voidious.mini.Komarious_1.88.jar<br /> vuen.Fractal 0.55,http://www.robocoderepository.com/BotFiles/1579/vuen.Fractal_0.55.jar<br /> wcsv.Engineer.Engineer 0.5.4,http://darkcanuck.net/rumble/robots/wcsv.Engineer.Engineer_0.5.4.jar<br /> wcsv.PowerHouse.PowerHouse 1.7e3,http://darkcanuck.net/rumble/robots/wcsv.PowerHouse.PowerHouse_1.7e3.jar<br /> wcsv.mega.PowerHouse2 0.2,http://darkcanuck.net/rumble/robots/wcsv.mega.PowerHouse2_0.2.jar<br /> wcsv.Stampede 1.3.3,http://www.robocoderepository.com/BotFiles/2527/wcsv.Stampede_1.3.3.jar<br /> wcsv.Stampede2.Stampede2 1.1.0,http://www.robocoderepository.com/BotFiles/2714/wcsv.Stampede2.Stampede2_1.1.0.jar<br /> WdV.Lesserbee 0.01,http://www.robocoderepository.com/BotFiles/4046/WdV.Lesserbee_0.01.jar<br /> whind.Constitution 0.7.1,http://www.robocoderepository.com/BotFiles/2812/whind.Constitution_0.7.1.jar<br /> whind.Strength 0.6.4,http://whindgames.50webs.com/otherstuff/whind.Strength_0.6.4.jar<br /> whind.StrengthBee 0.6.4,http://whindgames.50webs.com/otherstuff/whind.StrengthBee_0.6.4.jar<br /> whind.Wisdom 0.5.1,http://www.robocoderepository.com/BotFiles/2742/whind.Wisdom_0.5.1.jar<br /> wiki.BasicGFSurfer 1.02,http://www.dijitari.com/void/robocode/wiki.BasicGFSurfer_1.02.jar<br /> wiki.mako.MakoHT 1.2.2.1,http://www.robocoderepository.com/BotFiles/1374/wiki.mako.MakoHT_1.2.2.1.jar<br /> wiki.mini.BlackDestroyer 0.9.0,http://www.robocoderepository.com/BotFiles/1927/wiki.mini.BlackDestroyer_0.9.0.jar<br /> wiki.mini.GouldingiHT 1.0,http://www.robocoderepository.com/BotFiles/1383/wiki.mini.GouldingiHT_1.0.jar<br /> wiki.mini.Griffon 0.1,http://www.robocoderepository.com/BotFiles/1774/wiki.mini.Griffon_0.1.jar<br /> wiki.mini.Sedan 1.0,http://www.robocoderepository.com/BotFiles/1676/wiki.mini.Sedan_1.0.jar<br /> wiki.nano.DevilFISH 1.0,http://www.robocoderepository.com/BotFiles/2235/wiki.nano.DevilFISH_1.0.jar<br /> wiki.nano.RaikoNano 1.1,http://www.robocoderepository.com/BotFiles/2163/wiki.nano.RaikoNano_1.1.jar<br /> wiki.WaveRammer 1.0,http://www.robocoderepository.com/BotFiles/3505/wiki.WaveRammer_1.0.jar<br /> wiki.Wolverine 2.1,http://darkcanuck.net/rumble/robots/wiki.Wolverine_2.1.jar<br /> wilson.Chameleon 0.91,http://www.robocoderepository.com/BotFiles/1608/wilson.Chameleon_0.91.jar<br /> winamp32.micro.MicroMacro 1.0,http://www.robocoderepository.com/BotFiles/2891/winamp32.micro.MicroMacro_1.0.jar<br /> wit.Chuliath 1.0,http://www.robocoderepository.com/BotFiles/2306/wit.Chuliath_1.0.jar<br /> wit.Deep7 2.0,http://www.robocoderepository.com/BotFiles/2313/wit.Deep7_2.0.jar<br /> xandercat.XanderCat 2.1,http://www.distantvisions.net/robocode/xandercat.XanderCat-2.1.jar<br /> xandercat.XanderCat 3.0,http://www.distantvisions.net/robocode/xandercat.XanderCat-3.0.jar<br /> xiongan.Xiongan 1.1,http://www.robocoderepository.com/BotFiles/3565/xiongan.Xiongan_1.1.jar<br /> yarghard.Y101 1.0,http://sliwa.ws/RoboCode/yarghard.Y101_1.0.jar<br /> yk.JahMicro 1.0,http://www.robocoderepository.com/BotFiles/3033/yk.JahMicro_1.0.jar<br /> yk.JahRoslav 1.1,http://www.robocoderepository.com/BotFiles/3032/yk.JahRoslav_1.1.jar<br /> zen.Lindada 0.2,http://www.robocoderepository.com/BotFiles/1679/zen.Lindada_0.2.jar<br /> zeze2.OperatorZeze 1.05,http://www.robocoderepository.com/BotFiles/3330/zeze2.OperatorZeze_1.05.jar<br /> zch.David 0.21,http://www.robocoderepository.com/BotFiles/3575/zch.David_0.21.jar<br /> zch.Hirkan 0.11,http://www.robocoderepository.com/BotFiles/1288/zch.Hirkan_0.11.jar<br /> zh.UnderDog 0.0.2,http://www.robocoderepository.com/BotFiles/3053/zh.UnderDog_0.0.2.jar<br /> zyx.mega.YersiniaPestis 3.0,http://darkcanuck.net/rumble/robots/zyx.mega.YersiniaPestis_3.0.jar<br /> zyx.micro.Ant 1.1,http://www.robocoderepository.com/BotFiles/3481/zyx.micro.Ant_1.1.jar<br /> zyx.nano.Ant 1.1,http://www.robocoderepository.com/BotFiles/3493/zyx.nano.Ant_1.1.jar<br /> zyx.nano.EscherichiaColi 1.0,http://darkcanuck.net/rumble/robots/zyx.nano.EscherichiaColi_1.0.jar<br /> zyx.nano.RedBull 1.0,http://darkcanuck.net/rumble/robots/zyx.nano.RedBull_1.0.jar<br /> &lt;/pre&gt;<br /> ----<br /> '''''No chatting on this page. Use the /ParticipantsChat page for that.'''''<br /> <br /> '''''Removed because the jarcontent/filename is not correct'''''&lt;br&gt;<br /> ''cberendt.Bot1 0.160''&lt;br&gt;<br /> ''dmsr.MiniR101 0.6''&lt;br&gt;<br /> ''henriquevilela.TieFighter 0.1,3224''&lt;br&gt;<br /> ''jgap.Aspirant_7980_gen7 1.0,3552''br&gt;<br /> ''jgap.Aspirant_13029_gen7 1.0,3553''&lt;br&gt;<br /> ''techdude.Carruthers 1.2.6''&lt;br&gt;<br /> ''uccc.Orbiter 1.0''&lt;br&gt;<br /> ''WhoAmI.WhoAmI 1.00''&lt;br&gt;<br /> <br /> '''''Removed until file corruption is resolved:'''''<br /> <br /> ''cas.CelsoKiller 1.0,3465''<br /> <br /> '''''Removed due to almost always giving '0' scores:'''''<br /> <br /> ''com.syncleus.robocode.Dreadnaught 0.1,3426''&lt;br&gt;<br /> ''lazarecki.PinkerStinker 0.1,http://www.robocoderepository.com/BotFiles/3824/lazarecki.PinkerStinker_0.1.jar''<br /> <br /> '''''Removed because it's incorrectly packaged:'''''<br /> <br /> ''Indesh.Indesh 1.1,http://jakobserlier.250free.com/Indesh.jar''<br /> <br /> <br /> ----<br /> <br /> '''''Removed due to WontFix issues in Robocode 1.7+:'''''&lt;br&gt;<br /> ''* Hviela: ([[http://sourceforge.net/tracker/?func=detail&amp;aid=2953268&amp;group_id=37202&amp;atid=419486 SF #2953268]])''&lt;br&gt;<br /> '': hvilela.HVilela 0.9.3,http://henrique.vilela.googlepages.com/hvilela.HVilela_0.9.3.jar''&lt;br&gt;<br /> ''* Barney (Tries to write files without using RobocodeOutputStream. Robocode 1.7 punishes for that more harshly which will give 0 scores)&lt;br&gt;<br /> '': Homer.Barney 1.0,http://www.robocoderepository.com/BotFiles/1932/Homer.Barney_1.0.jar&lt;br&gt;</div>

Miked0801 http://robowiki.net/w/index.php?title=RoboRumble/Participants&diff=19434 2011-06-04T04:41:21Z

<p>Miked0801: Test upload of new version of LBB from google. If this works, I'll pull the old LBB.</p> <hr /> <div>{{:RoboRumble/Navigation}}<br /> <br /> ----<br /> Just add your bot name ('''as appears in the Robocode selector after packaging''', so including versionnumber) and the RobocodeRepository id number separated by &quot;,&quot; (there must be no space after the comma).&lt;br&gt; <br /> Please, make sure your bot is not in the list before adding it, and delete the old version if you are adding a new one.<br /> &lt;br&gt;<br /> The list is in '''alphabetical''' order. Add your bot in the right slot.<br /> <br /> ----<br /> &lt;pre&gt;<br /> ab.DengerousRoBatra 1.3,http://www.robocoderepository.com/BotFiles/3664/ab.DengerousRoBatra_1.3.jar<br /> abc.Shadow 3.83c,http://robocode.aclsi.pt/abc.Shadow_3.83c.jar<br /> abc.tron3.Tron 3.11,http://www.robocoderepository.com/BotFiles/2205/abc.tron3.Tron_3.11.jar<br /> abc.Tron 2.02,http://www.robocoderepository.com/BotFiles/241/abc.Tron_2.02.jar<br /> abud.ThirdRobo 1.0,http://www.robocoderepository.com/BotFiles/2479/abud.ThirdRobo_1.0.jar<br /> ad.last.Bottom 1.0,http://www.robocoderepository.com/BotFiles/1876/ad.last.Bottom_1.0.jar<br /> ad.Quest 0.10,http://www.robocoderepository.com/BotFiles/1846/ad.Quest_0.10.jar<br /> adt.Ar1 2.1,http://www.robocoderepository.com/BotFiles/2254/adt.Ar1_2.1.jar<br /> adt.Ar2 1.0,http://www.robocoderepository.com/BotFiles/2303/adt.Ar2_1.0.jar<br /> ag.Gir 0.99,http://www.robocoderepository.com/BotFiles/3065/ag.Gir_0.99.jar<br /> agd.Mooserwirt2 2.7,http://www.glyndavies.org/robocode/agd.Mooserwirt2.jar<br /> ags.Glacier 0.2.7,http://rednaxela-robocode.dyndns.org/data/robots/ags.Glacier_0.2.7.jar<br /> ags.micro.Carpet 1.1,http://rednaxela-robocode.dyndns.org/data/robots/ags.micro.Carpet_1.1.jar<br /> ags.Midboss 1s,http://rednaxela-robocode.dyndns.org/data/robots/ags.Midboss_1s.jar<br /> ags.polished.PolishedRuby 1,http://rednaxela-robocode.dyndns.org/data/robots/ags.polished.PolishedRuby_1.jar<br /> ags.rougedc.RougeDC willow,http://rednaxela-robocode.dyndns.org/data/robots/ags.rougedc.RougeDC_willow.jar<br /> ahf.Acero 1.0,http://www.robocoderepository.com/BotFiles/2151/ahf.Acero_1.0.jar<br /> ahf.NanoAndrew .4,http://www.robocoderepository.com/BotFiles/2002/ahf.NanoAndrew_.4.jar<br /> ahf.r2d2.R2d2 0.86,http://www.robocoderepository.com/BotFiles/2035/ahf.r2d2.R2d2_0.86.jar<br /> ahr.ice.Ice 1.0,http://robocoderepository.com/BotFiles/3966/ahr.ice.Ice_1.0.jar<br /> ahr.ice.Ice 1.0.1,http://robocoderepository.com/BotFiles/3978/ahr.ice.Ice_1.0.1.jar<br /> AIR.iRobot 1.0,http://www.robocoderepository.com/BotFiles/3205/AIR.iRobot_1.0.jar<br /> ak.Fermat 2.0,http://www.robocoderepository.com/BotFiles/799/ak.Fermat_2.0.jar<br /> alex.Diabolo5 1.1,http://darkcanuck.net/rumble/robots/alex.Diabolo5_1.1.jar<br /> alk.lap.LoudAndProud 2.23,http://www.robocoderepository.com/BotFiles/3601/alk.lap.LoudAndProud_2.23.jar<br /> am.Miedzix 2.0,http://www.robocoderepository.com/BotFiles/3383/am.Miedzix_2.0.jar<br /> am.Miedzix 3.0,http://darkcanuck.net/rumble/robots/am.Miedzix_3.0.jar<br /> amarok.Rookie 1.1,http://www.robocoderepository.com/BotFiles/422/amarok.Rookie_1.1.jar<br /> amk.ChumbaMini 0.2,http://www.robocoderepository.com/BotFiles/2655/amk.ChumbaMini_0.2.jar<br /> amk.ChumbaWumba 0.3,http://www.robocoderepository.com/BotFiles/2646/amk.ChumbaWumba_0.3.jar<br /> amk.jointstrike.JointStrike 0.2,http://www.robocoderepository.com/BotFiles/2597/amk.jointstrike.JointStrike_0.2.jar<br /> amk.ShizzleStiX.ShizzleStiX 0.6,http://www.robocoderepository.com/BotFiles/2603/amk.ShizzleStiX.ShizzleStiX_0.6.jar<br /> amk.superstrike.SuperStrike 0.3,http://www.robocoderepository.com/BotFiles/2600/amk.superstrike.SuperStrike_0.3.jar<br /> amk.Punbot.Punbot 0.01,http://www.robocoderepository.com/BotFiles/2604/amk.Punbot.Punbot_0.01.jar<br /> ao.T100 0.9,http://www.robocoderepository.com/BotFiles/3385/ao.T100_0.9.jar<br /> ap.Frederick 1.1,http://darkcanuck.net/rumble/robots/ap.Frederick_1.1.jar<br /> apollokidd.ApolloKidd 0.9,http://www.robocoderepository.com/BotFiles/321/apollokidd.ApolloKidd_0.9.jar<br /> apv.Aspid 1.7,http://www.robocoderepository.com/BotFiles/1412/apv.Aspid_1.7.jar<br /> apv.AspidReloaded 0.6,http://www.robocoderepository.com/BotFiles/1985/apv.AspidReloaded_0.6.jar<br /> apv.LauLectrik 1.2,http://www.robocoderepository.com/BotFiles/1300/apv.LauLectrik_1.2.jar<br /> apv.MicroAspid 1.8,http://www.robocoderepository.com/BotFiles/2519/apv.MicroAspid_1.8.jar<br /> apv.NanoLauLectrik 1.0,http://www.robocoderepository.com/BotFiles/1399/apv.NanoLauLectrik_1.0.jar<br /> apv.NanoLauLectrikTheCannibal 1.1,http://www.robocoderepository.com/BotFiles/2147/apv.NanoLauLectrikTheCannibal_1.1.jar<br /> apv.ScruchiPu 1.0,http://www.robocoderepository.com/BotFiles/1367/apv.ScruchiPu_1.0.jar<br /> apv.test.Virus 0.6.1,http://www.robocoderepository.com/BotFiles/2645/apv.test.Virus_0.6.1.jar<br /> apv.TheBrainPi 0.5fix,http://darkcanuck.net/rumble/robots/apv.TheBrainPi_0.5fix.jar<br /> ar.horizon.Horizon 1.2.2,http://www.robocoderepository.com/BotFiles/3286/ar.horizon.Horizon_1.2.2.jar<br /> ar.QuantumChromodynamics 1.2.1,http://www.robocoderepository.com/BotFiles/3220/ar.QuantumChromodynamics_1.2.1.jar<br /> ar.TheoryOfEverything 1.2.1,http://www.robocoderepository.com/BotFiles/3221/ar.TheoryOfEverything_1.2.1.jar<br /> ara.Shera 0.88,http://www.robocoderepository.com/BotFiles/1050/ara.Shera_0.88.jar<br /> areb.Union 1.06,http://www.robocoderepository.com/BotFiles/2893/areb.Union_1.06.jar<br /> arthord.micro.Apoptygma 0.4,http://www.robocoderepository.com/BotFiles/1688/arthord.micro.Apoptygma_0.4.jar<br /> arthord.micro.Muffin 0.6.1,http://www.robocoderepository.com/BotFiles/1963/arthord.micro.Muffin_0.6.1.jar<br /> arthord.KostyaTszyu Beta2,http://www.robocoderepository.com/BotFiles/2322/arthord.KostyaTszyu_Beta2.jar<br /> arthord.MannyPacquiao Delta2,http://scoutery.awardspace.com/arthord.MannyPacquiao_Delta2.jar<br /> arthord.NanoSatan Mu,http://www.robocoderepository.com/BotFiles/2157/arthord.NanoSatan_Mu.jar<br /> arthord.NanoSatanMelee Beta,http://www.robocoderepository.com/BotFiles/2088/arthord.NanoSatanMelee_Beta.jar<br /> ary.micro.Weak 1.2,http://www.robocoderepository.com/BotFiles/3433/ary.micro.Weak_1.2.jar<br /> ary.mini.Nimi 1.0,http://www.robocoderepository.com/BotFiles/3397/ary.mini.Nimi_1.0.jar<br /> ary.nano.AceSurf 1.2,http://www.robocoderepository.com/BotFiles/3352/ary.nano.AceSurf_1.2.jar<br /> ary.nano.ColorNanoP 1.1,http://www.robocoderepository.com/BotFiles/3629/ary.nano.ColorNanoP_1.1.jar<br /> ary.Crisis 1.0,http://www.robocoderepository.com/BotFiles/3495/ary.Crisis_1.0.jar<br /> ary.Help 1.0,http://darkcanuck.net/rumble/robots/ary.Help_1.0.jar<br /> ary.FourWD 1.3d,http://darkcanuck.net/rumble/robots/ary.FourWD_1.3d.jar<br /> ary.SMG 1.01,http://ary-robocode.110mb.com/ary.SMG_1.01.jar<br /> as.xbots 1.0,http://darkcanuck.net/rumble/robots/as.xbots_1.0.jar<br /> asd.Cthulhu 1.2,http://darkcanuck.net/rumble/robots/asd.Cthulhu_1.2.jar<br /> asm.Statistas 0.1,http://www.robocoderepository.com/BotFiles/1989/asm.Statistas_0.1.jar<br /> aw.GreatWolf 2.0,https://sites.google.com/site/awusa94/robocode/aw.GreatWolf_2.0.jar<br /> awesomeness.Elite 1.0,http://robocoderepository.com/BotFiles/3597/awesomeness.Elite.jar<br /> awl.Locutus 1.0,3844<br /> axeBots.HataMoto 3.09,http://www.robocoderepository.com/BotFiles/1655/axeBots.HataMoto_3.09.jar<br /> axeBots.Musashi 2.18,http://www.robocoderepository.com/BotFiles/1759/axeBots.Musashi_2.18.jar<br /> axeBots.Okami 1.04,http://www.robocoderepository.com/BotFiles/2016/axeBots.Okami_1.04.jar<br /> axeBots.SilverSurfer 2.53.33fix,http://rednaxela-robocode.dyndns.org/data/robots/axeBots.SilverSurfer_2.53.33fix.jar<br /> ayk.WallHugger 1.0,https://sites.google.com/site/khanguyprojects/file-cabinet/ayk.WallHugger_1.0.jar<br /> baal.nano.N 1.42,http://webpages.charter.net/eleeleth/Robots/baal.nano.N_1.42.jar<br /> banshee.mini.Nexus6 0.2.0,http://www.robocoderepository.com/BotFiles/3467/banshee.mini.Nexus6_0.2.0.jar<br /> banshee.micro.Nexus6 0.3.0,http://www.robocoderepository.com/BotFiles/3473/banshee.micro.Nexus6_0.3.0.jar<br /> bayen.nano.Squirrel 0.2,http://www.freewebs.com/bayen/files/bayen.nano.Squirrel_0.2.jar<br /> bayen.nut.Squirrel 1.621,http://darkcanuck.net/rumble/robots/bayen.nut.Squirrel_1.621.jar<br /> bayen.UbaMicro 1.4,http://www.robocoderepository.com/BotFiles/2830/bayen.UbaMicro_1.4.jar<br /> bayen.UbaRamLT 1.0,http://www.robocoderepository.com/BotFiles/2868/bayen.UbaRamLT_1.0.jar<br /> bbo.RamboT 0.3,http://www.robocoderepository.com/BotFiles/2210/bbo.RamboT_0.3.jar<br /> bbo.TheRoof 1.4.3,http://www.robocoderepository.com/BotFiles/2179/bbo.TheRoof_1.4.3.jar<br /> Bemo.Sweet30 1.6.1,http://www.stg-volleyball.de/images/Bemo.Sweet30_1.6.1.jar<br /> benhorner.PureAggression 0.2.6,http://www.robocoderepository.com/BotFiles/3421/benhorner.PureAggression_0.2.6.jar<br /> bh.PencilRain 0.01,http://www.robocoderepository.com/BotFiles/3670/bh.PencilRain-0.01.jar<br /> bigpete.Stewie 1.0,http://www.robocoderepository.com/BotFiles/2927/bigpete.Stewie_1.0.jar<br /> bing2.Melody 1.3.1,http://www.ccs.neu.edu/home/bing/robocode/bing2.Melody_1.3.1.jar<br /> bjl.LoneDragon 0.5,http://www.robocoderepository.com/BotFiles/1929/bjl.LoneDragon_0.5.jar<br /> bndl.LostLion 1.2,http://www.robocoderepository.com/BotFiles/1033/bndl.LostLion_1.2.jar<br /> bons.NanoStalker 1.2,http://www.robocoderepository.com/BotFiles/1179/bons.NanoStalker_1.2.jar<br /> bp.Kuma 1.0,http://www.robocoderepository.com/BotFiles/3238/bp.Kuma_1.0.jar<br /> braaropolis.Abot 1.0,http://darkcanuck.net/rumble/robots/braaropolis.Abot_1.0.jar<br /> brainfade.Fallen 0.63,http://www.robocoderepository.com/BotFiles/2250/brainfade.Fallen_0.63.jar<br /> brainfade.melee.Dusk 0.44,http://www.robocoderepository.com/BotFiles/2518/brainfade.melee.Dusk_0.44.jar<br /> buba.Archivist 0.1,http://www.robocoderepository.com/BotFiles/3899/buba.Archivist_0.1.jar<br /> buba.Buba 0.3,http://www.robocoderepository.com/BotFiles/3896/buba.Buba_0.3.jar<br /> bvh.fnr.Fenrir 0.36l,http://www.robocoderepository.com/BotFiles/1428/bvh.fnr.Fenrir_0.36l.jar<br /> bvh.frg.Friga 0.112dev,http://darkcanuck.net/rumble/robots/bvh.frg.Friga_0.112dev.jar<br /> bvh.fry.Freya 0.82,http://darkcanuck.net/rumble/robots/bvh.fry.Freya_0.82.jar<br /> bvh.hdr.Hodur 0.4,http://www.robocoderepository.com/BotFiles/1954/bvh.hdr.Hodur_0.4.jar<br /> bvh.loki.Loki 0.5,http://www.robocoderepository.com/BotFiles/885/bvh.loki.Loki_0.5.jar<br /> bvh.micro.Freya 0.3,http://www.robocoderepository.com/BotFiles/2815/bvh.micro.Freya_0.3.jar<br /> bvh.micro.Svadilfari 0.2,http://www.robocoderepository.com/BotFiles/1086/bvh.micro.Svadilfari_0.2.jar<br /> bvh.mini.Fenrir 0.39,http://www.robocoderepository.com/BotFiles/1429/bvh.mini.Fenrir_0.39.jar<br /> bvh.mini.Freya 0.55,http://darkcanuck.net/rumble/robots/bvh.mini.Freya_0.55.jar<br /> bvh.mini.Mjolnir 0.3,http://www.robocoderepository.com/BotFiles/2220/bvh.mini.Mjolnir_0.3.jar<br /> bvh.mini.Wodan 0.50,http://www.robocoderepository.com/BotFiles/2064/bvh.mini.Wodan_0.50.jar<br /> bvh.tyr.Tyr 1.74,http://www.robocoderepository.com/BotFiles/886/bvh.tyr.Tyr_1.74.jar<br /> bzdp.BoxCar 2.0,http://www.robocoderepository.com/BotFiles/3703/bzdp.BoxCar_2.0.jar<br /> bzdp.Pansy 2.1,http://www.robocoderepository.com/BotFiles/3726/bzdp.Pansy_2.1.jar<br /> caimano.Furia_Ceca 0.22,http://www.robocoderepository.com/BotFiles/1843/caimano.Furia_Ceca_0.22.jar<br /> cbot.agile.Nibbler 0.2,http://www.robocoderepository.com/BotFiles/1537/cbot.agile.Nibbler_0.2.jar<br /> cbot.cbot.CBot 0.8,http://www.robocoderepository.com/BotFiles/1375/cbot.cbot.CBot_0.8.jar<br /> cf.mini.Chiva 1.0,http://www.robocoderepository.com/BotFiles/2331/cf.mini.Chiva_1.0.jar<br /> cf.OldMan.OldManXP 0.1,http://www.robocoderepository.com/BotFiles/1968/cf.OldMan.OldManXP_0.1.jar<br /> cf.proto.Shiva 2.2,http://www.robocoderepository.com/BotFiles/2409/cf.proto.Shiva_2.2.jar<br /> cf.star.Star2 1.23,http://www.robocoderepository.com/BotFiles/2255/cf.star.Star2_1.23.jar<br /> ch.rhj.rbc.RHJ1 1.0,http://www.robocoderepository.com/BotFiles/1879/ch.rhj.rbc.RHJ1_1.0.jar<br /> CharlieN.Omega.Omega 1.03,http://www.robocoderepository.com/BotFiles/3503/CharlieN.Omega.Omega_1.03.jar<br /> chase.c.Wristwatch 1.0,http://file.csdgn.org/robocode/chase.c.Wristwatch_1.0.jar<br /> chase.pm.Pytko 1.0,http://file.csdgn.org/robocode/chase.pm.Pytko_1.0.jar<br /> chase.s2.Genesis 1.1,http://file.csdgn.org/robocode/chase.s2.Genesis_1.1.jar<br /> chase.s2.Seraphim 2.0.9,http://file.csdgn.org/robocode/chase.s2.Seraphim_2.0.9.jar<br /> chickenfuego.UrChicken2 1.0,http://www.robocoderepository.com/BotFiles/3422/chickenfuego.UrChicken2_1.0.jar<br /> cjk.Merkava 0.1.1,http://www.robocoderepository.com/BotFiles/2637/cjk.Merkava_0.1.1.jar<br /> cjk.Merkava 0.2.0,http://www.robocoderepository.com/BotFiles/2640/cjk.Merkava_0.2.0.jar<br /> cjk.Merkava 0.3.0,http://darkcanuck.net/rumble/robots/cjk.Merkava_0.3.0.jar<br /> cjm.chalk.Chalk 2.6.Be,http://scatterbright.com/robots/cjm.chalk.Chalk_2.6.Be.jar<br /> cjm.Charo 1.1,http://scatterbright.com/robots/cjm.Charo_1.1.jar<br /> cjm.Che 1.2,http://www.robocoderepository.com/BotFiles/2703/cjm.Che_1.2.jar<br /> cjm.Chomsky 1.5,http://scatterbright.com/robots/cjm.Chomsky_1.5.jar<br /> codemojo.nano.Woot 1.0,http://darkcanuck.net/rumble/robots/codemojo.nano.Woot_1.0.jar<br /> cs.ExclusionNano 1.1,http://file.csdgn.org/robocode/cs.ExclusionNano_1.1.jar<br /> csm.NthGeneration 0.04,http://www.robocoderepository.com/BotFiles/1214/csm.NthGeneration_0.04.jar<br /> csp.Eagle 3.30,http://www.robocoderepository.com/BotFiles/2436/csp.Eagle_3.30.jar<br /> css.Delitioner 0.11,http://darkcanuck.net/rumble/robots/css.Delitioner_0.11.jar<br /> cx.BlestPain 1.41,http://www.robocoderepository.com/BotFiles/1671/cx.BlestPain_1.41.jar<br /> cx.CigaretBH 1.03,http://www.robocoderepository.com/BotFiles/1414/cx.CigaretBH_1.03.jar<br /> cx.Lacrimas 1.36,http://www.robocoderepository.com/BotFiles/1820/cx.Lacrimas_1.36.jar<br /> cx.micro.Blur 0.2,http://www.robocoderepository.com/BotFiles/2447/cx.micro.Blur_0.2.jar<br /> cx.micro.Smoke 0.96,http://www.robocoderepository.com/BotFiles/1037/cx.micro.Smoke_0.96.jar<br /> cx.micro.Spark 0.6,http://www.robocoderepository.com/BotFiles/1320/cx.micro.Spark_0.6.jar<br /> cx.mini.BlackSwans 0.60,http://www.robocoderepository.com/BotFiles/1158/cx.mini.BlackSwans_0.60.jar<br /> cx.mini.Cigaret 1.31,http://www.robocoderepository.com/BotFiles/1152/cx.mini.Cigaret_1.31.jar<br /> cx.mini.Nimrod 0.55,http://www.robocoderepository.com/BotFiles/1236/cx.mini.Nimrod_0.55.jar<br /> cx.nano.Smog 2.6,http://www.robocoderepository.com/BotFiles/1036/cx.nano.Smog_2.6.jar<br /> cx.Princess 1.0,http://www.robocoderepository.com/BotFiles/1343/cx.Princess_1.0.jar<br /> da.NewBGank 1.4,http://www.robocoderepository.com/BotFiles/3312/da.NewBGank_1.4.jar<br /> dam.MogBot 2.9,http://www.robocoderepository.com/BotFiles/555/dam.MogBot_2.9.jar<br /> dans.Cinnamon 1.2,http://www.robocoderepository.com/BotFiles/1976/dans.Cinnamon_1.2.jar<br /> darkcanuck.Gaff 1.50,http://darkcanuck.net/rumble/robots/darkcanuck.Gaff_1.50.jar<br /> darkcanuck.Holden 1.13a,http://darkcanuck.net/rumble/robots/darkcanuck.Holden_1.13a.jar<br /> darkcanuck.Pris 0.88,http://darkcanuck.net/rumble/robots/darkcanuck.Pris_0.88.jar<br /> davidalves.Firebird 0.25,http://davidalves.net/robocode/robots/davidalves.Firebird_0.25.jar<br /> davidalves.Phoenix 1.02,http://davidalves.net/robocode/robots/davidalves.Phoenix_1.02.jar<br /> davidalves.PhoenixOS 1.1,http://davidalves.net/robocode/robots/davidalves.PhoenixOS_1.1.jar<br /> davidalves.net.Duelist 0.1.6src,http://www.robocoderepository.com/BotFiles/1000/davidalves.net.Duelist_0.1.6src.jar<br /> davidalves.net.DuelistMicro 1.22,http://www.robocoderepository.com/BotFiles/1144/davidalves.net.DuelistMicro_1.22.jar<br /> davidalves.net.DuelistMicroMkII 1.1,http://www.robocoderepository.com/BotFiles/1281/davidalves.net.DuelistMicroMkII_1.1.jar<br /> davidalves.net.DuelistMini 1.1,http://www.robocoderepository.com/BotFiles/1181/davidalves.net.DuelistMini_1.1.jar<br /> davidalves.net.DuelistNano 1.0,http://www.robocoderepository.com/BotFiles/1272/davidalves.net.DuelistNano_1.0.jar<br /> dcs.Eater_of_Worlds 1.1.3-A,http://www.robocoderepository.com/BotFiles/2578/dcs.Eater_of_Worlds_1.1.3-A.jar<br /> dcs.Eater_of_Worlds_Mini 1.0,http://www.robocoderepository.com/BotFiles/2850/dcs.Eater_of_Worlds_Mini_1.0.jar<br /> dcs.PM.Eater_of_Worlds_PM 1.2,http://www.robocoderepository.com/BotFiles/2856/dcs.PM.Eater_of_Worlds_PM_1.2.jar<br /> de.erdega.robocode.Polyphemos 0.4,http://darkcanuck.net/rumble/robots/de.erdega.robocode.Polyphemos_0.4.jar<br /> deewiant.Anomaly 0.2,http://www.iki.fi/~deewiant/files/deewiant.Anomaly_0.2.jar<br /> deith.Czolgzilla 0.11,http://www.robocoderepository.com/BotFiles/3256/deith.Czolgzilla_0.11.jar<br /> demetrix.ForceMajeure 0.75,http://ever-rage.narod.ru/robowiki/demetrix.ForceMajeure_0.75.jar<br /> demetrix.nano.Neutrino 0.27,http://ever-rage.narod.ru/robowiki/demetrix.nano.Neutrino_0.27.jar<br /> demetrix.nano.SledgeHammer 0.22,http://ever-rage.narod.ru/robowiki/demetrix.nano.SledgeHammer_0.22.jar<br /> deo.CloudBot 1.3,http://robocoderepository.com/BotFiles/3644/deo.CloudBot_1.3.jar<br /> deo.FlowerBot 1.0,http://robocoderepository.com/BotFiles/3683/deo.FlowerBot_1.0.jar<br /> deo.virtual.RainbowBot 1.0,http://robocoderepository.com/BotFiles/3694/deo.virtual.RainbowBot_1.0.jar<br /> dft.Calliope 5.6,http://www.robocoderepository.com/BotFiles/237/dft.Calliope_5.6.jar<br /> dft.Cyanide 1.90,http://darkcanuck.net/rumble/robots/dft.Cyanide_1.90.jar<br /> dft.Cyprus 3.0,http://www.robocoderepository.com/BotFiles/377/dft.Cyprus_3.0.jar<br /> dft.Freddie 1.32,http://darkcanuck.net/rumble/robots/dft.Freddie_1.32.jar<br /> dft.Guppy 1.0,http://darkcanuck.net/rumble/robots/dft.Guppy_1.0.jar<br /> dft.Immortal 1.40,http://darkcanuck.net/rumble/robots/dft.Immortal_1.40.jar<br /> dft.Krazy 1.5,http://www.robocoderepository.com/BotFiles/2099/dft.Krazy_1.5.jar<br /> dft.Virgin 1.25,http://www.robocoderepository.com/BotFiles/1447/dft.Virgin_1.25.jar<br /> dggp.haiku.gpBot_0 1.1,http://www.robocoderepository.com/BotFiles/3154/dggp.haiku.gpBot_0_1.1.jar<br /> dittman.BlindSquirl Retired,http://home.comcast.net/~kokyunage/robocode/ugluk/dittman.BlindSquirl_Retired.jar<br /> djc.Aardvark 0.3.6,http://www.robocoderepository.com/BotFiles/652/djc.Aardvark_0.3.6.jar<br /> djdjdj.NanoSkunk10 1.0,http://davidjoerg.com/robocode/djdjdj.NanoSkunk10_1.0.jar<br /> dk.stable.Gorgatron 1.1,http://www.robocoderepository.com/BotFiles/2112/dk.stable.Gorgatron_1.1.jar<br /> dks.MicroDanMK2 1.0,http://darkcanuck.net/rumble/robots/dks.MicroDanMK2_1.0.jar<br /> DM.Capriite 3.7.2,http://www.robocoderepository.com/BotFiles/2989/DM.Capriite_3.7.2.jar<br /> DM.Chicken 4.0,http://www.robocoderepository.com/BotFiles/3020/DM.Chicken_4.0.jar<br /> DM.Mijit .3,http://www.robocoderepository.com/BotFiles/3043/DM.Mijit_.3.jar<br /> dmp.micro.Aurora 1.41,http://www.robocoderepository.com/BotFiles/853/dmp.micro.Aurora_1.41.jar<br /> dmp.nano.Eve 3.41,http://www.robocoderepository.com/BotFiles/842/dmp.nano.Eve_3.41.jar<br /> donjezza.Jezza 1.0,http://www.robocoderepository.com/BotFiles/3385/donjezza.Jezza_1.0.jar<br /> donjezza.Muncho 1.0,http://www.robocoderepository.com/BotFiles/3384/donjezza.Muncho_1.0.jar<br /> drd.Dreadknoght 0.9,http://www.robocoderepository.com/BotFiles/3835/drd.Dreadknoght_0.9.jar<br /> drm.CobraBora 1.12,http://www.robocoderepository.com/BotFiles/1146/drm.CobraBora_1.12.jar<br /> drm.Magazine 0.39,http://www.robocoderepository.com/BotFiles/989/drm.Magazine_0.39.jar<br /> ds.OoV4 0.3b,http://www.robocoderepository.com/BotFiles/2851/ds.OoV4_0.3b.jar<br /> dsw.StaticD 1.0,http://darkcanuck.net/rumble/robots/dsw.StaticD_1.0.jar<br /> dsx724.VSAB_EP3a 1.0,http://darkcanuck.net/rumble/robots/dsx724.VSAB_EP3a_1.0.jar<br /> dsx724.VSAB_EP3_ATR 1.1,http://www.robocoderepository.com/BotFiles/3432/dsx724.VSAB_EP3_ATR_1.1.jar<br /> DTF.Kludgy 1.2b,http://www.robocoderepository.com/BotFiles/4041/DTF.Kludgy_1.2b.jar<br /> dukie.Ambassador 1.0,http://www.robocoderepository.com/BotFiles/2845/dukie.Ambassador_1.0.jar<br /> dummy.micro.HummingBird 2.14,http://www.robocoderepository.com/BotFiles/369/dummy.micro.HummingBird_2.14.jar<br /> dummy.micro.Sparrow 2.5,http://www.robocoderepository.com/BotFiles/484/dummy.micro.Sparrow_2.5.jar<br /> dummy.mini.Parakeet 2.40,http://www.robocoderepository.com/BotFiles/400/dummy.mini.Parakeet_2.40.jar<br /> dvogon.GangBang 1.0,http://www.robocoderepository.com/BotFiles/3193/dvogon.GangBang_1.0.jar<br /> dy.LevelOne 2.0,http://www.robocoderepository.com/BotFiles/3452/dy.LevelOne_2.0.jar<br /> dz.Caedo 1.4,http://www.robocoderepository.com/BotFiles/1044/dz.Caedo_1.4.jar<br /> dz.GalbaMicro 0.11,http://www.robocoderepository.com/BotFiles/2482/dz.GalbaMicro_0.11.jar<br /> dz.GalbaMini 0.121,http://darkcanuck.net/rumble/robots/dz.GalbaMini_0.121.jar<br /> dz.MostlyHarmlessNano 2.1,http://www.robocoderepository.com/BotFiles/2166/dz.MostlyHarmlessNano_2.1.jar<br /> dz.OthoMicro 0.12,http://www.robocoderepository.com/BotFiles/2198/dz.OthoMicro_0.12.jar<br /> dz.OthoMini 0.15,http://www.robocoderepository.com/BotFiles/2221/dz.OthoMini_0.15.jar<br /> eat.HumblePieLite 1.0,http://www.robocoderepository.com/BotFiles/1088/eat.HumblePieLite_1.0.jar<br /> ebo.Sparse 0.02,http://www.4geeks.de/files/ebo.Sparse_0.02.jar<br /> ebo.Tahoe 1.1.79,http://www.4geeks.de/files/ebo.Tahoe_1.1.79.jar<br /> EE.LittleBig 1.0,http://www.robocoderepository.com/BotFiles/4009/EE.LittleBig_1.0.jar<br /> EFD.AdvancedEFD 0.4.5a,http://sites.google.com/site/jannisbeese/robots/EFD.AdvancedEFD_0.4.5a.jar<br /> el.Attackr 0.1,http://darkcanuck.net/rumble/robots/el.Attackr_0.1.jar<br /> el.JumpShoot 0.2,http://www.robocoderepository.com/BotFiles/3360/el.JumpShoot_0.2.jar<br /> el33t.EL33tGangstarr2 2.0,http://www.robocoderepository.com/BotFiles/2069/el33t.EL33tGangstarr2_2.0.jar<br /> eld.Hmm 1.0,http://darkcanuck.net/rumble/robots/eld.Hmm_1.0.jar<br /> element.Earth 1.1,http://www.robocoderepository.com/BotFiles/3587/element.Earth_1.1.jar<br /> elloco.Flower 0.1r1,http://www.robocoderepository.com/BotFiles/3242/elloco.Flower_0.1r1.jar<br /> elloco.Kabuto 0.2r,http://www.robocoderepository.com/BotFiles/3229/elloco.Kabuto_0.2r.jar<br /> elvbot.ElverionBot 0.3,http://www.robocoderepository.com/BotFiles/3541/elvbot.ElverionBot_0.3.jar<br /> emp.Yngwie 1.11,http://www.robocoderepository.com/BotFiles/1928/emp.Yngwie_1.11.jar<br /> erdnis.Rover 0.3,http://www.free-games-fun.com/erdnis.Rover_0.3.jar<br /> eskimo.micro.Echo 0.1,http://robocoderepository.com/BotFiles/3969/eskimo.micro.Echo_0.1.jar<br /> et.Predator 1.8,http://www.robocoderepository.com/BotFiles/668/et.Predator_1.8.jar<br /> ethdsy.Malacka 2.4,http://www.robocoderepository.com/BotFiles/1159/ethdsy.Malacka_2.4.jar<br /> evd.X1 0.01,http://www.robocoderepository.com/BotFiles/3503/evd.X1_0.01.jar<br /> exauge.GateKeeper 1.1.121g,http://www.robocoderepository.com/BotFiles/3928/exauge.GateKeeper_1.1.121g.jar<br /> exauge.LemonDrop 1.6.130,http://www.robocoderepository.com/BotFiles/3911/exauge.LemonDrop_1.6.130.jar<br /> exauge.Leopard 1.1.019,http://www.robocoderepository.com/BotFiles/3917/exauge.Leopard_1.1.019.jar<br /> extra.LightSauce 0.01,http://www.robocoderepository.com/BotFiles/4031/extra.LightSauce_0.01.jar<br /> extra.Sauce .01,http://robocoderepository.com/BotFiles/4029/extra.Sauce_.01.jar<br /> fala.robocode.FalaRobot 1.0,http://www.robocoderepository.com/BotFiles/3474/fala.robocode.FalaRobot_1.0.jar<br /> fcr.First 1.0,http://www.robocoderepository.com/BotFiles/3362/fcr.First_1.0.jar<br /> Fenix.FenixTrack 1.0,http://www.robocoderepository.com/BotFiles/1627/Fenix.FenixTrack_1.0.jar<br /> florent.FloatingTadpole 1.2.6,http://www.robocoderepository.com/BotFiles/2675/florent.FloatingTadpole_1.2.6.jar<br /> florent.small.LittleAngel 1.8,http://www.robocoderepository.com/BotFiles/2917/florent.small.LittleAngel_1.8.jar<br /> florent.test.Toad 0.14t,http://wesley3.free.fr/florent.test.Toad_0.14t.jar<br /> florent.XSeries.X2 0.17,http://wesley3.free.fr/florent.XSeries.X2_0.17.jar<br /> fm.claire 1.7,http://www.robocoderepository.com/BotFiles/2251/fm.claire_1.7.jar<br /> fm.mammillarias 1.3,http://www.robocoderepository.com/BotFiles/2238/fm.mammillarias_1.3.jar<br /> fnc.bandit.Bandit 5.2.0,http://www.robocoderepository.com/BotFiles/2155/fnc.bandit.Bandit_5.2.0.jar<br /> fnc.bandit2002.Bandit2002 4.0.2,http://www.robocoderepository.com/BotFiles/2202/fnc.bandit2002.Bandit2002_4.0.2.jar<br /> frag.FragBot 1.0,http://darkcanuck.net/rumble/robots/frag.FragBot_1.0.jar<br /> franzor.Lizt 1.3.1,http://pages.prodigy.net/franz1/house/franzor.Lizt_1.3.1.jar<br /> fromHell.CHCl3 0.0.1,http://fromhell.schreiende-stille.de/fromHell.CHCl3_0.0.1.jar<br /> fullsail.LaxativeTeaTwo 1.0,http://www.robocoderepository.com/BotFiles/3403/fullsail.LaxativeTeaTwo_1.0.jar<br /> fullsail.TimbotNoPrediction 1.0,http://darkcanuck.net/rumble/robots/fullsail.TimbotNoPrediction_1.0.jar<br /> fullsail.SweetTea 1.1,http://darkcanuck.net/rumble/robots/fullsail.SweetTea_1.1.jar<br /> fushi.PvP1.PvP1 2004-02-16,http://www.robocoderepository.com/BotFiles/2023/fushi.PvP1.PvP1_2004-02-16.jar<br /> fw.Number1 1.0b,http://www.dijitari.com/void/robocode/fw.Number1_1.0b.jar<br /> gadsky.Gadsky 1.01,http://www.robocoderepository.com/BotFiles/3595/gadsky.Gadsky_1.01.jar<br /> Gecko.ultimateGeckoBot 1.0,http://www.robocoderepository.com/BotFiles/4039/Gecko.ultimateGeckoBot_1.0.jar<br /> geep.mini.GPBotA 1.0,http://www.robocoderepository.com/BotFiles/2361/geep.mini.GPBotA_1.0.jar<br /> geep.mini.GPBotB 1.1,http://www.robocoderepository.com/BotFiles/2363/geep.mini.GPBotB_1.1.jar<br /> germ.TheMind .2,http://www.robocoderepository.com/BotFiles/2525/germ.TheMind_.2.jar<br /> gg.Squaraus 0.6,http://www.robocoderepository.com/BotFiles/1788/gg.Squaraus_0.6.jar<br /> gg.Wolverine 2.0,http://darkcanuck.net/rumble/robots/gg.Wolverine_2.0.jar<br /> gh.GresSuffurd 0.3.2,http://home.versatel.nl/gheijenk/robocode/jarfiles/gh.GresSuffurd_0.3.2.jar<br /> gh.GrubbmGrb 1.2.4,http://home.versatel.nl/gheijenk/robocode/jarfiles/gh.GrubbmGrb_1.2.4.jar<br /> gh.GrypRepetyf 0.13,http://www.robocoderepository.com/BotFiles/2650/gh.GrypRepetyf_0.13.jar<br /> gh.micro.Grinnik 0.7,http://www.robocoderepository.com/BotFiles/3208/gh.micro.Grinnik_0.7.jar<br /> gh.micro.GrubbmThree 0.9,http://www.robocoderepository.com/BotFiles/2444/gh.micro.GrubbmThree_0.9.jar<br /> gh.mini.Gruwel 0.9,http://www.robocoderepository.com/BotFiles/2511/gh.mini.Gruwel_0.9.jar<br /> gh.nano.Grofvuil 0.2,http://www.robocoderepository.com/BotFiles/2553/gh.nano.Grofvuil_0.2.jar<br /> gimp.GimpBot 0.1,http://www.robocoderepository.com/BotFiles/2434/gimp.GimpBot_0.1.jar<br /> gio.RealGioBot 1.0,http://www.robocoderepository.com/BotFiles/2521/gio.RealGioBot_1.0.jar<br /> gjr.Cephalosporin 0.2,http://www.robocoderepository.com/BotFiles/2240/gjr.Cephalosporin_0.2.jar<br /> gm.GaetanoA 2.15,http://www.robocoderepository.com/BotFiles/2188/gm.GaetanoA_2.15.jar<br /> goblin.Bender 2.4,http://www.robocoderepository.com/BotFiles/1871/goblin.Bender_2.4.jar<br /> grybgoofy.GoofyBot 0.10,http://www.robocoderepository.com/BotFiles/2196/grybgoofy.GoofyBot_0.10.jar<br /> gu.MicroScoob 1.3,http://www.robocoderepository.com/BotFiles/2086/gu.MicroScoob_1.3.jar<br /> gwah.GBotMarkIV 1.0,http://www.horula.ca/roborumble/participants/download.php?file=18<br /> gwah.GerryBotMkII 1.5.1,http://www.horula.ca/roborumble/participants/download.php?file=17<br /> hamilton.Hamilton 1.0,http://www.robocoderepository.com/BotFiles/1408/hamilton.Hamilton_1.0.jar<br /> hapiel.Spiral 0.1,http://robocoderepository.com/BotFiles/3997/hapiel.Spiral_0.1.jar<br /> hirataatsushi.Neo 1.6,http://www.robocoderepository.com/BotFiles/1081/hirataatsushi.Neo_1.6.jar<br /> hirataatsushi.Trinity 0.003,http://www.robocoderepository.com/BotFiles/1145/hirataatsushi.Trinity_0.003.jar<br /> homerbots.h1 1.0,http://www.robocoderepository.com/BotFiles/2999/homerbots.h1_1.0.jar<br /> hp.Athena 0.1,http://www.robocoderepository.com/BotFiles/3415/hp.Athena_0.1.jar<br /> hvilela.HVilela 0.9,http://henrique.vilela.googlepages.com/hvilela.HVilela_0.9.jar<br /> ins.MobyNano 0.8,http://www.robocoderepository.com/BotFiles/939/ins.MobyNano_0.8.jar<br /> intruder.PrairieWolf 2.61,http://darkcanuck.net/rumble/robots/intruder.PrairieWolf_2.61.jar<br /> ivor.prophet.Prophet 0.01,http://www.ivan.php5.sk/ivor.prophet.Prophet_0.01.jar<br /> is.fon.rs.FonDestroyer3084 1.0,http://www.robocoderepository.com/BotFiles/4047/is.fon.rs.FonDestroyer3084_1.0.jar<br /> jaara.LambdaBot 1.1,http://www.robocoderepository.com/BotFiles/3514/jaara.LambdaBot_1.1.jar<br /> jab.avk.ManuelGallegus 0.6,http://darkcanuck.net/rumble/robots/jab.avk.ManuelGallegus_0.6.jar<br /> jab.DiamondStealer 5,http://darkcanuck.net/rumble/robots/jab.DiamondStealers_5.jar<br /> jab.micro.Sanguijuela 0.8,http://darkcanuck.net/rumble/robots/jab.micro.Sanguijuela_0.8.jar<br /> janm.Jammy 1.0,http://www.robocoderepository.com/BotFiles/3543/janm.Jammy_1.0.jar<br /> jam.micro.RaikoMicro 1.44,http://www.robocoderepository.com/BotFiles/1983/jam.micro.RaikoMicro_1.44.jar<br /> jam.mini.Raiko 0.43,http://www.robocoderepository.com/BotFiles/1922/jam.mini.Raiko_0.43.jar<br /> jam.RaikoMX 0.32,http://www.robocoderepository.com/BotFiles/1961/jam.RaikoMX_0.32.jar<br /> japs.Serenity 1.0,http://www.robocoderepository.com/BotFiles/2217/japs.Serenity_1.0.jar<br /> japs.Sjonniebot 0.9.1,http://www.robocoderepository.com/BotFiles/2203/japs.Sjonniebot_0.9.1.jar<br /> jasolo.Sonda 0.55,http://www.robocoderepository.com/BotFiles/1534/jasolo.Sonda_0.55.jar<br /> jaw.Mouse 0.11,http://www.robocoderepository.com/BotFiles/2472/jaw.Mouse_0.11.jar<br /> jaw.KarenCain 0.11,http://www.robocoderepository.com/BotFiles/2474/jaw.KarenCain_0.11.jar<br /> jaybot.adv.bots.JayBot 2.0,http://darkcanuck.net/rumble/robots/jaybot.adv.bots.JayBot_2.0.jar<br /> jaybot.bots.Oddball 4.0,http://darkcanuck.net/rumble/robots/jaybot.bots.Oddball_4.0.jar<br /> jbot.Rabbit2 1.1,http://darkcanuck.net/rumble/robots/jbot.Rabbit2_1.1.jar<br /> jcs.AutoBot 4.2.1,http://www.robocoderepository.com/BotFiles/2616/jcs.AutoBot_4.2.1.jar<br /> jcs.Decepticon 2.5.3,http://www.robocoderepository.com/BotFiles/2620/jcs.Decepticon_2.5.3.jar<br /> jcs.Megatron 1.2,http://www.robocoderepository.com/BotFiles/2632/jcs.Megatron_1.2.jar<br /> jcs.Seth 1.8,http://darkcanuck.net/rumble/robots/jcs.Seth_1.8.jar<br /> jcw.ArcherOne 1.0,http://darkcanuck.net/rumble/robots/jcw.ArcherOne_1.0.jar<br /> jekl.DarkHallow .90.9,http://www.robocoderepository.com/BotFiles/2296/jekl.DarkHallow_.90.9.jar<br /> jekl.Jekyl .70,http://www.robocoderepository.com/BotFiles/1837/jekl.Jekyl_.70.jar<br /> jekl.mini.BlackPearl .91,http://www.robocoderepository.com/BotFiles/1875/jekl.mini.BlackPearl_.91.jar<br /> jep.nano.Hawkwing 0.4.1,http://www.robocoderepository.com/BotFiles/1561/jep.nano.Hawkwing_0.4.1.jar<br /> jep.nano.Hotspur 0.1,http://www.robocoderepository.com/BotFiles/1877/jep.nano.Hotspur_0.1.jar<br /> jep.Terrible 0.4.1,http://www.robocoderepository.com/BotFiles/1536/jep.Terrible_0.4.1.jar<br /> jeremyreeder.Vincent 2011.12.09,http://www.robocoderepository.com/BotFiles/3993/jeremyreeder.Vincent_2011.12.09.jar<br /> jf.Dodger 1.1,http://keenehs.dyndns.org:90/rumble/robots/jf.Dodger_1.1.jar<br /> jf.Dodger 1.3,http://keenehs.dyndns.org:90/rumble/robots/jf.Dodger_1.3.jar<br /> jgap.JGAP12584 1.0,http://www.robocoderepository.com/BotFiles/3383/jgap.JGAP12584_1.0.jar<br /> jgap.JGAP130166 1.0,http://www.robocoderepository.com/BotFiles/3371/jgap.JGAP130166_1.0.jar<br /> jgap.JGAP23423 1.0,http://www.robocoderepository.com/BotFiles/3378/jgap.JGAP23423_1.0.jar<br /> jgap.JGAP6139 1.0,http://www.robocoderepository.com/BotFiles/3372/jgap.JGAP6139_1.0.jar<br /> jgap.JGAP7247_2 1.0,http://www.robocoderepository.com/BotFiles/3382/jgap.JGAP7247_2_1.0.jar<br /> jgap.JGAP7958 1.0,http://www.robocoderepository.com/BotFiles/3373/jgap.JGAP7958_1.0.jar<br /> jje.BagPuss 1.2,http://darkcanuck.net/rumble/robots/jje.BagPuss_1.2.jar<br /> jk.mega.DrussGT 1.9.8,http://www.minifly.rchomepage.com/robocode/jk.mega.DrussGT_1.9.8.jar<br /> jk.micro.Toorkild 0.2.4b,http://www.minifly.rchomepage.com/robocode/jk.micro.Toorkild_0.2.4b.jar<br /> jk.mini.CunobelinDC 0.6,https://sites.google.com/site/jkflying/jk.mini.CunobelinDC_0.6.jar<br /> jk.precise.Wintermute 0.7,http://www.minifly.rchomepage.com/robocode/jk.precise.Wintermute_0.7.jar<br /> jmcd.BeoWulf 2.8,http://www.robocoderepository.com/BotFiles/1377/jmcd.BeoWulf_2.8.jar<br /> joe.ADinosaur 1.0,http://www.robocoderepository.com/BotFiles/2822/joe.ADinosaur_1.0.jar<br /> josago.Jorgito 0.16,http://www.robocoderepository.com/BotFiles/4000/josago.Jorgito_0.16.jar<br /> jp.Perpy 16.0,http://www.robocoderepository.com/BotFiles/3001/jp.Perpy_16.0.jar<br /> jp.SineWall 1.0,http://www.robocoderepository.com/BotFiles/2968/jp.SineWall_1.0.jar<br /> jrm.Test0 1.0,http://www.robocoderepository.com/BotFiles/3636/jrm.Test0_1.0.jar<br /> js.PinBall 1.6,http://www.robocoderepository.com/BotFiles/684/js.PinBall_1.6.jar<br /> jsal.Jsalbot 1.0,http://jeremybubs.googlepages.com/jsal.Jsalbot_1.0.jar<br /> jt.SpearmintCT Alpha,http://www.robocoderepository.com/BotFiles/2164/jt.SpearmintCT_Alpha.jar<br /> justin.DemonicRage 3.20,http://sites.google.com/site/justinsitehere/file-cabinet/justin.DemonicRage_3.20.jar<br /> jw.Booring 1.11,http://www.robocoderepository.com/BotFiles/1250/jw.Booring_1.11.jar<br /> jwst.DAD.DarkAndDarker 1.1,http://darkcanuck.net/rumble/robots/jwst.DAD.DarkAndDarker_1.1.jar<br /> kanishk.Fr0z3n 1.1,http://darkcanuck.net/rumble/robots/kanishk.Fr0z3n_1.1.jar<br /> kano.gamma.KanoGamma 1.8,http://www.robocoderepository.com/BotFiles/1098/kano.gamma.KanoGamma_1.8.jar<br /> kawam.kmBot9 1.0,http://www.robocoderepository.com/BotFiles/967/kawam.kmBot9_1.0.jar<br /> kawigi.f.FhqwhgadsMicro 1.0,http://www.robocoderepository.com/BotFiles/1673/kawigi.f.FhqwhgadsMicro_1.0.jar<br /> kawigi.micro.Shiz 1.1,http://www.robocoderepository.com/BotFiles/2007/kawigi.micro.Shiz_1.1.jar<br /> kawigi.mini.Coriantumr 1.1,http://www.robocoderepository.com/BotFiles/1988/kawigi.mini.Coriantumr_1.1.jar<br /> kawigi.mini.Fhqwhgads 1.1,http://www.robocoderepository.com/BotFiles/1604/kawigi.mini.Fhqwhgads_1.1.jar<br /> kawigi.nano.FunkyChicken 1.1,http://www.robocoderepository.com/BotFiles/1512/kawigi.nano.FunkyChicken_1.1.jar<br /> kawigi.nano.ThnikkaBot 0.9,http://www.robocoderepository.com/BotFiles/2059/kawigi.nano.ThnikkaBot_0.9.jar<br /> kawigi.robot.Girl 1.2,http://www.robocoderepository.com/BotFiles/2124/kawigi.robot.Girl_1.2.jar<br /> kawigi.sbf.Barracuda 1.0,http://www.robocoderepository.com/BotFiles/1535/kawigi.sbf.Barracuda_1.0.jar<br /> kawigi.sbf.FloodHT 0.9.2,http://www.robocoderepository.com/BotFiles/1552/kawigi.sbf.FloodHT_0.9.2.jar<br /> kawigi.sbf.FloodMicro 1.5,http://www.robocoderepository.com/BotFiles/1381/kawigi.sbf.FloodMicro_1.5.jar<br /> kawigi.sbf.FloodMini 1.4,http://www.robocoderepository.com/BotFiles/1462/kawigi.sbf.FloodMini_1.4.jar<br /> kawigi.sbf.FloodNano 1.2,http://www.robocoderepository.com/BotFiles/1421/kawigi.sbf.FloodNano_1.2.jar<br /> kawigi.sbf.FloodSonnet 0.9,http://www.robocoderepository.com/BotFiles/1779/kawigi.sbf.FloodSonnet_0.9.jar<br /> kawigi.sbf.Teancum 1.3,http://www.robocoderepository.com/BotFiles/1470/kawigi.sbf.Teancum_1.3.jar<br /> kawigi.spare.SpareParts 0.7.6nosnd,http://www.robocoderepository.com/BotFiles/1335/kawigi.spare.SpareParts_0.7.6nosnd.jar<br /> kc.micro.Needle 0.101,http://www.robocoderepository.com/BotFiles/3379/kc.micro.Needle_0.101.jar<br /> kc.micro.Thorn 1.252,http://sites.google.com/site/kevcsite/robocode/kc.micro.Thorn_1.252.jar<br /> kc.micro.WaveShark 0.31,http://www.robocoderepository.com/BotFiles/3822/kc.micro.WaveShark_0.31.jar<br /> kc.mini.Vyper 0.311,http://darkcanuck.net/rumble/robots/kc.mini.Vyper_0.311.jar<br /> kc.nano.Splinter 1.2,http://darkcanuck.net/rumble/robots/kc.nano.Splinter_1.2.jar<br /> kc.serpent.Hydra 0.21,http://darkcanuck.net/rumble/robots/kc.serpent.Hydra_0.21.jar<br /> kc.serpent.WaveSerpent 2.11,http://sites.google.com/site/kevcsite/robocode/kc.serpent.WaveSerpent_2.11.jar<br /> kcn.percept.PerceptBot 2.3,http://www.robocoderepository.com/BotFiles/1075/kcn.percept.PerceptBot_2.3.jar<br /> kcn.unnamed.Unnamed 1.21,http://www.robocoderepository.com/BotFiles/1969/kcn.unnamed.Unnamed_1.21.jar<br /> kenran.mega.Pantheist 1.1,http://sites.google.com/site/kenranbots/robocode/kenran.mega.Pantheist_1.1.jar<br /> kid.Gladiator .7.2,http://darkcanuck.net/rumble/robots/kid.Gladiator_.7.2.jar<br /> kid.Toa .0.5,http://rednaxela-robocode.dyndns.org/data/robot_archive/kid.Toa_.0.5.jar<br /> KiraNL.Chupacabra 0.5,http://sandbox-project.nl/robocode/KiraNL.Chupacabra_0.5.jar<br /> KiraNL.ChupaLite 0.4,http://sandbox-project.nl/robocode/KiraNL.ChupaLite_0.4.jar<br /> KiraNL.SpaceKees 0.1,http://sandbox-project.nl/robocode/KiraNL.SpaceKees_0.1.jar<br /> kinsen.melee.Angsaichmophobia 1.8c,http://sites.google.com/site/dcvqksyb/robocode/kinsen.melee.Angsaichmophobia_1.8c.jar<br /> kinsen.nano.Hoplomachy 1.6,http://sites.google.com/site/dcvqksyb/robocode/kinsen.nano.Hoplomachy_1.6.jar<br /> kinsen.nano.Quarrelet 1.0,http://sites.google.com/site/dcvqksyb/robocode/kinsen.nano.Quarrelet_1.0.jar<br /> kinsen.nano.Senticous 1.0,http://sites.google.com/site/dcvqksyb/robocode/kinsen.nano.Senticous_1.0.jar<br /> kjc.etc.Dharok 1.0,http://www.robocoderepository.com/BotFiles/3293/kjc.etc.Dharok_1.0.jar<br /> kjc.MailManX 2.0,http://www.robocoderepository.com/BotFiles/3288/kjc.MailManX_2.0.jar<br /> kjc.Karaykan 1.0,http://www.robocoderepository.com/BotFiles/3289/kjc.Karaykan_1.0.jar<br /> klein.GottesKrieger 1.1,http://www.robocoderepository.com/BotFiles/3258/klein.GottesKrieger_1.1.jar<br /> Krabb.fe4r.Fe4r 0.4,http://www.robocoderepository.com/BotFiles/2766/Krabb.fe4r.Fe4r_0.4.jar<br /> Krabb.sliNk.Garm 0.9u,http://designnj.de/roboking/Krabb.sliNk.Garm_0.9u.jar<br /> Krabb.krabby.Krabby 1.18b,http://darkcanuck.net/rumble/robots/Krabb.krabby.Krabby_1.18b.jar<br /> Krabb.krabby2.Krabby2 1.9o,http://darkcanuck.net/rumble/robots/Krabb.krabby2.Krabby2_1.9o.jar<br /> krillr.mini.JointStrike 2.0.0,http://darkcanuck.net/rumble/robots/krillr.mini.JointStrike_2.0.0.jar<br /> krillr.mega.Psyche 0.0.3,http://darkcanuck.net/rumble/robots/krillr.mega.Psyche_0.0.3.jar<br /> kronenthaler.Basilisk 1.0,http://www.robocoderepository.com/BotFiles/4051/kronenthaler.Basilisk_1.0.jar<br /> krzysiek.robbo2.Robbo 1.0.0,http://darkcanuck.net/rumble/robots/krzysiek.robbo2.Robbo_1.0.0.jar<br /> kurios.DOSexe .9a,http://www.kuriosly.com/roborumble/kurios.DOSexe_.9a.jar<br /> kurios.DOSexe .9b,http://www.kuriosly.com/roborumble/kurios.DOSexe_.9b.jar<br /> kvk.HebusLeTroll 0.41,http://www.robocoderepository.com/BotFiles/2125/kvk.HebusLeTroll_0.41.jar<br /> labg.Cataclysm 2.05,http://www.robocoderepository.com/BotFiles/2399/labg.Cataclysm_2.05.jar<br /> lancel.Lynx 1.09,http://www.robocoderepository.com/BotFiles/3992/lancel.Lynx_1.09.jar<br /> lazarecki.mega.PinkerStinker 0.7,http://www.robocoderepository.com/BotFiles/3838/lazarecki.mega.PinkerStinker_0.7.jar<br /> leb.ShootAnArrow 0.1,http://www.robocoderepository.com/BotFiles/2648/leb.ShootAnArrow_0.1.jar<br /> lechu.Ala 0.0.4,http://www.robocoderepository.com/BotFiles/3497/lechu.Ala_0.0.4.jar<br /> lechu.Lechu 1.1,http://www.robocoderepository.com/BotFiles/3480/lechu.Lechu_1.1.jar<br /> lion.Kresnanano 1.0,http://www.robocoderepository.com/BotFiles/2295/lion.Kresnanano_1.0.jar<br /> lk.nano.Avesnar 1.1,http://www.robocoderepository.com/BotFiles/1597/lk.nano.Avesnar_1.1.jar<br /> lorneswork.Predator 1.0,http://www.robocoderepository.com/BotFiles/2609/lorneswork.Predator_1.0.jar<br /> lrem.Spectre 0.4.4,http://www.robocoderepository.com/BotFiles/2253/lrem.Spectre_0.4.4.jar<br /> lrem.magic.TormentedAngel Antiquitie,http://maxnet.org.pl/~lrem/lrem.magic.TormentedAngel_Antiquitie.jar<br /> lrem.micro.MoggFanatic 0.2,http://www.robocoderepository.com/BotFiles/2639/lrem.micro.MoggFanatic_0.2.jar<br /> lrem.micro.FalseProphet Alpha,http://www.robocoderepository.com/BotFiles/2415/lrem.micro.FalseProphet_Alpha.jar<br /> lrem.quickhack.QuickHack 1.0,http://www.robocoderepository.com/BotFiles/2555/lrem.quickhack.QuickHack_1.0.jar<br /> lunchie.Lunchbox 0.93,http://darkcanuck.net/rumble/robots/lunchie.Lunchbox_0.93.jar<br /> lw.LuthersTest 0.1,http://darkcanuck.net/rumble/robots/lw.LuthersTest_0.1.jar<br /> m3thos.Eva00 1.1,http://darkcanuck.net/rumble/robots/m3thos.Eva00_1.1.jar<br /> m3thos.Eva02 0.7.1,http://darkcanuck.net/rumble/robots/m3thos.Eva02_0.7.1.jar<br /> m3thos.mini.Eva01 0.5.5,http://darkcanuck.net/rumble/robots/m3thos.mini.Eva01_0.5.5.jar<br /> ma.is.fon.rs.RobotA 0.01,http://www.robocoderepository.com/BotFiles/4048/ma.is.fon.rs.RobotA_0.01.jar<br /> madmath.Cow 0.1.1,http://www.robocoderepository.com/BotFiles/3476/madmath.Cow_0.1.1.jar<br /> marcinek.TopGun 1.3,http://www.robocoderepository.com/BotFiles/3458/marcinek.TopGun_1.3.jar<br /> marksteam.Phoenix 1.0,http://www.robocoderepository.com/BotFiles/2749/marksteam.Phoenix_1.0.jar<br /> matt.advanced.Katana 1.0,http://www.robocoderepository.com/BotFiles/2498/matt.advanced.Katana_1.0.jar<br /> matt.BlueMind 0.8.00,http://www.robocoderepository.com/BotFiles/2685/matt.BlueMind_0.8.00.jar<br /> matt.UnderDark3 2.4.34,http://www.robocoderepository.com/BotFiles/2485/matt.UnderDark3_2.4.34.jar<br /> matt.UnderDark4 0.4.00,http://www.robocoderepository.com/BotFiles/2644/matt.UnderDark4_0.4.00.jar<br /> mbh.Mbh 0.1,http://www.robocoderepository.com/BotFiles/3365/mbh.Mbh_0.1.jar<br /> mbro.BelajarBot 0.0.3,http://www.robocoderepository.com/BotFiles/2471/mbro.BelajarBot_0.0.3.jar<br /> mbro.Detektor3 0.1.1,http://www.robocoderepository.com/BotFiles/2478/mbro.Detektor3_0.1.1.jar<br /> mc.Messapia 0.1.8,http://www.robocoderepository.com/BotFiles/2223/mc.Messapia_0.1.8.jar<br /> mcb.Audace 1.3,http://www.robocoderepository.com/BotFiles/3424/mcb.Audace_1.3.jar<br /> md.November 1.0,http://www.robocoderepository.com/BotFiles/1004/md.November_1.0.jar<br /> md.Pasta 1.1,http://www.robocoderepository.com/BotFiles/1014/md.Pasta_1.1.jar<br /> md.VelociRaptor 1.3,http://www.robocoderepository.com/BotFiles/232/md.VelociRaptor_1.3.jar<br /> mdouet.BotKicker 2.0,http://www.robocoderepository.com/BotFiles/1478/mdouet.BotKicker_2.0.jar<br /> metal.small.MCool 1.21,http://www.robocoderepository.com/BotFiles/1698/metal.small.MCool_1.21.jar<br /> metal.small.dna2.MCoolDNA 1.5,http://www.robocoderepository.com/BotFiles/2354/metal.small.dna2.MCoolDNA_1.5.jar<br /> microtestbotpack.MicroTestBot 1.0,http://dl.dropbox.com/u/4547352/robocode/microtestbotpack.MicroTestBot_1.0.jar<br /> mk.Alpha 0.2.1,http://darkcanuck.net/rumble/robots/mk.Alpha_0.2.1.jar<br /> mladjo.AIR 0.7,http://www.robocoderepository.com/BotFiles/3187/mladjo.AIR_0.7.jar<br /> mladjo.GnuKlub 0.1,http://darkcanuck.net/rumble/robots/mladjo.GnuKlub_0.1.jar<br /> mladjo.Grrrrr 0.9,http://www.robocoderepository.com/BotFiles/3189/mladjo.Grrrrr_0.9.jar<br /> mladjo.iRobot 0.3,http://www.robocoderepository.com/BotFiles/3149/mladjo.iRobot_0.3.jar<br /> mladjo.Startko 1.0,http://www.robocoderepository.com/BotFiles/3186/mladjo.Startko_1.0.jar<br /> mld.DustBunny 3.8,http://www.robocoderepository.com/BotFiles/3650/mld.DustBunny_3.8.jar<br /> mld.Infinity 2.2,http://www.robocoderepository.com/BotFiles/3591/mld.Infinity_2.2.jar<br /> mld.LittleBlackBook 1.69c,http://www.robocoderepository.com/BotFiles/3873/mld.LittleBlackBook_1.69c.jar<br /> mld.LittleBlackBook 1.69d,https://sites.google.com/site/dorganrobocode/mld.LittleBlackBook_1.69d.jar<br /> mld.Moebius 2.9.3,http://www.robocoderepository.com/BotFiles/3634/mld.Moebius_2.9.3.jar<br /> mld.Wisdom 1.0,http://www.robocoderepository.com/BotFiles/3640/mld.Wisdom_1.0.jar<br /> mmb.Roskilde 0.5,http://www.robocoderepository.com/BotFiles/3965/mmb.Roskilde_0.5.jar<br /> mme.NikeEnhanced 2.0,http://www.robocoderepository.com/BotFiles/2828/mme.NikeEnhanced_2.0.jar<br /> mn.Combat 1.0,http://www.robocoderepository.com/BotFiles/2351/mn.Combat_1.0.jar<br /> mn.WarMachine 1.1,http://www.robocoderepository.com/BotFiles/2574/mn.WarMachine_1.1.jar<br /> mnt.AHEB 0.6a,http://www.robocoderepository.com/BotFiles/2417/mnt.AHEB_0.6a.jar<br /> mnt.SurferBot 0.2.5,http://www.robocoderepository.com/BotFiles/2433/mnt.SurferBot_0.2.5.jar<br /> morbid.MorbidPriest 1.0,http://www.robocoderepository.com/BotFiles/1758/morbid.MorbidPriest_1.0.jar<br /> mrm.MightyMoose .2,http://darkcanuck.net/rumble/robots/mrm.MightyMoose_.2.jar<br /> ms.Ares 0.19,http://www.robocoderepository.com/BotFiles/730/ms.Ares_0.19.jar<br /> mue.Ascendant 1.2.27,http://mue.sonar-echo.de/robocode/mue.Ascendant_1.2.27.jar<br /> mue.Hyperion 0.8,http://www.robocoderepository.com/BotFiles/2224/mue.Hyperion_0.8.jar<br /> muf.CrazyKitten 0.9,http://www.robocoderepository.com/BotFiles/1946/muf.CrazyKitten_0.9.jar<br /> mwj.A1176183 1.0,http://robocode.rleach.id.au/mwj.A1176183_1.0.jar<br /> myl.micro.Avipes 1.00,http://www.robocoderepository.com/BotFiles/1347/myl.micro.Avipes_1.00.jar<br /> myl.micro.NekoNinja 1.30,http://www.robocoderepository.com/BotFiles/944/myl.micro.NekoNinja_1.30.jar<br /> myl.micro.Predator 1.50,http://www.robocoderepository.com/BotFiles/1097/myl.micro.Predator_1.50.jar<br /> myl.micro.Troodon 1.10,http://www.robocoderepository.com/BotFiles/1226/myl.micro.Troodon_1.10.jar<br /> myl.nano.Graviton 1.10,http://www.robocoderepository.com/BotFiles/770/myl.nano.Graviton_1.10.jar<br /> myl.nano.Kakuru 1.20,http://www.robocoderepository.com/BotFiles/1330/myl.nano.Kakuru_1.20.jar<br /> myl.nano.KomoriNinja 1.1,http://www.robocoderepository.com/BotFiles/978/myl.nano.KomoriNinja_1.1.jar<br /> mym.EdgeStalker 1.0,http://www.robocoderepository.com/BotFiles/3956/mym.EdgeStalker_1.0.jar<br /> mz.Adept 2.65,http://www.robocoderepository.com/BotFiles/2090/mz.Adept_2.65.jar<br /> mz.AdeptBSB 1.03,http://www.robocoderepository.com/BotFiles/2113/mz.AdeptBSB_1.03.jar<br /> mz.Movement 1.8,http://www.robocoderepository.com/BotFiles/2145/mz.Movement_1.8.jar<br /> mz.NanoDeath 2.56,http://www.robocoderepository.com/BotFiles/2010/mz.NanoDeath_2.56.jar<br /> mz.NanoGod 2.02,http://www.robocoderepository.com/BotFiles/1996/mz.NanoGod_2.02.jar<br /> nammyung.ModelT 0.23,http://www.robocoderepository.com/BotFiles/969/nammyung.ModelT_0.23.jar<br /> nanoskank.NanoSkank 1.0,http://darkcanuck.net/rumble/robots/nanoskank.NanoSkank_1.0.jar<br /> nat.BlackHole 2.0gamma,http://nat.robothai.net/robots/nat.BlackHole_2.0gamma.jar<br /> nat.micro.NP 1.34,http://nat.robothai.net/robots/nat.micro.NP_1.34.jar<br /> nat.micro.Reepicheep 0.1a,http://nat.robothai.net/robots/nat.micro.Reepicheep_0.1a.jar<br /> nat.nano.Ocnirp 1.73,http://nat.robothai.net/robots/nat.nano.Ocnirp_1.73.jar<br /> nat.nano.OcnirpPM 1.0,http://nat.robothai.net/robots/nat.nano.OcnirpPM_1.0.jar<br /> nat.nano.OcnirpSNG 1.0b,http://nat.robothai.net/robots/nat.nano.OcnirpSNG_1.0b.jar<br /> nat.Samekh 0.4,http://nat.robothai.net/robots/nat.Samekh_0.4.jar<br /> ncj.MoxieBot 1.0,http://www.robocoderepository.com/BotFiles/4003/ncj.MoxieBot_1.0.jar<br /> ndn.DyslexicMonkey 1.1,http://www.robocoderepository.com/BotFiles/1141/ndn.DyslexicMonkey_1.1.jar<br /> NDH.GuessFactor 1.0, http://www.robocoderepository.com/BotFiles/3949/NDH.GuessFactor_1.0.jar<br /> ne.Chimera 1.2,http://www.robocoderepository.com/BotFiles/3276/ne.Chimera_1.2.jar<br /> nexus.One 1.0,http://darkcanuck.net/rumble/robots/nexus.One_1.0.jar<br /> nexus.Prototype 1.0,http://darkcanuck.net/rumble/robots/nexus.Prototype_1.0.jar<br /> nic.Nicator 2.4,http://www.robocoderepository.com/BotFiles/193/nic.Nicator_2.4.jar<br /> nic.SnippetBot 1.0,http://www.robocoderepository.com/BotFiles/286/nic.SnippetBot_1.0.jar<br /> nkn.mini.Jskr0 0.1,http://www.robocoderepository.com/BotFiles/3852/nkn.mini.Jskr0_0.1.jar<br /> NG.LegatusLegionis 1.0,http://www.robocoderepository.com/BotFiles/3888/NG.LegatusLegionis_1.0.jar<br /> NG.LegatusLegionis 1.1,http://www.robocoderepository.com/BotFiles/3889/NG.LegatusLegionis_1.1.jar<br /> NG.LegatusLegionis 1.2,http://www.robocoderepository.com/BotFiles/4026/NG.LegatusLegionis_1.2.jar<br /> non.mega.NaN 0.1,http://www.robocoderepository.com/BotFiles/1960/non.mega.NaN_0.1.jar<br /> non.mega.NoName 0.0,http://www.robocoderepository.com/BotFiles/1957/non.mega.NoName_0.0.jar<br /> Noran.BitchingElk 0.054,http://www.robocoderepository.com/BotFiles/1855/Noran.BitchingElk_0.054.jar<br /> Noran.RandomTargeting 0.02,http://www.robocoderepository.com/BotFiles/1849/Noran.RandomTargeting_0.02.jar<br /> nova.Snow 1.0,http://www.robocoderepository.com/BotFiles/3623/nova.Snow_1.0.jar<br /> ntc.Cannon 1.12test,http://www.robocoderepository.com/BotFiles/3815/ntc.Cannon_1.12test.jar<br /> ntc.Evader 1.2,http://www.robocoderepository.com/BotFiles/3355/ntc.Evader_1.2.jar<br /> ntc.Knowledge 1.1,http://www.robocoderepository.com/BotFiles/3354/ntc.Knowledge_1.1.jar<br /> ntc.Lasers.Lasers 0.9,http://www.robocoderepository.com/BotFiles/3359/ntc.Lasers.Lasers_0.9.jar<br /> ntc.Plains 0.9,http://www.robocoderepository.com/BotFiles/3381/ntc.Plains_0.9.jar<br /> ntc.Swim 0.9,http://www.robocoderepository.com/BotFiles/3820/ntc.Swim_0.9.jar<br /> ntw.Sighup 1.5,http://darkcanuck.net/rumble/robots/ntw.Sighup_1.5.jar<br /> ntw.Sigsys 1.6,http://darkcanuck.net/rumble/robots/ntw.Sigsys_1.6.jar<br /> nz.jdc.micro.HedgehogGF 1.3,http://www.robocoderepository.com/BotFiles/3626/nz.jdc.micro.HedgehogGF_1.3.jar<br /> nz.jdc.micro.HedgehogP 1.2,http://www.robocoderepository.com/BotFiles/3622/nz.jdc.micro.HedgehogP_1.2.jar<br /> nz.jdc.nano.NeophytePattern 1.0,http://www.robocoderepository.com/BotFiles/3578/nz.jdc.nano.NeophytePattern_1.0.jar<br /> nz.jdc.nano.NeophytePRAL 1.2,http://www.robocoderepository.com/BotFiles/3568/nz.jdc.nano.NeophytePRAL_1.2.jar<br /> nz.jdc.nano.NeophyteSRAL 1.2,http://www.robocoderepository.com/BotFiles/3567/nz.jdc.nano.NeophyteSRAL_1.2.jar<br /> oa.weak.BotherBot 0.1,http://www.robocoderepository.com/BotFiles/2956/oa.weak.BotherBot_0.1.jar<br /> oa.weak.FlyMk1 0.1,http://www.robocoderepository.com/BotFiles/2958/oa.weak.FlyMk1_0.1.jar<br /> ola.Puffin 1.0,http://www.robocoderepository.com/BotFiles/3380/ola.Puffin_1.0.jar<br /> oog.melee.Capulet 1.1,https://sites.google.com/site/crazybassoon/oog.melee.Capulet_1.1.jar<br /> oog.melee.Mercutio 1.0,http://www.robocoderepository.com/BotFiles/3848/oog.melee.Mercutio_1.0.jar<br /> oog.micro.MagicD3 0.41,http://www.robocoderepository.com/BotFiles/3801/oog.micro.MagicD3_0.41.jar<br /> oog.micro.Maui 1.2,https://sites.google.com/site/crazybassoon/oog.micro.Maui_1.2.jar<br /> oog.micro.SavantMicro 1.0,http://www.robocoderepository.com/BotFiles/3958/oog.micro.SavantMicro_1.0.jar<br /> oog.mini.AlphaDragon 0.1,http://www.robocoderepository.com/BotFiles/4015/oog.mini.AlphaDragon_0.1.jar<br /> oog.nano.Caligula 1.15,http://www.robocoderepository.com/BotFiles/4022/oog.nano.Caligula_1.15.jar<br /> oog.nano.Fuatisha 1.1,http://www.robocoderepository.com/BotFiles/4045/oog.nano.Fuatisha_1.1.jar<br /> oog.nano.MagicD2 2.4,http://www.robocoderepository.com/BotFiles/3749/oog.nano.MagicD2_2.4.jar<br /> oog.nano.SavantVS 1.1,http://www.robocoderepository.com/BotFiles/3714/oog.nano.SavantVS_1.1.jar<br /> oog.nano.SavantWS 0.1,http://www.robocoderepository.com/BotFiles/3709/oog.nano.SavantWS_0.1.jar<br /> oog.PricklyPear 1.0.4,https://sites.google.com/site/crazybassoon/oog.PricklyPear_1.0.4.jar<br /> pa.Improved 1.1,http://darkcanuck.net/rumble/robots/pa.Improved_1.1.jar<br /> pak.JakeTheTestingRobot .1b,http://www.robocoderepository.com/BotFiles/3373/pak.JakeTheTestingRobot_.1b.jar<br /> pak.Dargon 1.0b,http://www.robocoderepository.com/BotFiles/3388/pak.Dargon_1.0b.jar<br /> pak.Dargon .2c,http://www.robocoderepository.com/BotFiles/3389/pak.Dargon_.2c.jar<br /> panzer.Panzer 0.2,http://www.robocoderepository.com/BotFiles/4008/panzer.Panzer_0.2.jar<br /> paolord.TheHulk 1.0,http://www.robocoderepository.com/BotFiles/3595/paolord.TheHulk_1.0.jar<br /> patson.PatsonTestBot 1.0,http://www.robocoderepository.com/BotFiles/3324/patson.PatsonTestBot_1.0.jar<br /> paulk.PaulV3 1.7,http://www.robocoderepository.com/BotFiles/3502/paulk.PaulV3_1.7.jar<br /> paulk.PaulV3 1.6,http://www.robocoderepository.com/BotFiles/3497/paulk.PaulV3_1.6.jar<br /> paulk.PaulV3 1.5,http://www.robocoderepository.com/BotFiles/3496/paulk.PaulV3_1.5.jar<br /> paulk.PaulV3 1.3,http://www.robocoderepository.com/BotFiles/3495/paulk.PaulV3_1.3.jar<br /> pb.Oscillator 1.0,http://www.robocoderepository.com/BotFiles/2070/pb.Oscillator_1.0.jar<br /> pe.mini.SandboxMini 1.2,http://www.robocoderepository.com/BotFiles/917/pe.mini.SandboxMini_1.2.jar<br /> pe.minimelee.SandboxMiniMelee 1.1,http://www.robocoderepository.com/BotFiles/934/pe.minimelee.SandboxMiniMelee_1.1.jar<br /> pe.SandboxDT 3.02,http://www.robocoderepository.com/BotFiles/793/pe.SandboxDT_3.02.jar<br /> pe.SandboxLump 1.52,http://www.robocoderepository.com/BotFiles/731/pe.SandboxLump_1.52.jar<br /> pedersen.Hubris 2.4,http://home.comcast.net/~kokyunage/robocode/hubris/pedersen.Hubris_2.4.jar<br /> pedersen.Ugluk 1.0,http://home.comcast.net/~kokyunage/robocode/ugluk/pedersen.Ugluk_1.0.jar<br /> pez.clean.Swiffer 0.2.9,http://www.robocoderepository.com/BotFiles/1883/pez.clean.Swiffer_0.2.9.jar<br /> pez.frankie.Frankie 0.9.6.1,http://www.robocoderepository.com/BotFiles/1565/pez.frankie.Frankie_0.9.6.1.jar<br /> pez.gloom.GloomyDark 0.9.2,http://www.robocoderepository.com/BotFiles/1741/pez.gloom.GloomyDark_0.9.2.jar<br /> pez.mako.Mako 1.5,http://www.robocoderepository.com/BotFiles/1317/pez.mako.Mako_1.5.jar<br /> pez.micro.Aristocles 0.3.7,http://www.robocoderepository.com/BotFiles/1923/pez.micro.Aristocles_0.3.7.jar<br /> pez.mini.ChironexFleckeri 0.5,http://www.robocoderepository.com/BotFiles/2513/pez.mini.ChironexFleckeri_0.5.jar<br /> pez.mini.Gouldingi 1.5,http://www.robocoderepository.com/BotFiles/1351/pez.mini.Gouldingi_1.5.jar<br /> pez.mini.Pugilist 2.4.18,http://darkcanuck.net/rumble/robots/pez.mini.Pugilist_2.4.18.jar<br /> pez.mini.Tityus 0.9.1,http://www.robocoderepository.com/BotFiles/1657/pez.mini.Tityus_0.9.1.jar<br /> pez.mini.VertiLeach 0.4.0,http://www.robocoderepository.com/BotFiles/1744/pez.mini.VertiLeach_0.4.0.jar<br /> pez.nano.Icarus 0.3,http://www.robocoderepository.com/BotFiles/2353/pez.nano.Icarus_0.3.jar<br /> pez.nano.LittleEvilBrother 0.1,http://www.robocoderepository.com/BotFiles/2056/pez.nano.LittleEvilBrother_0.1.jar<br /> pez.rumble.Ali 0.4.9,http://www.robocoderepository.com/BotFiles/2416/pez.rumble.Ali_0.4.9.jar<br /> pez.rumble.CassiusClay 2rho.01b,http://www.dijitari.com/void/robocode/pez.rumble.CassiusClay_2rho.01b.jar<br /> pfvicm.Sobieski 7.2.3b,http://www.robocoderepository.com/BotFiles/2911/pfvicm.Sobieski_7.2.3b.jar<br /> ph.micro.Pikeman 0.4.5,http://www.robocoderepository.com/BotFiles/2364/ph.micro.Pikeman_0.4.5.jar<br /> ph.mini.Archer 0.6.6,http://www.robocoderepository.com/BotFiles/2326/ph.mini.Archer_0.6.6.jar<br /> ph.musketeer.Musketeer 0.6,http://www.robocoderepository.com/BotFiles/2281/ph.musketeer.Musketeer_0.6.jar<br /> ph.Thinker 0.2.5,http://www.robocoderepository.com/BotFiles/2336/ph.Thinker_0.2.5.jar<br /> pi.Dark 10,http://darkcanuck.net/rumble/robots/pi.Dark_10.jar<br /> pl.Drum 0.1,http://darkcanuck.net/rumble/robots/pl.Drum_0.1.jar<br /> pl.Patton.GeneralPatton 1.54,http://darkcanuck.net/rumble/robots/pl.Patton.GeneralPatton_1.54.jar<br /> pla.Memnoch 0.5,http://www.robocoderepository.com/BotFiles/2211/pla.Memnoch_0.5.jar<br /> PK.Twardy 0.4.2,http://www.robocoderepository.com/BotFiles/3272/PK.Twardy_0.4.2.jar<br /> pkdeken.Paladin 1.0,http://www.robocoderepository.com/BotFiles/3556/pkdeken.Paladin_1.0.jar<br /> PkKillers.PkAssassin 1.0,http://www.robocoderepository.com/BotFiles/3485/PkKillers.PkAssassin_1.0.jar<br /> pmc.SniperBot 1.0,http://darkcanuck.net/rumble/robots/pmc.SniperBot_1.0.jar<br /> populations.TrainStoopidbot 0.01,http://www.robocoderepository.com/BotFiles/4052/populations.TrainStoopidbot_0.01.jar<br /> positive.Portia 1.26e,http://sites.google.com/site/robopositive/portia/positive.Portia_1.26e.jar<br /> povik.nano.Smilee 0.2.1,http://www.robocoderepository.com/BotFiles/3950/povik.nano.Smilee_0.2.1.jar<br /> projectx.ProjectNano 2.0,http://darkcanuck.net/rumble/robots/projectx.ProjectNano_2.0.jar<br /> projectx.TestNano 1.0,http://www.robocoderepository.com/BotFiles/3444/projectx.TestNano_1.0.jar<br /> pulsar.PulsarMax 0.8.9,http://www.robocoderepository.com/BotFiles/2227/pulsar.PulsarMax_0.8.9.jar<br /> pulsar.PulsarNano 0.2.4,http://www.robocoderepository.com/BotFiles/2335/pulsar.PulsarNano_0.2.4.jar<br /> pulsar.Nanis 0.3,http://www.robocoderepository.com/BotFiles/2560/pulsar.Nanis_0.3.jar<br /> qohnil.blot.BlotBot 3.61,http://www.robocoderepository.com/BotFiles/546/qohnil.blot.BlotBot_3.61.jar<br /> Queens_teamrobot.UltraRazor 1.0,http://www.robocoderepository.com/BotFiles/2108/Queens_teamrobot.UltraRazor_1.0.jar<br /> quietus.Invader 0.1,http://robocode.rleach.id.au/quietus.Invader_0.1.jar<br /> quietus.NarrowRadar 0.1,http://robocode.rleach.id.au/quietus.NarrowRadar_0.1.jar<br /> radnor.DoctorBob 1.42,http://www.robocoderepository.com/BotFiles/2133/radnor.DoctorBob_1.42.jar<br /> radnor.RamRod 1.0,http://www.robocoderepository.com/BotFiles/2085/radnor.RamRod_1.0.jar<br /> rampancy.Durandal 2.2d,http://stanford.edu/~mchunlum/robocode/rampancy.Durandal_2.2d.jar<br /> rampancy.micro.Epiphron 1.0,http://stanford.edu/~mchunlum/robocode/rampancy.micro.Epiphron_1.0.jar<br /> rapture.Rapture 2.13,http://www.robocoderepository.com/BotFiles/15/rapture.Rapture_2.13.jar<br /> ratosh.nano.Debo 1.36,http://www.robocoderepository.com/BotFiles/1702/ratosh.nano.Debo_1.36.jar<br /> ratosh.Nobo 0.21,http://www.robocoderepository.com/BotFiles/1612/ratosh.Nobo_0.21.jar<br /> ratosh.Wesco 1.4,http://www.robocoderepository.com/BotFiles/1914/ratosh.Wesco_1.4.jar<br /> rc.yoda.Yoda 1.0.6c.fix,http://rednaxela-robocode.dyndns.org/data/robots/rc.yoda.Yoda_1.0.6c.fix.jar<br /> rcb.Vanessa03 0,http://www.robocoderepository.com/BotFiles/1364/rcb.Vanessa03_0.jar<br /> rcp.Kuramatron 1.0,http://www.robocoderepository.com/BotFiles/3307/rcp.Kuramatron_1.0.jar<br /> rdt199.Warlord 0.73,http://www.robocoderepository.com/BotFiles/1130/rdt199.Warlord_0.73.jar<br /> reaper.Reaper 1.1,http://www.robocoderepository.com/BotFiles/3412/reaper.Reaper_1.1.jar<br /> repositorio.NanoStep 1.0,http://darkcanuck.net/rumble/robots/repositorio.NanoStep_1.0.jar<br /> rfj.Sunburn 1.1,http://www.robocoderepository.com/BotFiles/1060/rfj.Sunburn_1.1.jar<br /> rijteam.SmartDodge 1.1,http://www.robocoderepository.com/BotFiles/2959/rijteam.SmartDodge_1.1.jar<br /> robar.haiku.Spike 1.0,http://invitel.hu/artrog/robar.haiku.Spike_1.0.jar<br /> robar.micro.Gladius 1.15,http://invitel.hu/artrog/robar.micro.Gladius_1.15.jar<br /> robar.micro.Kirbyi 1.0,http://hunrobar.freeblog.hu/files/myrobots/robar.micro.Kirbyi_1.0.jar<br /> robar.micro.Topaz 0.25,http://invitel.hu/artrog/robar.micro.Topaz_0.25.jar<br /> robar.nano.Assertive 0.3,http://invitel.hu/artrog/robar.nano.Assertive_0.3.jar<br /> robar.nano.BlackWidow 1.3,http://www.robocoderepository.com/BotFiles/3574/robar.nano.BlackWidow_1.3.jar<br /> robar.nano.Breeze 0.3,http://hunrobar.freeblog.hu/files/myrobots/robar.nano.Breeze_0.3.jar<br /> robar.nano.Mosquito 1.1,http://hunrobar.freeblog.hu/files/myrobots/robar.nano.Mosquito_1.1.jar<br /> robar.nano.MosquitoPM 1.0,http://www.robocoderepository.com/BotFiles/3559/robar.nano.MosquitoPM_1.0.jar<br /> robar.nano.Prestige 1.0,http://www.robocoderepository.com/BotFiles/3507/robar.nano.Prestige_1.0.jar<br /> robar.nano.Pugio 1.49,http://www.robocoderepository.com/BotFiles/3710/robar.nano.Pugio_1.49.jar<br /> robar.nano.Scytodes 0.3,http://hunrobar.freeblog.hu/files/myrobots/robar.nano.Scytodes_0.3.jar<br /> robar.nano.Vespa 0.95,http://hunrobar.freeblog.hu/files/myrobots/robar.nano.Vespa_0.95.jar<br /> robo.PartsBot 1.1,http://darkcanuck.net/rumble/robots/robo.PartsBot_1.1.jar<br /> RobotMarco.MarcoV 0.1,http://www.robocoderepository.com/BotFiles/3941/RobotMarco.MarcoV_0.1.jar<br /> rsim.micro.uCatcher 0.1,http://sites.google.com/site/rsimander/robocode/rsim.micro.uCatcher_0.1.jar<br /> rsim.mini.BulletCatcher 0.4,http://www.robocoderepository.com/BotFiles/3737/rsim.mini.BulletCatcher_0.4.jar<br /> rsk1.RSK1 4.0,http://www.robocoderepository.com/BotFiles/3284/rsk1.RSK1_4.0.jar<br /> ruc.nano.Zealot 0.2,http://www.robocoderepository.com/BotFiles/1229/ruc.nano.Zealot_0.2.jar<br /> rus.vv.Dzhigit 1.1,http://www.robocoderepository.com/BotFiles/4002/rus.vv.Dzhigit1.1.jar<br /> rus.vv.Snezhok 1.1,http://www.robocoderepository.com/BotFiles/3998/rus.vv.Snezhok1.1.jar<br /> ry.LightningBug 1.0,http://www.robocoderepository.com/BotFiles/3472/ry.LightningBug_1.0.jar<br /> ry.VirtualGunExperiment 1.2.0,http://www.robocoderepository.com/BotFiles/3662/ry.VirtualGunExperiment_1.2.0.jar<br /> ry.Worst 1.0,http://www.robocoderepository.com/BotFiles/3645/ry.Worst_1.0.jar<br /> rz.Aleph 0.34,http://www.robocoderepository.com/BotFiles/1993/rz.Aleph_0.34.jar<br /> rz.Apollon 0.23,http://www.robocoderepository.com/BotFiles/2098/rz.Apollon_0.23.jar<br /> rz.Artist 0.2,http://www.robocoderepository.com/BotFiles/2156/rz.Artist_0.2.jar<br /> rz.GlowBlow 2.31,http://www.robocoderepository.com/BotFiles/1354/rz.GlowBlow_2.31.jar<br /> rz.GlowBlowAPM 1.0,http://www.robocoderepository.com/BotFiles/1382/rz.GlowBlowAPM_1.0.jar<br /> rz.GlowBlowMelee 1.4,http://www.robocoderepository.com/BotFiles/1436/rz.GlowBlowMelee_1.4.jar<br /> rz.HawkOnFire 0.1,http://www.robocoderepository.com/BotFiles/1575/rz.HawkOnFire_0.1.jar<br /> rz.SmallDevil 1.502,http://www.robocoderepository.com/BotFiles/1322/rz.SmallDevil_1.502.jar<br /> sadoner.killer 0.2,http://www.robocoderepository.com/BotFiles/4020/sadoner.killer_0.2.jar<br /> sam.ChipmunkDuelist 1.0,http://www.robocoderepository.com/BotFiles/3094/sam.ChipmunkDuelist_1.0.jar<br /> sam.Samspin 1.0,http://www.robocoderepository.com/BotFiles/2823/sam.Samspin_1.0.jar<br /> sanyi.mikrobi.Roberto 1.0,http://www.robocoderepository.com/BotFiles/3929/sanyi.mikrobi.Roberto_1.0.jar<br /> sch.Simone 0.3d,http://www.robocoderepository.com/BotFiles/374/sch.Simone_0.3d.jar<br /> serenity.moonlightBat 1.17,http://www.robocoderepository.com/BotFiles/2877/serenity.moonlightBat_1.17.jar<br /> serenity.nonSense 1.39,http://www.robocoderepository.com/BotFiles/3586/serenity.nonSense_1.39.jar<br /> serenity.serenityFire 1.29,http://www.robocoderepository.com/BotFiles/3071/serenity.serenityFire_1.29.jar<br /> sgp.JollyNinja 3.53,http://www.robocoderepository.com/BotFiles/183/sgp.JollyNinja_3.53.jar<br /> sgp.MadHatter 4.13,http://www.robocoderepository.com/BotFiles/156/sgp.MadHatter_4.13.jar<br /> sgp.nano.FurryLeech 1.0,http://www.robocoderepository.com/BotFiles/802/sgp.nano.FurryLeech_1.0.jar<br /> sgp.ShiningBeetle 1.1,http://www.robocoderepository.com/BotFiles/498/sgp.ShiningBeetle_1.1.jar<br /> sgp.SleepingGoat 1.1,http://www.robocoderepository.com/BotFiles/500/sgp.SleepingGoat_1.1.jar<br /> SHAM.WOW 1.4,http://darkcanuck.net/rumble/robots/SHAM.WOW_1.4.jar<br /> shinh.Entangled 0.3,http://www.robocoderepository.com/BotFiles/1070/shinh.Entangled_0.3.jar<br /> shrub.Silver v048,http://www.robocoderepository.com/BotFiles/449/shrub.Silver_v048.jar<br /> shrub.Vapour v159,http://www.robocoderepository.com/BotFiles/2654/shrub.Vapour_v159.jar<br /> shu.nitro.LENIN .T34,http://www.robocoderepository.com/BotFiles/1956/shu.nitro.LENIN_.T34.jar<br /> sigterm.Sigterm 1.0,http://darkcanuck.net/rumble/robots/sigterm.Sigterm_1.0.jar<br /> simonton.beta.LifelongObsession 0.5.1,http://www.robocoderepository.com/BotFiles/3195/simonton.beta.LifelongObsession_0.5.1.jar<br /> simonton.GFNano_D 3.1b,http://www.robocoderepository.com/BotFiles/3114/simonton.GFNano_D_3.1b.jar<br /> simonton.nano.WeekendObsession_S 1.7,http://www.robocoderepository.com/BotFiles/3117/simonton.nano.WeekendObsession_S_1.7.jar<br /> simonton.mega.SniperFrog 1.0.fix2,http://rednaxela-robocode.dyndns.org/data/robots/simonton.mega.SniperFrog_1.0.fix2.jar<br /> simonton.micro.GFMicro 1.0,http://darkcanuck.net/rumble/robots/simonton.micro.GFMicro_1.0.jar<br /> simonton.micro.WeeklongObsession 3.4.1,http://darkcanuck.net/rumble/robots/simonton.micro.WeeklongObsession_3.4.1.jar<br /> simonton.mini.WeeksOnEnd 1.10.4,http://darkcanuck.net/rumble/robots/simonton.mini.WeeksOnEnd_1.10.4.jar<br /> skm.butterfly 1.0,http://www.robocoderepository.com/BotFiles/3868/sean1.jar<br /> skm.Ryubot 1.0,http://www.robocoderepository.com/BotFiles/3594/skm.Ryubot_1.0.jar<br /> skm.PateranBotlock2 1.0,http://www.robocoderepository.com/BotFiles/3591/skm.PateranBotlock2_1.0.jar<br /> sL300.Mozart life,http://www.robocoderepository.com/BotFiles/1992/sL300.Mozart_life.jar<br /> sm.Devil 7.3,http://www.robocoderepository.com/BotFiles/1481/sm.Devil_7.3.jar<br /> sng.arco.Arco 0.0,http://www.robocoderepository.com/BotFiles/3279/sng.arco.Arco_0.0.jar<br /> sos.SOS 1.0,http://www.robocoderepository.com/BotFiles/3489/sos.SOS_1.0.jar<br /> spinnercat.CopyKat 1.2.3,http://www.robocoderepository.com/BotFiles/3818/spinnercat.CopyKat_1.2.3.jar<br /> spinnercat.Limit .01,http://www.robocoderepository.com/BotFiles/3659/spinnercat.Limit_.01.jar<br /> spinnercat.Kitten 1.6,http://www.robocoderepository.com/BotFiles/3819/spinnercat.Kitten_1.6.jar<br /> spinnercat.haiku.Refrigerator 1.1,http://www.robocoderepository.com/BotFiles/3688/spinnercat.haiku.Refrigerator_1.1.jar<br /> spinnercat.mega.Tardis 1.2,http://www.robocoderepository.com/BotFiles/3692/spinnercat.mega.Tardis_1.2.jar<br /> spinnercat.Robovirus 2.718,http://www.robocoderepository.com/BotFiles/3657/spinnercat.Robovirus_2.718.jar<br /> sqTank.waveSurfing.LionWWSVMvoid 0.01,http://www.robocoderepository.com/BotFiles/3436/sqTank.waveSurfing.LionWWSVMvoid_0.01.jar<br /> starpkg.StarViewerZ 1.26,http://www.robocoderepository.com/BotFiles/1931/starpkg.StarViewerZ_1.26.jar<br /> staticline.Whiskey 0.5.3,http://www.robocoderepository.com/BotFiles/3972/staticline.Whiskey_0.5.3.jar<br /> staticline.whiskey.Whiskey 0.6,http://rednaxela-robocode.dyndns.org/data/robot_archive/staticline.whiskey.Whiskey_0.6.jar<br /> stefw.Tigger 0.0.23,http://darkcanuck.net/rumble/robots/stefw.Tigger_0.0.23.jar<br /> stelo.Chord 1.0,http://darkcanuck.net/rumble/robots/stelo.Chord_1.0.jar<br /> stelo.FretNano 1.1,http://darkcanuck.net/rumble/robots/stelo.FretNano_1.1.jar<br /> stelo.Lifestealer 1.0,http://darkcanuck.net/rumble/robots/stelo.Lifestealer_1.0.jar<br /> stelo.MatchupMini 1.1,http://darkcanuck.net/rumble/robots/stelo.MatchupMini_1.1.jar<br /> stelo.MatchupMicro 1.2,http://darkcanuck.net/rumble/robots/stelo.MatchupMicro_1.2.jar<br /> stelo.MatchupAGF 1.1,http://darkcanuck.net/rumble/robots/stelo.MatchupAGF_1.1.jar<br /> stelo.MatchupWS 1.2c,http://darkcanuck.net/rumble/robots/stelo.MatchupWS_1.2c.jar<br /> stelo.Mirror 1.1,http://www.robocoderepository.com/BotFiles/3034/stelo.Mirror_1.1.jar<br /> stelo.MirrorMicro 1.1,http://darkcanuck.net/rumble/robots/stelo.MirrorMicro_1.1.jar<br /> stelo.MirrorNano 1.4,http://darkcanuck.net/rumble/robots/stelo.MirrorNano_1.4.jar<br /> stelo.MoojukNano 1.2,http://darkcanuck.net/rumble/robots/stelo.MoojukNano_1.2.jar<br /> stelo.PastFuture 2.1.9,http://www.robocoderepository.com/BotFiles/3910/stelo.PastFuture_2.1.9.jar<br /> stelo.PatternRobot 1.0,http://www.robocoderepository.com/BotFiles/2995/stelo.PatternRobot_1.0.jar<br /> stelo.PianistNano 1.3,http://darkcanuck.net/rumble/robots/stelo.PianistNano_1.3.jar<br /> stelo.RamTrackSurfer 1.2,http://darkcanuck.net/rumble/robots/stelo.RamTrackSurfer_1.2.jar<br /> stelo.Randomness 1.1,http://www.robocoderepository.com/BotFiles/3021/stelo.Randomness_1.1.jar<br /> stelo.Spread 0.2,http://www.robocoderepository.com/BotFiles/3922/stelo.Spread_0.2.jar<br /> stelo.SteloTestNano 1.0,http://darkcanuck.net/rumble/robots/stelo.SteloTestNano_1.0.jar<br /> stelo.UnfoolableNano 1.0,http://darkcanuck.net/rumble/robots/stelo.UnfoolableNano_1.0.jar<br /> stelo.UntouchableNano 1.4,http://darkcanuck.net/rumble/robots/stelo.UntouchableNano_1.4.jar<br /> step.nanoPri 1.0,http://www.robocoderepository.com/BotFiles/2996/step.nanoPri_1.0.jar<br /> step.NanoBidu 1.0,http://www.robocoderepository.com/BotFiles/3014/step.NanoBidu_1.0.jar<br /> stf.PanzerGeneral 0.1,http://www.robocoderepository.com/BotFiles/2233/stf.PanzerGeneral_0.1.jar<br /> stordy.StordyBot 1.0,http://sites.google.com/site/stordyrobo/Home/stordy.StordyBot_1.0.jar<br /> strider.Festis 1.2.1,http://www.robocoderepository.com/BotFiles/2355/strider.Festis_1.2.1.jar<br /> strider.Mer 1.1.0,http://www.robocoderepository.com/BotFiles/2360/strider.Mer_1.1.0.jar<br /> stuff.Vlad 0.1,http://www.robocoderepository.com/BotFiles/3701/stuff.Vlad_0.1.jar<br /> sul.NanoR2 1.32,http://www.robocoderepository.com/BotFiles/3348/sul.NanoR2_1.32.jar<br /> sul.Pinkbot 1.1,http://www.robocoderepository.com/BotFiles/3346/sul.Pinkbot_1.1.jar<br /> sul.Bicephal 1.2,http://www.robocoderepository.com/BotFiles/3343/sul.Bicephal_1.2.jar<br /> sul.BlueBot 1.0,http://www.robocoderepository.com/BotFiles/3347/sul.BlueBot_1.0.jar<br /> SuperSample.SuperCrazy 1.0,http://file.csdgn.org/robocode/SuperSample.SuperCrazy_1.0.jar<br /> syl.Centipede 0.5,http://www.robocoderepository.com/BotFiles/1254/syl.Centipede_0.5.jar<br /> synapse.Geomancy 15,http://sites.google.com/site/synapsebots/home/synapse.Geomancy_15.jar?attredirects=0<br /> synapse.rsim.GeomancyBS 0.11,http://robocoderepository.com/BotFiles/3758/synapse.rsim.GeomancyBS_0.11.jar<br /> synnalagma.NeuralPremier 0.51,http://www.robocoderepository.com/BotFiles/1557/synnalagma.NeuralPremier_0.51.jar<br /> synnalagma.test.MiniNeural 1.1,http://www.robocoderepository.com/BotFiles/1754/synnalagma.test.MiniNeural_1.1.jar<br /> tad.Dalek98 0.98,http://darkcanuck.net/rumble/robots/tad.Dalek98_0.98.jar<br /> takeBot.SpinSpiral 1.2,http://www.robocoderepository.com/BotFiles/312/takeBot.SpinSpiral_1.2.jar<br /> takeBot.SpiralCrash 1.0,http://www.robocoderepository.com/BotFiles/1013/takeBot.SpiralCrash_1.0.jar<br /> takeBot.WeavingWiggle 1.1,http://www.robocoderepository.com/BotFiles/1012/takeBot.WeavingWiggle_1.1.jar<br /> tango.Recrimpo 2.51,http://www.robocoderepository.com/BotFiles/2015/tango.Recrimpo_2.51.jar<br /> taqho.taqbot 1.0,http://www.robocoderepository.com/BotFiles/1316/taqho.taqbot_1.0.jar<br /> tcf.Drifter 29,http://www.7sun.com/robocode/robots/tcf.Drifter_29.jar<br /> tcf.Repat3 2,http://www.robocoderepository.com/BotFiles/3328/tcf.Repat3_2.jar<br /> techdude.kombat.FlamingKombat 1.5,http://www.robocoderepository.com/BotFiles/2810/techdude.kombat.FlamingKombat_1.5.jar<br /> techdude.Class2C.Class2C 0.1,http://www.robocoderepository.com/BotFiles/3078/techdude.Class2C.Class2C_0.1.jar<br /> test.Podgy 4.0,http://www.robocoderepository.com/BotFiles/3214/test.Podgy_4.0.jar<br /> test.Fuzzer 1.0.1,http://www.robocoderepository.com/BotFiles/3345/test.Fuzzer_1.0.1.jar<br /> testantiswapgun.AntiSwap 1.0,http://www.robocode.ilbello.com/asd.AntiSwap_1.0.jar<br /> throxbot.ThroxBot 0.1,http://www.robocoderepository.com/BotFiles/2548/throxbot.ThroxBot_0.1.jar<br /> tide.pear.Pear 0.62.1,http://www.robocoderepository.com/BotFiles/2393/tide.pear.Pear_0.62.1.jar<br /> timmit.micro.TimXJ 0.22,http://www.robocoderepository.com/BotFiles/1683/timmit.micro.TimXJ_0.22.jar<br /> timmit.mini.TimVA 0.43,http://www.robocoderepository.com/BotFiles/1681/timmit.mini.TimVA_0.43.jar<br /> timmit.nano.TimCat 0.13,http://www.robocoderepository.com/BotFiles/1600/timmit.nano.TimCat_0.13.jar<br /> timmit.nano.TimDog 0.33,http://www.robocoderepository.com/BotFiles/1602/timmit.nano.TimDog_0.33.jar<br /> timmit.TimmiT 0.22,http://www.robocoderepository.com/BotFiles/1468/timmit.TimmiT_0.22.jar<br /> TJ.Exupery 1.39,http://www.robocoderepository.com/BotFiles/3970/TJ.Exupery1.39.jar<br /> tjk.deBroglie 0.66,http://robocoderepository.com/BotFiles/3989/tjk.deBroglie_0.66.jar<br /> tlp.ThreeLeggedPig 1,http://pages.prodigy.net/franz1/house/tlp.ThreeLeggedPig_1.jar<br /> tm.Yuugao 1.0,http://www.robocoderepository.com/BotFiles/1056/tm.Yuugao_1.0.jar<br /> tobe.calypso.Calypso 4.1,http://www.robocoderepository.com/BotFiles/784/tobe.calypso.Calypso_4.1.jar<br /> tobe.Fusion 1.0,http://www.robocoderepository.com/BotFiles/649/tobe.Fusion_1.0.jar<br /> tobe.mini.Charon 0.9,http://www.robocoderepository.com/BotFiles/836/tobe.mini.Charon_0.9.jar<br /> tobe.Relativity 3.9,http://www.robocoderepository.com/BotFiles/360/tobe.Relativity_3.9.jar<br /> tobe.Saturn lambda,http://www.robocoderepository.com/BotFiles/685/tobe.Saturn_lambda.jar<br /> tornyil.bottomup.BottomUp 1.05,http://www.alpha-consulting.hu/robo/tornyil.bottomup.BottomUp_1.05.jar<br /> tornyil.Lajcsi2.Lajcsi2sm 1.0,http://www.alpha-consulting.hu/robo/tornyil.Lajcsi2.Lajcsi2sm_1.0.jar<br /> toz.Gnome 1.1,http://darkcanuck.net/rumble/robots/toz.Gnome_1.1.jar<br /> trab.Crusader 0.1.7,http://www.stud.ntnu.no/~grashei/bots/trab.Crusader_0.1.7.jar<br /> trab.nano.AinippeNano 1.3,http://www.stud.ntnu.no/~grashei/bots/trab.nano.AinippeNano_1.3.jar<br /> tw.Exterminator 1.0,http://www.robocoderepository.com/BotFiles/3607/tw.Exterminator_1.0.jar<br /> tzu.TheArtOfWar 1.2,http://darkcanuck.net/rumble/robots/tzu.TheArtOfWar_1.2.jar<br /> uccc.Dorito 1.12,http://www.devfluid.com/csc_w/images/e/e9/Uccc.Dorito_1.12.jar<br /> uccc.MilkyWay 1.01,http://www.devfluid.com/csc_w/images/a/a6/Uccc.MilkyWay_1.01.jar<br /> uccc.RingDing 1.12,http://www.devfluid.com/csc_w/images/5/5f/Uccc.RingDing_1.12.jar<br /> uccc.Scrapple 1.0,http://www.devfluid.com/csc_w/images/7/7a/Uccc.Scrapple_1.0.jar<br /> urdos.URDOS 1.3,http://darkcanuck.net/rumble/robots/urdos.URDOS_1.3.jar<br /> usa.nano.Nemo 2.0,http://www.robocoderepository.com/BotFiles/2045/usa.nano.Nemo_2.0.jar<br /> vic.Locke 0.7.5.5,http://www.robocoderepository.com/BotFiles/2115/vic.Locke_0.7.5.5.jar<br /> vft.Valkyrie 1.0,http://www.robocoderepository.com/BotFiles/3009/vft.Valkyrie_1.0.jar<br /> vft.Hrist 1.0,http://darkcanuck.net/rumble/robots/vft.Hrist_1.0.jar<br /> vjik.UnViolation 1.1,http://www.robocoderepository.com/BotFiles/3886/vjik.UnViolation_1.1.jar<br /> voidious.Diamond 1.5.38b,http://www.dijitari.com/void/robocode/voidious.Diamond_1.5.38b.jar<br /> voidious.Dookious 1.573c,http://www.dijitari.com/void/robocode/voidious.Dookious_1.573c.jar<br /> voidious.micro.Jen 1.11,http://www.dijitari.com/void/robocode/voidious.micro.Jen_1.11.jar<br /> voidious.mini.Komarious 1.88,http://www.dijitari.com/void/robocode/voidious.mini.Komarious_1.88.jar<br /> vuen.Fractal 0.55,http://www.robocoderepository.com/BotFiles/1579/vuen.Fractal_0.55.jar<br /> wcsv.Engineer.Engineer 0.5.4,http://darkcanuck.net/rumble/robots/wcsv.Engineer.Engineer_0.5.4.jar<br /> wcsv.PowerHouse.PowerHouse 1.7e3,http://darkcanuck.net/rumble/robots/wcsv.PowerHouse.PowerHouse_1.7e3.jar<br /> wcsv.mega.PowerHouse2 0.2,http://darkcanuck.net/rumble/robots/wcsv.mega.PowerHouse2_0.2.jar<br /> wcsv.Stampede 1.3.3,http://www.robocoderepository.com/BotFiles/2527/wcsv.Stampede_1.3.3.jar<br /> wcsv.Stampede2.Stampede2 1.1.0,http://www.robocoderepository.com/BotFiles/2714/wcsv.Stampede2.Stampede2_1.1.0.jar<br /> WdV.Lesserbee 0.01,http://www.robocoderepository.com/BotFiles/4046/WdV.Lesserbee_0.01.jar<br /> whind.Constitution 0.7.1,http://www.robocoderepository.com/BotFiles/2812/whind.Constitution_0.7.1.jar<br /> whind.Strength 0.6.4,http://whindgames.50webs.com/otherstuff/whind.Strength_0.6.4.jar<br /> whind.StrengthBee 0.6.4,http://whindgames.50webs.com/otherstuff/whind.StrengthBee_0.6.4.jar<br /> whind.Wisdom 0.5.1,http://www.robocoderepository.com/BotFiles/2742/whind.Wisdom_0.5.1.jar<br /> wiki.BasicGFSurfer 1.02,http://www.dijitari.com/void/robocode/wiki.BasicGFSurfer_1.02.jar<br /> wiki.mako.MakoHT 1.2.2.1,http://www.robocoderepository.com/BotFiles/1374/wiki.mako.MakoHT_1.2.2.1.jar<br /> wiki.mini.BlackDestroyer 0.9.0,http://www.robocoderepository.com/BotFiles/1927/wiki.mini.BlackDestroyer_0.9.0.jar<br /> wiki.mini.GouldingiHT 1.0,http://www.robocoderepository.com/BotFiles/1383/wiki.mini.GouldingiHT_1.0.jar<br /> wiki.mini.Griffon 0.1,http://www.robocoderepository.com/BotFiles/1774/wiki.mini.Griffon_0.1.jar<br /> wiki.mini.Sedan 1.0,http://www.robocoderepository.com/BotFiles/1676/wiki.mini.Sedan_1.0.jar<br /> wiki.nano.DevilFISH 1.0,http://www.robocoderepository.com/BotFiles/2235/wiki.nano.DevilFISH_1.0.jar<br /> wiki.nano.RaikoNano 1.1,http://www.robocoderepository.com/BotFiles/2163/wiki.nano.RaikoNano_1.1.jar<br /> wiki.WaveRammer 1.0,http://www.robocoderepository.com/BotFiles/3505/wiki.WaveRammer_1.0.jar<br /> wiki.Wolverine 2.1,http://darkcanuck.net/rumble/robots/wiki.Wolverine_2.1.jar<br /> wilson.Chameleon 0.91,http://www.robocoderepository.com/BotFiles/1608/wilson.Chameleon_0.91.jar<br /> winamp32.micro.MicroMacro 1.0,http://www.robocoderepository.com/BotFiles/2891/winamp32.micro.MicroMacro_1.0.jar<br /> wit.Chuliath 1.0,http://www.robocoderepository.com/BotFiles/2306/wit.Chuliath_1.0.jar<br /> wit.Deep7 2.0,http://www.robocoderepository.com/BotFiles/2313/wit.Deep7_2.0.jar<br /> xandercat.XanderCat 2.1,http://www.distantvisions.net/robocode/xandercat.XanderCat-2.1.jar<br /> xandercat.XanderCat 3.0,http://www.distantvisions.net/robocode/xandercat.XanderCat-3.0.jar<br /> xiongan.Xiongan 1.1,http://www.robocoderepository.com/BotFiles/3565/xiongan.Xiongan_1.1.jar<br /> yarghard.Y101 1.0,http://sliwa.ws/RoboCode/yarghard.Y101_1.0.jar<br /> yk.JahMicro 1.0,http://www.robocoderepository.com/BotFiles/3033/yk.JahMicro_1.0.jar<br /> yk.JahRoslav 1.1,http://www.robocoderepository.com/BotFiles/3032/yk.JahRoslav_1.1.jar<br /> zen.Lindada 0.2,http://www.robocoderepository.com/BotFiles/1679/zen.Lindada_0.2.jar<br /> zeze2.OperatorZeze 1.05,http://www.robocoderepository.com/BotFiles/3330/zeze2.OperatorZeze_1.05.jar<br /> zch.David 0.21,http://www.robocoderepository.com/BotFiles/3575/zch.David_0.21.jar<br /> zch.Hirkan 0.11,http://www.robocoderepository.com/BotFiles/1288/zch.Hirkan_0.11.jar<br /> zh.UnderDog 0.0.2,http://www.robocoderepository.com/BotFiles/3053/zh.UnderDog_0.0.2.jar<br /> zyx.mega.YersiniaPestis 3.0,http://darkcanuck.net/rumble/robots/zyx.mega.YersiniaPestis_3.0.jar<br /> zyx.micro.Ant 1.1,http://www.robocoderepository.com/BotFiles/3481/zyx.micro.Ant_1.1.jar<br /> zyx.nano.Ant 1.1,http://www.robocoderepository.com/BotFiles/3493/zyx.nano.Ant_1.1.jar<br /> zyx.nano.EscherichiaColi 1.0,http://darkcanuck.net/rumble/robots/zyx.nano.EscherichiaColi_1.0.jar<br /> zyx.nano.RedBull 1.0,http://darkcanuck.net/rumble/robots/zyx.nano.RedBull_1.0.jar<br /> &lt;/pre&gt;<br /> ----<br /> '''''No chatting on this page. Use the /ParticipantsChat page for that.'''''<br /> <br /> '''''Removed because the jarcontent/filename is not correct'''''&lt;br&gt;<br /> ''cberendt.Bot1 0.160''&lt;br&gt;<br /> ''dmsr.MiniR101 0.6''&lt;br&gt;<br /> ''henriquevilela.TieFighter 0.1,3224''&lt;br&gt;<br /> ''jgap.Aspirant_7980_gen7 1.0,3552''br&gt;<br /> ''jgap.Aspirant_13029_gen7 1.0,3553''&lt;br&gt;<br /> ''techdude.Carruthers 1.2.6''&lt;br&gt;<br /> ''uccc.Orbiter 1.0''&lt;br&gt;<br /> ''WhoAmI.WhoAmI 1.00''&lt;br&gt;<br /> <br /> '''''Removed until file corruption is resolved:'''''<br /> <br /> ''cas.CelsoKiller 1.0,3465''<br /> <br /> '''''Removed due to almost always giving '0' scores:'''''<br /> <br /> ''com.syncleus.robocode.Dreadnaught 0.1,3426''&lt;br&gt;<br /> ''lazarecki.PinkerStinker 0.1,http://www.robocoderepository.com/BotFiles/3824/lazarecki.PinkerStinker_0.1.jar''<br /> <br /> '''''Removed because it's incorrectly packaged:'''''<br /> <br /> ''Indesh.Indesh 1.1,http://jakobserlier.250free.com/Indesh.jar''<br /> <br /> <br /> ----<br /> <br /> '''''Removed due to WontFix issues in Robocode 1.7+:'''''&lt;br&gt;<br /> ''* Hviela: ([[http://sourceforge.net/tracker/?func=detail&amp;aid=2953268&amp;group_id=37202&amp;atid=419486 SF #2953268]])''&lt;br&gt;<br /> '': hvilela.HVilela 0.9.3,http://henrique.vilela.googlepages.com/hvilela.HVilela_0.9.3.jar''&lt;br&gt;<br /> ''* Barney (Tries to write files without using RobocodeOutputStream. Robocode 1.7 punishes for that more harshly which will give 0 scores)&lt;br&gt;<br /> '': Homer.Barney 1.0,http://www.robocoderepository.com/BotFiles/1932/Homer.Barney_1.0.jar&lt;br&gt;</div>

Miked0801 http://robowiki.net/w/index.php?title=Talk:LittleBlackBook&diff=19393 2011-05-31T06:03:53Z

<p>Miked0801: </p> <hr /> <div>== Congrats! ==<br /> <br /> Congrats! It's nice to see some movement in the nano scene lately. I was pondering predefined data bots myself actually. I'm curious though, you say &quot;Any perfect dodge stop and go will kill it&quot;, which seems odd to me. It should be quite trivial for a distance/lateral segmented GF gun to hit that I'd think... --[[User:Rednaxela|Rednaxela]] 01:51, 15 June 2009 (UTC)<br /> : Math.signum() off e.velocity screws up 0 velocity checks and I have no velocity averaging. I'll check other bots for inspiration though. Has to be TINY though<br /> : What about... &lt;code&gt;static double foo = 1; foo = e.velocity + 0.01*foo; foo /= foo;&lt;/code&gt;? Not sure if that would be small enough, and I haven't checked it's codesize, but I think it's smaller than any others ways to handle that which come to my mind. I think it's smaller than &lt;code&gt;static double foo = 1; foo = (e.velocity == 0) ? foo : Math.signum(e.velocity);&lt;/code&gt; anyway, since conditionals and function calls are expensive if I remember right. I'd also suggest seeing if you can get rid of the need to normalize the value to 1/-1 all together, but that may not be possible in this case. --[[User:Rednaxela|Rednaxela]] 04:15, 15 June 2009 (UTC)<br /> :: Anything having to do with statics are expensive. Your above code is probably around 25 bytes or so. Math.signum(e.getVelocity()) is 6 or so. I can easily fix my problem by adding +1 to the e.getVelocity() check on the inside of the gun( for 2 bytes)... But! It will only hit perfect stop/go 50% of the time as it is setup to use the velocity to know how far to lead. Also, bots like FretNano who have good guns, but get stuck on walls randomly, would then be unhittable. I get 1 lead value per distance segment at the moment. I've got a few ideas on how to improve this, though it will double+ the size of my string table. I will adhere to the 200k max limit and with 1000 or so bots to profile, I have to be careful on size. --[[User:Miked0801|Miked0801]] 13:38, 15 June 2009 (UTC)<br /> <br /> Hi! Awesome results! Now that I looked at the code, I think there is one little problem with the overall concept: every time a new robot or a new version of a robot appears, you have to update the stats in your bot. --[[User:Robar|HUNRobar]] 10:31, 15 June 2009 (UTC)<br /> : And a decent problem it is. I'm going to review the string libraries today to see if I can find a &quot;closest to this name&quot; type function for my search. That'll at least handle versioning. The version in there right now is using default behavior against [[Pugio]] because my table is setup for 1.40. When all your other versions get cleared from the rumble, my rating will go up another .5 or so. --[[User:Miked0801|Miked0801]] 13:38, 15 June 2009 (UTC)<br /> :: &lt;code&gt;HashMap&lt;String, String&gt; enemyGF; enemyGF.get(e.getName().split(&quot; &quot;)[0]);&lt;/code&gt; =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 14:03, 15 June 2009 (UTC)<br /> ::: Um, wow. That does work: e.getName().split(&quot; &quot;)[0]. I rediscovered it myself and you had it here the whole time. I feel very stupid. Thanks for the advice! --[[User:Miked0801|Miked0801]] 06:13, 23 June 2009 (UTC)<br /> :::: No problem at all. =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 11:05, 23 June 2009 (UTC)<br /> <br /> Nice! I may re-release [[Ocnirp]] 1.0 to screw your stats =) Updated Wikipedia page for you now. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 12:00, 15 June 2009 (UTC)<br /> : Don't bother, I'm already using default values against that bot so it wouldn't make any difference so Nyaa Nyaa! :) --[[User:Miked0801|Miked0801]] 13:48, 15 June 2009 (UTC)<br /> :: Really? I don't think so. (default is 50-40-30-20-10-0, right?). Beside, I'm working on Nano adaptive movement (Mysterious is its fail attempt) =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 14:03, 15 June 2009 (UTC)<br /> ::: Ok, you win. There are quite a few bots taht got default cases though. For some reason I thought Ocnrip was one. And, yeah, nice string match there. I could fit that if, oh I don't know, I took out all my movement code ;) --[[User:Miked0801|Miked0801]] 14:20, 15 June 2009 (UTC)<br /> :::: That doesn't call fit, really. :P &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 14:53, 15 June 2009 (UTC)<br /> <br /> Thanks! Links and work email address removed. --[[User:Miked0801|Miked0801]] 15:27, 15 June 2009 (UTC)<br /> <br /> : He he, the revision system still have it. =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 15:32, 15 June 2009 (UTC)<br /> :: Yep - but at least basic spider bots won't pick it up and spam be about male enhancement products :) --[[User:Miked0801|Miked0801]]<br /> <br /> Ok, new version in the wild. I expect this release to be better against stronger bots, but I also expect some startlingly poor results against a few bots. These I can tune back to either the old values or a combo of new and old. Stelo.MirrorNano being an example. My next release will beat this bot 90/10, but now LBB is losing 45/55. No panic :) --[[User:Miked0801|Miked0801]] 02:04, 18 June 2009 (UTC)<br /> : Good result. My next update tomorrow is going to absolutely destroy the competition. This is going to be a 1900+ rating bot. --[[User:Miked0801|Miked0801]] 05:45, 18 June 2009 (UTC)<br /> <br /> == Bot Blog ==<br /> Seems like a decent place for random ramblings. The averaging code is doing its job, it just needs some table number TLC. Alas, it also screwed with some other scores that will need attention. I also commited a cut and paste errored with nat's SNG 1.0b bot resulting in a 6% score. Lame. I may try taking the averaging back out and using firepower control instead. It'd probably help me more overall to fire at 3.0 firepower at range 80 or 120 and closer against everyone. The Micro scores have been decent thus far with their first autogeneration pass. 19th is a good starting point and I know I can get to 15th or even 10th with some work there. I'll drop the mini scores in Tuesday or so and for another overall ranking boost. I still believe I can get this bot to a 2k points score with over 80%APS in nanos with a few revisits to lagging numbers.<br /> <br /> Wow, a good day. Found another 10 bytes by just re-arranging the stack vars. Used that space to try out variable move distances. Helps quite a bit against the weakest bots. Also fixed bugs with a few bots that came from typos. Finally, I fixed poorer results against rambots wehre I wasn't aiming right at range 40 and in. My scores are now approaching [[DrussGT]]'s against the low-end bots. Using that bot's scores gives me a reasonable target to short for. I'm also going to experiment with variable firepower as well, though for some reason I keep pushing back on that - dunno. Next release tomorrow night. Shooting for APS of 78ish in nanos. That would put me close to my goal of a 2k score. Hopefully, my micro score will get me top 15 there as well. I'll start running Minis by end of week to see if I can get top 25 there and perhaps top 100 overall (aiming real high, I know.) --[[User:Miked0801|Miked0801]] 03:38, 23 June 2009 (UTC)<br /> <br /> : You should to remember the [[Code Size/Cheat sheet|Code Size/Cheat sheet]]. The most important part is the vars-on-register, which is discover by Simonton I think. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 11:02, 23 June 2009 (UTC)<br /> :: I just rearrange them all until I get the smallest result :)<br /> <br /> Another good day, but I found a dumb bug I introduced to my table generation a few days ago which will require me to revisit all the nano values. Sigh. Good news though, found another 8 bytes or so by declaring the string table final (never changes so I should have done it ages ago) and by rearranging a few typecasts to make sure we got int on int math wherever possible. That means I now have both distance and firepower control in the table! It hurts by aim a touch from 80 pixels and in, but for 1 more free byte I could fix this. I'll keep looking. 8 more bytes and I get variable string matching, though if firepower or move control prove poor, I can always swap this in for the other. Because I have to do a table revisit, I'm pushing my release back one more day. Who'd have though a variable GF, variable firepower, variable move distance, variable turn control bot could be done through a silly string table. It's like the synthesis of all the best nanos in one place. Next release will have some bugs, but the one following will be absolutely epic. --[[User:Miked0801|Miked0801]] 18:48, 23 June 2009 (UTC)<br /> <br /> Bleh. Had to work late a few nights. I'm just now getting all my initial micro/nano runs complete. Good news is that only [[Moebius]] is currently able to consistantly beat me now in nanos. I'm going to experiment with distance control next as many bots are optimized for certain ranges and I expect I will do well at varying ranges against many bots. If it works well, I'll trade something off to get it. We'll see about a tomorrow release, work allowing. --[[User:Miked0801|Miked0801]] 07:39, 25 June 2009 (UTC)<br /> <br /> Played around with enemy distancing and found it helps (much) more than firepower control. But, my test cycle is too far along to scrap and start again so I'll go ahead with what I have. Besides, I believe I found a way to fit all 5 factors into this nano anyways - Fire Power, Chance to reverse direction, Min Distance to move, desired distance from enemy, and Guess Factors. It requires my tables to be created differently (again), but I'll go for that next version. This is why I haven't bothered with minis or megas yet - the tables flux dramatically with each version. It also means yet another multiplier when creating my tables. I'm already running 20+ versions per bot through roboresearch. Adding distance is another x4 or so. Yikes. Back to 1 good test run and cull, cull, cull so that I have time to balance what makes sense. At least my testing methods are improving so that this doesn't take too long. Just need 1 more set up data to finish up for the guess factors and then we'll put this bot back together again. --[[User:Miked0801|Miked0801]] 07:29, 26 June 2009 (UTC)<br /> <br /> Ok, version is up and we gained nearly another 2% APS in nanos and even more in Micros. Nice. There's still a few bots that came out a bit half baked, even with all the care I put into the tables before releasing. I'll revisit those for one last version 1.5x release and then go onto version 1.6x with distance control. Still shooting for 80+% APS, a perfect PL score in nanos, and 2k in ratings. 72 Glicko's to go. --[[User:Miked0801|Miked0801]] 02:59, 27 June 2009 (UTC)<br /> <br /> Hey, you've taken my micro's place in the microrumble! I really should do something right after I finished my flash game. ;) --[[User:Robar|HUNRobar]] 17:31, 27 June 2009 (UTC)<br /> <br /> Dang it. Screwed up robar.nano.Scytodes 0.3's table, which costed me 50-60 battle points and .33 APS in the Nano Rumble (.15 in micro). Savant values are weaker too, but that can be attributed a little to random luck. Beyond that, a very good update. Solidly in 11th now in Micros and 1.5% APS from 80 in nanos. That's only 260 battle % points and 50 of those are from my above mistake. But, without distance control, I'm running out of big gains. I can probably push this bot to 80% APS and 2k Glicko without distance, but it will take a lot of work. I made a lot of gain my swapping appropriate bots to 2.0 fire power. Some of those I can switch back to get some ground I lost between 1.52 and 1.53. I did tie for the PL score this time and would have had it if not for Scytodes. Next version I'll get it right. I think I'll release a 1.54 just to try for 10th/9th in the micros without distance help. --[[User:Miked0801|Miked0801]] 03:46, 29 June 2009 (UTC)<br /> <br /> Well fixed Scytodes and decided to alphabetize my list and lo and behold I had missed 4 other bots - all micros. Adding those gave a decent score increase for them as well and would probably challenge Jen for 10th. But, I went ahead and started the HUGE roboresearch database needed for my next release. We're talking around 1 Million battles to be run before all is ready. I'm guessing my computer running 24/7 will get through this info in around 3 days. Wow. The good news is that my previous run is compatible so I saved 150k battles or so. All this will put me over 80APS in Nanos and will put me well into top 10 in micros. I'll know for sure once I start seeing some comparison results against the micros. The top nanos appear to be weak against different ranges, but I'm not sure on Micros yet. I'll post tomorrow with some initial results. --[[User:Miked0801|Miked0801]] 21:30, 30 June 2009 (UTC)<br /> <br /> Test run about 15% complete. I'm tuning back to breadth of the first run to speed it up so I can play before next week. --[[User:Miked0801|Miked0801]] 02:18, 2 July 2009 (UTC)<br /> <br /> 33% done and I'm not patient enough to wait for it to go much further so I put together the next version - and had another awesome idea on how to make it do more for less. I now have distance control and! - all other factors also are available based on distance as well. This means variable firewpower on distance. This means I can change my move mode out of oscillation at those distances where I run into head-on shots (around 280 or so). I can even change my desired distance based on distance meaning I can ping-pong between values to help with multi-mode movers and to throw off pattern bots. That plus partial string matches and I'm sitting at exactly 249. That's enough tech for my goals. Now it's time to do my last pass through the nano/micros and see just how much pwnage will be wrought. 85+ nano APS isn't out of reach.<br /> <br /> Work, work work. My job is heating up to the point where things have been on hold for a bit. This will continue for a few more days - grr. --[[User:Miked0801|Miked0801]] 17:39, 8 July 2009 (UTC)<br /> <br /> And even more work. I'm in crunch mode now and barely have time for breathing. I've still got my next bot upgrade ready, jsut need to find a couple uninterrupted hours to fix a few minor things. I'm still alive guys :) --[[User:Miked0801|Miked0801]] 20:44, 27 August 2009 (UTC)<br /> <br /> Good to hear =) I'm also pretty snowed under, but it seems that when that happens Robocode becomes my outlet =) --[[User:Skilgannon|Skilgannon]] 20:55, 27 August 2009 (UTC)<br /> <br /> Project starting to wrap up - we'll see if life returns to normal soon... --[[User:Miked0801|Miked0801]] 16:30, 6 October 2009 (UTC)<br /> <br /> Project's done! Vacation is started. Updates to follow :) --[[User:Miked0801|Miked0801]] 16:28, 6 December 2009 (UTC)<br /> <br /> : Yay, welcome back! =) --[[User:Voidious|Voidious]] 17:18, 6 December 2009 (UTC)<br /> <br /> Ok, Nanos mostly refit. I want to find another 1.5% of APS then its back to micros. Mostly hand tuning at this point. --[[User:Miked0801|Miked0801]] 22:46, 17 December 2009 (UTC)<br /> <br /> Actually changed a little base code with this version. I removed the adjustTurnForGun() call and replaced it with a bit of randomness added to the range index. This results in slightly more random ranges when firing. It makes it easier to hit multi-modes, bullet catchers, and wave surfers, but hurts my score against really, really weak bots and the best nanos a bit. Still, seems like a decent upgrade. Broke 2 nano bot solutions with this chagne that I can easily retrofit back to pwnage. I will also be able to make a further micro pass to get above Jen on my next update. I beginning to believe that this might get top 5ish in micro before I'm done. --[[User:Miked0801|Miked0801]] 00:07, 9 January 2010 (UTC)<br /> <br /> FYI, this bot needs to be compiled with Sun's Java Compiler in order for it to remain byte size complient. Got bit with that today. Made a major pass through the tables using the top Mega bot's scores in comparison to mine for inspiration on who to fix. Found many, many bots that were improved 10% APS or more. This should be the version, barring bugs, that hits 80%APS or even 81% APS in nanos - and should also hit 2k Glicko. And there's still a bit (not much!) more tuning that can be done. There are countless ways of ordering my tables to get 1-5% individual APS tweaks that I probably need a seperate program to find. Overall, this has ben a wonderful experiment and mega contenders should take note. I'll continue to tune it a touch more, but I'm also going to investiage Lateral Velocity segmentation as well. If I get inspired, it may not cost too much :) --[[User:Miked0801|Miked0801]] 23:07, 13 January 2010 (UTC)<br /> <br /> Results looking very nice so far, though not sure if it'll quite end up getting past 2k Glicko. What I find most impressive is how you fit so many movement modes alongside a GF gun, in a nano, that's an awful lot of movement modes for a nano, particularly with the distance-based selection of them! :) --[[User:Rednaxela|Rednaxela]] 03:50, 14 January 2010 (UTC)<br /> : Thank you! I'm a rather proud parent of this bot and all comments make me grin :) --[[User:Miked0801|Miked0801]] 15:49, 14 January 2010 (UTC)<br /> <br /> BTW, the build system seems to be completely confused at the moment. Would it help if I released a 1.60 version to fix it? --[[User:Miked0801|Miked0801]] 15:49, 14 January 2010 (UTC)<br /> <br /> : What do you mean by &quot;build system&quot;? --[[User:Voidious|Voidious]] 16:24, 14 January 2010 (UTC)<br /> :: Was about to ask the same, nearly got edit conflict :) --[[User:Rednaxela|Rednaxela]] 16:33, 14 January 2010 (UTC)<br /> <br /> :: At the moment, the rumble is only running LBB 1.58 (retired), not LBB 1.59. I believe it is because 1.59 lost roughly 30ish nano battles whilst retaining the micro and up battles before I fixed an issue on my local client. I could upload the missing nano battles and that may fix it, but I wanted permission to do so first as I would need to edit the results.txt file manully to add the missing numbers. --[[User:Miked0801|Miked0801]] 17:42, 14 January 2010 (UTC)<br /> <br /> ::: &quot;... fixed an issue on my local client&quot;? Please don't edit results.txt or upload any old results! Best thing to do is delete all files in the roborumble/files and roborumble/temp folders and start fresh -- preferably with uploads disabled for the first run just to make sure. --[[User:Darkcanuck|Darkcanuck]] 21:27, 14 January 2010 (UTC)<br /> <br /> :::: Not what I did. I have 2 copies of Robo installed. I created 1.59 in version 1.6.1.4 and it was 256 bytes in size. oops. I then fixed the problem and recreated it in my other version of robocode, but stupidly called it the same thing. I then took this version and copied it to both builds. But, the codesize.txt never updated to the new, reduced size for the updated lbb. Therefore, it didn't record roughly 30ish nano battles. When i noticed this, I completely killed the cache, the local 1.59 file, and removed it from the codesize file so that it could recreate it. This worked, but those 30 or so nano battles were lost as has since confused the server quite a bit. Another side effect of this is that when you first run the client, it correctly runs version 1.59 of LBB, but further iterations always run the previous verion. Long story short, be careful about versioning of bots... --[[User:Miked0801|Miked0801]] 21:45, 14 January 2010 (UTC)<br /> <br /> :: This is weird... If you look at its roborumble details, 1.58 only has 3 battles: [http://darkcanuck.net/rumble/RatingsDetails?game=roborumble&amp;name=mld.LittleBlackBook%201.58]. Only 2 for mini, but lots for micro and nano. Not sure how that would happen... The server tries to run all pairings for each version (after a certain point), even if it's retired, so maybe that's what's going on. If you delete 1.58 from your rumble dir, it won't run 1.58 any more. (But anyone that has 1.58 will until it has all pairings, if that's the reason.) --[[User:Voidious|Voidious]] 18:51, 14 January 2010 (UTC)<br /> <br /> :: Wow... this is very weird... the &quot;Last Updated&quot; times for LittleBlackBook 1.58 keep going <br /> up in mega/mini (and different update times from mini/nano), but the battle count is only increasing in mini/nano! Something is broken on the server side I think.... because all clients with LBB 1.58 (like mine) are ONLY running LBB 1.58, but the Rumble isn't recording the mega/mini results so it looks like it'll go on forever... --[[User:Rednaxela|Rednaxela]] 19:46, 14 January 2010 (UTC)<br /> <br /> :: It should be fixed now. Looks like a concurrent retirement/reactivation. My guess is one client saw no battles for 1.58 in the last 4 hours and started to retire it, first for the general rumble then the mini. But then another client uploaded new battles (either due to old results not yet uploaded or an old priority file) while the retirements were in progress leading to the corrupted states. I have a permanent fix in mind, but it will require a lot of testing which I have yet to find time for... --[[User:Darkcanuck|Darkcanuck]] 21:27, 14 January 2010 (UTC)<br /> <br /> ::: Wow, 1.58 has 7963 battles in mega... yep... clients sure working away at it when things were messed up before... :) --[[User:Rednaxela|Rednaxela]] 03:55, 15 January 2010 (UTC)<br /> <br /> Today was a huge update! Managed to redo and find roughly 20ish more bytes!!! Desired distance from enemy table became approach angle table for a big savings. Found 2 bytes in the averaging code. Came up with a new way to do bullet detection that costs only a couple more bytes than my simple one from before. Added Ramming ability. Overall, this bot will be weaker as the dodging stuff was so tightly coupled into the random movement, but next version will keep the massive increases against the simpler, linear aim bots while improving the general movement. This bot could very well reach top 5 in Micros. I have also decided that my string tables will not exceed 200k as per the Rumble rules to make it fair. Right the tables are sitting at 100kish and won't get much bigger until I add the Minis some day. I am now awaiting the results to see which bots are now broken and need another revisit :) --[[User:Miked0801|Miked0801]] 01:33, 16 January 2010 (UTC)<br /> <br /> Tables, tables, tables. Fixed 30 or so bots thus far that I had weakened with the improved oscollation code. This put me above where I was at 1.59. I've got roughly 30 more bots to modify to get back to where 1.59 was against all bots. That's a good days work. Then, there's a revisit to change some bots from random movement back to oscollation for a nice boost. The new and improved energy detection code as made me weaker overall against PM bots. I'm working on a solution to this now. If I can find one, that's another 2APS overall or so and makes this a contender for the Micro crown. Then it would be on to the minis. Big talk though; gotta get there first! --[[User:Miked0801|Miked0801]] 19:15, 18 January 2010 (UTC)<br /> <br /> Reviewed the movement code a bit because it still felt heavy and figured out a way to do near perfect stop-n-go movement. Good enough to fool Smog 90/10. It requires a bit of table wrangling to do though so I'll wait for version 1.70 or so to do it. I've still got lots of bots to tweak before I add yet another movement mode for maybe 5% of my opponents. Actually, stop-n-go overlaps most of my current oscollator bots so I'll have to review which helps more. I could use my extra few bytes to improve my gun instead by increasing the random range it uses for the index a bit more. Or again, look perpendicular velocity segmentation which is still a bit out of reach. Lots of choices here. Perhaps it's time for some heavy roboresearch... --[[User:Miked0801|Miked0801]] 19:27, 20 January 2010 (UTC)<br /> <br /> Latest version I accidently bugged Fuatisha and lost 5aps on him. In addition, I removed the minor random added to the aim and lost .25 overall APS and gained back a bunch of bytes. Improved micros a ton though. Now, I'm sitting at 240 bytes and looking into its next improvement. It will cost 0 bytes to added near perfect stop'n'go, but I inherit another string table. That would give me another full overall APS though so I will probably do it. After that, it's time to look into improving aim with my extra bytes. I may finally be reaching the end of what I can do on movement alone. --[[User:Miked0801|Miked0801]] 16:32, 22 January 2010 (UTC)<br /> <br /> Added perfect stop n go with this version at the cost of 8 bytes. This, plus some TLC with some aim tables, has moved me up roughly 1 full APS in the rankings. I'm now #4 in micros and may hit #3 when things stablize - with a bugged ntc.Knowledge entry that cost me 40ish points in that battle. I also seem to have comfortably hit 2k Glicko in Nanos! Party! I'm also a hairs breath away from 2K in both rankings which would be a first. I found a new, flatter movement curve and randomized my aim a bit more on generic bots for a good overall catagory bump. The same pattern can be used to help my scores against the top micros next time around. Hopefully, no reds on the micro screen sometime in my future. Still have 4 or 5 nanos I just have a very hard time beating. I'll keep working at it though. [[Fuatisha]], you are an awesome bot. Next upload goal is 3rd in micros approaching 80 APS. We'll see if I can pull it off. --[[User:Miked0801|Miked0801]] 07:32, 27 January 2010 (UTC)<br /> <br /> Looks like 3rd in Micros is achieved. Also, this build may give me a perfect PL score in Nanos. [[Fuatisha]] is the only question mark right now. I actually found a movement pattern that confuses some of the string PM guns and gained a nice chunk off the top bots in nano land. That means next updated will be mostly concentrating on Micros to see if I can approach 81% in the Micro rumble. That will be difficult, but doable. If I get there, then I am a micro crown contendor with my silly little nano. I also have a new home computer coming online this weekend. Hopefully reobocode is 64-bit Windows 7 compatible. Should be. If so, I will have roughly 10x the computing power I have right now for roboresearch and should be able to put together a first pass on mini-bots sometime next week. If it goes smoothly, I may just setup some scripts and add all the bots just to see if I'm top 100 overall or not yet. That would be a trick. Wow this bot has come far... --[[User:Miked0801|Miked0801]] 22:51, 28 January 2010 (UTC)<br /> <br /> About 50% complete with first pass at minibot tables. I have good movement types for them all, now am porting across aim. Then, I test against distances. Then, rebuild with best distance and test. Should take another 2-3 hours. I might get to that tonight. I will also probably pass the nano/micros back through a test pass again as well, now that I have enough CPU power to do a decent pass in a couple hours as opposed to a couple of days. Next release, I will skip to 1.70 because I'll have updated roughly 20% of the tables. I have no idea where I'll land against the minis, but not top 10. Initial testing is showing just how strong the top 5 bots in that division are. --[[User:Miked0801|Miked0801]] 18:55, 2 February 2010 (UTC)<br /> <br /> Sigh - compiling with minibot data crashes the java compiler. My bot cannot get any bigger than micro with this technique. --[[User:Miked0801|Miked0801]] 05:47, 3 February 2010 (UTC)<br /> <br /> : Perhaps try a java bytecode disassembeler/assembler to hack the additional string length in? That might work to circumvent any compiler crashing unless it's a limitation inherent in the bytecode standard itself. --[[User:Rednaxela|Rednaxela]] 06:09, 3 February 2010 (UTC)<br /> <br /> Solved it! Too many character concats blowing up the compiler. How to fix? I just discovered how to put a unicode literal into a string &quot;\u008f&quot; becomes character 8f! This also has the added benefit of making many, many of my entries a much more readable single constant that I can static const final declare above. I will also be able to use a real IDE again as my current version crashes ecclipse and visual studio. Happy days for unicode literals! --[[User:Miked0801|Miked0801]] 16:20, 3 February 2010 (UTC)<br /> <br /> Learned some Java things the last few days:<br /> * \u000a, \u000c, and \u0022 (\r, \n, and &quot;), when put into a string literal, are treated as a raw symbol meaning you have to \ them or use a seperate symbol.<br /> * Non-aligned tables make for bugs that are very hard to find. Much debugging was needed to fix these bugs.<br /> * RoboResearch on broken bots doesn't help much in terms of strength judging.<br /> * The top minis are STRONG!<br /> I have 1 more day of tweaking and then an update. --[[User:Miked0801|Miked0801]] 05:26, 6 February 2010 (UTC)<br /> <br /> Chugging lots of numbers this weekend - ran roughly 100k battles over 2 days, testing ideal range from target from 100 to 380 units per opponent. The results of this tuning pass will appear as soon as I find 2 or so hours to comb through the results and adjust my range table. On average, I was getting a good 5-10% APS kick every 3rd robot or so, but I also know that with such a large update, I will accidently break a few bots as well. Still, when this pass is complete, I could be contending for micros overall. Minis - not sure where I'll land, but at least top 20. [[Fuatisha]], I may finally have a marginal (52/48) solution for, but that's too small to count on. --[[User:Miked0801|Miked0801]] 19:00, 8 February 2010 (UTC)<br /> <br /> BAH! 1.67 jar is partially corrupted so the source isn't available. Lame. It also has 10 or so bot bugs to fix. I'll get those taken care of tonight and get a new version reloaded. --[[User:Miked0801|Miked0801]] 18:16, 9 February 2010 (UTC)<br /> <br /> Just uploaded a test for initial movement vs no dodge against 0.1 bullets and yes dodge up to 3.9 power change. Also may stick to walls slightly more. I know that this helps against ram bots, but am curious if it helps elsewhere. I've also fixed the mess that was 1.67. When adding that many entries, mistakes will be made. With 1.69, I finally got 10% ahead of the nearest nano, an achievement in itself. I think I found 1 more byte in the aim code if I want to redo 1/2 the aim values. The typecast to short can be dropped if I change my negative aim values to 2*Pi - values as I'm normalizing my gun anyway. I'll do that if the intial movement change turns out decent and I want the slightly better dodging code back. Then I do another comb through for 1 more byte. Always 1 more byte :) I'm now also thining about PhoneBook, a micro bot based on the lessons this bot has taught me. I won't abuse string literals like I have with this bot as I'll have enough room to handle things more elegantly (at first!). I'm also going to make another pass through [[Infinity]] and [[DustBunny]], using my new tricks to save a ton of space. That may free up enough space for them to go on a new melee run. For fun, I've calculated what it would require to brute force the best possible bot with this technique and it would cost about (40^6 x 30 x 8 x 20 x 50 x 100) x numBots=800 x numSeasonsToGetGoodResult=10 or 7.86e20 battles run. Even at 1 battle per second, I don't think I have time to wait around for this result to appear. And this is with some culling already built in. Perhaps I'll check out JGAP or something for fun to see if a genetic algo comes up with better answers than what I've been doing. --[[User:Miked0801|Miked0801]] 22:59, 12 February 2010 (UTC)<br /> <br /> : Some rough calculation told me that even at 1000 battles/second, by the time the result appear, out sun will be White Dwarf for 2E10 year already ((7.86E20)/(86400*365*1000) - 5E9 approx. = 1.99E10, give or take leap year) --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 04:48, 13 February 2010 (UTC)<br /> <br /> Funny how taking out &quot;code improvments&quot; actually gained me between .25 and 1.0% APS in divisions. Now I'm sitting at 243 bytes with 6 bytes to spend on whatever. I also believe I may have figured out a cheap size way to get (averaged) lateral velocity segmentation in. If it works, I will be micro champion and will challenge for minis. Just need some time to see if it works - or I can go optimize some tables a bit to squeak out another 1.5% in micros and try to win that way. Either will work given some time. --[[User:Miked0801|Miked0801]] 08:16, 14 February 2010 (UTC)<br /> <br /> I've coded in average lateral velocity / distance segmenting on my local copy at the cost of only 2 bytes. I'm not happy with my data gathering method though. With simpler bots like el33tGangstar &lt;sp&gt; or [[Infinity]] or even [[spinbot]], I should be able to get a near 100% lock on rate with my gun and my test bot is currently not able to do this. I even added in a segment for acceleration/deceration/steady to see if perhaps that was the issue without luck thus far. Or am I being too perfect here? Amazingly enough, multiple segments isn't as easy as I thought it would be. Perhaps that's why there are so many different ways of doing this out there right now. If I can get my dataset cleaned up, I can test it against 10-20 bots and see how much of a difference it will make. It will fix my current weakness against multi-mode moving bots as well as make my data tables in general more efficient in space. I'll basically be trading 80% of my movement tables (which are mostly unused anyways) for additional aiming information which can be very useful. I can also explore segment size being controled via a more complex formula than e.distance() / CONSTANT to better pack my data into useful areas - with size cost being controlled. Perhaps something like a bell curve centered around 200ish distance. Perhaps even something like AmplitudeConstant * Math.sin(Math.min(e.getDistance * Constant, maxRange)). That costs around 27ish bytes so maybe I'll just stick with the original :) If I do get this to work, it means revisitng every stinking entry in the bot; AGAIN. Man that sucks --[[User:Miked0801|Miked0801]] 21:57, 16 February 2010 (UTC)<br /> <br /> It's been a while and I have been doing various experiments. I've now got my helper bot generating a profile based on acceleration, avg angular velocity, distance, and fire power. I've also calculated the math such that I have a very good idea if a particular GF bin or sets of bins actually hit the target or not. From that, I can compare the various fire power bins to get a points per tic calculation to determine what firepower is most effective at what range calculation. So, I now have a system to automate firepower at distance selection. Just that alone put into the current LBB framework would probably grab a full aps and perhaps more. But, I'll be adding an additional module to the test bot to iterate over the various movement profiles I've created. If it can alternate best movement check, best gun check, and iterate back and forth until both values agree, I've now automated most of the table creation process. Once that works, then I can use this new process to generate a set of tables for angular velocity vs distance vs firepower tables and perhaps even acceleration if I can find the code space. This of course is time consuming. Ambitious, but if successful, I'll have a very, very nice bot upgrade and a low labor path to adding all bots regardless of codesize catagory. I envision a time where adding a new bot is just a matter of running my test bot against it a few thousand times until the numbers stabilze. If I place the movement checks into an external xml or whatever table, then I have a way of adding new movement types at will without recompiling. A fully automated LBB table system. This of course could be used as a spring board for larger, more complex bots in the future. --[[User:Miked0801|Miked0801]] 18:07, 22 February 2010 (UTC)<br /> <br /> No work this last week - interest is waining and work is picking back up. I will make time in the near future to claim the micro crown though :) --[[User:Miked0801|Miked0801]] 19:15, 2 March 2010 (UTC)<br /> <br /> Work still going strong here. Interest renewing. I will get this bot to #1 micro some day when I have a few days to work on it... --[[User:Miked0801|Miked0801]] 18:57, 21 April 2010 (UTC)<br /> <br /> One work project complete, but another short timeline project started. Ugh. Still a few weeks at least until I can start thinking here again. I've got at least 5 new bots that would want to be added to my library. The there's finishing my last edit run on a new improved gun... --[[User:Miked0801|Miked0801]] 16:48, 8 June 2010 (UTC)<br /> <br /> Hooray, a new nano to the field that is strong! I look forward to seeing how far you can go Caligula! Still busy, busy at work, but still watching the action here --[[User:Miked0801|Miked0801]] 17:47, 7 September 2010 (UTC)<br /> <br /> Fighting the urge to play again over winter break :) --[[User:Miked0801|Miked0801]] 05:07, 31 December 2010 (UTC)<br /> <br /> Got lates bots and ran 2/3s of the testing suite needed to add their info. Man I wish I could automate this better. --[[User:Miked0801|Miked0801]] 15:48, 21 May 2011 (UTC)<br /> <br /> Ok, I've only got a few more outlyers to redo. Then I gotta figure out the google upload thingy. --[[User:Miked0801|Miked0801]] 06:03, 31 May 2011 (UTC)<br /> <br /> == LBB Cheeze Factor ==<br /> <br /> I added PEZ's [[LittleEvilBrother]], because it also had a String based GF gun, I believe. There was some discussion about whether or not it was cheesy to load data for a bot not capable of saving data. Consensus at the time was that it was cheesy, but judging by how much better [[LittleBlackBook]] does, it seems like a pretty cool strategy that has a lot of room for experimentation. Plus there's been nothing new in nano-land for years! --[[User:Alcatraz|Alcatraz]] 03:09, 26 June 2009 (UTC)<br /> <br /> : I'd be of the opinion that it is cheesy, but don't object to keeping it around, at least till something particularly new happens in nano-land :) --[[User:Rednaxela|Rednaxela]] 04:26, 26 June 2009 (UTC)<br /> <br /> :: It's extremely cheesy an exploitive of a loophole in the codesize tool. Yet, I'm having some real fun with it right now (and this game is supposed to be fun! :). I literally believe I can get this bot as a top 10 in the micro competition as a nano. That's something that hasn't been done since just after we decided on weight classes. Right now, I'm still crunching a rather exhasutive set of numbers for firepower and movement types. Once that's done, I'll grab the numbers and give it a test run to see where it stands. Good chance it will go in tonight. --[[User:Miked0801|Miked0801]] 05:15, 26 June 2009 (UTC)<br /> <br /> ::: Well, I wouldn't call it &quot;exploitive of a loophole in the codesize tool&quot; exactly (unless someone makes a highly capable interpereter within nano size), since such preloading of data specific to certain bots is also cheesy for megabots. I think what's cheesey most fundumentally, is when a bot that looks up the enemy on a preloaded table based on bot names regardless of codesize. --[[User:Rednaxela|Rednaxela]] 13:11, 26 June 2009 (UTC)<br /> <br /> ::: I for one don't like this though, but it is acceptable for me. Unless, like Rednaxela, someone make a good enough nano-size compiler and fit DrussGT into nano. I'll not object, but I do think that when you fully tuned this robot to the top and have no more idea, you should retire this robot. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 13:30, 26 June 2009 (UTC)<br /> <br /> ::: Of course I agree that preloading data is kinda cheesy, but I think everyone understands that LBB is of a different ilk than other NanoBots. It's cool seeing how far you can go with it. To be honest, I think even hand-tuned segmentations are similar to pre-loading: with a different rumble population, different tunings would surely work better. We all take the rumble population into account when we write our bots; pre-loading is just a more explicit way of doing so. --[[User:Voidious|Voidious]] 14:10, 26 June 2009 (UTC)<br /> <br /> ::: Yep, it's cool to see how far LBB can go indeed. It is true that we all build our bots in way that considers the rumble population, but I don't think pre-loading itself is the cheesy thing. For one thing, I wouldn't consider it cheesy at all, if a GF gun preloads with the average data of a bunch of rumble bots, until it's learned enough about the specific enemy (hint, hint). I think tying pre-loaded data to a specific bot name is where the 'cheese' begins, but more general pre-loaded data is simply prudant rather than cheesy. --[[User:Rednaxela|Rednaxela]] 14:34, 26 June 2009 (UTC)<br /> <br /> ::: Personally, I think the only issue here is that pre-loading is used to get around the size class limits. A bot that saves its own data is fine by me, whether it's general or specific -- the 200k limit restricts how much you can really store anyway. LBB is a novel concept, but it would be disappointing to see it inspire a new generation of string table nanos/micros/minis. Now if you could make a nano that ''generates'' its own string tables, that would be really cool. You still have a few bytes left, right? ;) --[[User:Darkcanuck|Darkcanuck]] 15:02, 26 June 2009 (UTC)<br /> <br /> == AceSurf ==<br /> <br /> I noticed you make not of AceSurf being a problem. One possible solution (if you can fit it into the codesize) that would probably work well, would be having a special code in your data that says &quot;Aim at the last GF it went to&quot;. I'm kind of thinking that would probably eat too much codesize... but I think that's probably the simplest thing that could be done with the likes of AceSurf, besides random targeting anyway. --[[User:Rednaxela|Rednaxela]] 16:00, 20 June 2009 (UTC)<br /> <br /> : I'm not too worried. This bot just hit the 1900 club - the first ever in nanoland to do this. This is with untuned tables for 1/2 the bots. I will take a closer look at ace.surf results though and possibly setup alternating guess factors at every 40 pixels. This has been the best way recently to smash wave bots as it is nearly the same as 2 different guess factors every few shots. Wow I proud of this bot. I might be able to get it to the 2000 club when all is said and done. It just needs another 1000 percentage basis points or so. Plus, right after this bot was released, I figured out a way to better hit stop'n'go's without reducing accuracy against simpler bots who just get stuck. Next release will be fun! --[[User:Miked0801|Miked0801]] 16:06, 20 June 2009 (UTC)<br /> <br /> :: IIRC, The club score is base on ELO, not Glicko-2. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 16:13, 20 June 2009 (UTC)<br /> ::: then [[Toorkild]] isn't in the 2k club. I was pretty sure it was the Glicko. But, it all may be mute. I just realized how few battles it has run - only about 1 per bot. I'll therefore wait a bit before posting anything further on that :) --[[User:Miked0801|Miked0801]] 16:17, 20 June 2009 (UTC)<br /> ::: We're in a weird position with the clubs because it was based on ELO on the old server. ELO on Darkcanuck's server is way lower than it was on the old server, and Glicko-2 is a bit higher -- at least in MegaBot and MiniBot 1v1. As a point of reference, before the old RR server hit a few months of non-stop upwards drift, Dookious was about 2130 and Komarious was about 2085 in mini (prolly a few points higher now). Nevertheless, it's still easy to compare your bot to the competition, arbitrary rating systems aside. =) --[[User:Voidious|Voidious]] 16:26, 20 June 2009 (UTC)<br /> :::: The new server originally matched the old one, but ELO has drifted steadily downwards in the past few months. Why, I don't know. In late 2008, Glicko2 and ELO were in the same range, but now they're quite different. Maybe it's all the recent activity, plus some long-standing bots were removed earlier this year too. In any case, ELO is a relative ranking system so it's the difference between the scores that matters, not the absolute values. But it does leave the ELO clubs in a funny position. --[[User:Darkcanuck|Darkcanuck]] 17:34, 20 June 2009 (UTC)<br /> <br /> <br /> == Fuatisha==<br /> Well, it's nice to see that my nano is giving you so much trouble! Would you happen to have any idea why LBB seems to be having more trouble with it than other adaptive movement nanos? Of course, I wouldn't just be trying to figure out the best things to tweak in it......--[[User:CrazyBassoonist|CrazyBassoonist]] 03:34, 14 February 2010 (UTC)<br /> <br /> It's a number of things:<br /> * It really doesn't have a weakness in its good at any distance I can exploit. [[Moebius]] had a weakness at 260. <br /> * It's movement is adaptive - my gun is not. Plus it has a Very flat movement profile.<br /> * It's gun is just really, really good.<br /> * The opening stop/go movement has a signifigantly different GF profile than its later movements meaning I have to give up hit percentage later to get it out of its opening gambit.<br /> Basically, it is a better overall fighting bot than [[NeophytePattern]] and [[Moebius]], but does worse against weaker bots. If you were to tune anything, tune agaist the masses and you'll probably get #2 (and help me!) :) --[[User:Miked0801|Miked0801]] 05:27, 14 February 2010 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=Talk:LittleBlackBook&diff=19337 2011-05-21T15:48:08Z

<p>Miked0801: /* Bot Blog */</p> <hr /> <div>== Congrats! ==<br /> <br /> Congrats! It's nice to see some movement in the nano scene lately. I was pondering predefined data bots myself actually. I'm curious though, you say &quot;Any perfect dodge stop and go will kill it&quot;, which seems odd to me. It should be quite trivial for a distance/lateral segmented GF gun to hit that I'd think... --[[User:Rednaxela|Rednaxela]] 01:51, 15 June 2009 (UTC)<br /> : Math.signum() off e.velocity screws up 0 velocity checks and I have no velocity averaging. I'll check other bots for inspiration though. Has to be TINY though<br /> : What about... &lt;code&gt;static double foo = 1; foo = e.velocity + 0.01*foo; foo /= foo;&lt;/code&gt;? Not sure if that would be small enough, and I haven't checked it's codesize, but I think it's smaller than any others ways to handle that which come to my mind. I think it's smaller than &lt;code&gt;static double foo = 1; foo = (e.velocity == 0) ? foo : Math.signum(e.velocity);&lt;/code&gt; anyway, since conditionals and function calls are expensive if I remember right. I'd also suggest seeing if you can get rid of the need to normalize the value to 1/-1 all together, but that may not be possible in this case. --[[User:Rednaxela|Rednaxela]] 04:15, 15 June 2009 (UTC)<br /> :: Anything having to do with statics are expensive. Your above code is probably around 25 bytes or so. Math.signum(e.getVelocity()) is 6 or so. I can easily fix my problem by adding +1 to the e.getVelocity() check on the inside of the gun( for 2 bytes)... But! It will only hit perfect stop/go 50% of the time as it is setup to use the velocity to know how far to lead. Also, bots like FretNano who have good guns, but get stuck on walls randomly, would then be unhittable. I get 1 lead value per distance segment at the moment. I've got a few ideas on how to improve this, though it will double+ the size of my string table. I will adhere to the 200k max limit and with 1000 or so bots to profile, I have to be careful on size. --[[User:Miked0801|Miked0801]] 13:38, 15 June 2009 (UTC)<br /> <br /> Hi! Awesome results! Now that I looked at the code, I think there is one little problem with the overall concept: every time a new robot or a new version of a robot appears, you have to update the stats in your bot. --[[User:Robar|HUNRobar]] 10:31, 15 June 2009 (UTC)<br /> : And a decent problem it is. I'm going to review the string libraries today to see if I can find a &quot;closest to this name&quot; type function for my search. That'll at least handle versioning. The version in there right now is using default behavior against [[Pugio]] because my table is setup for 1.40. When all your other versions get cleared from the rumble, my rating will go up another .5 or so. --[[User:Miked0801|Miked0801]] 13:38, 15 June 2009 (UTC)<br /> :: &lt;code&gt;HashMap&lt;String, String&gt; enemyGF; enemyGF.get(e.getName().split(&quot; &quot;)[0]);&lt;/code&gt; =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 14:03, 15 June 2009 (UTC)<br /> ::: Um, wow. That does work: e.getName().split(&quot; &quot;)[0]. I rediscovered it myself and you had it here the whole time. I feel very stupid. Thanks for the advice! --[[User:Miked0801|Miked0801]] 06:13, 23 June 2009 (UTC)<br /> :::: No problem at all. =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 11:05, 23 June 2009 (UTC)<br /> <br /> Nice! I may re-release [[Ocnirp]] 1.0 to screw your stats =) Updated Wikipedia page for you now. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 12:00, 15 June 2009 (UTC)<br /> : Don't bother, I'm already using default values against that bot so it wouldn't make any difference so Nyaa Nyaa! :) --[[User:Miked0801|Miked0801]] 13:48, 15 June 2009 (UTC)<br /> :: Really? I don't think so. (default is 50-40-30-20-10-0, right?). Beside, I'm working on Nano adaptive movement (Mysterious is its fail attempt) =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 14:03, 15 June 2009 (UTC)<br /> ::: Ok, you win. There are quite a few bots taht got default cases though. For some reason I thought Ocnrip was one. And, yeah, nice string match there. I could fit that if, oh I don't know, I took out all my movement code ;) --[[User:Miked0801|Miked0801]] 14:20, 15 June 2009 (UTC)<br /> :::: That doesn't call fit, really. :P &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 14:53, 15 June 2009 (UTC)<br /> <br /> Thanks! Links and work email address removed. --[[User:Miked0801|Miked0801]] 15:27, 15 June 2009 (UTC)<br /> <br /> : He he, the revision system still have it. =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 15:32, 15 June 2009 (UTC)<br /> :: Yep - but at least basic spider bots won't pick it up and spam be about male enhancement products :) --[[User:Miked0801|Miked0801]]<br /> <br /> Ok, new version in the wild. I expect this release to be better against stronger bots, but I also expect some startlingly poor results against a few bots. These I can tune back to either the old values or a combo of new and old. Stelo.MirrorNano being an example. My next release will beat this bot 90/10, but now LBB is losing 45/55. No panic :) --[[User:Miked0801|Miked0801]] 02:04, 18 June 2009 (UTC)<br /> : Good result. My next update tomorrow is going to absolutely destroy the competition. This is going to be a 1900+ rating bot. --[[User:Miked0801|Miked0801]] 05:45, 18 June 2009 (UTC)<br /> <br /> == Bot Blog ==<br /> Seems like a decent place for random ramblings. The averaging code is doing its job, it just needs some table number TLC. Alas, it also screwed with some other scores that will need attention. I also commited a cut and paste errored with nat's SNG 1.0b bot resulting in a 6% score. Lame. I may try taking the averaging back out and using firepower control instead. It'd probably help me more overall to fire at 3.0 firepower at range 80 or 120 and closer against everyone. The Micro scores have been decent thus far with their first autogeneration pass. 19th is a good starting point and I know I can get to 15th or even 10th with some work there. I'll drop the mini scores in Tuesday or so and for another overall ranking boost. I still believe I can get this bot to a 2k points score with over 80%APS in nanos with a few revisits to lagging numbers.<br /> <br /> Wow, a good day. Found another 10 bytes by just re-arranging the stack vars. Used that space to try out variable move distances. Helps quite a bit against the weakest bots. Also fixed bugs with a few bots that came from typos. Finally, I fixed poorer results against rambots wehre I wasn't aiming right at range 40 and in. My scores are now approaching [[DrussGT]]'s against the low-end bots. Using that bot's scores gives me a reasonable target to short for. I'm also going to experiment with variable firepower as well, though for some reason I keep pushing back on that - dunno. Next release tomorrow night. Shooting for APS of 78ish in nanos. That would put me close to my goal of a 2k score. Hopefully, my micro score will get me top 15 there as well. I'll start running Minis by end of week to see if I can get top 25 there and perhaps top 100 overall (aiming real high, I know.) --[[User:Miked0801|Miked0801]] 03:38, 23 June 2009 (UTC)<br /> <br /> : You should to remember the [[Code Size/Cheat sheet|Code Size/Cheat sheet]]. The most important part is the vars-on-register, which is discover by Simonton I think. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 11:02, 23 June 2009 (UTC)<br /> :: I just rearrange them all until I get the smallest result :)<br /> <br /> Another good day, but I found a dumb bug I introduced to my table generation a few days ago which will require me to revisit all the nano values. Sigh. Good news though, found another 8 bytes or so by declaring the string table final (never changes so I should have done it ages ago) and by rearranging a few typecasts to make sure we got int on int math wherever possible. That means I now have both distance and firepower control in the table! It hurts by aim a touch from 80 pixels and in, but for 1 more free byte I could fix this. I'll keep looking. 8 more bytes and I get variable string matching, though if firepower or move control prove poor, I can always swap this in for the other. Because I have to do a table revisit, I'm pushing my release back one more day. Who'd have though a variable GF, variable firepower, variable move distance, variable turn control bot could be done through a silly string table. It's like the synthesis of all the best nanos in one place. Next release will have some bugs, but the one following will be absolutely epic. --[[User:Miked0801|Miked0801]] 18:48, 23 June 2009 (UTC)<br /> <br /> Bleh. Had to work late a few nights. I'm just now getting all my initial micro/nano runs complete. Good news is that only [[Moebius]] is currently able to consistantly beat me now in nanos. I'm going to experiment with distance control next as many bots are optimized for certain ranges and I expect I will do well at varying ranges against many bots. If it works well, I'll trade something off to get it. We'll see about a tomorrow release, work allowing. --[[User:Miked0801|Miked0801]] 07:39, 25 June 2009 (UTC)<br /> <br /> Played around with enemy distancing and found it helps (much) more than firepower control. But, my test cycle is too far along to scrap and start again so I'll go ahead with what I have. Besides, I believe I found a way to fit all 5 factors into this nano anyways - Fire Power, Chance to reverse direction, Min Distance to move, desired distance from enemy, and Guess Factors. It requires my tables to be created differently (again), but I'll go for that next version. This is why I haven't bothered with minis or megas yet - the tables flux dramatically with each version. It also means yet another multiplier when creating my tables. I'm already running 20+ versions per bot through roboresearch. Adding distance is another x4 or so. Yikes. Back to 1 good test run and cull, cull, cull so that I have time to balance what makes sense. At least my testing methods are improving so that this doesn't take too long. Just need 1 more set up data to finish up for the guess factors and then we'll put this bot back together again. --[[User:Miked0801|Miked0801]] 07:29, 26 June 2009 (UTC)<br /> <br /> Ok, version is up and we gained nearly another 2% APS in nanos and even more in Micros. Nice. There's still a few bots that came out a bit half baked, even with all the care I put into the tables before releasing. I'll revisit those for one last version 1.5x release and then go onto version 1.6x with distance control. Still shooting for 80+% APS, a perfect PL score in nanos, and 2k in ratings. 72 Glicko's to go. --[[User:Miked0801|Miked0801]] 02:59, 27 June 2009 (UTC)<br /> <br /> Hey, you've taken my micro's place in the microrumble! I really should do something right after I finished my flash game. ;) --[[User:Robar|HUNRobar]] 17:31, 27 June 2009 (UTC)<br /> <br /> Dang it. Screwed up robar.nano.Scytodes 0.3's table, which costed me 50-60 battle points and .33 APS in the Nano Rumble (.15 in micro). Savant values are weaker too, but that can be attributed a little to random luck. Beyond that, a very good update. Solidly in 11th now in Micros and 1.5% APS from 80 in nanos. That's only 260 battle % points and 50 of those are from my above mistake. But, without distance control, I'm running out of big gains. I can probably push this bot to 80% APS and 2k Glicko without distance, but it will take a lot of work. I made a lot of gain my swapping appropriate bots to 2.0 fire power. Some of those I can switch back to get some ground I lost between 1.52 and 1.53. I did tie for the PL score this time and would have had it if not for Scytodes. Next version I'll get it right. I think I'll release a 1.54 just to try for 10th/9th in the micros without distance help. --[[User:Miked0801|Miked0801]] 03:46, 29 June 2009 (UTC)<br /> <br /> Well fixed Scytodes and decided to alphabetize my list and lo and behold I had missed 4 other bots - all micros. Adding those gave a decent score increase for them as well and would probably challenge Jen for 10th. But, I went ahead and started the HUGE roboresearch database needed for my next release. We're talking around 1 Million battles to be run before all is ready. I'm guessing my computer running 24/7 will get through this info in around 3 days. Wow. The good news is that my previous run is compatible so I saved 150k battles or so. All this will put me over 80APS in Nanos and will put me well into top 10 in micros. I'll know for sure once I start seeing some comparison results against the micros. The top nanos appear to be weak against different ranges, but I'm not sure on Micros yet. I'll post tomorrow with some initial results. --[[User:Miked0801|Miked0801]] 21:30, 30 June 2009 (UTC)<br /> <br /> Test run about 15% complete. I'm tuning back to breadth of the first run to speed it up so I can play before next week. --[[User:Miked0801|Miked0801]] 02:18, 2 July 2009 (UTC)<br /> <br /> 33% done and I'm not patient enough to wait for it to go much further so I put together the next version - and had another awesome idea on how to make it do more for less. I now have distance control and! - all other factors also are available based on distance as well. This means variable firewpower on distance. This means I can change my move mode out of oscillation at those distances where I run into head-on shots (around 280 or so). I can even change my desired distance based on distance meaning I can ping-pong between values to help with multi-mode movers and to throw off pattern bots. That plus partial string matches and I'm sitting at exactly 249. That's enough tech for my goals. Now it's time to do my last pass through the nano/micros and see just how much pwnage will be wrought. 85+ nano APS isn't out of reach.<br /> <br /> Work, work work. My job is heating up to the point where things have been on hold for a bit. This will continue for a few more days - grr. --[[User:Miked0801|Miked0801]] 17:39, 8 July 2009 (UTC)<br /> <br /> And even more work. I'm in crunch mode now and barely have time for breathing. I've still got my next bot upgrade ready, jsut need to find a couple uninterrupted hours to fix a few minor things. I'm still alive guys :) --[[User:Miked0801|Miked0801]] 20:44, 27 August 2009 (UTC)<br /> <br /> Good to hear =) I'm also pretty snowed under, but it seems that when that happens Robocode becomes my outlet =) --[[User:Skilgannon|Skilgannon]] 20:55, 27 August 2009 (UTC)<br /> <br /> Project starting to wrap up - we'll see if life returns to normal soon... --[[User:Miked0801|Miked0801]] 16:30, 6 October 2009 (UTC)<br /> <br /> Project's done! Vacation is started. Updates to follow :) --[[User:Miked0801|Miked0801]] 16:28, 6 December 2009 (UTC)<br /> <br /> : Yay, welcome back! =) --[[User:Voidious|Voidious]] 17:18, 6 December 2009 (UTC)<br /> <br /> Ok, Nanos mostly refit. I want to find another 1.5% of APS then its back to micros. Mostly hand tuning at this point. --[[User:Miked0801|Miked0801]] 22:46, 17 December 2009 (UTC)<br /> <br /> Actually changed a little base code with this version. I removed the adjustTurnForGun() call and replaced it with a bit of randomness added to the range index. This results in slightly more random ranges when firing. It makes it easier to hit multi-modes, bullet catchers, and wave surfers, but hurts my score against really, really weak bots and the best nanos a bit. Still, seems like a decent upgrade. Broke 2 nano bot solutions with this chagne that I can easily retrofit back to pwnage. I will also be able to make a further micro pass to get above Jen on my next update. I beginning to believe that this might get top 5ish in micro before I'm done. --[[User:Miked0801|Miked0801]] 00:07, 9 January 2010 (UTC)<br /> <br /> FYI, this bot needs to be compiled with Sun's Java Compiler in order for it to remain byte size complient. Got bit with that today. Made a major pass through the tables using the top Mega bot's scores in comparison to mine for inspiration on who to fix. Found many, many bots that were improved 10% APS or more. This should be the version, barring bugs, that hits 80%APS or even 81% APS in nanos - and should also hit 2k Glicko. And there's still a bit (not much!) more tuning that can be done. There are countless ways of ordering my tables to get 1-5% individual APS tweaks that I probably need a seperate program to find. Overall, this has ben a wonderful experiment and mega contenders should take note. I'll continue to tune it a touch more, but I'm also going to investiage Lateral Velocity segmentation as well. If I get inspired, it may not cost too much :) --[[User:Miked0801|Miked0801]] 23:07, 13 January 2010 (UTC)<br /> <br /> Results looking very nice so far, though not sure if it'll quite end up getting past 2k Glicko. What I find most impressive is how you fit so many movement modes alongside a GF gun, in a nano, that's an awful lot of movement modes for a nano, particularly with the distance-based selection of them! :) --[[User:Rednaxela|Rednaxela]] 03:50, 14 January 2010 (UTC)<br /> : Thank you! I'm a rather proud parent of this bot and all comments make me grin :) --[[User:Miked0801|Miked0801]] 15:49, 14 January 2010 (UTC)<br /> <br /> BTW, the build system seems to be completely confused at the moment. Would it help if I released a 1.60 version to fix it? --[[User:Miked0801|Miked0801]] 15:49, 14 January 2010 (UTC)<br /> <br /> : What do you mean by &quot;build system&quot;? --[[User:Voidious|Voidious]] 16:24, 14 January 2010 (UTC)<br /> :: Was about to ask the same, nearly got edit conflict :) --[[User:Rednaxela|Rednaxela]] 16:33, 14 January 2010 (UTC)<br /> <br /> :: At the moment, the rumble is only running LBB 1.58 (retired), not LBB 1.59. I believe it is because 1.59 lost roughly 30ish nano battles whilst retaining the micro and up battles before I fixed an issue on my local client. I could upload the missing nano battles and that may fix it, but I wanted permission to do so first as I would need to edit the results.txt file manully to add the missing numbers. --[[User:Miked0801|Miked0801]] 17:42, 14 January 2010 (UTC)<br /> <br /> ::: &quot;... fixed an issue on my local client&quot;? Please don't edit results.txt or upload any old results! Best thing to do is delete all files in the roborumble/files and roborumble/temp folders and start fresh -- preferably with uploads disabled for the first run just to make sure. --[[User:Darkcanuck|Darkcanuck]] 21:27, 14 January 2010 (UTC)<br /> <br /> :::: Not what I did. I have 2 copies of Robo installed. I created 1.59 in version 1.6.1.4 and it was 256 bytes in size. oops. I then fixed the problem and recreated it in my other version of robocode, but stupidly called it the same thing. I then took this version and copied it to both builds. But, the codesize.txt never updated to the new, reduced size for the updated lbb. Therefore, it didn't record roughly 30ish nano battles. When i noticed this, I completely killed the cache, the local 1.59 file, and removed it from the codesize file so that it could recreate it. This worked, but those 30 or so nano battles were lost as has since confused the server quite a bit. Another side effect of this is that when you first run the client, it correctly runs version 1.59 of LBB, but further iterations always run the previous verion. Long story short, be careful about versioning of bots... --[[User:Miked0801|Miked0801]] 21:45, 14 January 2010 (UTC)<br /> <br /> :: This is weird... If you look at its roborumble details, 1.58 only has 3 battles: [http://darkcanuck.net/rumble/RatingsDetails?game=roborumble&amp;name=mld.LittleBlackBook%201.58]. Only 2 for mini, but lots for micro and nano. Not sure how that would happen... The server tries to run all pairings for each version (after a certain point), even if it's retired, so maybe that's what's going on. If you delete 1.58 from your rumble dir, it won't run 1.58 any more. (But anyone that has 1.58 will until it has all pairings, if that's the reason.) --[[User:Voidious|Voidious]] 18:51, 14 January 2010 (UTC)<br /> <br /> :: Wow... this is very weird... the &quot;Last Updated&quot; times for LittleBlackBook 1.58 keep going <br /> up in mega/mini (and different update times from mini/nano), but the battle count is only increasing in mini/nano! Something is broken on the server side I think.... because all clients with LBB 1.58 (like mine) are ONLY running LBB 1.58, but the Rumble isn't recording the mega/mini results so it looks like it'll go on forever... --[[User:Rednaxela|Rednaxela]] 19:46, 14 January 2010 (UTC)<br /> <br /> :: It should be fixed now. Looks like a concurrent retirement/reactivation. My guess is one client saw no battles for 1.58 in the last 4 hours and started to retire it, first for the general rumble then the mini. But then another client uploaded new battles (either due to old results not yet uploaded or an old priority file) while the retirements were in progress leading to the corrupted states. I have a permanent fix in mind, but it will require a lot of testing which I have yet to find time for... --[[User:Darkcanuck|Darkcanuck]] 21:27, 14 January 2010 (UTC)<br /> <br /> ::: Wow, 1.58 has 7963 battles in mega... yep... clients sure working away at it when things were messed up before... :) --[[User:Rednaxela|Rednaxela]] 03:55, 15 January 2010 (UTC)<br /> <br /> Today was a huge update! Managed to redo and find roughly 20ish more bytes!!! Desired distance from enemy table became approach angle table for a big savings. Found 2 bytes in the averaging code. Came up with a new way to do bullet detection that costs only a couple more bytes than my simple one from before. Added Ramming ability. Overall, this bot will be weaker as the dodging stuff was so tightly coupled into the random movement, but next version will keep the massive increases against the simpler, linear aim bots while improving the general movement. This bot could very well reach top 5 in Micros. I have also decided that my string tables will not exceed 200k as per the Rumble rules to make it fair. Right the tables are sitting at 100kish and won't get much bigger until I add the Minis some day. I am now awaiting the results to see which bots are now broken and need another revisit :) --[[User:Miked0801|Miked0801]] 01:33, 16 January 2010 (UTC)<br /> <br /> Tables, tables, tables. Fixed 30 or so bots thus far that I had weakened with the improved oscollation code. This put me above where I was at 1.59. I've got roughly 30 more bots to modify to get back to where 1.59 was against all bots. That's a good days work. Then, there's a revisit to change some bots from random movement back to oscollation for a nice boost. The new and improved energy detection code as made me weaker overall against PM bots. I'm working on a solution to this now. If I can find one, that's another 2APS overall or so and makes this a contender for the Micro crown. Then it would be on to the minis. Big talk though; gotta get there first! --[[User:Miked0801|Miked0801]] 19:15, 18 January 2010 (UTC)<br /> <br /> Reviewed the movement code a bit because it still felt heavy and figured out a way to do near perfect stop-n-go movement. Good enough to fool Smog 90/10. It requires a bit of table wrangling to do though so I'll wait for version 1.70 or so to do it. I've still got lots of bots to tweak before I add yet another movement mode for maybe 5% of my opponents. Actually, stop-n-go overlaps most of my current oscollator bots so I'll have to review which helps more. I could use my extra few bytes to improve my gun instead by increasing the random range it uses for the index a bit more. Or again, look perpendicular velocity segmentation which is still a bit out of reach. Lots of choices here. Perhaps it's time for some heavy roboresearch... --[[User:Miked0801|Miked0801]] 19:27, 20 January 2010 (UTC)<br /> <br /> Latest version I accidently bugged Fuatisha and lost 5aps on him. In addition, I removed the minor random added to the aim and lost .25 overall APS and gained back a bunch of bytes. Improved micros a ton though. Now, I'm sitting at 240 bytes and looking into its next improvement. It will cost 0 bytes to added near perfect stop'n'go, but I inherit another string table. That would give me another full overall APS though so I will probably do it. After that, it's time to look into improving aim with my extra bytes. I may finally be reaching the end of what I can do on movement alone. --[[User:Miked0801|Miked0801]] 16:32, 22 January 2010 (UTC)<br /> <br /> Added perfect stop n go with this version at the cost of 8 bytes. This, plus some TLC with some aim tables, has moved me up roughly 1 full APS in the rankings. I'm now #4 in micros and may hit #3 when things stablize - with a bugged ntc.Knowledge entry that cost me 40ish points in that battle. I also seem to have comfortably hit 2k Glicko in Nanos! Party! I'm also a hairs breath away from 2K in both rankings which would be a first. I found a new, flatter movement curve and randomized my aim a bit more on generic bots for a good overall catagory bump. The same pattern can be used to help my scores against the top micros next time around. Hopefully, no reds on the micro screen sometime in my future. Still have 4 or 5 nanos I just have a very hard time beating. I'll keep working at it though. [[Fuatisha]], you are an awesome bot. Next upload goal is 3rd in micros approaching 80 APS. We'll see if I can pull it off. --[[User:Miked0801|Miked0801]] 07:32, 27 January 2010 (UTC)<br /> <br /> Looks like 3rd in Micros is achieved. Also, this build may give me a perfect PL score in Nanos. [[Fuatisha]] is the only question mark right now. I actually found a movement pattern that confuses some of the string PM guns and gained a nice chunk off the top bots in nano land. That means next updated will be mostly concentrating on Micros to see if I can approach 81% in the Micro rumble. That will be difficult, but doable. If I get there, then I am a micro crown contendor with my silly little nano. I also have a new home computer coming online this weekend. Hopefully reobocode is 64-bit Windows 7 compatible. Should be. If so, I will have roughly 10x the computing power I have right now for roboresearch and should be able to put together a first pass on mini-bots sometime next week. If it goes smoothly, I may just setup some scripts and add all the bots just to see if I'm top 100 overall or not yet. That would be a trick. Wow this bot has come far... --[[User:Miked0801|Miked0801]] 22:51, 28 January 2010 (UTC)<br /> <br /> About 50% complete with first pass at minibot tables. I have good movement types for them all, now am porting across aim. Then, I test against distances. Then, rebuild with best distance and test. Should take another 2-3 hours. I might get to that tonight. I will also probably pass the nano/micros back through a test pass again as well, now that I have enough CPU power to do a decent pass in a couple hours as opposed to a couple of days. Next release, I will skip to 1.70 because I'll have updated roughly 20% of the tables. I have no idea where I'll land against the minis, but not top 10. Initial testing is showing just how strong the top 5 bots in that division are. --[[User:Miked0801|Miked0801]] 18:55, 2 February 2010 (UTC)<br /> <br /> Sigh - compiling with minibot data crashes the java compiler. My bot cannot get any bigger than micro with this technique. --[[User:Miked0801|Miked0801]] 05:47, 3 February 2010 (UTC)<br /> <br /> : Perhaps try a java bytecode disassembeler/assembler to hack the additional string length in? That might work to circumvent any compiler crashing unless it's a limitation inherent in the bytecode standard itself. --[[User:Rednaxela|Rednaxela]] 06:09, 3 February 2010 (UTC)<br /> <br /> Solved it! Too many character concats blowing up the compiler. How to fix? I just discovered how to put a unicode literal into a string &quot;\u008f&quot; becomes character 8f! This also has the added benefit of making many, many of my entries a much more readable single constant that I can static const final declare above. I will also be able to use a real IDE again as my current version crashes ecclipse and visual studio. Happy days for unicode literals! --[[User:Miked0801|Miked0801]] 16:20, 3 February 2010 (UTC)<br /> <br /> Learned some Java things the last few days:<br /> * \u000a, \u000c, and \u0022 (\r, \n, and &quot;), when put into a string literal, are treated as a raw symbol meaning you have to \ them or use a seperate symbol.<br /> * Non-aligned tables make for bugs that are very hard to find. Much debugging was needed to fix these bugs.<br /> * RoboResearch on broken bots doesn't help much in terms of strength judging.<br /> * The top minis are STRONG!<br /> I have 1 more day of tweaking and then an update. --[[User:Miked0801|Miked0801]] 05:26, 6 February 2010 (UTC)<br /> <br /> Chugging lots of numbers this weekend - ran roughly 100k battles over 2 days, testing ideal range from target from 100 to 380 units per opponent. The results of this tuning pass will appear as soon as I find 2 or so hours to comb through the results and adjust my range table. On average, I was getting a good 5-10% APS kick every 3rd robot or so, but I also know that with such a large update, I will accidently break a few bots as well. Still, when this pass is complete, I could be contending for micros overall. Minis - not sure where I'll land, but at least top 20. [[Fuatisha]], I may finally have a marginal (52/48) solution for, but that's too small to count on. --[[User:Miked0801|Miked0801]] 19:00, 8 February 2010 (UTC)<br /> <br /> BAH! 1.67 jar is partially corrupted so the source isn't available. Lame. It also has 10 or so bot bugs to fix. I'll get those taken care of tonight and get a new version reloaded. --[[User:Miked0801|Miked0801]] 18:16, 9 February 2010 (UTC)<br /> <br /> Just uploaded a test for initial movement vs no dodge against 0.1 bullets and yes dodge up to 3.9 power change. Also may stick to walls slightly more. I know that this helps against ram bots, but am curious if it helps elsewhere. I've also fixed the mess that was 1.67. When adding that many entries, mistakes will be made. With 1.69, I finally got 10% ahead of the nearest nano, an achievement in itself. I think I found 1 more byte in the aim code if I want to redo 1/2 the aim values. The typecast to short can be dropped if I change my negative aim values to 2*Pi - values as I'm normalizing my gun anyway. I'll do that if the intial movement change turns out decent and I want the slightly better dodging code back. Then I do another comb through for 1 more byte. Always 1 more byte :) I'm now also thining about PhoneBook, a micro bot based on the lessons this bot has taught me. I won't abuse string literals like I have with this bot as I'll have enough room to handle things more elegantly (at first!). I'm also going to make another pass through [[Infinity]] and [[DustBunny]], using my new tricks to save a ton of space. That may free up enough space for them to go on a new melee run. For fun, I've calculated what it would require to brute force the best possible bot with this technique and it would cost about (40^6 x 30 x 8 x 20 x 50 x 100) x numBots=800 x numSeasonsToGetGoodResult=10 or 7.86e20 battles run. Even at 1 battle per second, I don't think I have time to wait around for this result to appear. And this is with some culling already built in. Perhaps I'll check out JGAP or something for fun to see if a genetic algo comes up with better answers than what I've been doing. --[[User:Miked0801|Miked0801]] 22:59, 12 February 2010 (UTC)<br /> <br /> : Some rough calculation told me that even at 1000 battles/second, by the time the result appear, out sun will be White Dwarf for 2E10 year already ((7.86E20)/(86400*365*1000) - 5E9 approx. = 1.99E10, give or take leap year) --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 04:48, 13 February 2010 (UTC)<br /> <br /> Funny how taking out &quot;code improvments&quot; actually gained me between .25 and 1.0% APS in divisions. Now I'm sitting at 243 bytes with 6 bytes to spend on whatever. I also believe I may have figured out a cheap size way to get (averaged) lateral velocity segmentation in. If it works, I will be micro champion and will challenge for minis. Just need some time to see if it works - or I can go optimize some tables a bit to squeak out another 1.5% in micros and try to win that way. Either will work given some time. --[[User:Miked0801|Miked0801]] 08:16, 14 February 2010 (UTC)<br /> <br /> I've coded in average lateral velocity / distance segmenting on my local copy at the cost of only 2 bytes. I'm not happy with my data gathering method though. With simpler bots like el33tGangstar &lt;sp&gt; or [[Infinity]] or even [[spinbot]], I should be able to get a near 100% lock on rate with my gun and my test bot is currently not able to do this. I even added in a segment for acceleration/deceration/steady to see if perhaps that was the issue without luck thus far. Or am I being too perfect here? Amazingly enough, multiple segments isn't as easy as I thought it would be. Perhaps that's why there are so many different ways of doing this out there right now. If I can get my dataset cleaned up, I can test it against 10-20 bots and see how much of a difference it will make. It will fix my current weakness against multi-mode moving bots as well as make my data tables in general more efficient in space. I'll basically be trading 80% of my movement tables (which are mostly unused anyways) for additional aiming information which can be very useful. I can also explore segment size being controled via a more complex formula than e.distance() / CONSTANT to better pack my data into useful areas - with size cost being controlled. Perhaps something like a bell curve centered around 200ish distance. Perhaps even something like AmplitudeConstant * Math.sin(Math.min(e.getDistance * Constant, maxRange)). That costs around 27ish bytes so maybe I'll just stick with the original :) If I do get this to work, it means revisitng every stinking entry in the bot; AGAIN. Man that sucks --[[User:Miked0801|Miked0801]] 21:57, 16 February 2010 (UTC)<br /> <br /> It's been a while and I have been doing various experiments. I've now got my helper bot generating a profile based on acceleration, avg angular velocity, distance, and fire power. I've also calculated the math such that I have a very good idea if a particular GF bin or sets of bins actually hit the target or not. From that, I can compare the various fire power bins to get a points per tic calculation to determine what firepower is most effective at what range calculation. So, I now have a system to automate firepower at distance selection. Just that alone put into the current LBB framework would probably grab a full aps and perhaps more. But, I'll be adding an additional module to the test bot to iterate over the various movement profiles I've created. If it can alternate best movement check, best gun check, and iterate back and forth until both values agree, I've now automated most of the table creation process. Once that works, then I can use this new process to generate a set of tables for angular velocity vs distance vs firepower tables and perhaps even acceleration if I can find the code space. This of course is time consuming. Ambitious, but if successful, I'll have a very, very nice bot upgrade and a low labor path to adding all bots regardless of codesize catagory. I envision a time where adding a new bot is just a matter of running my test bot against it a few thousand times until the numbers stabilze. If I place the movement checks into an external xml or whatever table, then I have a way of adding new movement types at will without recompiling. A fully automated LBB table system. This of course could be used as a spring board for larger, more complex bots in the future. --[[User:Miked0801|Miked0801]] 18:07, 22 February 2010 (UTC)<br /> <br /> No work this last week - interest is waining and work is picking back up. I will make time in the near future to claim the micro crown though :) --[[User:Miked0801|Miked0801]] 19:15, 2 March 2010 (UTC)<br /> <br /> Work still going strong here. Interest renewing. I will get this bot to #1 micro some day when I have a few days to work on it... --[[User:Miked0801|Miked0801]] 18:57, 21 April 2010 (UTC)<br /> <br /> One work project complete, but another short timeline project started. Ugh. Still a few weeks at least until I can start thinking here again. I've got at least 5 new bots that would want to be added to my library. The there's finishing my last edit run on a new improved gun... --[[User:Miked0801|Miked0801]] 16:48, 8 June 2010 (UTC)<br /> <br /> Hooray, a new nano to the field that is strong! I look forward to seeing how far you can go Caligula! Still busy, busy at work, but still watching the action here --[[User:Miked0801|Miked0801]] 17:47, 7 September 2010 (UTC)<br /> <br /> Fighting the urge to play again over winter break :) --[[User:Miked0801|Miked0801]] 05:07, 31 December 2010 (UTC)<br /> <br /> Got lates bots and ran 2/3s of the testing suite needed to add their info. Man I wish I could automate this better. --[[User:Miked0801|Miked0801]] 15:48, 21 May 2011 (UTC)<br /> <br /> == LBB Cheeze Factor ==<br /> <br /> I added PEZ's [[LittleEvilBrother]], because it also had a String based GF gun, I believe. There was some discussion about whether or not it was cheesy to load data for a bot not capable of saving data. Consensus at the time was that it was cheesy, but judging by how much better [[LittleBlackBook]] does, it seems like a pretty cool strategy that has a lot of room for experimentation. Plus there's been nothing new in nano-land for years! --[[User:Alcatraz|Alcatraz]] 03:09, 26 June 2009 (UTC)<br /> <br /> : I'd be of the opinion that it is cheesy, but don't object to keeping it around, at least till something particularly new happens in nano-land :) --[[User:Rednaxela|Rednaxela]] 04:26, 26 June 2009 (UTC)<br /> <br /> :: It's extremely cheesy an exploitive of a loophole in the codesize tool. Yet, I'm having some real fun with it right now (and this game is supposed to be fun! :). I literally believe I can get this bot as a top 10 in the micro competition as a nano. That's something that hasn't been done since just after we decided on weight classes. Right now, I'm still crunching a rather exhasutive set of numbers for firepower and movement types. Once that's done, I'll grab the numbers and give it a test run to see where it stands. Good chance it will go in tonight. --[[User:Miked0801|Miked0801]] 05:15, 26 June 2009 (UTC)<br /> <br /> ::: Well, I wouldn't call it &quot;exploitive of a loophole in the codesize tool&quot; exactly (unless someone makes a highly capable interpereter within nano size), since such preloading of data specific to certain bots is also cheesy for megabots. I think what's cheesey most fundumentally, is when a bot that looks up the enemy on a preloaded table based on bot names regardless of codesize. --[[User:Rednaxela|Rednaxela]] 13:11, 26 June 2009 (UTC)<br /> <br /> ::: I for one don't like this though, but it is acceptable for me. Unless, like Rednaxela, someone make a good enough nano-size compiler and fit DrussGT into nano. I'll not object, but I do think that when you fully tuned this robot to the top and have no more idea, you should retire this robot. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 13:30, 26 June 2009 (UTC)<br /> <br /> ::: Of course I agree that preloading data is kinda cheesy, but I think everyone understands that LBB is of a different ilk than other NanoBots. It's cool seeing how far you can go with it. To be honest, I think even hand-tuned segmentations are similar to pre-loading: with a different rumble population, different tunings would surely work better. We all take the rumble population into account when we write our bots; pre-loading is just a more explicit way of doing so. --[[User:Voidious|Voidious]] 14:10, 26 June 2009 (UTC)<br /> <br /> ::: Yep, it's cool to see how far LBB can go indeed. It is true that we all build our bots in way that considers the rumble population, but I don't think pre-loading itself is the cheesy thing. For one thing, I wouldn't consider it cheesy at all, if a GF gun preloads with the average data of a bunch of rumble bots, until it's learned enough about the specific enemy (hint, hint). I think tying pre-loaded data to a specific bot name is where the 'cheese' begins, but more general pre-loaded data is simply prudant rather than cheesy. --[[User:Rednaxela|Rednaxela]] 14:34, 26 June 2009 (UTC)<br /> <br /> ::: Personally, I think the only issue here is that pre-loading is used to get around the size class limits. A bot that saves its own data is fine by me, whether it's general or specific -- the 200k limit restricts how much you can really store anyway. LBB is a novel concept, but it would be disappointing to see it inspire a new generation of string table nanos/micros/minis. Now if you could make a nano that ''generates'' its own string tables, that would be really cool. You still have a few bytes left, right? ;) --[[User:Darkcanuck|Darkcanuck]] 15:02, 26 June 2009 (UTC)<br /> <br /> == AceSurf ==<br /> <br /> I noticed you make not of AceSurf being a problem. One possible solution (if you can fit it into the codesize) that would probably work well, would be having a special code in your data that says &quot;Aim at the last GF it went to&quot;. I'm kind of thinking that would probably eat too much codesize... but I think that's probably the simplest thing that could be done with the likes of AceSurf, besides random targeting anyway. --[[User:Rednaxela|Rednaxela]] 16:00, 20 June 2009 (UTC)<br /> <br /> : I'm not too worried. This bot just hit the 1900 club - the first ever in nanoland to do this. This is with untuned tables for 1/2 the bots. I will take a closer look at ace.surf results though and possibly setup alternating guess factors at every 40 pixels. This has been the best way recently to smash wave bots as it is nearly the same as 2 different guess factors every few shots. Wow I proud of this bot. I might be able to get it to the 2000 club when all is said and done. It just needs another 1000 percentage basis points or so. Plus, right after this bot was released, I figured out a way to better hit stop'n'go's without reducing accuracy against simpler bots who just get stuck. Next release will be fun! --[[User:Miked0801|Miked0801]] 16:06, 20 June 2009 (UTC)<br /> <br /> :: IIRC, The club score is base on ELO, not Glicko-2. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 16:13, 20 June 2009 (UTC)<br /> ::: then [[Toorkild]] isn't in the 2k club. I was pretty sure it was the Glicko. But, it all may be mute. I just realized how few battles it has run - only about 1 per bot. I'll therefore wait a bit before posting anything further on that :) --[[User:Miked0801|Miked0801]] 16:17, 20 June 2009 (UTC)<br /> ::: We're in a weird position with the clubs because it was based on ELO on the old server. ELO on Darkcanuck's server is way lower than it was on the old server, and Glicko-2 is a bit higher -- at least in MegaBot and MiniBot 1v1. As a point of reference, before the old RR server hit a few months of non-stop upwards drift, Dookious was about 2130 and Komarious was about 2085 in mini (prolly a few points higher now). Nevertheless, it's still easy to compare your bot to the competition, arbitrary rating systems aside. =) --[[User:Voidious|Voidious]] 16:26, 20 June 2009 (UTC)<br /> :::: The new server originally matched the old one, but ELO has drifted steadily downwards in the past few months. Why, I don't know. In late 2008, Glicko2 and ELO were in the same range, but now they're quite different. Maybe it's all the recent activity, plus some long-standing bots were removed earlier this year too. In any case, ELO is a relative ranking system so it's the difference between the scores that matters, not the absolute values. But it does leave the ELO clubs in a funny position. --[[User:Darkcanuck|Darkcanuck]] 17:34, 20 June 2009 (UTC)<br /> <br /> <br /> == Fuatisha==<br /> Well, it's nice to see that my nano is giving you so much trouble! Would you happen to have any idea why LBB seems to be having more trouble with it than other adaptive movement nanos? Of course, I wouldn't just be trying to figure out the best things to tweak in it......--[[User:CrazyBassoonist|CrazyBassoonist]] 03:34, 14 February 2010 (UTC)<br /> <br /> It's a number of things:<br /> * It really doesn't have a weakness in its good at any distance I can exploit. [[Moebius]] had a weakness at 260. <br /> * It's movement is adaptive - my gun is not. Plus it has a Very flat movement profile.<br /> * It's gun is just really, really good.<br /> * The opening stop/go movement has a signifigantly different GF profile than its later movements meaning I have to give up hit percentage later to get it out of its opening gambit.<br /> Basically, it is a better overall fighting bot than [[NeophytePattern]] and [[Moebius]], but does worse against weaker bots. If you were to tune anything, tune agaist the masses and you'll probably get #2 (and help me!) :) --[[User:Miked0801|Miked0801]] 05:27, 14 February 2010 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=Talk:Main_Page&diff=19324 2011-05-19T04:16:37Z

<p>Miked0801: ty</p> <hr /> <div>== Why is the &quot;Robo Wiki&quot; icon in the upper left corner so small? ==<br /> The headline speaks for itself. --[[User:Awesomeness|Awesomeness]] 21:08, 3 May 2009 (UTC)<br /> <br /> So small? It seems just right to me really. --[[User:Rednaxela|Rednaxela]] 21:56, 3 May 2009 (UTC)<br /> <br /> Because it is the same size as the old wiki =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 23:41, 3 May 2009 (UTC)<br /> <br /> <br /> http://www.csdgn.org/files/images/robowiki2.png<br /> <br /> I have a solution to this! I was bored so I drew this (though it is probably too big!). I realize I forgot the radar, but to be honest, from this angle it would block to much however. Just consider it a drone! --[[User:Chase-san|Chase]] 21:50, 20 June 2010 (UTC)<br /> <br /> : You could just said that it is a Droid instead of saying that you forgot them... --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 13:36, 21 June 2010 (UTC)<br /> <br /> :: I like it - it looks good :) on the current one you cant really read wiki because its blocked but this looks really good :) --&lt;font style=&quot;font-family:helvetica,arial,sans-serif;font-size:90%;letter-spacing:-1px;&quot;&gt;[[User:Exauge|Exauge]] ◊ [[User talk:Exauge|talk]]&lt;/font&gt; 14:51, 21 June 2010 (UTC)<br /> <br /> :: I suppose I could have. On another note, I notice that some of my shadows are wrong/inconsistent. --[[User:Chase-san|Chase]] 15:30, 21 June 2010 (UTC)<br /> <br /> : Looks really nice! I like it. Of course I have a soft spot for the old one, but this one's also very true to the original idea. And the text is way more readable. --[[User:Voidious|Voidious]] 00:05, 22 June 2010 (UTC)<br /> <br /> http://www.csdgn.org/files/images/robowiki3.png<br /> <br /> I fixed some of my shadow work in this. I made the wording a bit more visible as well (by adding more depth to it). I also made the book lines heavier. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 06:25, 20 July 2010 (UTC)<br /> <br /> http://www.csdgn.org/files/images/robowiki_thumb.png<br /> <br /> Obviously this is to big to go in the corner, but I made a reduced size one. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 06:28, 20 July 2010 (UTC)<br /> <br /> Was a decision ever reached on this, because I am considering redrawing this (but better). &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 20:13, 18 January 2011 (UTC)<br /> <br /> I'm up for changing it and I don't think anybody objected. Just fell off my radar - sorry! I think my only criticism of that first one is that the &quot;IKI&quot; is a little smushed together. --[[User:Voidious|Voidious]] 20:20, 18 January 2011 (UTC)<br /> <br /> Well (I personally think) my art has improved considerably since I drew this. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 21:31, 18 January 2011 (UTC)<br /> <br /> : If nothing else, I will go over it with a pen and clean up the line work. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 21:38, 18 January 2011 (UTC)<br /> <br /> http://www.csdgn.org/files/images/robowiki2_small.png<br /> <br /> Here is the new version. It's a bit cleaner, though it doesn't have as much character (because it is so much cleaner). &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 02:01, 19 January 2011 (UTC)<br /> <br /> Nice stuff, looks pretty good to me :) --[[User:Rednaxela|Rednaxela]] 06:04, 19 January 2011 (UTC)<br /> <br /> So are we going to use it? &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 16:12, 8 February 2011 (UTC)<br /> <br /> Just updated it. I think it looks really nice, it really changes the look of the page a lot more than I expected. Let me know if anyone sees it looking weird anywhere - I'm not exactly a CSS guru. :-P Nice job, Chase! --[[User:Voidious|Voidious]] 17:40, 8 February 2011 (UTC)<br /> <br /> : You just change the $wgLogo, right? I don't think it would affect the page at all. I does feel weird at first, I agree. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 15:18, 9 February 2011 (UTC)<br /> <br /> :: Yeah, but the new one is taller so I had to move the sidebar down a bit. Took me a while to track down the right CSS to change. =) --[[User:Voidious|Voidious]] 15:22, 9 February 2011 (UTC)<br /> <br /> What about the favicon? --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 10:59, 11 February 2011 (UTC)<br /> <br /> == Does robo rumble work? ==<br /> hi im new to robocode, been doing it as part of my uni course and i was wondering, is it possible to run roborumble at home anymore because ive follwed the instructions and none of the battles ive been doing have been uploading.... [[User:Quietus|Quietus]] 15:47, 21 November 2008 (UTC)<br /> <br /> Yep! It sure as he heck still works! The thing is, the rumble.fervir.com server has been kind of broken for a while. You need to point your client at [http://darkcanuck.net/rumble/ this URL] instead now (See [[Darkcanuck/RRServer|here]] for more information). There's new fanciness in that server too :) --[[User:Rednaxela|Rednaxela]] 19:48, 21 November 2008 (UTC)<br /> <br /> == Article count ==<br /> <br /> A couple questions about the article count (after having some trouble Googling for answers). First, why isn't it updating automatically? Is that something I can trigger to update, or add to the &quot;job queue&quot;, does anyone know? (Notice if you edit / preview it is higher than 43, which it reads on the main page right now.) Second, what qualifies as an &quot;article&quot;? Is there a minimum length that a page needs to be (other than not being a user or talk page) to qualify as an article? --[[User:Voidious|Voidious]] 19:56, 12 November 2007 (UTC)<br /> :The main page just updated, it now says 48 articles. Also, the statistics page says that there are 145 pages total, but it is excluding, &quot;talk pages, pages about RoboWiki, minimal 'stub' pages, redirects, and others that probably don't qualify as content pages.&quot; --[[User:AaronR|AaronR]] 20:00, 12 November 2007 (UTC)<br /> <br /> According to the MediaWiki wiki (now that's a mouthful), the main page will come up to date as soon as its HTML cache is invalidated, at which point all of the templates, etc. will be transcluded again. Don't know if that helps... --[[User:AaronR|AaronR]] 20:27, 12 November 2007 (UTC)<br /> <br /> == Font size ==<br /> <br /> Just out of curiosity, why is the font size so large here compared to, say, Wikipedia? I know, I know, it's the same as the old wiki's font, but that wiki didn't have a sidebar. --[[User:AaronR|AaronR]] 07:04, 13 November 2007 (UTC)<br /> <br /> : Primarily because I thought &quot;x-small&quot; was just too small, and yes, it was also just sooo much smaller than the old wiki. I also figured that with the skins options, we could easily give people more choices to choose their own style, anyway. I will confess that tiny fonts for the sake of sleeker designs is a major pet peeve of mine. :-P --[[User:Voidious|Voidious]] 07:12, 13 November 2007 (UTC)<br /> <br /> == Smileys :-) ==<br /> <br /> I would be relly nice if we could somehow support smile, e.g. just as simple as stating:<br /> <br /> &lt;pre&gt;[[Image:HappySmiley.png]]&lt;/pre&gt;<br /> <br /> --[[User:FlemmingLarsen|Flemming N. Larsen]] 09:04, 28 November 2007 (UTC)<br /> <br /> Wikimedia Commons has a [http://commons.wikimedia.org/wiki/Smiley whole section] of GFDL'd or public domain smileys (look at the link at the bottom for more). I don't really see the point though. If you want to upload them and use them, feel free, but I'll stick with =) on the wiki. --&lt;code&gt;[[User:AaronR|AaronR]]&lt;/code&gt; 01:21, 30 November 2007 (UTC)<br /> <br /> == Old wiki ==<br /> The old wiki is not working (error 500), and so my roborumble client (it cannot find the list of partecipants), but i see many client is uploading. What is your solution?<br /> --[[User:Lestofante|Lestofante]] 10:35, 1 Dic 2008 (UTC)<br /> <br /> The clients currently running are just using the last copy of the participants list they downloaded from the old wiki. I emailed PEZ a bit ago and got a reply that he'll look into it so hopefully the old wiki will be up again in not too long. If that ends up taking longer than expected though, we could update/fix the participants page on the new wiki and point clients at that instead. (Note: Don't point clients at the one on the new wiki just yet, it's out of date and such. It needs to be copied over from a downloaded copy of the list from the old wiki) --[[User:Rednaxela|Rednaxela]] 12:00, 1 December 2008 (UTC)<br /> <br /> maybe we can drop definitely the old wiki for roborumble client, or better every ramble server can implements it's own participants list, maybe integrated with general wiki list<br /> --[[User:Lestofante|Lestofante]] 15:13, 1 Dic 2008 (UTC)<br /> <br /> I'd agree that migrating to using the new wiki participants list would be good, though I think some more veteran wikiers/rumblers than myself should give their input before any such switch is made 'official'. As far as keeping a participants list with the rumble server, well, there's only one working rumble server at the moment so I'm not sure what good that would do, and furthermore multiple rumble server would be a bad thing I think becacuse it would divide the processing power that goes towards making the battles. --[[User:Rednaxela|Rednaxela]] 17:47, 1 December 2008 (UTC)<br /> <br /> That's right, then I thing the server have to had a mirror of the wiki's official participants list, so in this case we can continue run our client, simple we cannot modify the list (if the two list are not synchronize together) <br /> --[[User:Lestofante|Lestofante]] 21:49, 1 Dic 2008 (UTC)<br /> <br /> Yeah, the real problem is getting the participants list from the currently-erroring wiki. The RR client has no problem parsing the new wiki format. I may be able to get that from the RoboWiki server when I get home (if it isn't fixed before then). <br /> <br /> The other issue we might encounter in the future would be when we move this wiki to robowiki.net, and we have RR clients pointing to testwiki.roborumble.org, but I don't think forwarding that URL and/or having people update their clients would be a big issue. I'm glad you contacted PEZ about the old wiki's current problems, I've been out of touch for at least a week...<br /> <br /> --[[User:Voidious|Voidious]] 19:03, 2 December 2008 (UTC)<br /> <br /> Okay to mention it here as well for people who haven't been checking up on it... The old wiki is back up! --[[User:Rednaxela|Rednaxela]] 18:43, 9 December 2008 (UTC)<br /> <br /> == mailer error ==<br /> I'm trying to confirm my user e-mail, but I still get &quot;mailer error&quot;. I've tried 3 different and working address... and there is a way for automatically sign the edits?<br /> --[[User:Lestofante|Lestofante]] 22:00, 1 Dic 2008 (UTC)<br /> <br /> : I couldn't get the mailer to work either, but you can easily sign your edits using &lt;nowiki&gt;--~~~~&lt;/nowiki&gt;. See http://meta.wikimedia.org/wiki/Cheatsheet for more tricks. --[[User:Darkcanuck|Darkcanuck]] 03:13, 2 December 2008 (UTC)<br /> <br /> == InterWiki Links ==<br /> Who have fully access to this server apart from [[User:David Alves|David Alves]]? I want both my thai wiki and this wiki a inter-languages link. Please look [[User_talk:Nat#New_Thai_RoboWiki|here]] for more detailed. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 15:16, 15 April 2009 (UTC)<br /> <br /> I have full access, or at least I do if I can remember the password. =) I'll see about logging in and taking a look at the InterWiki stuff. Sorry it took so long to respond about this. --[[User:Voidious|Voidious]] 14:50, 16 April 2009 (UTC)<br /> <br /> Hey Voidious, I believed that the SQL will take less than 1 seconds to copy/past/execute. Plus login/connecting time I think this can be accomplished within a minute so please do asap (or I must say NOW). &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 16:19, 22 April 2009 (UTC)<br /> <br /> Hey Nat - I will add the InterWiki link because I'd like to support your efforts to start a Thai Robocode community and wiki. But I really don't appreciate being commanded to do that (or much of anything, really), and especially to do so &quot;NOW&quot;. Please keep in mind the RoboWiki's only rule: &quot;Pretty please be polite.&quot; --[[User:Voidious|Voidious]] 18:48, 22 April 2009 (UTC)<br /> <br /> Cool, I read up on the InterWiki stuff, added your Thai wiki to the database, and posted a link on the main page. As I can't read Thai, please make sure that looks right and edit it if necessary. =) --[[User:Voidious|Voidious]] 22:54, 22 April 2009 (UTC)<br /> <br /> Sorry for that rude. But anyways, thank you very much. The link at main page is correct. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 01:37, 23 April 2009 (UTC)<br /> <br /> == Database error ==<br /> I didn't know where to put this, but here seems like a decent spot. All my posts are getting this message today (4 times, probably 5 with this one), the posts are still uploaded but the message is:<br /> &lt;pre&gt;<br /> A database query syntax error has occurred. This may indicate a bug in the software.<br /> The last attempted database query was:<br /> (SQL query hidden)<br /> from within function &quot;SearchMySQL4::update&quot;.<br /> MySQL returned error &quot;126: Incorrect key file for table './wikidb/searchindex.MYI'; try to repair it (localhost)&quot;.<br /> &lt;/pre&gt;<br /> <br /> I don't know if ''localhost'' is meant to be from mine point of view, or the server's. Maybe someone else is getting the same messages, I haven't tried to logout/in, because I just thought of that. --[[User:Zyx|zyx]] 23:47, 5 May 2009 (UTC)<br /> : Just like when you go to the mechanic, I didn't get the message this time. Another piece of information may be that all the other 4 posts where at [[Talk:PwnBot‎]], so maybe the problem relies in that page. --[[User:Zyx|zyx]] 23:49, 5 May 2009 (UTC)<br /> <br /> :: I found some mentions of people hitting this, and it sounds like a &quot;repair table&quot; SQL command is the remedy. I've run that now, so hopefully it's fixed. Can you let me know if it happens again? Thanks, --[[User:Voidious|Voidious]] 00:31, 6 May 2009 (UTC)<br /> <br /> ::: Just got it again, and again in the same page [[Talk:PwnBot‎]]. --[[User:Zyx|zyx]] 20:45, 6 May 2009 (UTC)<br /> <br /> :::: Thanks for the info. I saw it as well when I posted the downtime note. I'm guessing the server crashing corrupted the searchindex table -- I'll rerun the &quot;repair table&quot; and post here when I do. I'll also be backing up the database very soon. --[[User:Voidious|Voidious]] 20:52, 6 May 2009 (UTC)<br /> <br /> ::Is it... My fault?! I created that page. It seems whenever I change a page I get it too. It doesn't matter what page I go to. Also, for the majority of today, (for me at least) it seems your server has been down. I've been unable to connect. --[[User:Awesomeness|Awesomeness]] 22:04, 6 May 2009 (UTC)<br /> <br /> ::: It's not your fault, and I saw it on another page too. The server went down for a while as of last night, still not sure what happened, but glad it's back up. I've rerun the &quot;repair table&quot; command, so I think that database error will go away for now. --[[User:Voidious|Voidious]] 22:06, 6 May 2009 (UTC)<br /> <br /> :::: I now know why I can't access the wiki (and roborumble.org) yesterday. Night there, afternoon here. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 00:25, 7 May 2009 (UTC)<br /> <br /> == SourceForge.net Community Choices Awards ==<br /> <br /> &lt;div style=&quot;text-align:center; border: 5px solid #ccc&quot;&gt;<br /> http://sourceforge.net/images/cca/cca_nominate.png<br /> <br /> Please nominate Robocode to SourceForge.net Community Choices Awards!&lt;br /&gt;<br /> [http://sourceforge.net/community/cca09/nominate/?project_name=Robocode&amp;project_url=http://robocode.sourceforge.net/ Nominate Robocode]<br /> &lt;/div&gt;<br /> <br /> Anyone mind to put this to [[MediaWiki:Sitenotice]] or front page? I not sure if I can post to front page. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 10:21, 15 May 2009 (UTC)<br /> <br /> Please nominate Robocode in category of &quot;Best Project for Academia&quot; and &quot;Most Likely to Change the Way You Do Everything&quot;. If you nominate to another category, please post here so other robocoder can nominate in same categories (note that you can nominate in multiple categories) Nevertheless, please [http://sourceforge.net/community/cca09/nominate/?project_name=Robocode&amp;project_url=http://robocode.sourceforge.net/ nominate]! &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 11:26, 18 May 2009 (UTC)<br /> <br /> == [[Special:Disambiguations]] ==<br /> <br /> Do anyone know why the [[Special:Disambiguations]] has spammy report? &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 11:23, 18 May 2009 (UTC)<br /> <br /> == Image Uploads ==<br /> <br /> It looks like the image uploads folder is not set as writable to the wiki. Is this expected to change? -- [[User:Synapse|&lt;font style=&quot;font-size:0.8em;font-variant:small-caps;&quot;&gt;Synapse&lt;/font&gt;]] 05:27, 10 June 2009 (UTC)<br /> <br /> Haven't test yet. If this is true, I think this problem cause due the upgrading of MediaWiki. Voidious, check it please? Another note to Voidious, MediaWiki/1.15 just release =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 13:29, 10 June 2009 (UTC)<br /> <br /> Not sure why it stopped working, but I'll take a look at the image uploads and upgrading MediaWiki this afternoon. (And making a mental note to test that whenever I upgrade. =)) --[[User:Voidious|Voidious]] 15:41, 11 June 2009 (UTC)<br /> <br /> Fixed the uploading issue and upgraded MedaWiki to 1.15. Enjoy. =) --[[User:Voidious|Voidious]] 20:10, 11 June 2009 (UTC)<br /> <br /> == /wiki/PageName-style url ==<br /> <br /> Recently this day I noticed that the /wiki/PageName-style URL is now work. Voidious, why don't you set the &lt;code&gt;$wgArticlePath = &quot;/wiki/$1&quot;&lt;/code&gt; in LocalSettings.php? And I wonder why the old server at 174.132.4.195 now has new wiki code, and available in both /wiki/PageName and ?PageName style (but not /w/index.php?title=PageName style). What's going on? &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 12:56, 27 June 2009 (UTC)<br /> <br /> == Syntax Highlighting ==<br /> <br /> It would be great if we could have syntax highlighting for code snippets. This would make code snippets easier to read. Currently, if I want to read a code snippet from the wiki, I would copy and paste it into my favourite text editor.<br /> <br /> Wikipedia itself seems to use [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi SyntaxHighlight GeSHi].&amp;mdash;<br /> <br /> [[User:Duyn|Duyn]] 14:56, 17 January 2010 (UTC)<br /> <br /> [[User:Voidious/RoboWiki_To-Do]] --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 13:41, 18 January 2010 (UTC)<br /> <br /> Yeah, that's been on my to-do list for a while, I'll try to get it up and running soon. Can't be too tough. =) --[[User:Voidious|Voidious]] 16:12, 19 January 2010 (UTC)<br /> <br /> == Favicon ==<br /> <br /> I just noticed that the new Robowiki doesn't have a favicon. This is easily remedied by copying http://old.robowiki.net/favicon.ico so that it is accessible at http://robowiki.net/favicon.ico --[[User:Skilgannon|Skilgannon]] 18:00, 17 January 2010 (UTC)<br /> <br /> : Will do. --[[User:Voidious|Voidious]] 16:12, 19 January 2010 (UTC)<br /> <br /> == Robocode on Wikipedia ==<br /> <br /> Well, [[wikipedia:Robocode]] article is just challenged for reference, as well as a original research. Please help it by adding reference. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 15:09, 15 April 2010 (UTC)<br /> <br /> Honestly, I believe many things on the wikipedia article, at least 2/3rds of the page, just plain don't belong on Wikiedia, due to valid reasons. In fact I'm not sure anything beyond the overview and the first two sections belong, given how Wikipedia's 'original research' and 'notability' criteria apply to such sections. Even those sections which do make sense to keep to desperately need citations. Essentially, I don't feel the sections [http://en.wikipedia.org/w/index.php?title=Robocode&amp;action=historysubmit&amp;diff=37661690&amp;oldid=35178091 added by PEZ] fit wikipedia's criteria for what belongs. So... I think it does deserve to be challenged for good reason. I don't have time to improve what should stay though. --[[User:Rednaxela|Rednaxela]] 16:39, 15 April 2010 (UTC)<br /> <br /> I'll make more comments on the Wikipedia talk page, but I agree it needs a lot of cleanup and I'm willing to help out with that. I half agree with Rednaxela. The overview and first 2 sections are fine and neutral. The rest could use a lot of cleaning up, but I don't think it all needs just to be axed. Some editing down / revising / adding citations should do the trick. (I think the RoboWiki is a &quot;reliable source&quot;? If not, I don't know what is.) --[[User:Voidious|Voidious]] 19:03, 15 April 2010 (UTC)<br /> <br /> : Well, while I would personally consider Robowiki a &quot;reliable source&quot; for my own purposes, it seems to me it violates some of what is noted on [[wikipedia:Wikipedia:Verifiability#Self-published_sources_.28online_and_paper.29|Wikipedia:Verifiability#Self-published_sources]], in particular how it notes &quot;open wikis&quot; among other things as &quot;largely not acceptable&quot;. Also, note the &quot;no original research&quot; policies, and consider that much of the purpose of Robowiki is for &quot;original research&quot;. There is a significant difference between a source one trusts, and a source that fits Wikipedia's rules. --[[User:Rednaxela|Rednaxela]] 01:54, 16 April 2010 (UTC)<br /> <br /> : Hmm, thanks. I really don't know much about Wikipedia's policies, but just starting to read up on it now. In that case, you are probably right that a lot of stuff needs to just be axed... --[[User:Voidious|Voidious]] 13:46, 16 April 2010 (UTC)<br /> <br /> == &quot;Robocode Guidebook&quot; ==<br /> <br /> ''Migrated to [[Talk:Robocode Guidebook]]''<br /> <br /> == RoboCode Chat / IM ==<br /> <br /> So it is to my understanding that currently the only real way for robocoders to talk is on talk pages on this wiki so I had this idea... what if we had an IM type web chat system for Robocoders to talk :) within a few months i could probably get a website set up to do that and it would use the open-source [https://blueimp.net/ajax/ AJAX project]. What do you all think of the idea? --[[User:Exauge|Exauge]] 00:33, 15 May 2010 (UTC)<br /> <br /> I think we have an (deserted) IRC channel (or not?). But actually I do chat with some Robocoder through GTalk and e-mail. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 00:38, 15 May 2010 (UTC)<br /> <br /> Seems like a lot of work. =) Some of us have each other on IM. I use my handle on AIM and my handle at gmail for GTalk/Jabber. (But my AIM is set so you can't see my status if I don't have you as a buddy.) We used to have [[oldwiki:ContactInfo]], but there's no current page with that kind of info. --[[User:Voidious|Voidious]] 00:41, 15 May 2010 (UTC)<br /> <br /> Hi, anyways I've started working on a Robocode talk page and it's getting to be pretty sweet ;) I can probably have it finished in a few weeks (maybe sooner) and anyways if you like it you will all be very welcome to use it and if it's popular enough I might purchase a domain name for it :) and if not, well it's a good way for me to practice my website building skills :) anyways back to studying for tomorrow's exams lol :S --[[User:Exauge|Exauge]]<br /> <br /> Well, personally anyway, if were to have a robocode live chat place, I'd strongly prefer it be an IRC channel (i.e. on Freenode?). Mostly because I always have an IRC client running anyway, and those without an IRC client can still sign in via a web page (i.e. [http://www.mibbit.com/] and [http://webchat.freenode.net/]). Also, IRC is probably about the most mature system for such things anyway, and it's nearly maintain free to maintain a channel. --[[User:Rednaxela|Rednaxela]] 04:03, 17 May 2010 (UTC)<br /> <br /> == Wall Avoidance ==<br /> <br /> ''moved to [[Talk:DustBunny]]...''<br /> <br /> == Walking to the center of the wall ==<br /> <br /> Well, i'm trying to make a Robot that goes to one of the walls, walk to the center of it an then start to circulate the entire Field, touching the center of each wall.<br /> <br /> Anyway, I'm having problems to take the Robot to the center of one of the walls. That's what i'm doing:<br /> <br /> package MyRobots;<br /> import robocode.*;<br /> import java.awt.*;<br /> <br /> public class Walle extends AdvancedRobot<br /> {<br /> double moveAmount;<br /> int miss = 0, hit = 0;<br /> <br /> public void run() {<br /> <br /> moveAmount = Math.max(getBattleFieldWidth(), getBattleFieldHeight());<br /> <br /> setBodyColor(Color.black);<br /> setGunColor(Color.orange);<br /> setRadarColor(Color.yellow);<br /> setScanColor(Color.black);<br /> setBulletColor(Color.orange);<br /> <br /> turnLeft(getHeading() % 90);<br /> ahead(moveAmount);<br /> <br /> turnGunRight(90);<br /> turnRight(90);<br /> <br /> if((getY() + getWidth()/2) == getBattleFieldHeight() || (getY() - getWidth()/2) == 0) ahead(getX() - (getBattleFieldWidth()/2));<br /> if((getX() + getHeight()/2) == getBattleFieldWidth() || (getX() - getHeight()/2) == 0) ahead(getY() - (getBattleFieldHeight()/2));<br /> while(true) {<br /> }<br /> }<br /> <br /> The problem is obviously with the 2 'ifs', but I really can't get it. Thanks for any help!<br /> <br /> getX() &amp; getY() methods returns double value and you cannot compare them using ==, use something like this<br /> &lt;syntaxhighlight&gt;<br /> epsilon = 0.0001; // or another small value<br /> if (Math.abs((getY() + getWidth()/2) - getBattleFieldHeight()) &lt; eplsilon) {<br /> ahead(getX() - (getBattleFieldWidth()/2));<br /> }<br /> <br /> // or<br /> if (robocode.util.Utils.isNear(getY() + getWidth()/2, getBattleFieldHeight())) {<br /> ahead(getX() - (getBattleFieldWidth()/2));<br /> }<br /> &lt;/syntaxhighlight&gt;<br /> And it's better to ask questions like this on yours page --[[User:Jdev|Jdev]] 16:21, 14 September 2010 (UTC)<br /> <br /> == Strategy ==<br /> <br /> So I'm in high school and I'm in a first year Java class. Right now our project is to create a robot in robocode. The rules are the each battle will be fought with 3 to 4 players, the final battle will be 1 on 1, and we aren't allowed to use Advance Robot. There's so many opions in Robocode that I have no clue what's the best strategy going into this. Help!!!<br /> <br /> Thanks.<br /> <br /> The class [http://robocode.sourceforge.net/docs/robocode/robocode/JuniorRobot.html JuniorRobot] might work well for what you are doing. For your robot just make a class extending JuniorRobot. It could be helpful to override onScannedRobot() and perform actions in there. Also be sure to check out the [[Radar]] page and try to implement one of those radar locks because without a decent radar system your robot will be seriously limited. Just spinning the radar might work OK though. ex turnRadarRight(Double.POSITIVE_INFINITY);<br /> Also be sure to check out all the tutorials on this site.<br /> --&lt;font style=&quot;font-family:helvetica,arial,sans-serif;font-size:90%;letter-spacing:-1px;&quot;&gt;[[User:Exauge|Exauge]] ◊ [[User talk:Exauge|talk]]&lt;/font&gt; 02:56, 15 December 2010 (UTC)<br /> <br /> Well... don't get hit. :-) My advice to get started would be:<br /> * Check out the sample bots first, learn how and why they work.<br /> * Try to beat all the sample bots.<br /> * I'd also check with your teacher about using code from the RoboWiki / internet. There's plenty of code and tutorials available, but it's up to your teacher if you're allowed to use that code (even if the code's license says it's ok).<br /> * A page like [[Melee Strategy]] should be good to get the strategy gears turning.<br /> Good luck!<br /> <br /> --[[User:Voidious|Voidious]] 03:33, 15 December 2010 (UTC)<br /> <br /> == Question Forum ==<br /> <br /> Is there a question forum or something of the sort where people can ask random questions? {{unsigned|Starhammy}}<br /> <br /> No, but actually you can ask on [[Talk:Starhammy|your talk page]]. (I forgot to welcome you properly, so it's my bad you don't know where to ask) --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 12:53, 29 December 2010 (UTC)<br /> <br /> <br /> I got an email from some website (itbhu.ac.in). Apparently an Indian college is hosting a &quot;CodeFest&quot; tournament for about 730 something USD (35000 Indian Rupees, it says), and it's an extension of Robocode; it has different modes including Capture the Flag, and it adds walls to the battlefield itself. My main concern: is it safe to download, ie. it has no viruses or trojan horses whatsoever? --[[User:AWOL|AWOL]] 20:34, 31 January 2011 (UTC)<br /> <br /> : I don't know, but the first prize is only 15000, e.g. about 300 USD. The rest is for second, runner up, stuff like that. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 23:05, 31 January 2011 (UTC)<br /> <br /> : I'm rather confident it's safe. It is hosted at a well reputed Indian university, and the event seems to have some notable partners. I'll point this out though... it appears to be using a build of the &quot;custom-battlefields-workspace&quot; branch of Robocode, which hasn't kept up to date with the main Robocode changes since version 1.7.1.4. This means all known bugs in Robocode 1.7.1.4 likely apply, and some of them are rather... serious... for a competition (i.e. a teleport bug, and a kill-other-robot-threads bug) --[[User:Rednaxela|Rednaxela]] 00:20, 1 February 2011 (UTC)<br /> <br /> :: And also a lot of security vulnerabilities in that branch... --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 12:53, 1 February 2011 (UTC)<br /> <br /> : I've been playing around with it for the last couple days and it's seems to be just a different version of Robocode. Totally safe so far. Like Rednaxela said, it's just a reworked copy of the custom battlefield branch. I will say this, it's been a lot of fun working on how to detect objects in the battlefield... --[[User:KID|KID]] 20:58, 3 February 2011 (UTC)<br /> <br /> == Main Page overhaul ==<br /> <br /> I've been thinking the [[Main Page]] needs a serious overhaul. I'll probably experiment at [[User:Voidious/Main Page]] soon, and anyone else is of course free to do the same. Some of my thoughts apply to the wiki more generally, as well.<br /> * [[User:Rednaxela|Rednaxela]] commented to someone recently about how discussion-based this wiki community is. We've also been looking at [http://www.mediawiki.org/wiki/Extension:LiquidThreads LiquidThreads] because of that. We should probably point this out. I know I never visit Wikipedia's Recent Changes... I wonder how many people miss out on the community aspect of the RoboWiki?<br /> * Current events stuff needs to be removed or updated. <br /> * I don't think we need to list every Challenge. Maybe 2-3 of the recent ones and then links to the categories (which themselves could be polished a bit).<br /> * I think the &quot;Building a Bot&quot; section is really important. It's not bad right now, but could be better. We should probably link to more of the [[:Category:Robocode Documentation|Robocode docs]] stuff. [[Radar]] is the 2nd link and goes to a very detailed page, but [[:Category:Targeting|Targeting]] and [[:Category:Movement|Movement]] are not as newbie friendly.<br /> * Would be good to link to specific details about development tools - like [[:Category:Utilities|Utilities]], [[RoboResearch]], [[Robocode/Eclipse|Robocode/Eclipse]].<br /> * I think the layout and colors could also be revamped - especially that gray background is pretty drab.<br /> * Maybe more prominent and detailed info on the [[RoboRumble]].<br /> * Is the [http://twitter.com/roborumble @roborumble Twitter feed] interesting enough to include? (Like the [http://twitter.com/robowiki @robowiki] tweets on the sidebar.)<br /> I'm sure there's plenty more we could do, just some quick brainstorming for now...<br /> <br /> --[[User:Voidious|Voidious]] 19:01, 10 February 2011 (UTC)<br /> <br /> Another thing I think we need to note (especially to someone who is Wikipedia's editor) is that the RoboWiki is subpage-based, like we like Robocode/Getting_Start and not Getting_Start_to_Robocode. Just my two cents. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 10:59, 11 February 2011 (UTC)<br /> <br /> == About the spam... ==<br /> <br /> http://www.mediawiki.org/wiki/Extension:SpamBlacklist - See bottom of page for spamlists.<br /> http://www.mediawiki.org/wiki/Extension:ConfirmEdit - Has our old math captcha type thing in it.<br /> http://www.mediawiki.org/wiki/Extension:Bad_Behavior - No idea how this is suppose to work<br /> <br /> That is all. :)<br /> &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 16:39, 12 March 2011 (UTC)<br /> <br /> We already use ConfirmEdit in reCAPTCHA mode. I checked SpamBlacklist and it's blacklists don't match anything in the recent spam. Unsure about Bad_Behavior. Now, on the ConfirmEdit page, it does note that as of 2011 spammers seem to have gotten around reCAPTCHA by some means. --[[User:Rednaxela|Rednaxela]] 18:18, 12 March 2011 (UTC)<br /> <br /> I think the trick is to do something custom so that the usual anti-antispam techniques don't work. Just something simple like &quot;What is the next prime number after 7?&quot; or so. --[[User:Skilgannon|Skilgannon]] 08:40, 13 March 2011 (UTC)<br /> <br /> Maybe the spammer wait for autoconfirm to bypass the reCAPTCHA. Voidious, can we change the autoconfirm rules to four edits and ten days? And enable reCAPTCHA for every page edit in non-autoconfirm group? --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 01:41, 14 March 2011 (UTC)<br /> <br /> Ah, good call! I forgot about the autoconfirm stuff. I just changed it to 4 edits/10 days. I checked and we only skip the captcha if you're autoconfirmed, bot, or sysop, so I think we're good. Hopefully we'll be seeing less spam now... --[[User:Voidious|Voidious]] 01:56, 14 March 2011 (UTC)<br /> <br /> Since the spam was still coming in, I updated mediawiki, update the version of the ConfirmEdit extension, AND did some custom hacks to the ConfirmEdit extension to make it simultaneously require both reCAPTCHA and a LaTeX-rendered arithmetic question. Hopefully the combination of the two will keep this spam out for good :) --[[User:Rednaxela|Rednaxela]] 06:06, 19 March 2011 (UTC)<br /> <br /> I thought Voidious still keeping it up to date..... Well, Red, you have checked permission of upload folder, right? Every time Void upgrade the MediaWiki, he needs to re-set the permission of upload folder. Good thought with Recent Change cleanup, though.<br /> <br /> If the spam doesn't stop (as I believe many spambot can solve simple math image, I've face one), maybe you could have them solve equation ;-). --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 07:54, 19 March 2011 (UTC)<br /> <br /> Well, it wasn't *very* behind in versions, but was still 1.15.x as opposed to 1.16.x. Yep, I made sure to check the permissions for that I believe. Yeah, I wouldn't be surprised if some spambots can solve ConfirmEdit's MathCaptcha as-is, but I'm doubting that many spambots are designed to handle both that and reCAPTCHA on the same page. If they do however, I'll keep that suggestion in mind :) --[[User:Rednaxela|Rednaxela]] 13:57, 19 March 2011 (UTC)<br /> <br /> I took a look at the HTTP logs and the recent spambots have been jumping IP addresses, never solving the reCAPTCHA from the same IP that they requested it via. As a precaution, I further tweaked the captcha code to only accept answers as valid if they're from the same IP that was given that captcha. --[[User:Rednaxela|Rednaxela]] 15:34, 19 March 2011 (UTC)<br /> <br /> It seems like we're still getting a high number of users with odd names... might I suggest doing something custom? Doesn't have to be complicated, just &quot;the next prime number after X&quot; or &quot;the next number in the sequence 3 6 9 ...&quot; or some such. The trick is to make it not worth the time and effort for the spammer to implement a custom cracker just for robowiki. --[[User:Skilgannon|Skilgannon]] 13:04, 21 March 2011 (UTC)<br /> <br /> I've looked at the http logs for the IP addresses of those recent users, and they appear to be real people. They browsed some pages, made an account for some reason, browsed some more pages. Btw, an interesting stat: On March 21st so far (based on the server's clock), there have been 76 failed signup attempts due to captcha, and none of them browse pages before the signup attempt. --[[User:Rednaxela|Rednaxela]] 23:25, 21 March 2011 (UTC)<br /> <br /> Just seems odd to have 3 new people in 1 day =) Looks like it's stopped, nice work Red. I'm guessing the usage patterns would be a good attribute to block on if the spam ever picks up again in the future. --[[User:Skilgannon|Skilgannon]] 12:16, 22 March 2011 (UTC)<br /> <br /> Glad I could help by starting a thread about the problem. I also like making custom security. One of my favorite methods is changing the URL to the php or module that does the add page/register, and making a fake captcha (hidden via CSS, putting `anything` in it means you fail the check). :P &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 15:31, 24 March 2011 (UTC)<br /> <br /> ----<br /> Robot Repository is down. Can't get any of the newer bots nor run the game efficiencty :) --[[User:Miked0801|Miked0801]] 16:00, 16 May 2011 (UTC)<br /> I can delete this entry when the issue is fixed...<br /> <br /> It seems that Robot Repository has been down for about a week. Been trying to upload my newest bot but its not working. I need a place to upload my bot. --[[User:Khanguy|Khanguy]] 03:08, 17 May 2011 (UTC)<br /> <br /> Well, one idea for both of you would be to using Google Sites to upload your bot; I started doing that recently and found it to be much simpler and easier than uploading bots onto the repository.--[[User:CrazyBassoonist|CrazyBassoonist]] 03:45, 17 May 2011 (UTC)<br /> <br /> The problem being, I can't get the latest bots for running the rumble nor competing against you CB :) --[[User:Miked0801|Miked0801]] 04:28, 17 May 2011 (UTC)<br /> <br /> The Robocode repository has always been sort of unreliable, hence why I've never used it personally. Anyway, perhaps look for backups of the relevant bots [http://darkcanuck.net/rumble/robots/ here] or [http://rednaxela-robocode.dyndns.org/data/robot_archive/ here]? If missing ones that are avaliable in neither, list the ones that are missing? --[[User:Rednaxela|Rednaxela]] 11:57, 17 May 2011 (UTC)<br /> <br /> Neither of these locations contain CrazyBassoonists latest nanos, Fuatisha 1.1 nor Caligula 1.15. I'm also pretty sure they are missing a few of the other minis that were updated within the last 6 months as well. --[[User:Miked0801|Miked0801]] 14:57, 17 May 2011 (UTC)<br /> <br /> If you go ahead and post your bot, I'll run a few battles to get some rankings. From now on none of my bots will be on the repository, but they won't make the switch until the next version.--[[User:CrazyBassoonist|CrazyBassoonist]] 20:12, 17 May 2011 (UTC)<br /> <br /> Is is possible to upload bots here on the wiki?--[[User:Khanguy|Khanguy]] 23:43, 17 May 2011 (UTC)<br /> <br /> Technically, yes. The issue we ran into is that it forces all filenames to start with upper case, while we all want the package name lower case. But we want the enforced on page titles, so we're kind of stuck. We could setup some kind of external file upload solution on the wiki server, just hasn't been a pressing issue because of other options, like Google Sites. --[[User:Voidious|Voidious]] 00:59, 18 May 2011 (UTC)<br /> <br /> I can't post a new version of my bots because I have no way of testing against your current bots Bassoon :) And I can't really contribute without a complete set of bots for the tournament server stuff. Grrr. --[[User:Miked0801|Miked0801]] 01:25, 18 May 2011 (UTC)<br /> <br /> Hey Voidious, can you upload all the bots currently in the rumble to your dijitari site? or maybe another site. Its to help poor Miked here.--[[User:Khanguy|Khanguy]] 04:21, 18 May 2011 (UTC)<br /> <br /> Yep, here's every JAR in my RoboRumble directory, but I didn't take the time to remove multiple versions of older bots (I'm sure there are a ton). So probably want to cherry pick the ones you need. [http://www.dijitari.com/void/robocode/roborumble_bots.zip roborumble_bots.zip] (69 MB) --[[User:Voidious|Voidious]] 13:42, 18 May 2011 (UTC)<br /> <br /> Dl'ing now. Can't wait to see how things have changed :) --[[User:Miked0801|Miked0801]] 04:16, 19 May 2011 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=Talk:Main_Page&diff=19309 2011-05-18T01:25:06Z

<p>Miked0801: </p> <hr /> <div>== Why is the &quot;Robo Wiki&quot; icon in the upper left corner so small? ==<br /> The headline speaks for itself. --[[User:Awesomeness|Awesomeness]] 21:08, 3 May 2009 (UTC)<br /> <br /> So small? It seems just right to me really. --[[User:Rednaxela|Rednaxela]] 21:56, 3 May 2009 (UTC)<br /> <br /> Because it is the same size as the old wiki =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 23:41, 3 May 2009 (UTC)<br /> <br /> <br /> http://www.csdgn.org/files/images/robowiki2.png<br /> <br /> I have a solution to this! I was bored so I drew this (though it is probably too big!). I realize I forgot the radar, but to be honest, from this angle it would block to much however. Just consider it a drone! --[[User:Chase-san|Chase]] 21:50, 20 June 2010 (UTC)<br /> <br /> : You could just said that it is a Droid instead of saying that you forgot them... --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 13:36, 21 June 2010 (UTC)<br /> <br /> :: I like it - it looks good :) on the current one you cant really read wiki because its blocked but this looks really good :) --&lt;font style=&quot;font-family:helvetica,arial,sans-serif;font-size:90%;letter-spacing:-1px;&quot;&gt;[[User:Exauge|Exauge]] ◊ [[User talk:Exauge|talk]]&lt;/font&gt; 14:51, 21 June 2010 (UTC)<br /> <br /> :: I suppose I could have. On another note, I notice that some of my shadows are wrong/inconsistent. --[[User:Chase-san|Chase]] 15:30, 21 June 2010 (UTC)<br /> <br /> : Looks really nice! I like it. Of course I have a soft spot for the old one, but this one's also very true to the original idea. And the text is way more readable. --[[User:Voidious|Voidious]] 00:05, 22 June 2010 (UTC)<br /> <br /> http://www.csdgn.org/files/images/robowiki3.png<br /> <br /> I fixed some of my shadow work in this. I made the wording a bit more visible as well (by adding more depth to it). I also made the book lines heavier. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 06:25, 20 July 2010 (UTC)<br /> <br /> http://www.csdgn.org/files/images/robowiki_thumb.png<br /> <br /> Obviously this is to big to go in the corner, but I made a reduced size one. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 06:28, 20 July 2010 (UTC)<br /> <br /> Was a decision ever reached on this, because I am considering redrawing this (but better). &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 20:13, 18 January 2011 (UTC)<br /> <br /> I'm up for changing it and I don't think anybody objected. Just fell off my radar - sorry! I think my only criticism of that first one is that the &quot;IKI&quot; is a little smushed together. --[[User:Voidious|Voidious]] 20:20, 18 January 2011 (UTC)<br /> <br /> Well (I personally think) my art has improved considerably since I drew this. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 21:31, 18 January 2011 (UTC)<br /> <br /> : If nothing else, I will go over it with a pen and clean up the line work. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 21:38, 18 January 2011 (UTC)<br /> <br /> http://www.csdgn.org/files/images/robowiki2_small.png<br /> <br /> Here is the new version. It's a bit cleaner, though it doesn't have as much character (because it is so much cleaner). &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 02:01, 19 January 2011 (UTC)<br /> <br /> Nice stuff, looks pretty good to me :) --[[User:Rednaxela|Rednaxela]] 06:04, 19 January 2011 (UTC)<br /> <br /> So are we going to use it? &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 16:12, 8 February 2011 (UTC)<br /> <br /> Just updated it. I think it looks really nice, it really changes the look of the page a lot more than I expected. Let me know if anyone sees it looking weird anywhere - I'm not exactly a CSS guru. :-P Nice job, Chase! --[[User:Voidious|Voidious]] 17:40, 8 February 2011 (UTC)<br /> <br /> : You just change the $wgLogo, right? I don't think it would affect the page at all. I does feel weird at first, I agree. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 15:18, 9 February 2011 (UTC)<br /> <br /> :: Yeah, but the new one is taller so I had to move the sidebar down a bit. Took me a while to track down the right CSS to change. =) --[[User:Voidious|Voidious]] 15:22, 9 February 2011 (UTC)<br /> <br /> What about the favicon? --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 10:59, 11 February 2011 (UTC)<br /> <br /> == Does robo rumble work? ==<br /> hi im new to robocode, been doing it as part of my uni course and i was wondering, is it possible to run roborumble at home anymore because ive follwed the instructions and none of the battles ive been doing have been uploading.... [[User:Quietus|Quietus]] 15:47, 21 November 2008 (UTC)<br /> <br /> Yep! It sure as he heck still works! The thing is, the rumble.fervir.com server has been kind of broken for a while. You need to point your client at [http://darkcanuck.net/rumble/ this URL] instead now (See [[Darkcanuck/RRServer|here]] for more information). There's new fanciness in that server too :) --[[User:Rednaxela|Rednaxela]] 19:48, 21 November 2008 (UTC)<br /> <br /> == Article count ==<br /> <br /> A couple questions about the article count (after having some trouble Googling for answers). First, why isn't it updating automatically? Is that something I can trigger to update, or add to the &quot;job queue&quot;, does anyone know? (Notice if you edit / preview it is higher than 43, which it reads on the main page right now.) Second, what qualifies as an &quot;article&quot;? Is there a minimum length that a page needs to be (other than not being a user or talk page) to qualify as an article? --[[User:Voidious|Voidious]] 19:56, 12 November 2007 (UTC)<br /> :The main page just updated, it now says 48 articles. Also, the statistics page says that there are 145 pages total, but it is excluding, &quot;talk pages, pages about RoboWiki, minimal 'stub' pages, redirects, and others that probably don't qualify as content pages.&quot; --[[User:AaronR|AaronR]] 20:00, 12 November 2007 (UTC)<br /> <br /> According to the MediaWiki wiki (now that's a mouthful), the main page will come up to date as soon as its HTML cache is invalidated, at which point all of the templates, etc. will be transcluded again. Don't know if that helps... --[[User:AaronR|AaronR]] 20:27, 12 November 2007 (UTC)<br /> <br /> == Font size ==<br /> <br /> Just out of curiosity, why is the font size so large here compared to, say, Wikipedia? I know, I know, it's the same as the old wiki's font, but that wiki didn't have a sidebar. --[[User:AaronR|AaronR]] 07:04, 13 November 2007 (UTC)<br /> <br /> : Primarily because I thought &quot;x-small&quot; was just too small, and yes, it was also just sooo much smaller than the old wiki. I also figured that with the skins options, we could easily give people more choices to choose their own style, anyway. I will confess that tiny fonts for the sake of sleeker designs is a major pet peeve of mine. :-P --[[User:Voidious|Voidious]] 07:12, 13 November 2007 (UTC)<br /> <br /> == Smileys :-) ==<br /> <br /> I would be relly nice if we could somehow support smile, e.g. just as simple as stating:<br /> <br /> &lt;pre&gt;[[Image:HappySmiley.png]]&lt;/pre&gt;<br /> <br /> --[[User:FlemmingLarsen|Flemming N. Larsen]] 09:04, 28 November 2007 (UTC)<br /> <br /> Wikimedia Commons has a [http://commons.wikimedia.org/wiki/Smiley whole section] of GFDL'd or public domain smileys (look at the link at the bottom for more). I don't really see the point though. If you want to upload them and use them, feel free, but I'll stick with =) on the wiki. --&lt;code&gt;[[User:AaronR|AaronR]]&lt;/code&gt; 01:21, 30 November 2007 (UTC)<br /> <br /> == Old wiki ==<br /> The old wiki is not working (error 500), and so my roborumble client (it cannot find the list of partecipants), but i see many client is uploading. What is your solution?<br /> --[[User:Lestofante|Lestofante]] 10:35, 1 Dic 2008 (UTC)<br /> <br /> The clients currently running are just using the last copy of the participants list they downloaded from the old wiki. I emailed PEZ a bit ago and got a reply that he'll look into it so hopefully the old wiki will be up again in not too long. If that ends up taking longer than expected though, we could update/fix the participants page on the new wiki and point clients at that instead. (Note: Don't point clients at the one on the new wiki just yet, it's out of date and such. It needs to be copied over from a downloaded copy of the list from the old wiki) --[[User:Rednaxela|Rednaxela]] 12:00, 1 December 2008 (UTC)<br /> <br /> maybe we can drop definitely the old wiki for roborumble client, or better every ramble server can implements it's own participants list, maybe integrated with general wiki list<br /> --[[User:Lestofante|Lestofante]] 15:13, 1 Dic 2008 (UTC)<br /> <br /> I'd agree that migrating to using the new wiki participants list would be good, though I think some more veteran wikiers/rumblers than myself should give their input before any such switch is made 'official'. As far as keeping a participants list with the rumble server, well, there's only one working rumble server at the moment so I'm not sure what good that would do, and furthermore multiple rumble server would be a bad thing I think becacuse it would divide the processing power that goes towards making the battles. --[[User:Rednaxela|Rednaxela]] 17:47, 1 December 2008 (UTC)<br /> <br /> That's right, then I thing the server have to had a mirror of the wiki's official participants list, so in this case we can continue run our client, simple we cannot modify the list (if the two list are not synchronize together) <br /> --[[User:Lestofante|Lestofante]] 21:49, 1 Dic 2008 (UTC)<br /> <br /> Yeah, the real problem is getting the participants list from the currently-erroring wiki. The RR client has no problem parsing the new wiki format. I may be able to get that from the RoboWiki server when I get home (if it isn't fixed before then). <br /> <br /> The other issue we might encounter in the future would be when we move this wiki to robowiki.net, and we have RR clients pointing to testwiki.roborumble.org, but I don't think forwarding that URL and/or having people update their clients would be a big issue. I'm glad you contacted PEZ about the old wiki's current problems, I've been out of touch for at least a week...<br /> <br /> --[[User:Voidious|Voidious]] 19:03, 2 December 2008 (UTC)<br /> <br /> Okay to mention it here as well for people who haven't been checking up on it... The old wiki is back up! --[[User:Rednaxela|Rednaxela]] 18:43, 9 December 2008 (UTC)<br /> <br /> == mailer error ==<br /> I'm trying to confirm my user e-mail, but I still get &quot;mailer error&quot;. I've tried 3 different and working address... and there is a way for automatically sign the edits?<br /> --[[User:Lestofante|Lestofante]] 22:00, 1 Dic 2008 (UTC)<br /> <br /> : I couldn't get the mailer to work either, but you can easily sign your edits using &lt;nowiki&gt;--~~~~&lt;/nowiki&gt;. See http://meta.wikimedia.org/wiki/Cheatsheet for more tricks. --[[User:Darkcanuck|Darkcanuck]] 03:13, 2 December 2008 (UTC)<br /> <br /> == InterWiki Links ==<br /> Who have fully access to this server apart from [[User:David Alves|David Alves]]? I want both my thai wiki and this wiki a inter-languages link. Please look [[User_talk:Nat#New_Thai_RoboWiki|here]] for more detailed. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 15:16, 15 April 2009 (UTC)<br /> <br /> I have full access, or at least I do if I can remember the password. =) I'll see about logging in and taking a look at the InterWiki stuff. Sorry it took so long to respond about this. --[[User:Voidious|Voidious]] 14:50, 16 April 2009 (UTC)<br /> <br /> Hey Voidious, I believed that the SQL will take less than 1 seconds to copy/past/execute. Plus login/connecting time I think this can be accomplished within a minute so please do asap (or I must say NOW). &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 16:19, 22 April 2009 (UTC)<br /> <br /> Hey Nat - I will add the InterWiki link because I'd like to support your efforts to start a Thai Robocode community and wiki. But I really don't appreciate being commanded to do that (or much of anything, really), and especially to do so &quot;NOW&quot;. Please keep in mind the RoboWiki's only rule: &quot;Pretty please be polite.&quot; --[[User:Voidious|Voidious]] 18:48, 22 April 2009 (UTC)<br /> <br /> Cool, I read up on the InterWiki stuff, added your Thai wiki to the database, and posted a link on the main page. As I can't read Thai, please make sure that looks right and edit it if necessary. =) --[[User:Voidious|Voidious]] 22:54, 22 April 2009 (UTC)<br /> <br /> Sorry for that rude. But anyways, thank you very much. The link at main page is correct. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 01:37, 23 April 2009 (UTC)<br /> <br /> == Database error ==<br /> I didn't know where to put this, but here seems like a decent spot. All my posts are getting this message today (4 times, probably 5 with this one), the posts are still uploaded but the message is:<br /> &lt;pre&gt;<br /> A database query syntax error has occurred. This may indicate a bug in the software.<br /> The last attempted database query was:<br /> (SQL query hidden)<br /> from within function &quot;SearchMySQL4::update&quot;.<br /> MySQL returned error &quot;126: Incorrect key file for table './wikidb/searchindex.MYI'; try to repair it (localhost)&quot;.<br /> &lt;/pre&gt;<br /> <br /> I don't know if ''localhost'' is meant to be from mine point of view, or the server's. Maybe someone else is getting the same messages, I haven't tried to logout/in, because I just thought of that. --[[User:Zyx|zyx]] 23:47, 5 May 2009 (UTC)<br /> : Just like when you go to the mechanic, I didn't get the message this time. Another piece of information may be that all the other 4 posts where at [[Talk:PwnBot‎]], so maybe the problem relies in that page. --[[User:Zyx|zyx]] 23:49, 5 May 2009 (UTC)<br /> <br /> :: I found some mentions of people hitting this, and it sounds like a &quot;repair table&quot; SQL command is the remedy. I've run that now, so hopefully it's fixed. Can you let me know if it happens again? Thanks, --[[User:Voidious|Voidious]] 00:31, 6 May 2009 (UTC)<br /> <br /> ::: Just got it again, and again in the same page [[Talk:PwnBot‎]]. --[[User:Zyx|zyx]] 20:45, 6 May 2009 (UTC)<br /> <br /> :::: Thanks for the info. I saw it as well when I posted the downtime note. I'm guessing the server crashing corrupted the searchindex table -- I'll rerun the &quot;repair table&quot; and post here when I do. I'll also be backing up the database very soon. --[[User:Voidious|Voidious]] 20:52, 6 May 2009 (UTC)<br /> <br /> ::Is it... My fault?! I created that page. It seems whenever I change a page I get it too. It doesn't matter what page I go to. Also, for the majority of today, (for me at least) it seems your server has been down. I've been unable to connect. --[[User:Awesomeness|Awesomeness]] 22:04, 6 May 2009 (UTC)<br /> <br /> ::: It's not your fault, and I saw it on another page too. The server went down for a while as of last night, still not sure what happened, but glad it's back up. I've rerun the &quot;repair table&quot; command, so I think that database error will go away for now. --[[User:Voidious|Voidious]] 22:06, 6 May 2009 (UTC)<br /> <br /> :::: I now know why I can't access the wiki (and roborumble.org) yesterday. Night there, afternoon here. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 00:25, 7 May 2009 (UTC)<br /> <br /> == SourceForge.net Community Choices Awards ==<br /> <br /> &lt;div style=&quot;text-align:center; border: 5px solid #ccc&quot;&gt;<br /> http://sourceforge.net/images/cca/cca_nominate.png<br /> <br /> Please nominate Robocode to SourceForge.net Community Choices Awards!&lt;br /&gt;<br /> [http://sourceforge.net/community/cca09/nominate/?project_name=Robocode&amp;project_url=http://robocode.sourceforge.net/ Nominate Robocode]<br /> &lt;/div&gt;<br /> <br /> Anyone mind to put this to [[MediaWiki:Sitenotice]] or front page? I not sure if I can post to front page. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 10:21, 15 May 2009 (UTC)<br /> <br /> Please nominate Robocode in category of &quot;Best Project for Academia&quot; and &quot;Most Likely to Change the Way You Do Everything&quot;. If you nominate to another category, please post here so other robocoder can nominate in same categories (note that you can nominate in multiple categories) Nevertheless, please [http://sourceforge.net/community/cca09/nominate/?project_name=Robocode&amp;project_url=http://robocode.sourceforge.net/ nominate]! &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 11:26, 18 May 2009 (UTC)<br /> <br /> == [[Special:Disambiguations]] ==<br /> <br /> Do anyone know why the [[Special:Disambiguations]] has spammy report? &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 11:23, 18 May 2009 (UTC)<br /> <br /> == Image Uploads ==<br /> <br /> It looks like the image uploads folder is not set as writable to the wiki. Is this expected to change? -- [[User:Synapse|&lt;font style=&quot;font-size:0.8em;font-variant:small-caps;&quot;&gt;Synapse&lt;/font&gt;]] 05:27, 10 June 2009 (UTC)<br /> <br /> Haven't test yet. If this is true, I think this problem cause due the upgrading of MediaWiki. Voidious, check it please? Another note to Voidious, MediaWiki/1.15 just release =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 13:29, 10 June 2009 (UTC)<br /> <br /> Not sure why it stopped working, but I'll take a look at the image uploads and upgrading MediaWiki this afternoon. (And making a mental note to test that whenever I upgrade. =)) --[[User:Voidious|Voidious]] 15:41, 11 June 2009 (UTC)<br /> <br /> Fixed the uploading issue and upgraded MedaWiki to 1.15. Enjoy. =) --[[User:Voidious|Voidious]] 20:10, 11 June 2009 (UTC)<br /> <br /> == /wiki/PageName-style url ==<br /> <br /> Recently this day I noticed that the /wiki/PageName-style URL is now work. Voidious, why don't you set the &lt;code&gt;$wgArticlePath = &quot;/wiki/$1&quot;&lt;/code&gt; in LocalSettings.php? And I wonder why the old server at 174.132.4.195 now has new wiki code, and available in both /wiki/PageName and ?PageName style (but not /w/index.php?title=PageName style). What's going on? &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 12:56, 27 June 2009 (UTC)<br /> <br /> == Syntax Highlighting ==<br /> <br /> It would be great if we could have syntax highlighting for code snippets. This would make code snippets easier to read. Currently, if I want to read a code snippet from the wiki, I would copy and paste it into my favourite text editor.<br /> <br /> Wikipedia itself seems to use [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi SyntaxHighlight GeSHi].&amp;mdash;<br /> <br /> [[User:Duyn|Duyn]] 14:56, 17 January 2010 (UTC)<br /> <br /> [[User:Voidious/RoboWiki_To-Do]] --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 13:41, 18 January 2010 (UTC)<br /> <br /> Yeah, that's been on my to-do list for a while, I'll try to get it up and running soon. Can't be too tough. =) --[[User:Voidious|Voidious]] 16:12, 19 January 2010 (UTC)<br /> <br /> == Favicon ==<br /> <br /> I just noticed that the new Robowiki doesn't have a favicon. This is easily remedied by copying http://old.robowiki.net/favicon.ico so that it is accessible at http://robowiki.net/favicon.ico --[[User:Skilgannon|Skilgannon]] 18:00, 17 January 2010 (UTC)<br /> <br /> : Will do. --[[User:Voidious|Voidious]] 16:12, 19 January 2010 (UTC)<br /> <br /> == Robocode on Wikipedia ==<br /> <br /> Well, [[wikipedia:Robocode]] article is just challenged for reference, as well as a original research. Please help it by adding reference. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 15:09, 15 April 2010 (UTC)<br /> <br /> Honestly, I believe many things on the wikipedia article, at least 2/3rds of the page, just plain don't belong on Wikiedia, due to valid reasons. In fact I'm not sure anything beyond the overview and the first two sections belong, given how Wikipedia's 'original research' and 'notability' criteria apply to such sections. Even those sections which do make sense to keep to desperately need citations. Essentially, I don't feel the sections [http://en.wikipedia.org/w/index.php?title=Robocode&amp;action=historysubmit&amp;diff=37661690&amp;oldid=35178091 added by PEZ] fit wikipedia's criteria for what belongs. So... I think it does deserve to be challenged for good reason. I don't have time to improve what should stay though. --[[User:Rednaxela|Rednaxela]] 16:39, 15 April 2010 (UTC)<br /> <br /> I'll make more comments on the Wikipedia talk page, but I agree it needs a lot of cleanup and I'm willing to help out with that. I half agree with Rednaxela. The overview and first 2 sections are fine and neutral. The rest could use a lot of cleaning up, but I don't think it all needs just to be axed. Some editing down / revising / adding citations should do the trick. (I think the RoboWiki is a &quot;reliable source&quot;? If not, I don't know what is.) --[[User:Voidious|Voidious]] 19:03, 15 April 2010 (UTC)<br /> <br /> : Well, while I would personally consider Robowiki a &quot;reliable source&quot; for my own purposes, it seems to me it violates some of what is noted on [[wikipedia:Wikipedia:Verifiability#Self-published_sources_.28online_and_paper.29|Wikipedia:Verifiability#Self-published_sources]], in particular how it notes &quot;open wikis&quot; among other things as &quot;largely not acceptable&quot;. Also, note the &quot;no original research&quot; policies, and consider that much of the purpose of Robowiki is for &quot;original research&quot;. There is a significant difference between a source one trusts, and a source that fits Wikipedia's rules. --[[User:Rednaxela|Rednaxela]] 01:54, 16 April 2010 (UTC)<br /> <br /> : Hmm, thanks. I really don't know much about Wikipedia's policies, but just starting to read up on it now. In that case, you are probably right that a lot of stuff needs to just be axed... --[[User:Voidious|Voidious]] 13:46, 16 April 2010 (UTC)<br /> <br /> == &quot;Robocode Guidebook&quot; ==<br /> <br /> ''Migrated to [[Talk:Robocode Guidebook]]''<br /> <br /> == RoboCode Chat / IM ==<br /> <br /> So it is to my understanding that currently the only real way for robocoders to talk is on talk pages on this wiki so I had this idea... what if we had an IM type web chat system for Robocoders to talk :) within a few months i could probably get a website set up to do that and it would use the open-source [https://blueimp.net/ajax/ AJAX project]. What do you all think of the idea? --[[User:Exauge|Exauge]] 00:33, 15 May 2010 (UTC)<br /> <br /> I think we have an (deserted) IRC channel (or not?). But actually I do chat with some Robocoder through GTalk and e-mail. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 00:38, 15 May 2010 (UTC)<br /> <br /> Seems like a lot of work. =) Some of us have each other on IM. I use my handle on AIM and my handle at gmail for GTalk/Jabber. (But my AIM is set so you can't see my status if I don't have you as a buddy.) We used to have [[oldwiki:ContactInfo]], but there's no current page with that kind of info. --[[User:Voidious|Voidious]] 00:41, 15 May 2010 (UTC)<br /> <br /> Hi, anyways I've started working on a Robocode talk page and it's getting to be pretty sweet ;) I can probably have it finished in a few weeks (maybe sooner) and anyways if you like it you will all be very welcome to use it and if it's popular enough I might purchase a domain name for it :) and if not, well it's a good way for me to practice my website building skills :) anyways back to studying for tomorrow's exams lol :S --[[User:Exauge|Exauge]]<br /> <br /> Well, personally anyway, if were to have a robocode live chat place, I'd strongly prefer it be an IRC channel (i.e. on Freenode?). Mostly because I always have an IRC client running anyway, and those without an IRC client can still sign in via a web page (i.e. [http://www.mibbit.com/] and [http://webchat.freenode.net/]). Also, IRC is probably about the most mature system for such things anyway, and it's nearly maintain free to maintain a channel. --[[User:Rednaxela|Rednaxela]] 04:03, 17 May 2010 (UTC)<br /> <br /> == Wall Avoidance ==<br /> <br /> ''moved to [[Talk:DustBunny]]...''<br /> <br /> == Walking to the center of the wall ==<br /> <br /> Well, i'm trying to make a Robot that goes to one of the walls, walk to the center of it an then start to circulate the entire Field, touching the center of each wall.<br /> <br /> Anyway, I'm having problems to take the Robot to the center of one of the walls. That's what i'm doing:<br /> <br /> package MyRobots;<br /> import robocode.*;<br /> import java.awt.*;<br /> <br /> public class Walle extends AdvancedRobot<br /> {<br /> double moveAmount;<br /> int miss = 0, hit = 0;<br /> <br /> public void run() {<br /> <br /> moveAmount = Math.max(getBattleFieldWidth(), getBattleFieldHeight());<br /> <br /> setBodyColor(Color.black);<br /> setGunColor(Color.orange);<br /> setRadarColor(Color.yellow);<br /> setScanColor(Color.black);<br /> setBulletColor(Color.orange);<br /> <br /> turnLeft(getHeading() % 90);<br /> ahead(moveAmount);<br /> <br /> turnGunRight(90);<br /> turnRight(90);<br /> <br /> if((getY() + getWidth()/2) == getBattleFieldHeight() || (getY() - getWidth()/2) == 0) ahead(getX() - (getBattleFieldWidth()/2));<br /> if((getX() + getHeight()/2) == getBattleFieldWidth() || (getX() - getHeight()/2) == 0) ahead(getY() - (getBattleFieldHeight()/2));<br /> while(true) {<br /> }<br /> }<br /> <br /> The problem is obviously with the 2 'ifs', but I really can't get it. Thanks for any help!<br /> <br /> getX() &amp; getY() methods returns double value and you cannot compare them using ==, use something like this<br /> &lt;syntaxhighlight&gt;<br /> epsilon = 0.0001; // or another small value<br /> if (Math.abs((getY() + getWidth()/2) - getBattleFieldHeight()) &lt; eplsilon) {<br /> ahead(getX() - (getBattleFieldWidth()/2));<br /> }<br /> <br /> // or<br /> if (robocode.util.Utils.isNear(getY() + getWidth()/2, getBattleFieldHeight())) {<br /> ahead(getX() - (getBattleFieldWidth()/2));<br /> }<br /> &lt;/syntaxhighlight&gt;<br /> And it's better to ask questions like this on yours page --[[User:Jdev|Jdev]] 16:21, 14 September 2010 (UTC)<br /> <br /> == Strategy ==<br /> <br /> So I'm in high school and I'm in a first year Java class. Right now our project is to create a robot in robocode. The rules are the each battle will be fought with 3 to 4 players, the final battle will be 1 on 1, and we aren't allowed to use Advance Robot. There's so many opions in Robocode that I have no clue what's the best strategy going into this. Help!!!<br /> <br /> Thanks.<br /> <br /> The class [http://robocode.sourceforge.net/docs/robocode/robocode/JuniorRobot.html JuniorRobot] might work well for what you are doing. For your robot just make a class extending JuniorRobot. It could be helpful to override onScannedRobot() and perform actions in there. Also be sure to check out the [[Radar]] page and try to implement one of those radar locks because without a decent radar system your robot will be seriously limited. Just spinning the radar might work OK though. ex turnRadarRight(Double.POSITIVE_INFINITY);<br /> Also be sure to check out all the tutorials on this site.<br /> --&lt;font style=&quot;font-family:helvetica,arial,sans-serif;font-size:90%;letter-spacing:-1px;&quot;&gt;[[User:Exauge|Exauge]] ◊ [[User talk:Exauge|talk]]&lt;/font&gt; 02:56, 15 December 2010 (UTC)<br /> <br /> Well... don't get hit. :-) My advice to get started would be:<br /> * Check out the sample bots first, learn how and why they work.<br /> * Try to beat all the sample bots.<br /> * I'd also check with your teacher about using code from the RoboWiki / internet. There's plenty of code and tutorials available, but it's up to your teacher if you're allowed to use that code (even if the code's license says it's ok).<br /> * A page like [[Melee Strategy]] should be good to get the strategy gears turning.<br /> Good luck!<br /> <br /> --[[User:Voidious|Voidious]] 03:33, 15 December 2010 (UTC)<br /> <br /> == Question Forum ==<br /> <br /> Is there a question forum or something of the sort where people can ask random questions? {{unsigned|Starhammy}}<br /> <br /> No, but actually you can ask on [[Talk:Starhammy|your talk page]]. (I forgot to welcome you properly, so it's my bad you don't know where to ask) --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 12:53, 29 December 2010 (UTC)<br /> <br /> <br /> I got an email from some website (itbhu.ac.in). Apparently an Indian college is hosting a &quot;CodeFest&quot; tournament for about 730 something USD (35000 Indian Rupees, it says), and it's an extension of Robocode; it has different modes including Capture the Flag, and it adds walls to the battlefield itself. My main concern: is it safe to download, ie. it has no viruses or trojan horses whatsoever? --[[User:AWOL|AWOL]] 20:34, 31 January 2011 (UTC)<br /> <br /> : I don't know, but the first prize is only 15000, e.g. about 300 USD. The rest is for second, runner up, stuff like that. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 23:05, 31 January 2011 (UTC)<br /> <br /> : I'm rather confident it's safe. It is hosted at a well reputed Indian university, and the event seems to have some notable partners. I'll point this out though... it appears to be using a build of the &quot;custom-battlefields-workspace&quot; branch of Robocode, which hasn't kept up to date with the main Robocode changes since version 1.7.1.4. This means all known bugs in Robocode 1.7.1.4 likely apply, and some of them are rather... serious... for a competition (i.e. a teleport bug, and a kill-other-robot-threads bug) --[[User:Rednaxela|Rednaxela]] 00:20, 1 February 2011 (UTC)<br /> <br /> :: And also a lot of security vulnerabilities in that branch... --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 12:53, 1 February 2011 (UTC)<br /> <br /> : I've been playing around with it for the last couple days and it's seems to be just a different version of Robocode. Totally safe so far. Like Rednaxela said, it's just a reworked copy of the custom battlefield branch. I will say this, it's been a lot of fun working on how to detect objects in the battlefield... --[[User:KID|KID]] 20:58, 3 February 2011 (UTC)<br /> <br /> == Main Page overhaul ==<br /> <br /> I've been thinking the [[Main Page]] needs a serious overhaul. I'll probably experiment at [[User:Voidious/Main Page]] soon, and anyone else is of course free to do the same. Some of my thoughts apply to the wiki more generally, as well.<br /> * [[User:Rednaxela|Rednaxela]] commented to someone recently about how discussion-based this wiki community is. We've also been looking at [http://www.mediawiki.org/wiki/Extension:LiquidThreads LiquidThreads] because of that. We should probably point this out. I know I never visit Wikipedia's Recent Changes... I wonder how many people miss out on the community aspect of the RoboWiki?<br /> * Current events stuff needs to be removed or updated. <br /> * I don't think we need to list every Challenge. Maybe 2-3 of the recent ones and then links to the categories (which themselves could be polished a bit).<br /> * I think the &quot;Building a Bot&quot; section is really important. It's not bad right now, but could be better. We should probably link to more of the [[:Category:Robocode Documentation|Robocode docs]] stuff. [[Radar]] is the 2nd link and goes to a very detailed page, but [[:Category:Targeting|Targeting]] and [[:Category:Movement|Movement]] are not as newbie friendly.<br /> * Would be good to link to specific details about development tools - like [[:Category:Utilities|Utilities]], [[RoboResearch]], [[Robocode/Eclipse|Robocode/Eclipse]].<br /> * I think the layout and colors could also be revamped - especially that gray background is pretty drab.<br /> * Maybe more prominent and detailed info on the [[RoboRumble]].<br /> * Is the [http://twitter.com/roborumble @roborumble Twitter feed] interesting enough to include? (Like the [http://twitter.com/robowiki @robowiki] tweets on the sidebar.)<br /> I'm sure there's plenty more we could do, just some quick brainstorming for now...<br /> <br /> --[[User:Voidious|Voidious]] 19:01, 10 February 2011 (UTC)<br /> <br /> Another thing I think we need to note (especially to someone who is Wikipedia's editor) is that the RoboWiki is subpage-based, like we like Robocode/Getting_Start and not Getting_Start_to_Robocode. Just my two cents. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 10:59, 11 February 2011 (UTC)<br /> <br /> == About the spam... ==<br /> <br /> http://www.mediawiki.org/wiki/Extension:SpamBlacklist - See bottom of page for spamlists.<br /> http://www.mediawiki.org/wiki/Extension:ConfirmEdit - Has our old math captcha type thing in it.<br /> http://www.mediawiki.org/wiki/Extension:Bad_Behavior - No idea how this is suppose to work<br /> <br /> That is all. :)<br /> &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 16:39, 12 March 2011 (UTC)<br /> <br /> We already use ConfirmEdit in reCAPTCHA mode. I checked SpamBlacklist and it's blacklists don't match anything in the recent spam. Unsure about Bad_Behavior. Now, on the ConfirmEdit page, it does note that as of 2011 spammers seem to have gotten around reCAPTCHA by some means. --[[User:Rednaxela|Rednaxela]] 18:18, 12 March 2011 (UTC)<br /> <br /> I think the trick is to do something custom so that the usual anti-antispam techniques don't work. Just something simple like &quot;What is the next prime number after 7?&quot; or so. --[[User:Skilgannon|Skilgannon]] 08:40, 13 March 2011 (UTC)<br /> <br /> Maybe the spammer wait for autoconfirm to bypass the reCAPTCHA. Voidious, can we change the autoconfirm rules to four edits and ten days? And enable reCAPTCHA for every page edit in non-autoconfirm group? --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 01:41, 14 March 2011 (UTC)<br /> <br /> Ah, good call! I forgot about the autoconfirm stuff. I just changed it to 4 edits/10 days. I checked and we only skip the captcha if you're autoconfirmed, bot, or sysop, so I think we're good. Hopefully we'll be seeing less spam now... --[[User:Voidious|Voidious]] 01:56, 14 March 2011 (UTC)<br /> <br /> Since the spam was still coming in, I updated mediawiki, update the version of the ConfirmEdit extension, AND did some custom hacks to the ConfirmEdit extension to make it simultaneously require both reCAPTCHA and a LaTeX-rendered arithmetic question. Hopefully the combination of the two will keep this spam out for good :) --[[User:Rednaxela|Rednaxela]] 06:06, 19 March 2011 (UTC)<br /> <br /> I thought Voidious still keeping it up to date..... Well, Red, you have checked permission of upload folder, right? Every time Void upgrade the MediaWiki, he needs to re-set the permission of upload folder. Good thought with Recent Change cleanup, though.<br /> <br /> If the spam doesn't stop (as I believe many spambot can solve simple math image, I've face one), maybe you could have them solve equation ;-). --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 07:54, 19 March 2011 (UTC)<br /> <br /> Well, it wasn't *very* behind in versions, but was still 1.15.x as opposed to 1.16.x. Yep, I made sure to check the permissions for that I believe. Yeah, I wouldn't be surprised if some spambots can solve ConfirmEdit's MathCaptcha as-is, but I'm doubting that many spambots are designed to handle both that and reCAPTCHA on the same page. If they do however, I'll keep that suggestion in mind :) --[[User:Rednaxela|Rednaxela]] 13:57, 19 March 2011 (UTC)<br /> <br /> I took a look at the HTTP logs and the recent spambots have been jumping IP addresses, never solving the reCAPTCHA from the same IP that they requested it via. As a precaution, I further tweaked the captcha code to only accept answers as valid if they're from the same IP that was given that captcha. --[[User:Rednaxela|Rednaxela]] 15:34, 19 March 2011 (UTC)<br /> <br /> It seems like we're still getting a high number of users with odd names... might I suggest doing something custom? Doesn't have to be complicated, just &quot;the next prime number after X&quot; or &quot;the next number in the sequence 3 6 9 ...&quot; or some such. The trick is to make it not worth the time and effort for the spammer to implement a custom cracker just for robowiki. --[[User:Skilgannon|Skilgannon]] 13:04, 21 March 2011 (UTC)<br /> <br /> I've looked at the http logs for the IP addresses of those recent users, and they appear to be real people. They browsed some pages, made an account for some reason, browsed some more pages. Btw, an interesting stat: On March 21st so far (based on the server's clock), there have been 76 failed signup attempts due to captcha, and none of them browse pages before the signup attempt. --[[User:Rednaxela|Rednaxela]] 23:25, 21 March 2011 (UTC)<br /> <br /> Just seems odd to have 3 new people in 1 day =) Looks like it's stopped, nice work Red. I'm guessing the usage patterns would be a good attribute to block on if the spam ever picks up again in the future. --[[User:Skilgannon|Skilgannon]] 12:16, 22 March 2011 (UTC)<br /> <br /> Glad I could help by starting a thread about the problem. I also like making custom security. One of my favorite methods is changing the URL to the php or module that does the add page/register, and making a fake captcha (hidden via CSS, putting `anything` in it means you fail the check). :P &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 15:31, 24 March 2011 (UTC)<br /> <br /> ----<br /> Robot Repository is down. Can't get any of the newer bots nor run the game efficiencty :) --[[User:Miked0801|Miked0801]] 16:00, 16 May 2011 (UTC)<br /> I can delete this entry when the issue is fixed...<br /> <br /> It seems that Robot Repository has been down for about a week. Been trying to upload my newest bot but its not working. I need a place to upload my bot. --[[User:Khanguy|Khanguy]] 03:08, 17 May 2011 (UTC)<br /> <br /> Well, one idea for both of you would be to using Google Sites to upload your bot; I started doing that recently and found it to be much simpler and easier than uploading bots onto the repository.--[[User:CrazyBassoonist|CrazyBassoonist]] 03:45, 17 May 2011 (UTC)<br /> <br /> The problem being, I can't get the latest bots for running the rumble nor competing against you CB :) --[[User:Miked0801|Miked0801]] 04:28, 17 May 2011 (UTC)<br /> <br /> The Robocode repository has always been sort of unreliable, hence why I've never used it personally. Anyway, perhaps look for backups of the relevant bots [http://darkcanuck.net/rumble/robots/ here] or [http://rednaxela-robocode.dyndns.org/data/robot_archive/ here]? If missing ones that are avaliable in neither, list the ones that are missing? --[[User:Rednaxela|Rednaxela]] 11:57, 17 May 2011 (UTC)<br /> <br /> Neither of these locations contain CrazyBassoonists latest nanos, Fuatisha 1.1 nor Caligula 1.15. I'm also pretty sure they are missing a few of the other minis that were updated within the last 6 months as well. --[[User:Miked0801|Miked0801]] 14:57, 17 May 2011 (UTC)<br /> <br /> If you go ahead and post your bot, I'll run a few battles to get some rankings. From now on none of my bots will be on the repository, but they won't make the switch until the next version.--[[User:CrazyBassoonist|CrazyBassoonist]] 20:12, 17 May 2011 (UTC)<br /> <br /> Is is possible to upload bots here on the wiki?--[[User:Khanguy|Khanguy]] 23:43, 17 May 2011 (UTC)<br /> <br /> Technically, yes. The issue we ran into is that it forces all filenames to start with upper case, while we all want the package name lower case. But we want the enforced on page titles, so we're kind of stuck. We could setup some kind of external file upload solution on the wiki server, just hasn't been a pressing issue because of other options, like Google Sites. --[[User:Voidious|Voidious]] 00:59, 18 May 2011 (UTC)<br /> <br /> I can't post a new version of my bots because I have no way of testing against your current bots Bassoon :) And I can't really contribute without a complete set of bots for the tournament server stuff. Grrr. --[[User:Miked0801|Miked0801]] 01:25, 18 May 2011 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=Talk:Main_Page&diff=19300 2011-05-17T14:57:38Z

<p>Miked0801: </p> <hr /> <div>== Why is the &quot;Robo Wiki&quot; icon in the upper left corner so small? ==<br /> The headline speaks for itself. --[[User:Awesomeness|Awesomeness]] 21:08, 3 May 2009 (UTC)<br /> <br /> So small? It seems just right to me really. --[[User:Rednaxela|Rednaxela]] 21:56, 3 May 2009 (UTC)<br /> <br /> Because it is the same size as the old wiki =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 23:41, 3 May 2009 (UTC)<br /> <br /> <br /> http://www.csdgn.org/files/images/robowiki2.png<br /> <br /> I have a solution to this! I was bored so I drew this (though it is probably too big!). I realize I forgot the radar, but to be honest, from this angle it would block to much however. Just consider it a drone! --[[User:Chase-san|Chase]] 21:50, 20 June 2010 (UTC)<br /> <br /> : You could just said that it is a Droid instead of saying that you forgot them... --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 13:36, 21 June 2010 (UTC)<br /> <br /> :: I like it - it looks good :) on the current one you cant really read wiki because its blocked but this looks really good :) --&lt;font style=&quot;font-family:helvetica,arial,sans-serif;font-size:90%;letter-spacing:-1px;&quot;&gt;[[User:Exauge|Exauge]] ◊ [[User talk:Exauge|talk]]&lt;/font&gt; 14:51, 21 June 2010 (UTC)<br /> <br /> :: I suppose I could have. On another note, I notice that some of my shadows are wrong/inconsistent. --[[User:Chase-san|Chase]] 15:30, 21 June 2010 (UTC)<br /> <br /> : Looks really nice! I like it. Of course I have a soft spot for the old one, but this one's also very true to the original idea. And the text is way more readable. --[[User:Voidious|Voidious]] 00:05, 22 June 2010 (UTC)<br /> <br /> http://www.csdgn.org/files/images/robowiki3.png<br /> <br /> I fixed some of my shadow work in this. I made the wording a bit more visible as well (by adding more depth to it). I also made the book lines heavier. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 06:25, 20 July 2010 (UTC)<br /> <br /> http://www.csdgn.org/files/images/robowiki_thumb.png<br /> <br /> Obviously this is to big to go in the corner, but I made a reduced size one. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 06:28, 20 July 2010 (UTC)<br /> <br /> Was a decision ever reached on this, because I am considering redrawing this (but better). &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 20:13, 18 January 2011 (UTC)<br /> <br /> I'm up for changing it and I don't think anybody objected. Just fell off my radar - sorry! I think my only criticism of that first one is that the &quot;IKI&quot; is a little smushed together. --[[User:Voidious|Voidious]] 20:20, 18 January 2011 (UTC)<br /> <br /> Well (I personally think) my art has improved considerably since I drew this. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 21:31, 18 January 2011 (UTC)<br /> <br /> : If nothing else, I will go over it with a pen and clean up the line work. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 21:38, 18 January 2011 (UTC)<br /> <br /> http://www.csdgn.org/files/images/robowiki2_small.png<br /> <br /> Here is the new version. It's a bit cleaner, though it doesn't have as much character (because it is so much cleaner). &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 02:01, 19 January 2011 (UTC)<br /> <br /> Nice stuff, looks pretty good to me :) --[[User:Rednaxela|Rednaxela]] 06:04, 19 January 2011 (UTC)<br /> <br /> So are we going to use it? &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 16:12, 8 February 2011 (UTC)<br /> <br /> Just updated it. I think it looks really nice, it really changes the look of the page a lot more than I expected. Let me know if anyone sees it looking weird anywhere - I'm not exactly a CSS guru. :-P Nice job, Chase! --[[User:Voidious|Voidious]] 17:40, 8 February 2011 (UTC)<br /> <br /> : You just change the $wgLogo, right? I don't think it would affect the page at all. I does feel weird at first, I agree. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 15:18, 9 February 2011 (UTC)<br /> <br /> :: Yeah, but the new one is taller so I had to move the sidebar down a bit. Took me a while to track down the right CSS to change. =) --[[User:Voidious|Voidious]] 15:22, 9 February 2011 (UTC)<br /> <br /> What about the favicon? --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 10:59, 11 February 2011 (UTC)<br /> <br /> == Does robo rumble work? ==<br /> hi im new to robocode, been doing it as part of my uni course and i was wondering, is it possible to run roborumble at home anymore because ive follwed the instructions and none of the battles ive been doing have been uploading.... [[User:Quietus|Quietus]] 15:47, 21 November 2008 (UTC)<br /> <br /> Yep! It sure as he heck still works! The thing is, the rumble.fervir.com server has been kind of broken for a while. You need to point your client at [http://darkcanuck.net/rumble/ this URL] instead now (See [[Darkcanuck/RRServer|here]] for more information). There's new fanciness in that server too :) --[[User:Rednaxela|Rednaxela]] 19:48, 21 November 2008 (UTC)<br /> <br /> == Article count ==<br /> <br /> A couple questions about the article count (after having some trouble Googling for answers). First, why isn't it updating automatically? Is that something I can trigger to update, or add to the &quot;job queue&quot;, does anyone know? (Notice if you edit / preview it is higher than 43, which it reads on the main page right now.) Second, what qualifies as an &quot;article&quot;? Is there a minimum length that a page needs to be (other than not being a user or talk page) to qualify as an article? --[[User:Voidious|Voidious]] 19:56, 12 November 2007 (UTC)<br /> :The main page just updated, it now says 48 articles. Also, the statistics page says that there are 145 pages total, but it is excluding, &quot;talk pages, pages about RoboWiki, minimal 'stub' pages, redirects, and others that probably don't qualify as content pages.&quot; --[[User:AaronR|AaronR]] 20:00, 12 November 2007 (UTC)<br /> <br /> According to the MediaWiki wiki (now that's a mouthful), the main page will come up to date as soon as its HTML cache is invalidated, at which point all of the templates, etc. will be transcluded again. Don't know if that helps... --[[User:AaronR|AaronR]] 20:27, 12 November 2007 (UTC)<br /> <br /> == Font size ==<br /> <br /> Just out of curiosity, why is the font size so large here compared to, say, Wikipedia? I know, I know, it's the same as the old wiki's font, but that wiki didn't have a sidebar. --[[User:AaronR|AaronR]] 07:04, 13 November 2007 (UTC)<br /> <br /> : Primarily because I thought &quot;x-small&quot; was just too small, and yes, it was also just sooo much smaller than the old wiki. I also figured that with the skins options, we could easily give people more choices to choose their own style, anyway. I will confess that tiny fonts for the sake of sleeker designs is a major pet peeve of mine. :-P --[[User:Voidious|Voidious]] 07:12, 13 November 2007 (UTC)<br /> <br /> == Smileys :-) ==<br /> <br /> I would be relly nice if we could somehow support smile, e.g. just as simple as stating:<br /> <br /> &lt;pre&gt;[[Image:HappySmiley.png]]&lt;/pre&gt;<br /> <br /> --[[User:FlemmingLarsen|Flemming N. Larsen]] 09:04, 28 November 2007 (UTC)<br /> <br /> Wikimedia Commons has a [http://commons.wikimedia.org/wiki/Smiley whole section] of GFDL'd or public domain smileys (look at the link at the bottom for more). I don't really see the point though. If you want to upload them and use them, feel free, but I'll stick with =) on the wiki. --&lt;code&gt;[[User:AaronR|AaronR]]&lt;/code&gt; 01:21, 30 November 2007 (UTC)<br /> <br /> == Old wiki ==<br /> The old wiki is not working (error 500), and so my roborumble client (it cannot find the list of partecipants), but i see many client is uploading. What is your solution?<br /> --[[User:Lestofante|Lestofante]] 10:35, 1 Dic 2008 (UTC)<br /> <br /> The clients currently running are just using the last copy of the participants list they downloaded from the old wiki. I emailed PEZ a bit ago and got a reply that he'll look into it so hopefully the old wiki will be up again in not too long. If that ends up taking longer than expected though, we could update/fix the participants page on the new wiki and point clients at that instead. (Note: Don't point clients at the one on the new wiki just yet, it's out of date and such. It needs to be copied over from a downloaded copy of the list from the old wiki) --[[User:Rednaxela|Rednaxela]] 12:00, 1 December 2008 (UTC)<br /> <br /> maybe we can drop definitely the old wiki for roborumble client, or better every ramble server can implements it's own participants list, maybe integrated with general wiki list<br /> --[[User:Lestofante|Lestofante]] 15:13, 1 Dic 2008 (UTC)<br /> <br /> I'd agree that migrating to using the new wiki participants list would be good, though I think some more veteran wikiers/rumblers than myself should give their input before any such switch is made 'official'. As far as keeping a participants list with the rumble server, well, there's only one working rumble server at the moment so I'm not sure what good that would do, and furthermore multiple rumble server would be a bad thing I think becacuse it would divide the processing power that goes towards making the battles. --[[User:Rednaxela|Rednaxela]] 17:47, 1 December 2008 (UTC)<br /> <br /> That's right, then I thing the server have to had a mirror of the wiki's official participants list, so in this case we can continue run our client, simple we cannot modify the list (if the two list are not synchronize together) <br /> --[[User:Lestofante|Lestofante]] 21:49, 1 Dic 2008 (UTC)<br /> <br /> Yeah, the real problem is getting the participants list from the currently-erroring wiki. The RR client has no problem parsing the new wiki format. I may be able to get that from the RoboWiki server when I get home (if it isn't fixed before then). <br /> <br /> The other issue we might encounter in the future would be when we move this wiki to robowiki.net, and we have RR clients pointing to testwiki.roborumble.org, but I don't think forwarding that URL and/or having people update their clients would be a big issue. I'm glad you contacted PEZ about the old wiki's current problems, I've been out of touch for at least a week...<br /> <br /> --[[User:Voidious|Voidious]] 19:03, 2 December 2008 (UTC)<br /> <br /> Okay to mention it here as well for people who haven't been checking up on it... The old wiki is back up! --[[User:Rednaxela|Rednaxela]] 18:43, 9 December 2008 (UTC)<br /> <br /> == mailer error ==<br /> I'm trying to confirm my user e-mail, but I still get &quot;mailer error&quot;. I've tried 3 different and working address... and there is a way for automatically sign the edits?<br /> --[[User:Lestofante|Lestofante]] 22:00, 1 Dic 2008 (UTC)<br /> <br /> : I couldn't get the mailer to work either, but you can easily sign your edits using &lt;nowiki&gt;--~~~~&lt;/nowiki&gt;. See http://meta.wikimedia.org/wiki/Cheatsheet for more tricks. --[[User:Darkcanuck|Darkcanuck]] 03:13, 2 December 2008 (UTC)<br /> <br /> == InterWiki Links ==<br /> Who have fully access to this server apart from [[User:David Alves|David Alves]]? I want both my thai wiki and this wiki a inter-languages link. Please look [[User_talk:Nat#New_Thai_RoboWiki|here]] for more detailed. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 15:16, 15 April 2009 (UTC)<br /> <br /> I have full access, or at least I do if I can remember the password. =) I'll see about logging in and taking a look at the InterWiki stuff. Sorry it took so long to respond about this. --[[User:Voidious|Voidious]] 14:50, 16 April 2009 (UTC)<br /> <br /> Hey Voidious, I believed that the SQL will take less than 1 seconds to copy/past/execute. Plus login/connecting time I think this can be accomplished within a minute so please do asap (or I must say NOW). &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 16:19, 22 April 2009 (UTC)<br /> <br /> Hey Nat - I will add the InterWiki link because I'd like to support your efforts to start a Thai Robocode community and wiki. But I really don't appreciate being commanded to do that (or much of anything, really), and especially to do so &quot;NOW&quot;. Please keep in mind the RoboWiki's only rule: &quot;Pretty please be polite.&quot; --[[User:Voidious|Voidious]] 18:48, 22 April 2009 (UTC)<br /> <br /> Cool, I read up on the InterWiki stuff, added your Thai wiki to the database, and posted a link on the main page. As I can't read Thai, please make sure that looks right and edit it if necessary. =) --[[User:Voidious|Voidious]] 22:54, 22 April 2009 (UTC)<br /> <br /> Sorry for that rude. But anyways, thank you very much. The link at main page is correct. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 01:37, 23 April 2009 (UTC)<br /> <br /> == Database error ==<br /> I didn't know where to put this, but here seems like a decent spot. All my posts are getting this message today (4 times, probably 5 with this one), the posts are still uploaded but the message is:<br /> &lt;pre&gt;<br /> A database query syntax error has occurred. This may indicate a bug in the software.<br /> The last attempted database query was:<br /> (SQL query hidden)<br /> from within function &quot;SearchMySQL4::update&quot;.<br /> MySQL returned error &quot;126: Incorrect key file for table './wikidb/searchindex.MYI'; try to repair it (localhost)&quot;.<br /> &lt;/pre&gt;<br /> <br /> I don't know if ''localhost'' is meant to be from mine point of view, or the server's. Maybe someone else is getting the same messages, I haven't tried to logout/in, because I just thought of that. --[[User:Zyx|zyx]] 23:47, 5 May 2009 (UTC)<br /> : Just like when you go to the mechanic, I didn't get the message this time. Another piece of information may be that all the other 4 posts where at [[Talk:PwnBot‎]], so maybe the problem relies in that page. --[[User:Zyx|zyx]] 23:49, 5 May 2009 (UTC)<br /> <br /> :: I found some mentions of people hitting this, and it sounds like a &quot;repair table&quot; SQL command is the remedy. I've run that now, so hopefully it's fixed. Can you let me know if it happens again? Thanks, --[[User:Voidious|Voidious]] 00:31, 6 May 2009 (UTC)<br /> <br /> ::: Just got it again, and again in the same page [[Talk:PwnBot‎]]. --[[User:Zyx|zyx]] 20:45, 6 May 2009 (UTC)<br /> <br /> :::: Thanks for the info. I saw it as well when I posted the downtime note. I'm guessing the server crashing corrupted the searchindex table -- I'll rerun the &quot;repair table&quot; and post here when I do. I'll also be backing up the database very soon. --[[User:Voidious|Voidious]] 20:52, 6 May 2009 (UTC)<br /> <br /> ::Is it... My fault?! I created that page. It seems whenever I change a page I get it too. It doesn't matter what page I go to. Also, for the majority of today, (for me at least) it seems your server has been down. I've been unable to connect. --[[User:Awesomeness|Awesomeness]] 22:04, 6 May 2009 (UTC)<br /> <br /> ::: It's not your fault, and I saw it on another page too. The server went down for a while as of last night, still not sure what happened, but glad it's back up. I've rerun the &quot;repair table&quot; command, so I think that database error will go away for now. --[[User:Voidious|Voidious]] 22:06, 6 May 2009 (UTC)<br /> <br /> :::: I now know why I can't access the wiki (and roborumble.org) yesterday. Night there, afternoon here. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 00:25, 7 May 2009 (UTC)<br /> <br /> == SourceForge.net Community Choices Awards ==<br /> <br /> &lt;div style=&quot;text-align:center; border: 5px solid #ccc&quot;&gt;<br /> http://sourceforge.net/images/cca/cca_nominate.png<br /> <br /> Please nominate Robocode to SourceForge.net Community Choices Awards!&lt;br /&gt;<br /> [http://sourceforge.net/community/cca09/nominate/?project_name=Robocode&amp;project_url=http://robocode.sourceforge.net/ Nominate Robocode]<br /> &lt;/div&gt;<br /> <br /> Anyone mind to put this to [[MediaWiki:Sitenotice]] or front page? I not sure if I can post to front page. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 10:21, 15 May 2009 (UTC)<br /> <br /> Please nominate Robocode in category of &quot;Best Project for Academia&quot; and &quot;Most Likely to Change the Way You Do Everything&quot;. If you nominate to another category, please post here so other robocoder can nominate in same categories (note that you can nominate in multiple categories) Nevertheless, please [http://sourceforge.net/community/cca09/nominate/?project_name=Robocode&amp;project_url=http://robocode.sourceforge.net/ nominate]! &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 11:26, 18 May 2009 (UTC)<br /> <br /> == [[Special:Disambiguations]] ==<br /> <br /> Do anyone know why the [[Special:Disambiguations]] has spammy report? &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 11:23, 18 May 2009 (UTC)<br /> <br /> == Image Uploads ==<br /> <br /> It looks like the image uploads folder is not set as writable to the wiki. Is this expected to change? -- [[User:Synapse|&lt;font style=&quot;font-size:0.8em;font-variant:small-caps;&quot;&gt;Synapse&lt;/font&gt;]] 05:27, 10 June 2009 (UTC)<br /> <br /> Haven't test yet. If this is true, I think this problem cause due the upgrading of MediaWiki. Voidious, check it please? Another note to Voidious, MediaWiki/1.15 just release =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 13:29, 10 June 2009 (UTC)<br /> <br /> Not sure why it stopped working, but I'll take a look at the image uploads and upgrading MediaWiki this afternoon. (And making a mental note to test that whenever I upgrade. =)) --[[User:Voidious|Voidious]] 15:41, 11 June 2009 (UTC)<br /> <br /> Fixed the uploading issue and upgraded MedaWiki to 1.15. Enjoy. =) --[[User:Voidious|Voidious]] 20:10, 11 June 2009 (UTC)<br /> <br /> == /wiki/PageName-style url ==<br /> <br /> Recently this day I noticed that the /wiki/PageName-style URL is now work. Voidious, why don't you set the &lt;code&gt;$wgArticlePath = &quot;/wiki/$1&quot;&lt;/code&gt; in LocalSettings.php? And I wonder why the old server at 174.132.4.195 now has new wiki code, and available in both /wiki/PageName and ?PageName style (but not /w/index.php?title=PageName style). What's going on? &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 12:56, 27 June 2009 (UTC)<br /> <br /> == Syntax Highlighting ==<br /> <br /> It would be great if we could have syntax highlighting for code snippets. This would make code snippets easier to read. Currently, if I want to read a code snippet from the wiki, I would copy and paste it into my favourite text editor.<br /> <br /> Wikipedia itself seems to use [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi SyntaxHighlight GeSHi].&amp;mdash;<br /> <br /> [[User:Duyn|Duyn]] 14:56, 17 January 2010 (UTC)<br /> <br /> [[User:Voidious/RoboWiki_To-Do]] --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 13:41, 18 January 2010 (UTC)<br /> <br /> Yeah, that's been on my to-do list for a while, I'll try to get it up and running soon. Can't be too tough. =) --[[User:Voidious|Voidious]] 16:12, 19 January 2010 (UTC)<br /> <br /> == Favicon ==<br /> <br /> I just noticed that the new Robowiki doesn't have a favicon. This is easily remedied by copying http://old.robowiki.net/favicon.ico so that it is accessible at http://robowiki.net/favicon.ico --[[User:Skilgannon|Skilgannon]] 18:00, 17 January 2010 (UTC)<br /> <br /> : Will do. --[[User:Voidious|Voidious]] 16:12, 19 January 2010 (UTC)<br /> <br /> == Robocode on Wikipedia ==<br /> <br /> Well, [[wikipedia:Robocode]] article is just challenged for reference, as well as a original research. Please help it by adding reference. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 15:09, 15 April 2010 (UTC)<br /> <br /> Honestly, I believe many things on the wikipedia article, at least 2/3rds of the page, just plain don't belong on Wikiedia, due to valid reasons. In fact I'm not sure anything beyond the overview and the first two sections belong, given how Wikipedia's 'original research' and 'notability' criteria apply to such sections. Even those sections which do make sense to keep to desperately need citations. Essentially, I don't feel the sections [http://en.wikipedia.org/w/index.php?title=Robocode&amp;action=historysubmit&amp;diff=37661690&amp;oldid=35178091 added by PEZ] fit wikipedia's criteria for what belongs. So... I think it does deserve to be challenged for good reason. I don't have time to improve what should stay though. --[[User:Rednaxela|Rednaxela]] 16:39, 15 April 2010 (UTC)<br /> <br /> I'll make more comments on the Wikipedia talk page, but I agree it needs a lot of cleanup and I'm willing to help out with that. I half agree with Rednaxela. The overview and first 2 sections are fine and neutral. The rest could use a lot of cleaning up, but I don't think it all needs just to be axed. Some editing down / revising / adding citations should do the trick. (I think the RoboWiki is a &quot;reliable source&quot;? If not, I don't know what is.) --[[User:Voidious|Voidious]] 19:03, 15 April 2010 (UTC)<br /> <br /> : Well, while I would personally consider Robowiki a &quot;reliable source&quot; for my own purposes, it seems to me it violates some of what is noted on [[wikipedia:Wikipedia:Verifiability#Self-published_sources_.28online_and_paper.29|Wikipedia:Verifiability#Self-published_sources]], in particular how it notes &quot;open wikis&quot; among other things as &quot;largely not acceptable&quot;. Also, note the &quot;no original research&quot; policies, and consider that much of the purpose of Robowiki is for &quot;original research&quot;. There is a significant difference between a source one trusts, and a source that fits Wikipedia's rules. --[[User:Rednaxela|Rednaxela]] 01:54, 16 April 2010 (UTC)<br /> <br /> : Hmm, thanks. I really don't know much about Wikipedia's policies, but just starting to read up on it now. In that case, you are probably right that a lot of stuff needs to just be axed... --[[User:Voidious|Voidious]] 13:46, 16 April 2010 (UTC)<br /> <br /> == &quot;Robocode Guidebook&quot; ==<br /> <br /> ''Migrated to [[Talk:Robocode Guidebook]]''<br /> <br /> == RoboCode Chat / IM ==<br /> <br /> So it is to my understanding that currently the only real way for robocoders to talk is on talk pages on this wiki so I had this idea... what if we had an IM type web chat system for Robocoders to talk :) within a few months i could probably get a website set up to do that and it would use the open-source [https://blueimp.net/ajax/ AJAX project]. What do you all think of the idea? --[[User:Exauge|Exauge]] 00:33, 15 May 2010 (UTC)<br /> <br /> I think we have an (deserted) IRC channel (or not?). But actually I do chat with some Robocoder through GTalk and e-mail. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 00:38, 15 May 2010 (UTC)<br /> <br /> Seems like a lot of work. =) Some of us have each other on IM. I use my handle on AIM and my handle at gmail for GTalk/Jabber. (But my AIM is set so you can't see my status if I don't have you as a buddy.) We used to have [[oldwiki:ContactInfo]], but there's no current page with that kind of info. --[[User:Voidious|Voidious]] 00:41, 15 May 2010 (UTC)<br /> <br /> Hi, anyways I've started working on a Robocode talk page and it's getting to be pretty sweet ;) I can probably have it finished in a few weeks (maybe sooner) and anyways if you like it you will all be very welcome to use it and if it's popular enough I might purchase a domain name for it :) and if not, well it's a good way for me to practice my website building skills :) anyways back to studying for tomorrow's exams lol :S --[[User:Exauge|Exauge]]<br /> <br /> Well, personally anyway, if were to have a robocode live chat place, I'd strongly prefer it be an IRC channel (i.e. on Freenode?). Mostly because I always have an IRC client running anyway, and those without an IRC client can still sign in via a web page (i.e. [http://www.mibbit.com/] and [http://webchat.freenode.net/]). Also, IRC is probably about the most mature system for such things anyway, and it's nearly maintain free to maintain a channel. --[[User:Rednaxela|Rednaxela]] 04:03, 17 May 2010 (UTC)<br /> <br /> == Wall Avoidance ==<br /> <br /> ''moved to [[Talk:DustBunny]]...''<br /> <br /> == Walking to the center of the wall ==<br /> <br /> Well, i'm trying to make a Robot that goes to one of the walls, walk to the center of it an then start to circulate the entire Field, touching the center of each wall.<br /> <br /> Anyway, I'm having problems to take the Robot to the center of one of the walls. That's what i'm doing:<br /> <br /> package MyRobots;<br /> import robocode.*;<br /> import java.awt.*;<br /> <br /> public class Walle extends AdvancedRobot<br /> {<br /> double moveAmount;<br /> int miss = 0, hit = 0;<br /> <br /> public void run() {<br /> <br /> moveAmount = Math.max(getBattleFieldWidth(), getBattleFieldHeight());<br /> <br /> setBodyColor(Color.black);<br /> setGunColor(Color.orange);<br /> setRadarColor(Color.yellow);<br /> setScanColor(Color.black);<br /> setBulletColor(Color.orange);<br /> <br /> turnLeft(getHeading() % 90);<br /> ahead(moveAmount);<br /> <br /> turnGunRight(90);<br /> turnRight(90);<br /> <br /> if((getY() + getWidth()/2) == getBattleFieldHeight() || (getY() - getWidth()/2) == 0) ahead(getX() - (getBattleFieldWidth()/2));<br /> if((getX() + getHeight()/2) == getBattleFieldWidth() || (getX() - getHeight()/2) == 0) ahead(getY() - (getBattleFieldHeight()/2));<br /> while(true) {<br /> }<br /> }<br /> <br /> The problem is obviously with the 2 'ifs', but I really can't get it. Thanks for any help!<br /> <br /> getX() &amp; getY() methods returns double value and you cannot compare them using ==, use something like this<br /> &lt;syntaxhighlight&gt;<br /> epsilon = 0.0001; // or another small value<br /> if (Math.abs((getY() + getWidth()/2) - getBattleFieldHeight()) &lt; eplsilon) {<br /> ahead(getX() - (getBattleFieldWidth()/2));<br /> }<br /> <br /> // or<br /> if (robocode.util.Utils.isNear(getY() + getWidth()/2, getBattleFieldHeight())) {<br /> ahead(getX() - (getBattleFieldWidth()/2));<br /> }<br /> &lt;/syntaxhighlight&gt;<br /> And it's better to ask questions like this on yours page --[[User:Jdev|Jdev]] 16:21, 14 September 2010 (UTC)<br /> <br /> == Strategy ==<br /> <br /> So I'm in high school and I'm in a first year Java class. Right now our project is to create a robot in robocode. The rules are the each battle will be fought with 3 to 4 players, the final battle will be 1 on 1, and we aren't allowed to use Advance Robot. There's so many opions in Robocode that I have no clue what's the best strategy going into this. Help!!!<br /> <br /> Thanks.<br /> <br /> The class [http://robocode.sourceforge.net/docs/robocode/robocode/JuniorRobot.html JuniorRobot] might work well for what you are doing. For your robot just make a class extending JuniorRobot. It could be helpful to override onScannedRobot() and perform actions in there. Also be sure to check out the [[Radar]] page and try to implement one of those radar locks because without a decent radar system your robot will be seriously limited. Just spinning the radar might work OK though. ex turnRadarRight(Double.POSITIVE_INFINITY);<br /> Also be sure to check out all the tutorials on this site.<br /> --&lt;font style=&quot;font-family:helvetica,arial,sans-serif;font-size:90%;letter-spacing:-1px;&quot;&gt;[[User:Exauge|Exauge]] ◊ [[User talk:Exauge|talk]]&lt;/font&gt; 02:56, 15 December 2010 (UTC)<br /> <br /> Well... don't get hit. :-) My advice to get started would be:<br /> * Check out the sample bots first, learn how and why they work.<br /> * Try to beat all the sample bots.<br /> * I'd also check with your teacher about using code from the RoboWiki / internet. There's plenty of code and tutorials available, but it's up to your teacher if you're allowed to use that code (even if the code's license says it's ok).<br /> * A page like [[Melee Strategy]] should be good to get the strategy gears turning.<br /> Good luck!<br /> <br /> --[[User:Voidious|Voidious]] 03:33, 15 December 2010 (UTC)<br /> <br /> == Question Forum ==<br /> <br /> Is there a question forum or something of the sort where people can ask random questions? {{unsigned|Starhammy}}<br /> <br /> No, but actually you can ask on [[Talk:Starhammy|your talk page]]. (I forgot to welcome you properly, so it's my bad you don't know where to ask) --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 12:53, 29 December 2010 (UTC)<br /> <br /> <br /> I got an email from some website (itbhu.ac.in). Apparently an Indian college is hosting a &quot;CodeFest&quot; tournament for about 730 something USD (35000 Indian Rupees, it says), and it's an extension of Robocode; it has different modes including Capture the Flag, and it adds walls to the battlefield itself. My main concern: is it safe to download, ie. it has no viruses or trojan horses whatsoever? --[[User:AWOL|AWOL]] 20:34, 31 January 2011 (UTC)<br /> <br /> : I don't know, but the first prize is only 15000, e.g. about 300 USD. The rest is for second, runner up, stuff like that. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 23:05, 31 January 2011 (UTC)<br /> <br /> : I'm rather confident it's safe. It is hosted at a well reputed Indian university, and the event seems to have some notable partners. I'll point this out though... it appears to be using a build of the &quot;custom-battlefields-workspace&quot; branch of Robocode, which hasn't kept up to date with the main Robocode changes since version 1.7.1.4. This means all known bugs in Robocode 1.7.1.4 likely apply, and some of them are rather... serious... for a competition (i.e. a teleport bug, and a kill-other-robot-threads bug) --[[User:Rednaxela|Rednaxela]] 00:20, 1 February 2011 (UTC)<br /> <br /> :: And also a lot of security vulnerabilities in that branch... --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 12:53, 1 February 2011 (UTC)<br /> <br /> : I've been playing around with it for the last couple days and it's seems to be just a different version of Robocode. Totally safe so far. Like Rednaxela said, it's just a reworked copy of the custom battlefield branch. I will say this, it's been a lot of fun working on how to detect objects in the battlefield... --[[User:KID|KID]] 20:58, 3 February 2011 (UTC)<br /> <br /> == Main Page overhaul ==<br /> <br /> I've been thinking the [[Main Page]] needs a serious overhaul. I'll probably experiment at [[User:Voidious/Main Page]] soon, and anyone else is of course free to do the same. Some of my thoughts apply to the wiki more generally, as well.<br /> * [[User:Rednaxela|Rednaxela]] commented to someone recently about how discussion-based this wiki community is. We've also been looking at [http://www.mediawiki.org/wiki/Extension:LiquidThreads LiquidThreads] because of that. We should probably point this out. I know I never visit Wikipedia's Recent Changes... I wonder how many people miss out on the community aspect of the RoboWiki?<br /> * Current events stuff needs to be removed or updated. <br /> * I don't think we need to list every Challenge. Maybe 2-3 of the recent ones and then links to the categories (which themselves could be polished a bit).<br /> * I think the &quot;Building a Bot&quot; section is really important. It's not bad right now, but could be better. We should probably link to more of the [[:Category:Robocode Documentation|Robocode docs]] stuff. [[Radar]] is the 2nd link and goes to a very detailed page, but [[:Category:Targeting|Targeting]] and [[:Category:Movement|Movement]] are not as newbie friendly.<br /> * Would be good to link to specific details about development tools - like [[:Category:Utilities|Utilities]], [[RoboResearch]], [[Robocode/Eclipse|Robocode/Eclipse]].<br /> * I think the layout and colors could also be revamped - especially that gray background is pretty drab.<br /> * Maybe more prominent and detailed info on the [[RoboRumble]].<br /> * Is the [http://twitter.com/roborumble @roborumble Twitter feed] interesting enough to include? (Like the [http://twitter.com/robowiki @robowiki] tweets on the sidebar.)<br /> I'm sure there's plenty more we could do, just some quick brainstorming for now...<br /> <br /> --[[User:Voidious|Voidious]] 19:01, 10 February 2011 (UTC)<br /> <br /> Another thing I think we need to note (especially to someone who is Wikipedia's editor) is that the RoboWiki is subpage-based, like we like Robocode/Getting_Start and not Getting_Start_to_Robocode. Just my two cents. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 10:59, 11 February 2011 (UTC)<br /> <br /> == About the spam... ==<br /> <br /> http://www.mediawiki.org/wiki/Extension:SpamBlacklist - See bottom of page for spamlists.<br /> http://www.mediawiki.org/wiki/Extension:ConfirmEdit - Has our old math captcha type thing in it.<br /> http://www.mediawiki.org/wiki/Extension:Bad_Behavior - No idea how this is suppose to work<br /> <br /> That is all. :)<br /> &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 16:39, 12 March 2011 (UTC)<br /> <br /> We already use ConfirmEdit in reCAPTCHA mode. I checked SpamBlacklist and it's blacklists don't match anything in the recent spam. Unsure about Bad_Behavior. Now, on the ConfirmEdit page, it does note that as of 2011 spammers seem to have gotten around reCAPTCHA by some means. --[[User:Rednaxela|Rednaxela]] 18:18, 12 March 2011 (UTC)<br /> <br /> I think the trick is to do something custom so that the usual anti-antispam techniques don't work. Just something simple like &quot;What is the next prime number after 7?&quot; or so. --[[User:Skilgannon|Skilgannon]] 08:40, 13 March 2011 (UTC)<br /> <br /> Maybe the spammer wait for autoconfirm to bypass the reCAPTCHA. Voidious, can we change the autoconfirm rules to four edits and ten days? And enable reCAPTCHA for every page edit in non-autoconfirm group? --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 01:41, 14 March 2011 (UTC)<br /> <br /> Ah, good call! I forgot about the autoconfirm stuff. I just changed it to 4 edits/10 days. I checked and we only skip the captcha if you're autoconfirmed, bot, or sysop, so I think we're good. Hopefully we'll be seeing less spam now... --[[User:Voidious|Voidious]] 01:56, 14 March 2011 (UTC)<br /> <br /> Since the spam was still coming in, I updated mediawiki, update the version of the ConfirmEdit extension, AND did some custom hacks to the ConfirmEdit extension to make it simultaneously require both reCAPTCHA and a LaTeX-rendered arithmetic question. Hopefully the combination of the two will keep this spam out for good :) --[[User:Rednaxela|Rednaxela]] 06:06, 19 March 2011 (UTC)<br /> <br /> I thought Voidious still keeping it up to date..... Well, Red, you have checked permission of upload folder, right? Every time Void upgrade the MediaWiki, he needs to re-set the permission of upload folder. Good thought with Recent Change cleanup, though.<br /> <br /> If the spam doesn't stop (as I believe many spambot can solve simple math image, I've face one), maybe you could have them solve equation ;-). --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 07:54, 19 March 2011 (UTC)<br /> <br /> Well, it wasn't *very* behind in versions, but was still 1.15.x as opposed to 1.16.x. Yep, I made sure to check the permissions for that I believe. Yeah, I wouldn't be surprised if some spambots can solve ConfirmEdit's MathCaptcha as-is, but I'm doubting that many spambots are designed to handle both that and reCAPTCHA on the same page. If they do however, I'll keep that suggestion in mind :) --[[User:Rednaxela|Rednaxela]] 13:57, 19 March 2011 (UTC)<br /> <br /> I took a look at the HTTP logs and the recent spambots have been jumping IP addresses, never solving the reCAPTCHA from the same IP that they requested it via. As a precaution, I further tweaked the captcha code to only accept answers as valid if they're from the same IP that was given that captcha. --[[User:Rednaxela|Rednaxela]] 15:34, 19 March 2011 (UTC)<br /> <br /> It seems like we're still getting a high number of users with odd names... might I suggest doing something custom? Doesn't have to be complicated, just &quot;the next prime number after X&quot; or &quot;the next number in the sequence 3 6 9 ...&quot; or some such. The trick is to make it not worth the time and effort for the spammer to implement a custom cracker just for robowiki. --[[User:Skilgannon|Skilgannon]] 13:04, 21 March 2011 (UTC)<br /> <br /> I've looked at the http logs for the IP addresses of those recent users, and they appear to be real people. They browsed some pages, made an account for some reason, browsed some more pages. Btw, an interesting stat: On March 21st so far (based on the server's clock), there have been 76 failed signup attempts due to captcha, and none of them browse pages before the signup attempt. --[[User:Rednaxela|Rednaxela]] 23:25, 21 March 2011 (UTC)<br /> <br /> Just seems odd to have 3 new people in 1 day =) Looks like it's stopped, nice work Red. I'm guessing the usage patterns would be a good attribute to block on if the spam ever picks up again in the future. --[[User:Skilgannon|Skilgannon]] 12:16, 22 March 2011 (UTC)<br /> <br /> Glad I could help by starting a thread about the problem. I also like making custom security. One of my favorite methods is changing the URL to the php or module that does the add page/register, and making a fake captcha (hidden via CSS, putting `anything` in it means you fail the check). :P &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 15:31, 24 March 2011 (UTC)<br /> <br /> ----<br /> Robot Repository is down. Can't get any of the newer bots nor run the game efficiencty :) --[[User:Miked0801|Miked0801]] 16:00, 16 May 2011 (UTC)<br /> I can delete this entry when the issue is fixed...<br /> <br /> It seems that Robot Repository has been down for about a week. Been trying to upload my newest bot but its not working. I need a place to upload my bot. --[[User:Khanguy|Khanguy]] 03:08, 17 May 2011 (UTC)<br /> <br /> Well, one idea for both of you would be to using Google Sites to upload your bot; I started doing that recently and found it to be much simpler and easier than uploading bots onto the repository.--[[User:CrazyBassoonist|CrazyBassoonist]] 03:45, 17 May 2011 (UTC)<br /> <br /> The problem being, I can't get the latest bots for running the rumble nor competing against you CB :) --[[User:Miked0801|Miked0801]] 04:28, 17 May 2011 (UTC)<br /> <br /> The Robocode repository has always been sort of unreliable, hence why I've never used it personally. Anyway, perhaps look for backups of the relevant bots [http://darkcanuck.net/rumble/robots/ here] or [http://rednaxela-robocode.dyndns.org/data/robot_archive/ here]? If missing ones that are avaliable in neither, list the ones that are missing? --[[User:Rednaxela|Rednaxela]] 11:57, 17 May 2011 (UTC)<br /> <br /> Neither of these locations contain CrazyBassoonists latest nanos, Fuatisha 1.1 nor Caligula 1.15. I'm also pretty sure they are missing a few of the other minis that were updated within the last 6 months as well. --[[User:Miked0801|Miked0801]] 14:57, 17 May 2011 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=Talk:Main_Page&diff=19296 2011-05-17T04:28:50Z

<p>Miked0801: </p> <hr /> <div>== Why is the &quot;Robo Wiki&quot; icon in the upper left corner so small? ==<br /> The headline speaks for itself. --[[User:Awesomeness|Awesomeness]] 21:08, 3 May 2009 (UTC)<br /> <br /> So small? It seems just right to me really. --[[User:Rednaxela|Rednaxela]] 21:56, 3 May 2009 (UTC)<br /> <br /> Because it is the same size as the old wiki =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 23:41, 3 May 2009 (UTC)<br /> <br /> <br /> http://www.csdgn.org/files/images/robowiki2.png<br /> <br /> I have a solution to this! I was bored so I drew this (though it is probably too big!). I realize I forgot the radar, but to be honest, from this angle it would block to much however. Just consider it a drone! --[[User:Chase-san|Chase]] 21:50, 20 June 2010 (UTC)<br /> <br /> : You could just said that it is a Droid instead of saying that you forgot them... --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 13:36, 21 June 2010 (UTC)<br /> <br /> :: I like it - it looks good :) on the current one you cant really read wiki because its blocked but this looks really good :) --&lt;font style=&quot;font-family:helvetica,arial,sans-serif;font-size:90%;letter-spacing:-1px;&quot;&gt;[[User:Exauge|Exauge]] ◊ [[User talk:Exauge|talk]]&lt;/font&gt; 14:51, 21 June 2010 (UTC)<br /> <br /> :: I suppose I could have. On another note, I notice that some of my shadows are wrong/inconsistent. --[[User:Chase-san|Chase]] 15:30, 21 June 2010 (UTC)<br /> <br /> : Looks really nice! I like it. Of course I have a soft spot for the old one, but this one's also very true to the original idea. And the text is way more readable. --[[User:Voidious|Voidious]] 00:05, 22 June 2010 (UTC)<br /> <br /> http://www.csdgn.org/files/images/robowiki3.png<br /> <br /> I fixed some of my shadow work in this. I made the wording a bit more visible as well (by adding more depth to it). I also made the book lines heavier. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 06:25, 20 July 2010 (UTC)<br /> <br /> http://www.csdgn.org/files/images/robowiki_thumb.png<br /> <br /> Obviously this is to big to go in the corner, but I made a reduced size one. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 06:28, 20 July 2010 (UTC)<br /> <br /> Was a decision ever reached on this, because I am considering redrawing this (but better). &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 20:13, 18 January 2011 (UTC)<br /> <br /> I'm up for changing it and I don't think anybody objected. Just fell off my radar - sorry! I think my only criticism of that first one is that the &quot;IKI&quot; is a little smushed together. --[[User:Voidious|Voidious]] 20:20, 18 January 2011 (UTC)<br /> <br /> Well (I personally think) my art has improved considerably since I drew this. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 21:31, 18 January 2011 (UTC)<br /> <br /> : If nothing else, I will go over it with a pen and clean up the line work. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 21:38, 18 January 2011 (UTC)<br /> <br /> http://www.csdgn.org/files/images/robowiki2_small.png<br /> <br /> Here is the new version. It's a bit cleaner, though it doesn't have as much character (because it is so much cleaner). &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 02:01, 19 January 2011 (UTC)<br /> <br /> Nice stuff, looks pretty good to me :) --[[User:Rednaxela|Rednaxela]] 06:04, 19 January 2011 (UTC)<br /> <br /> So are we going to use it? &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 16:12, 8 February 2011 (UTC)<br /> <br /> Just updated it. I think it looks really nice, it really changes the look of the page a lot more than I expected. Let me know if anyone sees it looking weird anywhere - I'm not exactly a CSS guru. :-P Nice job, Chase! --[[User:Voidious|Voidious]] 17:40, 8 February 2011 (UTC)<br /> <br /> : You just change the $wgLogo, right? I don't think it would affect the page at all. I does feel weird at first, I agree. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 15:18, 9 February 2011 (UTC)<br /> <br /> :: Yeah, but the new one is taller so I had to move the sidebar down a bit. Took me a while to track down the right CSS to change. =) --[[User:Voidious|Voidious]] 15:22, 9 February 2011 (UTC)<br /> <br /> What about the favicon? --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 10:59, 11 February 2011 (UTC)<br /> <br /> == Does robo rumble work? ==<br /> hi im new to robocode, been doing it as part of my uni course and i was wondering, is it possible to run roborumble at home anymore because ive follwed the instructions and none of the battles ive been doing have been uploading.... [[User:Quietus|Quietus]] 15:47, 21 November 2008 (UTC)<br /> <br /> Yep! It sure as he heck still works! The thing is, the rumble.fervir.com server has been kind of broken for a while. You need to point your client at [http://darkcanuck.net/rumble/ this URL] instead now (See [[Darkcanuck/RRServer|here]] for more information). There's new fanciness in that server too :) --[[User:Rednaxela|Rednaxela]] 19:48, 21 November 2008 (UTC)<br /> <br /> == Article count ==<br /> <br /> A couple questions about the article count (after having some trouble Googling for answers). First, why isn't it updating automatically? Is that something I can trigger to update, or add to the &quot;job queue&quot;, does anyone know? (Notice if you edit / preview it is higher than 43, which it reads on the main page right now.) Second, what qualifies as an &quot;article&quot;? Is there a minimum length that a page needs to be (other than not being a user or talk page) to qualify as an article? --[[User:Voidious|Voidious]] 19:56, 12 November 2007 (UTC)<br /> :The main page just updated, it now says 48 articles. Also, the statistics page says that there are 145 pages total, but it is excluding, &quot;talk pages, pages about RoboWiki, minimal 'stub' pages, redirects, and others that probably don't qualify as content pages.&quot; --[[User:AaronR|AaronR]] 20:00, 12 November 2007 (UTC)<br /> <br /> According to the MediaWiki wiki (now that's a mouthful), the main page will come up to date as soon as its HTML cache is invalidated, at which point all of the templates, etc. will be transcluded again. Don't know if that helps... --[[User:AaronR|AaronR]] 20:27, 12 November 2007 (UTC)<br /> <br /> == Font size ==<br /> <br /> Just out of curiosity, why is the font size so large here compared to, say, Wikipedia? I know, I know, it's the same as the old wiki's font, but that wiki didn't have a sidebar. --[[User:AaronR|AaronR]] 07:04, 13 November 2007 (UTC)<br /> <br /> : Primarily because I thought &quot;x-small&quot; was just too small, and yes, it was also just sooo much smaller than the old wiki. I also figured that with the skins options, we could easily give people more choices to choose their own style, anyway. I will confess that tiny fonts for the sake of sleeker designs is a major pet peeve of mine. :-P --[[User:Voidious|Voidious]] 07:12, 13 November 2007 (UTC)<br /> <br /> == Smileys :-) ==<br /> <br /> I would be relly nice if we could somehow support smile, e.g. just as simple as stating:<br /> <br /> &lt;pre&gt;[[Image:HappySmiley.png]]&lt;/pre&gt;<br /> <br /> --[[User:FlemmingLarsen|Flemming N. Larsen]] 09:04, 28 November 2007 (UTC)<br /> <br /> Wikimedia Commons has a [http://commons.wikimedia.org/wiki/Smiley whole section] of GFDL'd or public domain smileys (look at the link at the bottom for more). I don't really see the point though. If you want to upload them and use them, feel free, but I'll stick with =) on the wiki. --&lt;code&gt;[[User:AaronR|AaronR]]&lt;/code&gt; 01:21, 30 November 2007 (UTC)<br /> <br /> == Old wiki ==<br /> The old wiki is not working (error 500), and so my roborumble client (it cannot find the list of partecipants), but i see many client is uploading. What is your solution?<br /> --[[User:Lestofante|Lestofante]] 10:35, 1 Dic 2008 (UTC)<br /> <br /> The clients currently running are just using the last copy of the participants list they downloaded from the old wiki. I emailed PEZ a bit ago and got a reply that he'll look into it so hopefully the old wiki will be up again in not too long. If that ends up taking longer than expected though, we could update/fix the participants page on the new wiki and point clients at that instead. (Note: Don't point clients at the one on the new wiki just yet, it's out of date and such. It needs to be copied over from a downloaded copy of the list from the old wiki) --[[User:Rednaxela|Rednaxela]] 12:00, 1 December 2008 (UTC)<br /> <br /> maybe we can drop definitely the old wiki for roborumble client, or better every ramble server can implements it's own participants list, maybe integrated with general wiki list<br /> --[[User:Lestofante|Lestofante]] 15:13, 1 Dic 2008 (UTC)<br /> <br /> I'd agree that migrating to using the new wiki participants list would be good, though I think some more veteran wikiers/rumblers than myself should give their input before any such switch is made 'official'. As far as keeping a participants list with the rumble server, well, there's only one working rumble server at the moment so I'm not sure what good that would do, and furthermore multiple rumble server would be a bad thing I think becacuse it would divide the processing power that goes towards making the battles. --[[User:Rednaxela|Rednaxela]] 17:47, 1 December 2008 (UTC)<br /> <br /> That's right, then I thing the server have to had a mirror of the wiki's official participants list, so in this case we can continue run our client, simple we cannot modify the list (if the two list are not synchronize together) <br /> --[[User:Lestofante|Lestofante]] 21:49, 1 Dic 2008 (UTC)<br /> <br /> Yeah, the real problem is getting the participants list from the currently-erroring wiki. The RR client has no problem parsing the new wiki format. I may be able to get that from the RoboWiki server when I get home (if it isn't fixed before then). <br /> <br /> The other issue we might encounter in the future would be when we move this wiki to robowiki.net, and we have RR clients pointing to testwiki.roborumble.org, but I don't think forwarding that URL and/or having people update their clients would be a big issue. I'm glad you contacted PEZ about the old wiki's current problems, I've been out of touch for at least a week...<br /> <br /> --[[User:Voidious|Voidious]] 19:03, 2 December 2008 (UTC)<br /> <br /> Okay to mention it here as well for people who haven't been checking up on it... The old wiki is back up! --[[User:Rednaxela|Rednaxela]] 18:43, 9 December 2008 (UTC)<br /> <br /> == mailer error ==<br /> I'm trying to confirm my user e-mail, but I still get &quot;mailer error&quot;. I've tried 3 different and working address... and there is a way for automatically sign the edits?<br /> --[[User:Lestofante|Lestofante]] 22:00, 1 Dic 2008 (UTC)<br /> <br /> : I couldn't get the mailer to work either, but you can easily sign your edits using &lt;nowiki&gt;--~~~~&lt;/nowiki&gt;. See http://meta.wikimedia.org/wiki/Cheatsheet for more tricks. --[[User:Darkcanuck|Darkcanuck]] 03:13, 2 December 2008 (UTC)<br /> <br /> == InterWiki Links ==<br /> Who have fully access to this server apart from [[User:David Alves|David Alves]]? I want both my thai wiki and this wiki a inter-languages link. Please look [[User_talk:Nat#New_Thai_RoboWiki|here]] for more detailed. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 15:16, 15 April 2009 (UTC)<br /> <br /> I have full access, or at least I do if I can remember the password. =) I'll see about logging in and taking a look at the InterWiki stuff. Sorry it took so long to respond about this. --[[User:Voidious|Voidious]] 14:50, 16 April 2009 (UTC)<br /> <br /> Hey Voidious, I believed that the SQL will take less than 1 seconds to copy/past/execute. Plus login/connecting time I think this can be accomplished within a minute so please do asap (or I must say NOW). &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 16:19, 22 April 2009 (UTC)<br /> <br /> Hey Nat - I will add the InterWiki link because I'd like to support your efforts to start a Thai Robocode community and wiki. But I really don't appreciate being commanded to do that (or much of anything, really), and especially to do so &quot;NOW&quot;. Please keep in mind the RoboWiki's only rule: &quot;Pretty please be polite.&quot; --[[User:Voidious|Voidious]] 18:48, 22 April 2009 (UTC)<br /> <br /> Cool, I read up on the InterWiki stuff, added your Thai wiki to the database, and posted a link on the main page. As I can't read Thai, please make sure that looks right and edit it if necessary. =) --[[User:Voidious|Voidious]] 22:54, 22 April 2009 (UTC)<br /> <br /> Sorry for that rude. But anyways, thank you very much. The link at main page is correct. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 01:37, 23 April 2009 (UTC)<br /> <br /> == Database error ==<br /> I didn't know where to put this, but here seems like a decent spot. All my posts are getting this message today (4 times, probably 5 with this one), the posts are still uploaded but the message is:<br /> &lt;pre&gt;<br /> A database query syntax error has occurred. This may indicate a bug in the software.<br /> The last attempted database query was:<br /> (SQL query hidden)<br /> from within function &quot;SearchMySQL4::update&quot;.<br /> MySQL returned error &quot;126: Incorrect key file for table './wikidb/searchindex.MYI'; try to repair it (localhost)&quot;.<br /> &lt;/pre&gt;<br /> <br /> I don't know if ''localhost'' is meant to be from mine point of view, or the server's. Maybe someone else is getting the same messages, I haven't tried to logout/in, because I just thought of that. --[[User:Zyx|zyx]] 23:47, 5 May 2009 (UTC)<br /> : Just like when you go to the mechanic, I didn't get the message this time. Another piece of information may be that all the other 4 posts where at [[Talk:PwnBot‎]], so maybe the problem relies in that page. --[[User:Zyx|zyx]] 23:49, 5 May 2009 (UTC)<br /> <br /> :: I found some mentions of people hitting this, and it sounds like a &quot;repair table&quot; SQL command is the remedy. I've run that now, so hopefully it's fixed. Can you let me know if it happens again? Thanks, --[[User:Voidious|Voidious]] 00:31, 6 May 2009 (UTC)<br /> <br /> ::: Just got it again, and again in the same page [[Talk:PwnBot‎]]. --[[User:Zyx|zyx]] 20:45, 6 May 2009 (UTC)<br /> <br /> :::: Thanks for the info. I saw it as well when I posted the downtime note. I'm guessing the server crashing corrupted the searchindex table -- I'll rerun the &quot;repair table&quot; and post here when I do. I'll also be backing up the database very soon. --[[User:Voidious|Voidious]] 20:52, 6 May 2009 (UTC)<br /> <br /> ::Is it... My fault?! I created that page. It seems whenever I change a page I get it too. It doesn't matter what page I go to. Also, for the majority of today, (for me at least) it seems your server has been down. I've been unable to connect. --[[User:Awesomeness|Awesomeness]] 22:04, 6 May 2009 (UTC)<br /> <br /> ::: It's not your fault, and I saw it on another page too. The server went down for a while as of last night, still not sure what happened, but glad it's back up. I've rerun the &quot;repair table&quot; command, so I think that database error will go away for now. --[[User:Voidious|Voidious]] 22:06, 6 May 2009 (UTC)<br /> <br /> :::: I now know why I can't access the wiki (and roborumble.org) yesterday. Night there, afternoon here. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 00:25, 7 May 2009 (UTC)<br /> <br /> == SourceForge.net Community Choices Awards ==<br /> <br /> &lt;div style=&quot;text-align:center; border: 5px solid #ccc&quot;&gt;<br /> http://sourceforge.net/images/cca/cca_nominate.png<br /> <br /> Please nominate Robocode to SourceForge.net Community Choices Awards!&lt;br /&gt;<br /> [http://sourceforge.net/community/cca09/nominate/?project_name=Robocode&amp;project_url=http://robocode.sourceforge.net/ Nominate Robocode]<br /> &lt;/div&gt;<br /> <br /> Anyone mind to put this to [[MediaWiki:Sitenotice]] or front page? I not sure if I can post to front page. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 10:21, 15 May 2009 (UTC)<br /> <br /> Please nominate Robocode in category of &quot;Best Project for Academia&quot; and &quot;Most Likely to Change the Way You Do Everything&quot;. If you nominate to another category, please post here so other robocoder can nominate in same categories (note that you can nominate in multiple categories) Nevertheless, please [http://sourceforge.net/community/cca09/nominate/?project_name=Robocode&amp;project_url=http://robocode.sourceforge.net/ nominate]! &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 11:26, 18 May 2009 (UTC)<br /> <br /> == [[Special:Disambiguations]] ==<br /> <br /> Do anyone know why the [[Special:Disambiguations]] has spammy report? &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 11:23, 18 May 2009 (UTC)<br /> <br /> == Image Uploads ==<br /> <br /> It looks like the image uploads folder is not set as writable to the wiki. Is this expected to change? -- [[User:Synapse|&lt;font style=&quot;font-size:0.8em;font-variant:small-caps;&quot;&gt;Synapse&lt;/font&gt;]] 05:27, 10 June 2009 (UTC)<br /> <br /> Haven't test yet. If this is true, I think this problem cause due the upgrading of MediaWiki. Voidious, check it please? Another note to Voidious, MediaWiki/1.15 just release =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 13:29, 10 June 2009 (UTC)<br /> <br /> Not sure why it stopped working, but I'll take a look at the image uploads and upgrading MediaWiki this afternoon. (And making a mental note to test that whenever I upgrade. =)) --[[User:Voidious|Voidious]] 15:41, 11 June 2009 (UTC)<br /> <br /> Fixed the uploading issue and upgraded MedaWiki to 1.15. Enjoy. =) --[[User:Voidious|Voidious]] 20:10, 11 June 2009 (UTC)<br /> <br /> == /wiki/PageName-style url ==<br /> <br /> Recently this day I noticed that the /wiki/PageName-style URL is now work. Voidious, why don't you set the &lt;code&gt;$wgArticlePath = &quot;/wiki/$1&quot;&lt;/code&gt; in LocalSettings.php? And I wonder why the old server at 174.132.4.195 now has new wiki code, and available in both /wiki/PageName and ?PageName style (but not /w/index.php?title=PageName style). What's going on? &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 12:56, 27 June 2009 (UTC)<br /> <br /> == Syntax Highlighting ==<br /> <br /> It would be great if we could have syntax highlighting for code snippets. This would make code snippets easier to read. Currently, if I want to read a code snippet from the wiki, I would copy and paste it into my favourite text editor.<br /> <br /> Wikipedia itself seems to use [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi SyntaxHighlight GeSHi].&amp;mdash;<br /> <br /> [[User:Duyn|Duyn]] 14:56, 17 January 2010 (UTC)<br /> <br /> [[User:Voidious/RoboWiki_To-Do]] --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 13:41, 18 January 2010 (UTC)<br /> <br /> Yeah, that's been on my to-do list for a while, I'll try to get it up and running soon. Can't be too tough. =) --[[User:Voidious|Voidious]] 16:12, 19 January 2010 (UTC)<br /> <br /> == Favicon ==<br /> <br /> I just noticed that the new Robowiki doesn't have a favicon. This is easily remedied by copying http://old.robowiki.net/favicon.ico so that it is accessible at http://robowiki.net/favicon.ico --[[User:Skilgannon|Skilgannon]] 18:00, 17 January 2010 (UTC)<br /> <br /> : Will do. --[[User:Voidious|Voidious]] 16:12, 19 January 2010 (UTC)<br /> <br /> == Robocode on Wikipedia ==<br /> <br /> Well, [[wikipedia:Robocode]] article is just challenged for reference, as well as a original research. Please help it by adding reference. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 15:09, 15 April 2010 (UTC)<br /> <br /> Honestly, I believe many things on the wikipedia article, at least 2/3rds of the page, just plain don't belong on Wikiedia, due to valid reasons. In fact I'm not sure anything beyond the overview and the first two sections belong, given how Wikipedia's 'original research' and 'notability' criteria apply to such sections. Even those sections which do make sense to keep to desperately need citations. Essentially, I don't feel the sections [http://en.wikipedia.org/w/index.php?title=Robocode&amp;action=historysubmit&amp;diff=37661690&amp;oldid=35178091 added by PEZ] fit wikipedia's criteria for what belongs. So... I think it does deserve to be challenged for good reason. I don't have time to improve what should stay though. --[[User:Rednaxela|Rednaxela]] 16:39, 15 April 2010 (UTC)<br /> <br /> I'll make more comments on the Wikipedia talk page, but I agree it needs a lot of cleanup and I'm willing to help out with that. I half agree with Rednaxela. The overview and first 2 sections are fine and neutral. The rest could use a lot of cleaning up, but I don't think it all needs just to be axed. Some editing down / revising / adding citations should do the trick. (I think the RoboWiki is a &quot;reliable source&quot;? If not, I don't know what is.) --[[User:Voidious|Voidious]] 19:03, 15 April 2010 (UTC)<br /> <br /> : Well, while I would personally consider Robowiki a &quot;reliable source&quot; for my own purposes, it seems to me it violates some of what is noted on [[wikipedia:Wikipedia:Verifiability#Self-published_sources_.28online_and_paper.29|Wikipedia:Verifiability#Self-published_sources]], in particular how it notes &quot;open wikis&quot; among other things as &quot;largely not acceptable&quot;. Also, note the &quot;no original research&quot; policies, and consider that much of the purpose of Robowiki is for &quot;original research&quot;. There is a significant difference between a source one trusts, and a source that fits Wikipedia's rules. --[[User:Rednaxela|Rednaxela]] 01:54, 16 April 2010 (UTC)<br /> <br /> : Hmm, thanks. I really don't know much about Wikipedia's policies, but just starting to read up on it now. In that case, you are probably right that a lot of stuff needs to just be axed... --[[User:Voidious|Voidious]] 13:46, 16 April 2010 (UTC)<br /> <br /> == &quot;Robocode Guidebook&quot; ==<br /> <br /> ''Migrated to [[Talk:Robocode Guidebook]]''<br /> <br /> == RoboCode Chat / IM ==<br /> <br /> So it is to my understanding that currently the only real way for robocoders to talk is on talk pages on this wiki so I had this idea... what if we had an IM type web chat system for Robocoders to talk :) within a few months i could probably get a website set up to do that and it would use the open-source [https://blueimp.net/ajax/ AJAX project]. What do you all think of the idea? --[[User:Exauge|Exauge]] 00:33, 15 May 2010 (UTC)<br /> <br /> I think we have an (deserted) IRC channel (or not?). But actually I do chat with some Robocoder through GTalk and e-mail. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 00:38, 15 May 2010 (UTC)<br /> <br /> Seems like a lot of work. =) Some of us have each other on IM. I use my handle on AIM and my handle at gmail for GTalk/Jabber. (But my AIM is set so you can't see my status if I don't have you as a buddy.) We used to have [[oldwiki:ContactInfo]], but there's no current page with that kind of info. --[[User:Voidious|Voidious]] 00:41, 15 May 2010 (UTC)<br /> <br /> Hi, anyways I've started working on a Robocode talk page and it's getting to be pretty sweet ;) I can probably have it finished in a few weeks (maybe sooner) and anyways if you like it you will all be very welcome to use it and if it's popular enough I might purchase a domain name for it :) and if not, well it's a good way for me to practice my website building skills :) anyways back to studying for tomorrow's exams lol :S --[[User:Exauge|Exauge]]<br /> <br /> Well, personally anyway, if were to have a robocode live chat place, I'd strongly prefer it be an IRC channel (i.e. on Freenode?). Mostly because I always have an IRC client running anyway, and those without an IRC client can still sign in via a web page (i.e. [http://www.mibbit.com/] and [http://webchat.freenode.net/]). Also, IRC is probably about the most mature system for such things anyway, and it's nearly maintain free to maintain a channel. --[[User:Rednaxela|Rednaxela]] 04:03, 17 May 2010 (UTC)<br /> <br /> == Wall Avoidance ==<br /> <br /> ''moved to [[Talk:DustBunny]]...''<br /> <br /> == Walking to the center of the wall ==<br /> <br /> Well, i'm trying to make a Robot that goes to one of the walls, walk to the center of it an then start to circulate the entire Field, touching the center of each wall.<br /> <br /> Anyway, I'm having problems to take the Robot to the center of one of the walls. That's what i'm doing:<br /> <br /> package MyRobots;<br /> import robocode.*;<br /> import java.awt.*;<br /> <br /> public class Walle extends AdvancedRobot<br /> {<br /> double moveAmount;<br /> int miss = 0, hit = 0;<br /> <br /> public void run() {<br /> <br /> moveAmount = Math.max(getBattleFieldWidth(), getBattleFieldHeight());<br /> <br /> setBodyColor(Color.black);<br /> setGunColor(Color.orange);<br /> setRadarColor(Color.yellow);<br /> setScanColor(Color.black);<br /> setBulletColor(Color.orange);<br /> <br /> turnLeft(getHeading() % 90);<br /> ahead(moveAmount);<br /> <br /> turnGunRight(90);<br /> turnRight(90);<br /> <br /> if((getY() + getWidth()/2) == getBattleFieldHeight() || (getY() - getWidth()/2) == 0) ahead(getX() - (getBattleFieldWidth()/2));<br /> if((getX() + getHeight()/2) == getBattleFieldWidth() || (getX() - getHeight()/2) == 0) ahead(getY() - (getBattleFieldHeight()/2));<br /> while(true) {<br /> }<br /> }<br /> <br /> The problem is obviously with the 2 'ifs', but I really can't get it. Thanks for any help!<br /> <br /> getX() &amp; getY() methods returns double value and you cannot compare them using ==, use something like this<br /> &lt;syntaxhighlight&gt;<br /> epsilon = 0.0001; // or another small value<br /> if (Math.abs((getY() + getWidth()/2) - getBattleFieldHeight()) &lt; eplsilon) {<br /> ahead(getX() - (getBattleFieldWidth()/2));<br /> }<br /> <br /> // or<br /> if (robocode.util.Utils.isNear(getY() + getWidth()/2, getBattleFieldHeight())) {<br /> ahead(getX() - (getBattleFieldWidth()/2));<br /> }<br /> &lt;/syntaxhighlight&gt;<br /> And it's better to ask questions like this on yours page --[[User:Jdev|Jdev]] 16:21, 14 September 2010 (UTC)<br /> <br /> == Strategy ==<br /> <br /> So I'm in high school and I'm in a first year Java class. Right now our project is to create a robot in robocode. The rules are the each battle will be fought with 3 to 4 players, the final battle will be 1 on 1, and we aren't allowed to use Advance Robot. There's so many opions in Robocode that I have no clue what's the best strategy going into this. Help!!!<br /> <br /> Thanks.<br /> <br /> The class [http://robocode.sourceforge.net/docs/robocode/robocode/JuniorRobot.html JuniorRobot] might work well for what you are doing. For your robot just make a class extending JuniorRobot. It could be helpful to override onScannedRobot() and perform actions in there. Also be sure to check out the [[Radar]] page and try to implement one of those radar locks because without a decent radar system your robot will be seriously limited. Just spinning the radar might work OK though. ex turnRadarRight(Double.POSITIVE_INFINITY);<br /> Also be sure to check out all the tutorials on this site.<br /> --&lt;font style=&quot;font-family:helvetica,arial,sans-serif;font-size:90%;letter-spacing:-1px;&quot;&gt;[[User:Exauge|Exauge]] ◊ [[User talk:Exauge|talk]]&lt;/font&gt; 02:56, 15 December 2010 (UTC)<br /> <br /> Well... don't get hit. :-) My advice to get started would be:<br /> * Check out the sample bots first, learn how and why they work.<br /> * Try to beat all the sample bots.<br /> * I'd also check with your teacher about using code from the RoboWiki / internet. There's plenty of code and tutorials available, but it's up to your teacher if you're allowed to use that code (even if the code's license says it's ok).<br /> * A page like [[Melee Strategy]] should be good to get the strategy gears turning.<br /> Good luck!<br /> <br /> --[[User:Voidious|Voidious]] 03:33, 15 December 2010 (UTC)<br /> <br /> == Question Forum ==<br /> <br /> Is there a question forum or something of the sort where people can ask random questions? {{unsigned|Starhammy}}<br /> <br /> No, but actually you can ask on [[Talk:Starhammy|your talk page]]. (I forgot to welcome you properly, so it's my bad you don't know where to ask) --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 12:53, 29 December 2010 (UTC)<br /> <br /> <br /> I got an email from some website (itbhu.ac.in). Apparently an Indian college is hosting a &quot;CodeFest&quot; tournament for about 730 something USD (35000 Indian Rupees, it says), and it's an extension of Robocode; it has different modes including Capture the Flag, and it adds walls to the battlefield itself. My main concern: is it safe to download, ie. it has no viruses or trojan horses whatsoever? --[[User:AWOL|AWOL]] 20:34, 31 January 2011 (UTC)<br /> <br /> : I don't know, but the first prize is only 15000, e.g. about 300 USD. The rest is for second, runner up, stuff like that. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 23:05, 31 January 2011 (UTC)<br /> <br /> : I'm rather confident it's safe. It is hosted at a well reputed Indian university, and the event seems to have some notable partners. I'll point this out though... it appears to be using a build of the &quot;custom-battlefields-workspace&quot; branch of Robocode, which hasn't kept up to date with the main Robocode changes since version 1.7.1.4. This means all known bugs in Robocode 1.7.1.4 likely apply, and some of them are rather... serious... for a competition (i.e. a teleport bug, and a kill-other-robot-threads bug) --[[User:Rednaxela|Rednaxela]] 00:20, 1 February 2011 (UTC)<br /> <br /> :: And also a lot of security vulnerabilities in that branch... --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 12:53, 1 February 2011 (UTC)<br /> <br /> : I've been playing around with it for the last couple days and it's seems to be just a different version of Robocode. Totally safe so far. Like Rednaxela said, it's just a reworked copy of the custom battlefield branch. I will say this, it's been a lot of fun working on how to detect objects in the battlefield... --[[User:KID|KID]] 20:58, 3 February 2011 (UTC)<br /> <br /> == Main Page overhaul ==<br /> <br /> I've been thinking the [[Main Page]] needs a serious overhaul. I'll probably experiment at [[User:Voidious/Main Page]] soon, and anyone else is of course free to do the same. Some of my thoughts apply to the wiki more generally, as well.<br /> * [[User:Rednaxela|Rednaxela]] commented to someone recently about how discussion-based this wiki community is. We've also been looking at [http://www.mediawiki.org/wiki/Extension:LiquidThreads LiquidThreads] because of that. We should probably point this out. I know I never visit Wikipedia's Recent Changes... I wonder how many people miss out on the community aspect of the RoboWiki?<br /> * Current events stuff needs to be removed or updated. <br /> * I don't think we need to list every Challenge. Maybe 2-3 of the recent ones and then links to the categories (which themselves could be polished a bit).<br /> * I think the &quot;Building a Bot&quot; section is really important. It's not bad right now, but could be better. We should probably link to more of the [[:Category:Robocode Documentation|Robocode docs]] stuff. [[Radar]] is the 2nd link and goes to a very detailed page, but [[:Category:Targeting|Targeting]] and [[:Category:Movement|Movement]] are not as newbie friendly.<br /> * Would be good to link to specific details about development tools - like [[:Category:Utilities|Utilities]], [[RoboResearch]], [[Robocode/Eclipse|Robocode/Eclipse]].<br /> * I think the layout and colors could also be revamped - especially that gray background is pretty drab.<br /> * Maybe more prominent and detailed info on the [[RoboRumble]].<br /> * Is the [http://twitter.com/roborumble @roborumble Twitter feed] interesting enough to include? (Like the [http://twitter.com/robowiki @robowiki] tweets on the sidebar.)<br /> I'm sure there's plenty more we could do, just some quick brainstorming for now...<br /> <br /> --[[User:Voidious|Voidious]] 19:01, 10 February 2011 (UTC)<br /> <br /> Another thing I think we need to note (especially to someone who is Wikipedia's editor) is that the RoboWiki is subpage-based, like we like Robocode/Getting_Start and not Getting_Start_to_Robocode. Just my two cents. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 10:59, 11 February 2011 (UTC)<br /> <br /> == About the spam... ==<br /> <br /> http://www.mediawiki.org/wiki/Extension:SpamBlacklist - See bottom of page for spamlists.<br /> http://www.mediawiki.org/wiki/Extension:ConfirmEdit - Has our old math captcha type thing in it.<br /> http://www.mediawiki.org/wiki/Extension:Bad_Behavior - No idea how this is suppose to work<br /> <br /> That is all. :)<br /> &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 16:39, 12 March 2011 (UTC)<br /> <br /> We already use ConfirmEdit in reCAPTCHA mode. I checked SpamBlacklist and it's blacklists don't match anything in the recent spam. Unsure about Bad_Behavior. Now, on the ConfirmEdit page, it does note that as of 2011 spammers seem to have gotten around reCAPTCHA by some means. --[[User:Rednaxela|Rednaxela]] 18:18, 12 March 2011 (UTC)<br /> <br /> I think the trick is to do something custom so that the usual anti-antispam techniques don't work. Just something simple like &quot;What is the next prime number after 7?&quot; or so. --[[User:Skilgannon|Skilgannon]] 08:40, 13 March 2011 (UTC)<br /> <br /> Maybe the spammer wait for autoconfirm to bypass the reCAPTCHA. Voidious, can we change the autoconfirm rules to four edits and ten days? And enable reCAPTCHA for every page edit in non-autoconfirm group? --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 01:41, 14 March 2011 (UTC)<br /> <br /> Ah, good call! I forgot about the autoconfirm stuff. I just changed it to 4 edits/10 days. I checked and we only skip the captcha if you're autoconfirmed, bot, or sysop, so I think we're good. Hopefully we'll be seeing less spam now... --[[User:Voidious|Voidious]] 01:56, 14 March 2011 (UTC)<br /> <br /> Since the spam was still coming in, I updated mediawiki, update the version of the ConfirmEdit extension, AND did some custom hacks to the ConfirmEdit extension to make it simultaneously require both reCAPTCHA and a LaTeX-rendered arithmetic question. Hopefully the combination of the two will keep this spam out for good :) --[[User:Rednaxela|Rednaxela]] 06:06, 19 March 2011 (UTC)<br /> <br /> I thought Voidious still keeping it up to date..... Well, Red, you have checked permission of upload folder, right? Every time Void upgrade the MediaWiki, he needs to re-set the permission of upload folder. Good thought with Recent Change cleanup, though.<br /> <br /> If the spam doesn't stop (as I believe many spambot can solve simple math image, I've face one), maybe you could have them solve equation ;-). --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 07:54, 19 March 2011 (UTC)<br /> <br /> Well, it wasn't *very* behind in versions, but was still 1.15.x as opposed to 1.16.x. Yep, I made sure to check the permissions for that I believe. Yeah, I wouldn't be surprised if some spambots can solve ConfirmEdit's MathCaptcha as-is, but I'm doubting that many spambots are designed to handle both that and reCAPTCHA on the same page. If they do however, I'll keep that suggestion in mind :) --[[User:Rednaxela|Rednaxela]] 13:57, 19 March 2011 (UTC)<br /> <br /> I took a look at the HTTP logs and the recent spambots have been jumping IP addresses, never solving the reCAPTCHA from the same IP that they requested it via. As a precaution, I further tweaked the captcha code to only accept answers as valid if they're from the same IP that was given that captcha. --[[User:Rednaxela|Rednaxela]] 15:34, 19 March 2011 (UTC)<br /> <br /> It seems like we're still getting a high number of users with odd names... might I suggest doing something custom? Doesn't have to be complicated, just &quot;the next prime number after X&quot; or &quot;the next number in the sequence 3 6 9 ...&quot; or some such. The trick is to make it not worth the time and effort for the spammer to implement a custom cracker just for robowiki. --[[User:Skilgannon|Skilgannon]] 13:04, 21 March 2011 (UTC)<br /> <br /> I've looked at the http logs for the IP addresses of those recent users, and they appear to be real people. They browsed some pages, made an account for some reason, browsed some more pages. Btw, an interesting stat: On March 21st so far (based on the server's clock), there have been 76 failed signup attempts due to captcha, and none of them browse pages before the signup attempt. --[[User:Rednaxela|Rednaxela]] 23:25, 21 March 2011 (UTC)<br /> <br /> Just seems odd to have 3 new people in 1 day =) Looks like it's stopped, nice work Red. I'm guessing the usage patterns would be a good attribute to block on if the spam ever picks up again in the future. --[[User:Skilgannon|Skilgannon]] 12:16, 22 March 2011 (UTC)<br /> <br /> Glad I could help by starting a thread about the problem. I also like making custom security. One of my favorite methods is changing the URL to the php or module that does the add page/register, and making a fake captcha (hidden via CSS, putting `anything` in it means you fail the check). :P &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 15:31, 24 March 2011 (UTC)<br /> <br /> ----<br /> Robot Repository is down. Can't get any of the newer bots nor run the game efficiencty :) --[[User:Miked0801|Miked0801]] 16:00, 16 May 2011 (UTC)<br /> I can delete this entry when the issue is fixed...<br /> <br /> It seems that Robot Repository has been down for about a week. Been trying to upload my newest bot but its not working. I need a place to upload my bot. --[[User:Khanguy|Khanguy]] 03:08, 17 May 2011 (UTC)<br /> <br /> Well, one idea for both of you would be to using Google Sites to upload your bot; I started doing that recently and found it to be much simpler and easier than uploading bots onto the repository.--[[User:CrazyBassoonist|CrazyBassoonist]] 03:45, 17 May 2011 (UTC)<br /> <br /> The problem being, I can't get the latest bots for running the rumble nor competing against you CB :) --[[User:Miked0801|Miked0801]] 04:28, 17 May 2011 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=Talk:Main_Page&diff=19293 2011-05-16T16:00:02Z

<p>Miked0801: Repository down. Can't play :)</p> <hr /> <div>== Why is the &quot;Robo Wiki&quot; icon in the upper left corner so small? ==<br /> The headline speaks for itself. --[[User:Awesomeness|Awesomeness]] 21:08, 3 May 2009 (UTC)<br /> <br /> So small? It seems just right to me really. --[[User:Rednaxela|Rednaxela]] 21:56, 3 May 2009 (UTC)<br /> <br /> Because it is the same size as the old wiki =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 23:41, 3 May 2009 (UTC)<br /> <br /> <br /> http://www.csdgn.org/files/images/robowiki2.png<br /> <br /> I have a solution to this! I was bored so I drew this (though it is probably too big!). I realize I forgot the radar, but to be honest, from this angle it would block to much however. Just consider it a drone! --[[User:Chase-san|Chase]] 21:50, 20 June 2010 (UTC)<br /> <br /> : You could just said that it is a Droid instead of saying that you forgot them... --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 13:36, 21 June 2010 (UTC)<br /> <br /> :: I like it - it looks good :) on the current one you cant really read wiki because its blocked but this looks really good :) --&lt;font style=&quot;font-family:helvetica,arial,sans-serif;font-size:90%;letter-spacing:-1px;&quot;&gt;[[User:Exauge|Exauge]] ◊ [[User talk:Exauge|talk]]&lt;/font&gt; 14:51, 21 June 2010 (UTC)<br /> <br /> :: I suppose I could have. On another note, I notice that some of my shadows are wrong/inconsistent. --[[User:Chase-san|Chase]] 15:30, 21 June 2010 (UTC)<br /> <br /> : Looks really nice! I like it. Of course I have a soft spot for the old one, but this one's also very true to the original idea. And the text is way more readable. --[[User:Voidious|Voidious]] 00:05, 22 June 2010 (UTC)<br /> <br /> http://www.csdgn.org/files/images/robowiki3.png<br /> <br /> I fixed some of my shadow work in this. I made the wording a bit more visible as well (by adding more depth to it). I also made the book lines heavier. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 06:25, 20 July 2010 (UTC)<br /> <br /> http://www.csdgn.org/files/images/robowiki_thumb.png<br /> <br /> Obviously this is to big to go in the corner, but I made a reduced size one. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 06:28, 20 July 2010 (UTC)<br /> <br /> Was a decision ever reached on this, because I am considering redrawing this (but better). &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 20:13, 18 January 2011 (UTC)<br /> <br /> I'm up for changing it and I don't think anybody objected. Just fell off my radar - sorry! I think my only criticism of that first one is that the &quot;IKI&quot; is a little smushed together. --[[User:Voidious|Voidious]] 20:20, 18 January 2011 (UTC)<br /> <br /> Well (I personally think) my art has improved considerably since I drew this. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 21:31, 18 January 2011 (UTC)<br /> <br /> : If nothing else, I will go over it with a pen and clean up the line work. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 21:38, 18 January 2011 (UTC)<br /> <br /> http://www.csdgn.org/files/images/robowiki2_small.png<br /> <br /> Here is the new version. It's a bit cleaner, though it doesn't have as much character (because it is so much cleaner). &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 02:01, 19 January 2011 (UTC)<br /> <br /> Nice stuff, looks pretty good to me :) --[[User:Rednaxela|Rednaxela]] 06:04, 19 January 2011 (UTC)<br /> <br /> So are we going to use it? &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 16:12, 8 February 2011 (UTC)<br /> <br /> Just updated it. I think it looks really nice, it really changes the look of the page a lot more than I expected. Let me know if anyone sees it looking weird anywhere - I'm not exactly a CSS guru. :-P Nice job, Chase! --[[User:Voidious|Voidious]] 17:40, 8 February 2011 (UTC)<br /> <br /> : You just change the $wgLogo, right? I don't think it would affect the page at all. I does feel weird at first, I agree. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 15:18, 9 February 2011 (UTC)<br /> <br /> :: Yeah, but the new one is taller so I had to move the sidebar down a bit. Took me a while to track down the right CSS to change. =) --[[User:Voidious|Voidious]] 15:22, 9 February 2011 (UTC)<br /> <br /> What about the favicon? --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 10:59, 11 February 2011 (UTC)<br /> <br /> == Does robo rumble work? ==<br /> hi im new to robocode, been doing it as part of my uni course and i was wondering, is it possible to run roborumble at home anymore because ive follwed the instructions and none of the battles ive been doing have been uploading.... [[User:Quietus|Quietus]] 15:47, 21 November 2008 (UTC)<br /> <br /> Yep! It sure as he heck still works! The thing is, the rumble.fervir.com server has been kind of broken for a while. You need to point your client at [http://darkcanuck.net/rumble/ this URL] instead now (See [[Darkcanuck/RRServer|here]] for more information). There's new fanciness in that server too :) --[[User:Rednaxela|Rednaxela]] 19:48, 21 November 2008 (UTC)<br /> <br /> == Article count ==<br /> <br /> A couple questions about the article count (after having some trouble Googling for answers). First, why isn't it updating automatically? Is that something I can trigger to update, or add to the &quot;job queue&quot;, does anyone know? (Notice if you edit / preview it is higher than 43, which it reads on the main page right now.) Second, what qualifies as an &quot;article&quot;? Is there a minimum length that a page needs to be (other than not being a user or talk page) to qualify as an article? --[[User:Voidious|Voidious]] 19:56, 12 November 2007 (UTC)<br /> :The main page just updated, it now says 48 articles. Also, the statistics page says that there are 145 pages total, but it is excluding, &quot;talk pages, pages about RoboWiki, minimal 'stub' pages, redirects, and others that probably don't qualify as content pages.&quot; --[[User:AaronR|AaronR]] 20:00, 12 November 2007 (UTC)<br /> <br /> According to the MediaWiki wiki (now that's a mouthful), the main page will come up to date as soon as its HTML cache is invalidated, at which point all of the templates, etc. will be transcluded again. Don't know if that helps... --[[User:AaronR|AaronR]] 20:27, 12 November 2007 (UTC)<br /> <br /> == Font size ==<br /> <br /> Just out of curiosity, why is the font size so large here compared to, say, Wikipedia? I know, I know, it's the same as the old wiki's font, but that wiki didn't have a sidebar. --[[User:AaronR|AaronR]] 07:04, 13 November 2007 (UTC)<br /> <br /> : Primarily because I thought &quot;x-small&quot; was just too small, and yes, it was also just sooo much smaller than the old wiki. I also figured that with the skins options, we could easily give people more choices to choose their own style, anyway. I will confess that tiny fonts for the sake of sleeker designs is a major pet peeve of mine. :-P --[[User:Voidious|Voidious]] 07:12, 13 November 2007 (UTC)<br /> <br /> == Smileys :-) ==<br /> <br /> I would be relly nice if we could somehow support smile, e.g. just as simple as stating:<br /> <br /> &lt;pre&gt;[[Image:HappySmiley.png]]&lt;/pre&gt;<br /> <br /> --[[User:FlemmingLarsen|Flemming N. Larsen]] 09:04, 28 November 2007 (UTC)<br /> <br /> Wikimedia Commons has a [http://commons.wikimedia.org/wiki/Smiley whole section] of GFDL'd or public domain smileys (look at the link at the bottom for more). I don't really see the point though. If you want to upload them and use them, feel free, but I'll stick with =) on the wiki. --&lt;code&gt;[[User:AaronR|AaronR]]&lt;/code&gt; 01:21, 30 November 2007 (UTC)<br /> <br /> == Old wiki ==<br /> The old wiki is not working (error 500), and so my roborumble client (it cannot find the list of partecipants), but i see many client is uploading. What is your solution?<br /> --[[User:Lestofante|Lestofante]] 10:35, 1 Dic 2008 (UTC)<br /> <br /> The clients currently running are just using the last copy of the participants list they downloaded from the old wiki. I emailed PEZ a bit ago and got a reply that he'll look into it so hopefully the old wiki will be up again in not too long. If that ends up taking longer than expected though, we could update/fix the participants page on the new wiki and point clients at that instead. (Note: Don't point clients at the one on the new wiki just yet, it's out of date and such. It needs to be copied over from a downloaded copy of the list from the old wiki) --[[User:Rednaxela|Rednaxela]] 12:00, 1 December 2008 (UTC)<br /> <br /> maybe we can drop definitely the old wiki for roborumble client, or better every ramble server can implements it's own participants list, maybe integrated with general wiki list<br /> --[[User:Lestofante|Lestofante]] 15:13, 1 Dic 2008 (UTC)<br /> <br /> I'd agree that migrating to using the new wiki participants list would be good, though I think some more veteran wikiers/rumblers than myself should give their input before any such switch is made 'official'. As far as keeping a participants list with the rumble server, well, there's only one working rumble server at the moment so I'm not sure what good that would do, and furthermore multiple rumble server would be a bad thing I think becacuse it would divide the processing power that goes towards making the battles. --[[User:Rednaxela|Rednaxela]] 17:47, 1 December 2008 (UTC)<br /> <br /> That's right, then I thing the server have to had a mirror of the wiki's official participants list, so in this case we can continue run our client, simple we cannot modify the list (if the two list are not synchronize together) <br /> --[[User:Lestofante|Lestofante]] 21:49, 1 Dic 2008 (UTC)<br /> <br /> Yeah, the real problem is getting the participants list from the currently-erroring wiki. The RR client has no problem parsing the new wiki format. I may be able to get that from the RoboWiki server when I get home (if it isn't fixed before then). <br /> <br /> The other issue we might encounter in the future would be when we move this wiki to robowiki.net, and we have RR clients pointing to testwiki.roborumble.org, but I don't think forwarding that URL and/or having people update their clients would be a big issue. I'm glad you contacted PEZ about the old wiki's current problems, I've been out of touch for at least a week...<br /> <br /> --[[User:Voidious|Voidious]] 19:03, 2 December 2008 (UTC)<br /> <br /> Okay to mention it here as well for people who haven't been checking up on it... The old wiki is back up! --[[User:Rednaxela|Rednaxela]] 18:43, 9 December 2008 (UTC)<br /> <br /> == mailer error ==<br /> I'm trying to confirm my user e-mail, but I still get &quot;mailer error&quot;. I've tried 3 different and working address... and there is a way for automatically sign the edits?<br /> --[[User:Lestofante|Lestofante]] 22:00, 1 Dic 2008 (UTC)<br /> <br /> : I couldn't get the mailer to work either, but you can easily sign your edits using &lt;nowiki&gt;--~~~~&lt;/nowiki&gt;. See http://meta.wikimedia.org/wiki/Cheatsheet for more tricks. --[[User:Darkcanuck|Darkcanuck]] 03:13, 2 December 2008 (UTC)<br /> <br /> == InterWiki Links ==<br /> Who have fully access to this server apart from [[User:David Alves|David Alves]]? I want both my thai wiki and this wiki a inter-languages link. Please look [[User_talk:Nat#New_Thai_RoboWiki|here]] for more detailed. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 15:16, 15 April 2009 (UTC)<br /> <br /> I have full access, or at least I do if I can remember the password. =) I'll see about logging in and taking a look at the InterWiki stuff. Sorry it took so long to respond about this. --[[User:Voidious|Voidious]] 14:50, 16 April 2009 (UTC)<br /> <br /> Hey Voidious, I believed that the SQL will take less than 1 seconds to copy/past/execute. Plus login/connecting time I think this can be accomplished within a minute so please do asap (or I must say NOW). &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 16:19, 22 April 2009 (UTC)<br /> <br /> Hey Nat - I will add the InterWiki link because I'd like to support your efforts to start a Thai Robocode community and wiki. But I really don't appreciate being commanded to do that (or much of anything, really), and especially to do so &quot;NOW&quot;. Please keep in mind the RoboWiki's only rule: &quot;Pretty please be polite.&quot; --[[User:Voidious|Voidious]] 18:48, 22 April 2009 (UTC)<br /> <br /> Cool, I read up on the InterWiki stuff, added your Thai wiki to the database, and posted a link on the main page. As I can't read Thai, please make sure that looks right and edit it if necessary. =) --[[User:Voidious|Voidious]] 22:54, 22 April 2009 (UTC)<br /> <br /> Sorry for that rude. But anyways, thank you very much. The link at main page is correct. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 01:37, 23 April 2009 (UTC)<br /> <br /> == Database error ==<br /> I didn't know where to put this, but here seems like a decent spot. All my posts are getting this message today (4 times, probably 5 with this one), the posts are still uploaded but the message is:<br /> &lt;pre&gt;<br /> A database query syntax error has occurred. This may indicate a bug in the software.<br /> The last attempted database query was:<br /> (SQL query hidden)<br /> from within function &quot;SearchMySQL4::update&quot;.<br /> MySQL returned error &quot;126: Incorrect key file for table './wikidb/searchindex.MYI'; try to repair it (localhost)&quot;.<br /> &lt;/pre&gt;<br /> <br /> I don't know if ''localhost'' is meant to be from mine point of view, or the server's. Maybe someone else is getting the same messages, I haven't tried to logout/in, because I just thought of that. --[[User:Zyx|zyx]] 23:47, 5 May 2009 (UTC)<br /> : Just like when you go to the mechanic, I didn't get the message this time. Another piece of information may be that all the other 4 posts where at [[Talk:PwnBot‎]], so maybe the problem relies in that page. --[[User:Zyx|zyx]] 23:49, 5 May 2009 (UTC)<br /> <br /> :: I found some mentions of people hitting this, and it sounds like a &quot;repair table&quot; SQL command is the remedy. I've run that now, so hopefully it's fixed. Can you let me know if it happens again? Thanks, --[[User:Voidious|Voidious]] 00:31, 6 May 2009 (UTC)<br /> <br /> ::: Just got it again, and again in the same page [[Talk:PwnBot‎]]. --[[User:Zyx|zyx]] 20:45, 6 May 2009 (UTC)<br /> <br /> :::: Thanks for the info. I saw it as well when I posted the downtime note. I'm guessing the server crashing corrupted the searchindex table -- I'll rerun the &quot;repair table&quot; and post here when I do. I'll also be backing up the database very soon. --[[User:Voidious|Voidious]] 20:52, 6 May 2009 (UTC)<br /> <br /> ::Is it... My fault?! I created that page. It seems whenever I change a page I get it too. It doesn't matter what page I go to. Also, for the majority of today, (for me at least) it seems your server has been down. I've been unable to connect. --[[User:Awesomeness|Awesomeness]] 22:04, 6 May 2009 (UTC)<br /> <br /> ::: It's not your fault, and I saw it on another page too. The server went down for a while as of last night, still not sure what happened, but glad it's back up. I've rerun the &quot;repair table&quot; command, so I think that database error will go away for now. --[[User:Voidious|Voidious]] 22:06, 6 May 2009 (UTC)<br /> <br /> :::: I now know why I can't access the wiki (and roborumble.org) yesterday. Night there, afternoon here. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 00:25, 7 May 2009 (UTC)<br /> <br /> == SourceForge.net Community Choices Awards ==<br /> <br /> &lt;div style=&quot;text-align:center; border: 5px solid #ccc&quot;&gt;<br /> http://sourceforge.net/images/cca/cca_nominate.png<br /> <br /> Please nominate Robocode to SourceForge.net Community Choices Awards!&lt;br /&gt;<br /> [http://sourceforge.net/community/cca09/nominate/?project_name=Robocode&amp;project_url=http://robocode.sourceforge.net/ Nominate Robocode]<br /> &lt;/div&gt;<br /> <br /> Anyone mind to put this to [[MediaWiki:Sitenotice]] or front page? I not sure if I can post to front page. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 10:21, 15 May 2009 (UTC)<br /> <br /> Please nominate Robocode in category of &quot;Best Project for Academia&quot; and &quot;Most Likely to Change the Way You Do Everything&quot;. If you nominate to another category, please post here so other robocoder can nominate in same categories (note that you can nominate in multiple categories) Nevertheless, please [http://sourceforge.net/community/cca09/nominate/?project_name=Robocode&amp;project_url=http://robocode.sourceforge.net/ nominate]! &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 11:26, 18 May 2009 (UTC)<br /> <br /> == [[Special:Disambiguations]] ==<br /> <br /> Do anyone know why the [[Special:Disambiguations]] has spammy report? &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 11:23, 18 May 2009 (UTC)<br /> <br /> == Image Uploads ==<br /> <br /> It looks like the image uploads folder is not set as writable to the wiki. Is this expected to change? -- [[User:Synapse|&lt;font style=&quot;font-size:0.8em;font-variant:small-caps;&quot;&gt;Synapse&lt;/font&gt;]] 05:27, 10 June 2009 (UTC)<br /> <br /> Haven't test yet. If this is true, I think this problem cause due the upgrading of MediaWiki. Voidious, check it please? Another note to Voidious, MediaWiki/1.15 just release =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 13:29, 10 June 2009 (UTC)<br /> <br /> Not sure why it stopped working, but I'll take a look at the image uploads and upgrading MediaWiki this afternoon. (And making a mental note to test that whenever I upgrade. =)) --[[User:Voidious|Voidious]] 15:41, 11 June 2009 (UTC)<br /> <br /> Fixed the uploading issue and upgraded MedaWiki to 1.15. Enjoy. =) --[[User:Voidious|Voidious]] 20:10, 11 June 2009 (UTC)<br /> <br /> == /wiki/PageName-style url ==<br /> <br /> Recently this day I noticed that the /wiki/PageName-style URL is now work. Voidious, why don't you set the &lt;code&gt;$wgArticlePath = &quot;/wiki/$1&quot;&lt;/code&gt; in LocalSettings.php? And I wonder why the old server at 174.132.4.195 now has new wiki code, and available in both /wiki/PageName and ?PageName style (but not /w/index.php?title=PageName style). What's going on? &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 12:56, 27 June 2009 (UTC)<br /> <br /> == Syntax Highlighting ==<br /> <br /> It would be great if we could have syntax highlighting for code snippets. This would make code snippets easier to read. Currently, if I want to read a code snippet from the wiki, I would copy and paste it into my favourite text editor.<br /> <br /> Wikipedia itself seems to use [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi SyntaxHighlight GeSHi].&amp;mdash;<br /> <br /> [[User:Duyn|Duyn]] 14:56, 17 January 2010 (UTC)<br /> <br /> [[User:Voidious/RoboWiki_To-Do]] --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 13:41, 18 January 2010 (UTC)<br /> <br /> Yeah, that's been on my to-do list for a while, I'll try to get it up and running soon. Can't be too tough. =) --[[User:Voidious|Voidious]] 16:12, 19 January 2010 (UTC)<br /> <br /> == Favicon ==<br /> <br /> I just noticed that the new Robowiki doesn't have a favicon. This is easily remedied by copying http://old.robowiki.net/favicon.ico so that it is accessible at http://robowiki.net/favicon.ico --[[User:Skilgannon|Skilgannon]] 18:00, 17 January 2010 (UTC)<br /> <br /> : Will do. --[[User:Voidious|Voidious]] 16:12, 19 January 2010 (UTC)<br /> <br /> == Robocode on Wikipedia ==<br /> <br /> Well, [[wikipedia:Robocode]] article is just challenged for reference, as well as a original research. Please help it by adding reference. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 15:09, 15 April 2010 (UTC)<br /> <br /> Honestly, I believe many things on the wikipedia article, at least 2/3rds of the page, just plain don't belong on Wikiedia, due to valid reasons. In fact I'm not sure anything beyond the overview and the first two sections belong, given how Wikipedia's 'original research' and 'notability' criteria apply to such sections. Even those sections which do make sense to keep to desperately need citations. Essentially, I don't feel the sections [http://en.wikipedia.org/w/index.php?title=Robocode&amp;action=historysubmit&amp;diff=37661690&amp;oldid=35178091 added by PEZ] fit wikipedia's criteria for what belongs. So... I think it does deserve to be challenged for good reason. I don't have time to improve what should stay though. --[[User:Rednaxela|Rednaxela]] 16:39, 15 April 2010 (UTC)<br /> <br /> I'll make more comments on the Wikipedia talk page, but I agree it needs a lot of cleanup and I'm willing to help out with that. I half agree with Rednaxela. The overview and first 2 sections are fine and neutral. The rest could use a lot of cleaning up, but I don't think it all needs just to be axed. Some editing down / revising / adding citations should do the trick. (I think the RoboWiki is a &quot;reliable source&quot;? If not, I don't know what is.) --[[User:Voidious|Voidious]] 19:03, 15 April 2010 (UTC)<br /> <br /> : Well, while I would personally consider Robowiki a &quot;reliable source&quot; for my own purposes, it seems to me it violates some of what is noted on [[wikipedia:Wikipedia:Verifiability#Self-published_sources_.28online_and_paper.29|Wikipedia:Verifiability#Self-published_sources]], in particular how it notes &quot;open wikis&quot; among other things as &quot;largely not acceptable&quot;. Also, note the &quot;no original research&quot; policies, and consider that much of the purpose of Robowiki is for &quot;original research&quot;. There is a significant difference between a source one trusts, and a source that fits Wikipedia's rules. --[[User:Rednaxela|Rednaxela]] 01:54, 16 April 2010 (UTC)<br /> <br /> : Hmm, thanks. I really don't know much about Wikipedia's policies, but just starting to read up on it now. In that case, you are probably right that a lot of stuff needs to just be axed... --[[User:Voidious|Voidious]] 13:46, 16 April 2010 (UTC)<br /> <br /> == &quot;Robocode Guidebook&quot; ==<br /> <br /> ''Migrated to [[Talk:Robocode Guidebook]]''<br /> <br /> == RoboCode Chat / IM ==<br /> <br /> So it is to my understanding that currently the only real way for robocoders to talk is on talk pages on this wiki so I had this idea... what if we had an IM type web chat system for Robocoders to talk :) within a few months i could probably get a website set up to do that and it would use the open-source [https://blueimp.net/ajax/ AJAX project]. What do you all think of the idea? --[[User:Exauge|Exauge]] 00:33, 15 May 2010 (UTC)<br /> <br /> I think we have an (deserted) IRC channel (or not?). But actually I do chat with some Robocoder through GTalk and e-mail. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 00:38, 15 May 2010 (UTC)<br /> <br /> Seems like a lot of work. =) Some of us have each other on IM. I use my handle on AIM and my handle at gmail for GTalk/Jabber. (But my AIM is set so you can't see my status if I don't have you as a buddy.) We used to have [[oldwiki:ContactInfo]], but there's no current page with that kind of info. --[[User:Voidious|Voidious]] 00:41, 15 May 2010 (UTC)<br /> <br /> Hi, anyways I've started working on a Robocode talk page and it's getting to be pretty sweet ;) I can probably have it finished in a few weeks (maybe sooner) and anyways if you like it you will all be very welcome to use it and if it's popular enough I might purchase a domain name for it :) and if not, well it's a good way for me to practice my website building skills :) anyways back to studying for tomorrow's exams lol :S --[[User:Exauge|Exauge]]<br /> <br /> Well, personally anyway, if were to have a robocode live chat place, I'd strongly prefer it be an IRC channel (i.e. on Freenode?). Mostly because I always have an IRC client running anyway, and those without an IRC client can still sign in via a web page (i.e. [http://www.mibbit.com/] and [http://webchat.freenode.net/]). Also, IRC is probably about the most mature system for such things anyway, and it's nearly maintain free to maintain a channel. --[[User:Rednaxela|Rednaxela]] 04:03, 17 May 2010 (UTC)<br /> <br /> == Wall Avoidance ==<br /> <br /> ''moved to [[Talk:DustBunny]]...''<br /> <br /> == Walking to the center of the wall ==<br /> <br /> Well, i'm trying to make a Robot that goes to one of the walls, walk to the center of it an then start to circulate the entire Field, touching the center of each wall.<br /> <br /> Anyway, I'm having problems to take the Robot to the center of one of the walls. That's what i'm doing:<br /> <br /> package MyRobots;<br /> import robocode.*;<br /> import java.awt.*;<br /> <br /> public class Walle extends AdvancedRobot<br /> {<br /> double moveAmount;<br /> int miss = 0, hit = 0;<br /> <br /> public void run() {<br /> <br /> moveAmount = Math.max(getBattleFieldWidth(), getBattleFieldHeight());<br /> <br /> setBodyColor(Color.black);<br /> setGunColor(Color.orange);<br /> setRadarColor(Color.yellow);<br /> setScanColor(Color.black);<br /> setBulletColor(Color.orange);<br /> <br /> turnLeft(getHeading() % 90);<br /> ahead(moveAmount);<br /> <br /> turnGunRight(90);<br /> turnRight(90);<br /> <br /> if((getY() + getWidth()/2) == getBattleFieldHeight() || (getY() - getWidth()/2) == 0) ahead(getX() - (getBattleFieldWidth()/2));<br /> if((getX() + getHeight()/2) == getBattleFieldWidth() || (getX() - getHeight()/2) == 0) ahead(getY() - (getBattleFieldHeight()/2));<br /> while(true) {<br /> }<br /> }<br /> <br /> The problem is obviously with the 2 'ifs', but I really can't get it. Thanks for any help!<br /> <br /> getX() &amp; getY() methods returns double value and you cannot compare them using ==, use something like this<br /> &lt;syntaxhighlight&gt;<br /> epsilon = 0.0001; // or another small value<br /> if (Math.abs((getY() + getWidth()/2) - getBattleFieldHeight()) &lt; eplsilon) {<br /> ahead(getX() - (getBattleFieldWidth()/2));<br /> }<br /> <br /> // or<br /> if (robocode.util.Utils.isNear(getY() + getWidth()/2, getBattleFieldHeight())) {<br /> ahead(getX() - (getBattleFieldWidth()/2));<br /> }<br /> &lt;/syntaxhighlight&gt;<br /> And it's better to ask questions like this on yours page --[[User:Jdev|Jdev]] 16:21, 14 September 2010 (UTC)<br /> <br /> == Strategy ==<br /> <br /> So I'm in high school and I'm in a first year Java class. Right now our project is to create a robot in robocode. The rules are the each battle will be fought with 3 to 4 players, the final battle will be 1 on 1, and we aren't allowed to use Advance Robot. There's so many opions in Robocode that I have no clue what's the best strategy going into this. Help!!!<br /> <br /> Thanks.<br /> <br /> The class [http://robocode.sourceforge.net/docs/robocode/robocode/JuniorRobot.html JuniorRobot] might work well for what you are doing. For your robot just make a class extending JuniorRobot. It could be helpful to override onScannedRobot() and perform actions in there. Also be sure to check out the [[Radar]] page and try to implement one of those radar locks because without a decent radar system your robot will be seriously limited. Just spinning the radar might work OK though. ex turnRadarRight(Double.POSITIVE_INFINITY);<br /> Also be sure to check out all the tutorials on this site.<br /> --&lt;font style=&quot;font-family:helvetica,arial,sans-serif;font-size:90%;letter-spacing:-1px;&quot;&gt;[[User:Exauge|Exauge]] ◊ [[User talk:Exauge|talk]]&lt;/font&gt; 02:56, 15 December 2010 (UTC)<br /> <br /> Well... don't get hit. :-) My advice to get started would be:<br /> * Check out the sample bots first, learn how and why they work.<br /> * Try to beat all the sample bots.<br /> * I'd also check with your teacher about using code from the RoboWiki / internet. There's plenty of code and tutorials available, but it's up to your teacher if you're allowed to use that code (even if the code's license says it's ok).<br /> * A page like [[Melee Strategy]] should be good to get the strategy gears turning.<br /> Good luck!<br /> <br /> --[[User:Voidious|Voidious]] 03:33, 15 December 2010 (UTC)<br /> <br /> == Question Forum ==<br /> <br /> Is there a question forum or something of the sort where people can ask random questions? {{unsigned|Starhammy}}<br /> <br /> No, but actually you can ask on [[Talk:Starhammy|your talk page]]. (I forgot to welcome you properly, so it's my bad you don't know where to ask) --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 12:53, 29 December 2010 (UTC)<br /> <br /> <br /> I got an email from some website (itbhu.ac.in). Apparently an Indian college is hosting a &quot;CodeFest&quot; tournament for about 730 something USD (35000 Indian Rupees, it says), and it's an extension of Robocode; it has different modes including Capture the Flag, and it adds walls to the battlefield itself. My main concern: is it safe to download, ie. it has no viruses or trojan horses whatsoever? --[[User:AWOL|AWOL]] 20:34, 31 January 2011 (UTC)<br /> <br /> : I don't know, but the first prize is only 15000, e.g. about 300 USD. The rest is for second, runner up, stuff like that. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 23:05, 31 January 2011 (UTC)<br /> <br /> : I'm rather confident it's safe. It is hosted at a well reputed Indian university, and the event seems to have some notable partners. I'll point this out though... it appears to be using a build of the &quot;custom-battlefields-workspace&quot; branch of Robocode, which hasn't kept up to date with the main Robocode changes since version 1.7.1.4. This means all known bugs in Robocode 1.7.1.4 likely apply, and some of them are rather... serious... for a competition (i.e. a teleport bug, and a kill-other-robot-threads bug) --[[User:Rednaxela|Rednaxela]] 00:20, 1 February 2011 (UTC)<br /> <br /> :: And also a lot of security vulnerabilities in that branch... --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 12:53, 1 February 2011 (UTC)<br /> <br /> : I've been playing around with it for the last couple days and it's seems to be just a different version of Robocode. Totally safe so far. Like Rednaxela said, it's just a reworked copy of the custom battlefield branch. I will say this, it's been a lot of fun working on how to detect objects in the battlefield... --[[User:KID|KID]] 20:58, 3 February 2011 (UTC)<br /> <br /> == Main Page overhaul ==<br /> <br /> I've been thinking the [[Main Page]] needs a serious overhaul. I'll probably experiment at [[User:Voidious/Main Page]] soon, and anyone else is of course free to do the same. Some of my thoughts apply to the wiki more generally, as well.<br /> * [[User:Rednaxela|Rednaxela]] commented to someone recently about how discussion-based this wiki community is. We've also been looking at [http://www.mediawiki.org/wiki/Extension:LiquidThreads LiquidThreads] because of that. We should probably point this out. I know I never visit Wikipedia's Recent Changes... I wonder how many people miss out on the community aspect of the RoboWiki?<br /> * Current events stuff needs to be removed or updated. <br /> * I don't think we need to list every Challenge. Maybe 2-3 of the recent ones and then links to the categories (which themselves could be polished a bit).<br /> * I think the &quot;Building a Bot&quot; section is really important. It's not bad right now, but could be better. We should probably link to more of the [[:Category:Robocode Documentation|Robocode docs]] stuff. [[Radar]] is the 2nd link and goes to a very detailed page, but [[:Category:Targeting|Targeting]] and [[:Category:Movement|Movement]] are not as newbie friendly.<br /> * Would be good to link to specific details about development tools - like [[:Category:Utilities|Utilities]], [[RoboResearch]], [[Robocode/Eclipse|Robocode/Eclipse]].<br /> * I think the layout and colors could also be revamped - especially that gray background is pretty drab.<br /> * Maybe more prominent and detailed info on the [[RoboRumble]].<br /> * Is the [http://twitter.com/roborumble @roborumble Twitter feed] interesting enough to include? (Like the [http://twitter.com/robowiki @robowiki] tweets on the sidebar.)<br /> I'm sure there's plenty more we could do, just some quick brainstorming for now...<br /> <br /> --[[User:Voidious|Voidious]] 19:01, 10 February 2011 (UTC)<br /> <br /> Another thing I think we need to note (especially to someone who is Wikipedia's editor) is that the RoboWiki is subpage-based, like we like Robocode/Getting_Start and not Getting_Start_to_Robocode. Just my two cents. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 10:59, 11 February 2011 (UTC)<br /> <br /> == About the spam... ==<br /> <br /> http://www.mediawiki.org/wiki/Extension:SpamBlacklist - See bottom of page for spamlists.<br /> http://www.mediawiki.org/wiki/Extension:ConfirmEdit - Has our old math captcha type thing in it.<br /> http://www.mediawiki.org/wiki/Extension:Bad_Behavior - No idea how this is suppose to work<br /> <br /> That is all. :)<br /> &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 16:39, 12 March 2011 (UTC)<br /> <br /> We already use ConfirmEdit in reCAPTCHA mode. I checked SpamBlacklist and it's blacklists don't match anything in the recent spam. Unsure about Bad_Behavior. Now, on the ConfirmEdit page, it does note that as of 2011 spammers seem to have gotten around reCAPTCHA by some means. --[[User:Rednaxela|Rednaxela]] 18:18, 12 March 2011 (UTC)<br /> <br /> I think the trick is to do something custom so that the usual anti-antispam techniques don't work. Just something simple like &quot;What is the next prime number after 7?&quot; or so. --[[User:Skilgannon|Skilgannon]] 08:40, 13 March 2011 (UTC)<br /> <br /> Maybe the spammer wait for autoconfirm to bypass the reCAPTCHA. Voidious, can we change the autoconfirm rules to four edits and ten days? And enable reCAPTCHA for every page edit in non-autoconfirm group? --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 01:41, 14 March 2011 (UTC)<br /> <br /> Ah, good call! I forgot about the autoconfirm stuff. I just changed it to 4 edits/10 days. I checked and we only skip the captcha if you're autoconfirmed, bot, or sysop, so I think we're good. Hopefully we'll be seeing less spam now... --[[User:Voidious|Voidious]] 01:56, 14 March 2011 (UTC)<br /> <br /> Since the spam was still coming in, I updated mediawiki, update the version of the ConfirmEdit extension, AND did some custom hacks to the ConfirmEdit extension to make it simultaneously require both reCAPTCHA and a LaTeX-rendered arithmetic question. Hopefully the combination of the two will keep this spam out for good :) --[[User:Rednaxela|Rednaxela]] 06:06, 19 March 2011 (UTC)<br /> <br /> I thought Voidious still keeping it up to date..... Well, Red, you have checked permission of upload folder, right? Every time Void upgrade the MediaWiki, he needs to re-set the permission of upload folder. Good thought with Recent Change cleanup, though.<br /> <br /> If the spam doesn't stop (as I believe many spambot can solve simple math image, I've face one), maybe you could have them solve equation ;-). --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 07:54, 19 March 2011 (UTC)<br /> <br /> Well, it wasn't *very* behind in versions, but was still 1.15.x as opposed to 1.16.x. Yep, I made sure to check the permissions for that I believe. Yeah, I wouldn't be surprised if some spambots can solve ConfirmEdit's MathCaptcha as-is, but I'm doubting that many spambots are designed to handle both that and reCAPTCHA on the same page. If they do however, I'll keep that suggestion in mind :) --[[User:Rednaxela|Rednaxela]] 13:57, 19 March 2011 (UTC)<br /> <br /> I took a look at the HTTP logs and the recent spambots have been jumping IP addresses, never solving the reCAPTCHA from the same IP that they requested it via. As a precaution, I further tweaked the captcha code to only accept answers as valid if they're from the same IP that was given that captcha. --[[User:Rednaxela|Rednaxela]] 15:34, 19 March 2011 (UTC)<br /> <br /> It seems like we're still getting a high number of users with odd names... might I suggest doing something custom? Doesn't have to be complicated, just &quot;the next prime number after X&quot; or &quot;the next number in the sequence 3 6 9 ...&quot; or some such. The trick is to make it not worth the time and effort for the spammer to implement a custom cracker just for robowiki. --[[User:Skilgannon|Skilgannon]] 13:04, 21 March 2011 (UTC)<br /> <br /> I've looked at the http logs for the IP addresses of those recent users, and they appear to be real people. They browsed some pages, made an account for some reason, browsed some more pages. Btw, an interesting stat: On March 21st so far (based on the server's clock), there have been 76 failed signup attempts due to captcha, and none of them browse pages before the signup attempt. --[[User:Rednaxela|Rednaxela]] 23:25, 21 March 2011 (UTC)<br /> <br /> Just seems odd to have 3 new people in 1 day =) Looks like it's stopped, nice work Red. I'm guessing the usage patterns would be a good attribute to block on if the spam ever picks up again in the future. --[[User:Skilgannon|Skilgannon]] 12:16, 22 March 2011 (UTC)<br /> <br /> Glad I could help by starting a thread about the problem. I also like making custom security. One of my favorite methods is changing the URL to the php or module that does the add page/register, and making a fake captcha (hidden via CSS, putting `anything` in it means you fail the check). :P &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 15:31, 24 March 2011 (UTC)<br /> <br /> ----<br /> Robot Repository is down. Can't get any of the newer bots nor run the game efficiencty :) --[[User:Miked0801|Miked0801]] 16:00, 16 May 2011 (UTC)<br /> I can delete this entry when the issue is fixed...</div>

Miked0801 http://robowiki.net/w/index.php?title=User_talk:Miked0801&diff=19287 2011-05-16T04:34:14Z

<p>Miked0801: </p> <hr /> <div>Hey! Do you have to remove the &quot;Inactive Authors&quot; category now? =) --[[User:Voidious|Voidious]] 17:31, 28 April 2009 (UTC)<br /> <br /> Lol - I think I already did. Gotta upload an Infinty page now that I fixed a minor bug with him.<br /> <br /> Hey man, I happened to randomly notice that an old version of BrokenSword is appearing in the melee rumble. Did you point your client at the new [[RoboRumble/Participants/Melee]] page? Actually I don't know how that would happen anyway, unless it uses the last participants list it saw if it can't find the list. Or maybe you just had some cached / unuploaded results from the last time you ran it? --[[User:Voidious|Voidious]] 20:06, 28 April 2009 (UTC)<br /> <br /> Good call. Just fixed that. Sorry for the out of date files being added. I'm running the new link now. Someone's going to have to clean up my mess on that one. --[[User:Miked0801|Miked0801]]<br /> <br /> ----<br /> <br /> Just to let you know, I've noticed you signing with &lt;nowiki&gt;--[[User:Miked0801|Miked0801]] or --[[User:Miked0801]]&lt;/nowiki&gt;. Just to let you know, on the new wiki you can simply sign with &lt;nowiki&gt;--~~~~&lt;/nowiki&gt; (or the signature button if you have js enabled), and it'll automatically turn it to a complete signature including timestamp even. Just a tip :) --[[User:Rednaxela|Rednaxela]] 17:01, 29 April 2009 (UTC)<br /> <br /> : Yep, someone else let me know that too. :) --[[User:Miked0801|Miked0801]] 20:36, 29 April 2009 (UTC)<br /> <br /> Oh hey, speaking of code shrinking, I just thought I'd point out the new &quot;Rules&quot; class if you hadn't seen it. I resisted using it for the longest time to ensure compatibility with old Robocodes, but it's been in there for a while and we now have a way of filtering out old clients anyway. So now I'm compiling with Jikes and Robocode 1.4.9, so I can use Rules but still compile with Jikes. --[[User:Voidious|Voidious]] 14:21, 7 May 2009 (UTC)<br /> <br /> Alright, what is this rules class you speak of? --[[User:Miked0801|Miked0801]] 17:54, 7 May 2009 (UTC)<br /> <br /> The [http://robocode.sourceforge.net/docs/robocode/robocode/Rules.html robocode.Rules] class can be used to calculate the max turn rate, bullet power, bullet damage and so on. It is the one use by game engine, and it is now public. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 18:12, 7 May 2009 (UTC)<br /> <br /> (edit conflict) It's a utilities class that provides methods for a bunch of basic stuff, like bullet speed, damage, turn rate, etc. [http://robocode.sourceforge.net/docs/robocode/robocode/Rules.html Rules class in Robocode API]. It's definitely an unfair advantage over legacy bots, but that's your decision to grapple with. =) --[[User:Voidious|Voidious]] 18:16, 7 May 2009 (UTC)<br /> <br /> I checked it out and none of its functions would have use in [[DustBunny]] nor [[Infinity]], though bullet speed would become useful for linear leading if I stored my firepower instead of just calculating in place. --[[User:Miked0801|Miked0801]] 20:33, 7 May 2009 (UTC)<br /> <br /> ----<br /> <br /> Your client seems to be uploading 1-on-1 results for retired bots? stelo.PastFuture 1.0, for example. This is easy to fix but if there is a bigger problem going on... --[[User:Darkcanuck|Darkcanuck]] 03:55, 8 May 2009 (UTC)<br /> <br /> Perhaps I've got the wrong page pointed at (again) for rumble. I'll check when I get home. --[[User:Miked0801|Miked0801]] 20:27, 8 May 2009 (UTC)<br /> <br /> ----<br /> <br /> Hi, it's good to see a 'veteran' coming back and working on nanos. :D I have been on rest since the beginning of April, but now I think I should do something to get back the top 3 rank. ;) --[[User:Robar|HUNRobar]] 16:02, 13 May 2009 (UTC)<br /> :First Place in Melee and 1v1 are sooo close. I got back into this again because I've got some late night hours free with a newborn - just like last time I got into the fun. Come on, just 1% in each. There's gotta be something I can tweak to get that right? :) --[[User:Miked0801|Miked0801]] 18:49, 13 May 2009 (UTC)<br /> <br /> Just watch out because I'm going to make an update on my top bots. :) See Pugio 1.3 for example. ;) --[[User:Robar|HUNRobar]] 19:13, 13 May 2009 (UTC)<br /> : Wow, nice update. Game on! --[[User:Miked0801|Miked0801]] 20:28, 13 May 2009 (UTC)<br /> <br /> Are we allowed to use:<br /> Vector&lt;Double&gt; vect = new Vector&lt;Double&gt;();<br /> <br /> type things and set the &quot;-source 1.5&quot; flag for our bots? If so, that will save some codesize for me.<br /> <br /> Yep, Robocode has required Java 5 for a while now, so that should be fine. I use generics in [[Diamond]] and it definitely ran fine in my 1.5.4 RoboRumble clients, which is the oldest version allowed for the rumble. So that saves code size, eh? Hmm, thanks for the info... =) --[[User:Voidious|Voidious]] 01:12, 27 May 2009 (UTC)<br /> <br /> : Oh yeah, but I forgot, Jikes only supports Java 1.4, that's why I never used generics in my MiniBots. But I'll definitely compare it to normal javac with generics now that I know this. --[[User:Voidious|Voidious]] 01:15, 27 May 2009 (UTC)<br /> : Sorry for triple post, but what makes you say it will save you code size? I tried changing Komarious to use generics for its one collection, and it had no effect on code size. --[[User:Voidious|Voidious]] 01:23, 27 May 2009 (UTC)<br /> <br /> :: Lol, I just realized I never ran codesize on my micro with generics in place. Doh! Well, generics look cleaner if anything else :) --[[User:Miked0801|Miked0801]] 02:25, 27 May 2009 (UTC)<br /> <br /> ::: Generic only available in source, it will ease out at compile time and every casting will come back (try decompile the generic-ize class and see) The generic only to check the type sefty. This is from java specification. And because the codesize library check the byte code, not the not the source code so this has no effect. And this is not require Java 5 to run since it isn't in the byte code, ad long as you only use the classes from the target version.<br /> <br /> ----<br /> <br /> While scanning my local harddrive, I found a newer version of Radnor.DoctorBob (1.50). Any objections to me entering this into the fray and seeing how well it does in tandem with 1.42?<br /> : And removed. Failed experiment there.<br /> <br /> ----<br /> Does Kawigi's old floodGrapher stuff still work with the latest versions of Java for anyone else? I get tons of Javax.Swing exceptions when I try to view a graph. It looks like swing has be deprecrated. Is this so?<br /> : I've never tried FloodGrapher, but I'm almost certain swing is not deprecated, even in Java 7 beta versions, but may something changed that requires old code to work properly. --[[User:Zyx|zyx]] 02:05, 9 June 2009 (UTC)<br /> <br /> I use FloodGrapher myself. I think you are running Windows Vista then, because if you are running it as normal user, it will throw a lot of exceptions and generate NaN hit rate. You need to run it as administrator. I run with both Java 5 and Java 6 and it all work. If you are loading result from FloodGrapger saved file (not FloodMini saved file), you will need to add robocode.jar to classpath yourself. Andway, I bet PEZ's TGrapgher (aka FloodGrapher 1.0) is much more easier to use. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 02:44, 9 June 2009 (UTC)<br /> : I'm using XP Sp2 and while the program opens fine, it fails with all sorts of Swing exceptions for classes not found. No biggie as I got Pez's utility to work. Anyone know exactly what his FirePower/Distance values are that he decided to use A-E on? I'm guess 160 for the distance, but the rest is a guess.<br /> : Also, if you had to choose just 1 method of segmentation for guess factoring (against Nanos of course) do you think that distance would be the best one? My initial results seem to point at this, but was just wondering. Anyways, I'll have my first GF Nano done here shortly. --[[User:Miked0801|Miked0801]] 22:57, 9 June 2009 (UTC)<br /> <br /> : I don't know anything about PEZ's utility, but personally, I would definitely recommend lateral velocity over distance, and probably even absolute velocity over distance (seeing as code size is such an issue here and lateral is so expensive). But by all means, go with what your testing shows is best. =) --[[User:Voidious|Voidious]] 02:38, 10 June 2009 (UTC)<br /> <br /> : It seem to run fine with my old XP Sp3 (and Sp2 too before upgrade) Can you post the actual (partial?) exceptions? For the segmentation, I think lateral velocity is much important. Because many bots will be hit at the same GF at every segment (taking distance into account for flattener). &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 13:24, 10 June 2009 (UTC)<br /> <br /> ---<br /> I took a glance on your new nano. It's fascinating! Ok, it loses against some of my bots decently, but it scores awesomely against others. It scored 68% against nanolaulektrik!<br /> I'm looking forward to see the final rank. ;) --[[User:Robar|HUNRobar]] 21:33, 14 June 2009 (UTC)<br /> : Thanks. I had some inspiration from the 200k max conversation and went to town. I need to change RoboGrapher a bit to output a string per bot in the rumble to save me time (and accuracy in typing). That will help him out in other size catagories. I also, ideally, would average enemy velocity over a few ticks and add that to the guess factor velocity to be able to target true dodge, stop and go bots. That of course costs bytes :). My random movement code needs some tuning as well. But overall, I'm very pleased with this bot. I will put a hard limit of no more than 200k on the string though just to be fair. Maybe less. This bot would probably do ok in melee as well. I'll investigate that soon. I have to admit I was tempted to release no source until I had it tuned, but that wouldn't be fair. --[[User:Miked0801|Miked0801]] 22:22, 14 June 2009 (UTC)<br /> <br /> Is there any good way to get at the battle results from within a robot or are those classes restricted? --[[User:Miked0801|Miked0801]] 02:21, 16 June 2009 (UTC)<br /> <br /> : No, those classes are restricted unless you use -DNOSECURITY=true. I believe that in one-on-one, you can simulate the score calculator in your robot. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 02:55, 16 June 2009 (UTC)<br /> <br /> :: Just saw this go by in the recent changes... You can get scores and stuff from the Robot.onBattleEnded(BattleEndedEvent) method (also accessible from AdvancedRobots). The BattleEndedEvent has a method getResults() which returns a [[http://robocode.sourceforge.net/docs/robocode/ BattleResults]] object which contains fields you can access for all the columns of the results that pop up at the end of a battle. Not certain this is what you are looking for. --[[User:BenHorner|BenHorner]] 03:18, 16 June 2009 (UTC)<br /> ::: Either of these will work for me. Thanks. Expect my next blackbook update sometime tomorrow. My testbot is built and running through all the nanos now. --[[User:Miked0801|Miked0801]] 03:22, 16 June 2009 (UTC)<br /> :::: You must use my method since Skilgannon still ran 1.5.4 client... &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 03:24, 16 June 2009 (UTC)<br /> ::::: No I must not - it's for my local statistical gatherer only. That said, I'm using Excel and RoboResearch this time around to manage all my data. --[[User:Miked0801|Miked0801]] 05:31, 16 June 2009 (UTC)<br /> ::: There's a BattleEndedEvent? Interesting... --[[User:Darkcanuck|Darkcanuck]] 04:30, 16 June 2009 (UTC)<br /> ::: Interesting indeed... I'd personally suggest we try to phase out 1.5.4 asap... ;) --[[User:Rednaxela|Rednaxela]] 04:39, 16 June 2009 (UTC)<br /> :::: Darkcanuck, I think you should move on 1.7.1.3 instead =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 07:01, 16 June 2009 (UTC)<br /> :::: Yes, if 1.7.1.3 comes through with no rumble bugs, we could probably roll forward. Actually, with 1.6.1.4 so active, is there any reason to keep 1.5.4 or 1.6.0 alive? --[[User:Darkcanuck|Darkcanuck]] 07:16, 16 June 2009 (UTC)<br /> ::::: No, no reason to keep 1.5.4 or 1.6.0. At least, not in my opinion :) --[[User:Rednaxela|Rednaxela]] 13:26, 16 June 2009 (UTC)<br /> I added all the repository bots to my 1.7.1.3 install and it froze building the database, I'll file a bug this evening. --[[User:Skilgannon|Skilgannon]] 08:29, 16 June 2009 (UTC)<br /> <br /> Does anyone have a better site to upload bots to than the robocoderepository? Seems like it's down quite a bit. --[[User:Miked0801|Miked0801]] 02:28, 27 January 2010 (UTC)<br /> <br /> I personally use my university web space, but I hear [http://sites.google.com google sites] works fairly well and some others around here have recommended it. --[[User:Rednaxela|Rednaxela]] 03:10, 27 January 2010 (UTC)<br /> <br /> I reccommend Google Site too, buT i personally use my own web hosting. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 05:23, 27 January 2010 (UTC)<br /> <br /> ----<br /> Booted up my test suite. All still in order. Started with new bots. We'll see if I can get an update in by end of week... --[[User:Miked0801|Miked0801]] 04:34, 16 May 2011 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=User_talk:Miked0801&diff=19286 2011-05-16T04:33:50Z

<p>Miked0801: </p> <hr /> <div>Hey! Do you have to remove the &quot;Inactive Authors&quot; category now? =) --[[User:Voidious|Voidious]] 17:31, 28 April 2009 (UTC)<br /> <br /> Lol - I think I already did. Gotta upload an Infinty page now that I fixed a minor bug with him.<br /> <br /> Hey man, I happened to randomly notice that an old version of BrokenSword is appearing in the melee rumble. Did you point your client at the new [[RoboRumble/Participants/Melee]] page? Actually I don't know how that would happen anyway, unless it uses the last participants list it saw if it can't find the list. Or maybe you just had some cached / unuploaded results from the last time you ran it? --[[User:Voidious|Voidious]] 20:06, 28 April 2009 (UTC)<br /> <br /> Good call. Just fixed that. Sorry for the out of date files being added. I'm running the new link now. Someone's going to have to clean up my mess on that one. --[[User:Miked0801|Miked0801]]<br /> <br /> ----<br /> <br /> Just to let you know, I've noticed you signing with &lt;nowiki&gt;--[[User:Miked0801|Miked0801]] or --[[User:Miked0801]]&lt;/nowiki&gt;. Just to let you know, on the new wiki you can simply sign with &lt;nowiki&gt;--~~~~&lt;/nowiki&gt; (or the signature button if you have js enabled), and it'll automatically turn it to a complete signature including timestamp even. Just a tip :) --[[User:Rednaxela|Rednaxela]] 17:01, 29 April 2009 (UTC)<br /> <br /> : Yep, someone else let me know that too. :) --[[User:Miked0801|Miked0801]] 20:36, 29 April 2009 (UTC)<br /> <br /> Oh hey, speaking of code shrinking, I just thought I'd point out the new &quot;Rules&quot; class if you hadn't seen it. I resisted using it for the longest time to ensure compatibility with old Robocodes, but it's been in there for a while and we now have a way of filtering out old clients anyway. So now I'm compiling with Jikes and Robocode 1.4.9, so I can use Rules but still compile with Jikes. --[[User:Voidious|Voidious]] 14:21, 7 May 2009 (UTC)<br /> <br /> Alright, what is this rules class you speak of? --[[User:Miked0801|Miked0801]] 17:54, 7 May 2009 (UTC)<br /> <br /> The [http://robocode.sourceforge.net/docs/robocode/robocode/Rules.html robocode.Rules] class can be used to calculate the max turn rate, bullet power, bullet damage and so on. It is the one use by game engine, and it is now public. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 18:12, 7 May 2009 (UTC)<br /> <br /> (edit conflict) It's a utilities class that provides methods for a bunch of basic stuff, like bullet speed, damage, turn rate, etc. [http://robocode.sourceforge.net/docs/robocode/robocode/Rules.html Rules class in Robocode API]. It's definitely an unfair advantage over legacy bots, but that's your decision to grapple with. =) --[[User:Voidious|Voidious]] 18:16, 7 May 2009 (UTC)<br /> <br /> I checked it out and none of its functions would have use in [[DustBunny]] nor [[Infinity]], though bullet speed would become useful for linear leading if I stored my firepower instead of just calculating in place. --[[User:Miked0801|Miked0801]] 20:33, 7 May 2009 (UTC)<br /> <br /> ----<br /> <br /> Your client seems to be uploading 1-on-1 results for retired bots? stelo.PastFuture 1.0, for example. This is easy to fix but if there is a bigger problem going on... --[[User:Darkcanuck|Darkcanuck]] 03:55, 8 May 2009 (UTC)<br /> <br /> Perhaps I've got the wrong page pointed at (again) for rumble. I'll check when I get home. --[[User:Miked0801|Miked0801]] 20:27, 8 May 2009 (UTC)<br /> <br /> ----<br /> <br /> Hi, it's good to see a 'veteran' coming back and working on nanos. :D I have been on rest since the beginning of April, but now I think I should do something to get back the top 3 rank. ;) --[[User:Robar|HUNRobar]] 16:02, 13 May 2009 (UTC)<br /> :First Place in Melee and 1v1 are sooo close. I got back into this again because I've got some late night hours free with a newborn - just like last time I got into the fun. Come on, just 1% in each. There's gotta be something I can tweak to get that right? :) --[[User:Miked0801|Miked0801]] 18:49, 13 May 2009 (UTC)<br /> <br /> Just watch out because I'm going to make an update on my top bots. :) See Pugio 1.3 for example. ;) --[[User:Robar|HUNRobar]] 19:13, 13 May 2009 (UTC)<br /> : Wow, nice update. Game on! --[[User:Miked0801|Miked0801]] 20:28, 13 May 2009 (UTC)<br /> <br /> Are we allowed to use:<br /> Vector&lt;Double&gt; vect = new Vector&lt;Double&gt;();<br /> <br /> type things and set the &quot;-source 1.5&quot; flag for our bots? If so, that will save some codesize for me.<br /> <br /> Yep, Robocode has required Java 5 for a while now, so that should be fine. I use generics in [[Diamond]] and it definitely ran fine in my 1.5.4 RoboRumble clients, which is the oldest version allowed for the rumble. So that saves code size, eh? Hmm, thanks for the info... =) --[[User:Voidious|Voidious]] 01:12, 27 May 2009 (UTC)<br /> <br /> : Oh yeah, but I forgot, Jikes only supports Java 1.4, that's why I never used generics in my MiniBots. But I'll definitely compare it to normal javac with generics now that I know this. --[[User:Voidious|Voidious]] 01:15, 27 May 2009 (UTC)<br /> : Sorry for triple post, but what makes you say it will save you code size? I tried changing Komarious to use generics for its one collection, and it had no effect on code size. --[[User:Voidious|Voidious]] 01:23, 27 May 2009 (UTC)<br /> <br /> :: Lol, I just realized I never ran codesize on my micro with generics in place. Doh! Well, generics look cleaner if anything else :) --[[User:Miked0801|Miked0801]] 02:25, 27 May 2009 (UTC)<br /> <br /> ::: Generic only available in source, it will ease out at compile time and every casting will come back (try decompile the generic-ize class and see) The generic only to check the type sefty. This is from java specification. And because the codesize library check the byte code, not the not the source code so this has no effect. And this is not require Java 5 to run since it isn't in the byte code, ad long as you only use the classes from the target version.<br /> <br /> ----<br /> <br /> While scanning my local harddrive, I found a newer version of Radnor.DoctorBob (1.50). Any objections to me entering this into the fray and seeing how well it does in tandem with 1.42?<br /> : And removed. Failed experiment there.<br /> <br /> ----<br /> Does Kawigi's old floodGrapher stuff still work with the latest versions of Java for anyone else? I get tons of Javax.Swing exceptions when I try to view a graph. It looks like swing has be deprecrated. Is this so?<br /> : I've never tried FloodGrapher, but I'm almost certain swing is not deprecated, even in Java 7 beta versions, but may something changed that requires old code to work properly. --[[User:Zyx|zyx]] 02:05, 9 June 2009 (UTC)<br /> <br /> I use FloodGrapher myself. I think you are running Windows Vista then, because if you are running it as normal user, it will throw a lot of exceptions and generate NaN hit rate. You need to run it as administrator. I run with both Java 5 and Java 6 and it all work. If you are loading result from FloodGrapger saved file (not FloodMini saved file), you will need to add robocode.jar to classpath yourself. Andway, I bet PEZ's TGrapgher (aka FloodGrapher 1.0) is much more easier to use. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 02:44, 9 June 2009 (UTC)<br /> : I'm using XP Sp2 and while the program opens fine, it fails with all sorts of Swing exceptions for classes not found. No biggie as I got Pez's utility to work. Anyone know exactly what his FirePower/Distance values are that he decided to use A-E on? I'm guess 160 for the distance, but the rest is a guess.<br /> : Also, if you had to choose just 1 method of segmentation for guess factoring (against Nanos of course) do you think that distance would be the best one? My initial results seem to point at this, but was just wondering. Anyways, I'll have my first GF Nano done here shortly. --[[User:Miked0801|Miked0801]] 22:57, 9 June 2009 (UTC)<br /> <br /> : I don't know anything about PEZ's utility, but personally, I would definitely recommend lateral velocity over distance, and probably even absolute velocity over distance (seeing as code size is such an issue here and lateral is so expensive). But by all means, go with what your testing shows is best. =) --[[User:Voidious|Voidious]] 02:38, 10 June 2009 (UTC)<br /> <br /> : It seem to run fine with my old XP Sp3 (and Sp2 too before upgrade) Can you post the actual (partial?) exceptions? For the segmentation, I think lateral velocity is much important. Because many bots will be hit at the same GF at every segment (taking distance into account for flattener). &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 13:24, 10 June 2009 (UTC)<br /> <br /> ---<br /> I took a glance on your new nano. It's fascinating! Ok, it loses against some of my bots decently, but it scores awesomely against others. It scored 68% against nanolaulektrik!<br /> I'm looking forward to see the final rank. ;) --[[User:Robar|HUNRobar]] 21:33, 14 June 2009 (UTC)<br /> : Thanks. I had some inspiration from the 200k max conversation and went to town. I need to change RoboGrapher a bit to output a string per bot in the rumble to save me time (and accuracy in typing). That will help him out in other size catagories. I also, ideally, would average enemy velocity over a few ticks and add that to the guess factor velocity to be able to target true dodge, stop and go bots. That of course costs bytes :). My random movement code needs some tuning as well. But overall, I'm very pleased with this bot. I will put a hard limit of no more than 200k on the string though just to be fair. Maybe less. This bot would probably do ok in melee as well. I'll investigate that soon. I have to admit I was tempted to release no source until I had it tuned, but that wouldn't be fair. --[[User:Miked0801|Miked0801]] 22:22, 14 June 2009 (UTC)<br /> <br /> Is there any good way to get at the battle results from within a robot or are those classes restricted? --[[User:Miked0801|Miked0801]] 02:21, 16 June 2009 (UTC)<br /> <br /> : No, those classes are restricted unless you use -DNOSECURITY=true. I believe that in one-on-one, you can simulate the score calculator in your robot. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 02:55, 16 June 2009 (UTC)<br /> <br /> :: Just saw this go by in the recent changes... You can get scores and stuff from the Robot.onBattleEnded(BattleEndedEvent) method (also accessible from AdvancedRobots). The BattleEndedEvent has a method getResults() which returns a [[http://robocode.sourceforge.net/docs/robocode/ BattleResults]] object which contains fields you can access for all the columns of the results that pop up at the end of a battle. Not certain this is what you are looking for. --[[User:BenHorner|BenHorner]] 03:18, 16 June 2009 (UTC)<br /> ::: Either of these will work for me. Thanks. Expect my next blackbook update sometime tomorrow. My testbot is built and running through all the nanos now. --[[User:Miked0801|Miked0801]] 03:22, 16 June 2009 (UTC)<br /> :::: You must use my method since Skilgannon still ran 1.5.4 client... &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 03:24, 16 June 2009 (UTC)<br /> ::::: No I must not - it's for my local statistical gatherer only. That said, I'm using Excel and RoboResearch this time around to manage all my data. --[[User:Miked0801|Miked0801]] 05:31, 16 June 2009 (UTC)<br /> ::: There's a BattleEndedEvent? Interesting... --[[User:Darkcanuck|Darkcanuck]] 04:30, 16 June 2009 (UTC)<br /> ::: Interesting indeed... I'd personally suggest we try to phase out 1.5.4 asap... ;) --[[User:Rednaxela|Rednaxela]] 04:39, 16 June 2009 (UTC)<br /> :::: Darkcanuck, I think you should move on 1.7.1.3 instead =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 07:01, 16 June 2009 (UTC)<br /> :::: Yes, if 1.7.1.3 comes through with no rumble bugs, we could probably roll forward. Actually, with 1.6.1.4 so active, is there any reason to keep 1.5.4 or 1.6.0 alive? --[[User:Darkcanuck|Darkcanuck]] 07:16, 16 June 2009 (UTC)<br /> ::::: No, no reason to keep 1.5.4 or 1.6.0. At least, not in my opinion :) --[[User:Rednaxela|Rednaxela]] 13:26, 16 June 2009 (UTC)<br /> I added all the repository bots to my 1.7.1.3 install and it froze building the database, I'll file a bug this evening. --[[User:Skilgannon|Skilgannon]] 08:29, 16 June 2009 (UTC)<br /> <br /> Does anyone have a better site to upload bots to than the robocoderepository? Seems like it's down quite a bit. --[[User:Miked0801|Miked0801]] 02:28, 27 January 2010 (UTC)<br /> <br /> I personally use my university web space, but I hear [http://sites.google.com google sites] works fairly well and some others around here have recommended it. --[[User:Rednaxela|Rednaxela]] 03:10, 27 January 2010 (UTC)<br /> <br /> I reccommend Google Site too, buT i personally use my own web hosting. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 05:23, 27 January 2010 (UTC)<br /> <br /> ----<br /> Booted up my test suite. All still in order. Started with new bots. We'll see if I can get an update in by end of week...</div>

Miked0801 http://robowiki.net/w/index.php?title=User_talk:Miked0801&diff=19285 2011-05-16T04:33:27Z

<p>Miked0801: I'm back for a bit</p> <hr /> <div>Hey! Do you have to remove the &quot;Inactive Authors&quot; category now? =) --[[User:Voidious|Voidious]] 17:31, 28 April 2009 (UTC)<br /> <br /> Lol - I think I already did. Gotta upload an Infinty page now that I fixed a minor bug with him.<br /> <br /> Hey man, I happened to randomly notice that an old version of BrokenSword is appearing in the melee rumble. Did you point your client at the new [[RoboRumble/Participants/Melee]] page? Actually I don't know how that would happen anyway, unless it uses the last participants list it saw if it can't find the list. Or maybe you just had some cached / unuploaded results from the last time you ran it? --[[User:Voidious|Voidious]] 20:06, 28 April 2009 (UTC)<br /> <br /> Good call. Just fixed that. Sorry for the out of date files being added. I'm running the new link now. Someone's going to have to clean up my mess on that one. --[[User:Miked0801|Miked0801]]<br /> <br /> ----<br /> <br /> Just to let you know, I've noticed you signing with &lt;nowiki&gt;--[[User:Miked0801|Miked0801]] or --[[User:Miked0801]]&lt;/nowiki&gt;. Just to let you know, on the new wiki you can simply sign with &lt;nowiki&gt;--~~~~&lt;/nowiki&gt; (or the signature button if you have js enabled), and it'll automatically turn it to a complete signature including timestamp even. Just a tip :) --[[User:Rednaxela|Rednaxela]] 17:01, 29 April 2009 (UTC)<br /> <br /> : Yep, someone else let me know that too. :) --[[User:Miked0801|Miked0801]] 20:36, 29 April 2009 (UTC)<br /> <br /> Oh hey, speaking of code shrinking, I just thought I'd point out the new &quot;Rules&quot; class if you hadn't seen it. I resisted using it for the longest time to ensure compatibility with old Robocodes, but it's been in there for a while and we now have a way of filtering out old clients anyway. So now I'm compiling with Jikes and Robocode 1.4.9, so I can use Rules but still compile with Jikes. --[[User:Voidious|Voidious]] 14:21, 7 May 2009 (UTC)<br /> <br /> Alright, what is this rules class you speak of? --[[User:Miked0801|Miked0801]] 17:54, 7 May 2009 (UTC)<br /> <br /> The [http://robocode.sourceforge.net/docs/robocode/robocode/Rules.html robocode.Rules] class can be used to calculate the max turn rate, bullet power, bullet damage and so on. It is the one use by game engine, and it is now public. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 18:12, 7 May 2009 (UTC)<br /> <br /> (edit conflict) It's a utilities class that provides methods for a bunch of basic stuff, like bullet speed, damage, turn rate, etc. [http://robocode.sourceforge.net/docs/robocode/robocode/Rules.html Rules class in Robocode API]. It's definitely an unfair advantage over legacy bots, but that's your decision to grapple with. =) --[[User:Voidious|Voidious]] 18:16, 7 May 2009 (UTC)<br /> <br /> I checked it out and none of its functions would have use in [[DustBunny]] nor [[Infinity]], though bullet speed would become useful for linear leading if I stored my firepower instead of just calculating in place. --[[User:Miked0801|Miked0801]] 20:33, 7 May 2009 (UTC)<br /> <br /> ----<br /> <br /> Your client seems to be uploading 1-on-1 results for retired bots? stelo.PastFuture 1.0, for example. This is easy to fix but if there is a bigger problem going on... --[[User:Darkcanuck|Darkcanuck]] 03:55, 8 May 2009 (UTC)<br /> <br /> Perhaps I've got the wrong page pointed at (again) for rumble. I'll check when I get home. --[[User:Miked0801|Miked0801]] 20:27, 8 May 2009 (UTC)<br /> <br /> ----<br /> <br /> Hi, it's good to see a 'veteran' coming back and working on nanos. :D I have been on rest since the beginning of April, but now I think I should do something to get back the top 3 rank. ;) --[[User:Robar|HUNRobar]] 16:02, 13 May 2009 (UTC)<br /> :First Place in Melee and 1v1 are sooo close. I got back into this again because I've got some late night hours free with a newborn - just like last time I got into the fun. Come on, just 1% in each. There's gotta be something I can tweak to get that right? :) --[[User:Miked0801|Miked0801]] 18:49, 13 May 2009 (UTC)<br /> <br /> Just watch out because I'm going to make an update on my top bots. :) See Pugio 1.3 for example. ;) --[[User:Robar|HUNRobar]] 19:13, 13 May 2009 (UTC)<br /> : Wow, nice update. Game on! --[[User:Miked0801|Miked0801]] 20:28, 13 May 2009 (UTC)<br /> <br /> Are we allowed to use:<br /> Vector&lt;Double&gt; vect = new Vector&lt;Double&gt;();<br /> <br /> type things and set the &quot;-source 1.5&quot; flag for our bots? If so, that will save some codesize for me.<br /> <br /> Yep, Robocode has required Java 5 for a while now, so that should be fine. I use generics in [[Diamond]] and it definitely ran fine in my 1.5.4 RoboRumble clients, which is the oldest version allowed for the rumble. So that saves code size, eh? Hmm, thanks for the info... =) --[[User:Voidious|Voidious]] 01:12, 27 May 2009 (UTC)<br /> <br /> : Oh yeah, but I forgot, Jikes only supports Java 1.4, that's why I never used generics in my MiniBots. But I'll definitely compare it to normal javac with generics now that I know this. --[[User:Voidious|Voidious]] 01:15, 27 May 2009 (UTC)<br /> : Sorry for triple post, but what makes you say it will save you code size? I tried changing Komarious to use generics for its one collection, and it had no effect on code size. --[[User:Voidious|Voidious]] 01:23, 27 May 2009 (UTC)<br /> <br /> :: Lol, I just realized I never ran codesize on my micro with generics in place. Doh! Well, generics look cleaner if anything else :) --[[User:Miked0801|Miked0801]] 02:25, 27 May 2009 (UTC)<br /> <br /> ::: Generic only available in source, it will ease out at compile time and every casting will come back (try decompile the generic-ize class and see) The generic only to check the type sefty. This is from java specification. And because the codesize library check the byte code, not the not the source code so this has no effect. And this is not require Java 5 to run since it isn't in the byte code, ad long as you only use the classes from the target version.<br /> <br /> ----<br /> <br /> While scanning my local harddrive, I found a newer version of Radnor.DoctorBob (1.50). Any objections to me entering this into the fray and seeing how well it does in tandem with 1.42?<br /> : And removed. Failed experiment there.<br /> <br /> ----<br /> Does Kawigi's old floodGrapher stuff still work with the latest versions of Java for anyone else? I get tons of Javax.Swing exceptions when I try to view a graph. It looks like swing has be deprecrated. Is this so?<br /> : I've never tried FloodGrapher, but I'm almost certain swing is not deprecated, even in Java 7 beta versions, but may something changed that requires old code to work properly. --[[User:Zyx|zyx]] 02:05, 9 June 2009 (UTC)<br /> <br /> I use FloodGrapher myself. I think you are running Windows Vista then, because if you are running it as normal user, it will throw a lot of exceptions and generate NaN hit rate. You need to run it as administrator. I run with both Java 5 and Java 6 and it all work. If you are loading result from FloodGrapger saved file (not FloodMini saved file), you will need to add robocode.jar to classpath yourself. Andway, I bet PEZ's TGrapgher (aka FloodGrapher 1.0) is much more easier to use. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 02:44, 9 June 2009 (UTC)<br /> : I'm using XP Sp2 and while the program opens fine, it fails with all sorts of Swing exceptions for classes not found. No biggie as I got Pez's utility to work. Anyone know exactly what his FirePower/Distance values are that he decided to use A-E on? I'm guess 160 for the distance, but the rest is a guess.<br /> : Also, if you had to choose just 1 method of segmentation for guess factoring (against Nanos of course) do you think that distance would be the best one? My initial results seem to point at this, but was just wondering. Anyways, I'll have my first GF Nano done here shortly. --[[User:Miked0801|Miked0801]] 22:57, 9 June 2009 (UTC)<br /> <br /> : I don't know anything about PEZ's utility, but personally, I would definitely recommend lateral velocity over distance, and probably even absolute velocity over distance (seeing as code size is such an issue here and lateral is so expensive). But by all means, go with what your testing shows is best. =) --[[User:Voidious|Voidious]] 02:38, 10 June 2009 (UTC)<br /> <br /> : It seem to run fine with my old XP Sp3 (and Sp2 too before upgrade) Can you post the actual (partial?) exceptions? For the segmentation, I think lateral velocity is much important. Because many bots will be hit at the same GF at every segment (taking distance into account for flattener). &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 13:24, 10 June 2009 (UTC)<br /> <br /> ---<br /> I took a glance on your new nano. It's fascinating! Ok, it loses against some of my bots decently, but it scores awesomely against others. It scored 68% against nanolaulektrik!<br /> I'm looking forward to see the final rank. ;) --[[User:Robar|HUNRobar]] 21:33, 14 June 2009 (UTC)<br /> : Thanks. I had some inspiration from the 200k max conversation and went to town. I need to change RoboGrapher a bit to output a string per bot in the rumble to save me time (and accuracy in typing). That will help him out in other size catagories. I also, ideally, would average enemy velocity over a few ticks and add that to the guess factor velocity to be able to target true dodge, stop and go bots. That of course costs bytes :). My random movement code needs some tuning as well. But overall, I'm very pleased with this bot. I will put a hard limit of no more than 200k on the string though just to be fair. Maybe less. This bot would probably do ok in melee as well. I'll investigate that soon. I have to admit I was tempted to release no source until I had it tuned, but that wouldn't be fair. --[[User:Miked0801|Miked0801]] 22:22, 14 June 2009 (UTC)<br /> <br /> Is there any good way to get at the battle results from within a robot or are those classes restricted? --[[User:Miked0801|Miked0801]] 02:21, 16 June 2009 (UTC)<br /> <br /> : No, those classes are restricted unless you use -DNOSECURITY=true. I believe that in one-on-one, you can simulate the score calculator in your robot. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 02:55, 16 June 2009 (UTC)<br /> <br /> :: Just saw this go by in the recent changes... You can get scores and stuff from the Robot.onBattleEnded(BattleEndedEvent) method (also accessible from AdvancedRobots). The BattleEndedEvent has a method getResults() which returns a [[http://robocode.sourceforge.net/docs/robocode/ BattleResults]] object which contains fields you can access for all the columns of the results that pop up at the end of a battle. Not certain this is what you are looking for. --[[User:BenHorner|BenHorner]] 03:18, 16 June 2009 (UTC)<br /> ::: Either of these will work for me. Thanks. Expect my next blackbook update sometime tomorrow. My testbot is built and running through all the nanos now. --[[User:Miked0801|Miked0801]] 03:22, 16 June 2009 (UTC)<br /> :::: You must use my method since Skilgannon still ran 1.5.4 client... &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 03:24, 16 June 2009 (UTC)<br /> ::::: No I must not - it's for my local statistical gatherer only. That said, I'm using Excel and RoboResearch this time around to manage all my data. --[[User:Miked0801|Miked0801]] 05:31, 16 June 2009 (UTC)<br /> ::: There's a BattleEndedEvent? Interesting... --[[User:Darkcanuck|Darkcanuck]] 04:30, 16 June 2009 (UTC)<br /> ::: Interesting indeed... I'd personally suggest we try to phase out 1.5.4 asap... ;) --[[User:Rednaxela|Rednaxela]] 04:39, 16 June 2009 (UTC)<br /> :::: Darkcanuck, I think you should move on 1.7.1.3 instead =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 07:01, 16 June 2009 (UTC)<br /> :::: Yes, if 1.7.1.3 comes through with no rumble bugs, we could probably roll forward. Actually, with 1.6.1.4 so active, is there any reason to keep 1.5.4 or 1.6.0 alive? --[[User:Darkcanuck|Darkcanuck]] 07:16, 16 June 2009 (UTC)<br /> ::::: No, no reason to keep 1.5.4 or 1.6.0. At least, not in my opinion :) --[[User:Rednaxela|Rednaxela]] 13:26, 16 June 2009 (UTC)<br /> I added all the repository bots to my 1.7.1.3 install and it froze building the database, I'll file a bug this evening. --[[User:Skilgannon|Skilgannon]] 08:29, 16 June 2009 (UTC)<br /> <br /> Does anyone have a better site to upload bots to than the robocoderepository? Seems like it's down quite a bit. --[[User:Miked0801|Miked0801]] 02:28, 27 January 2010 (UTC)<br /> <br /> I personally use my university web space, but I hear [http://sites.google.com google sites] works fairly well and some others around here have recommended it. --[[User:Rednaxela|Rednaxela]] 03:10, 27 January 2010 (UTC)<br /> <br /> I reccommend Google Site too, buT i personally use my own web hosting. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 05:23, 27 January 2010 (UTC)<br /> <br /> ---<br /> Booted up my test suite. All still in order. Started with new bots. We'll see if I can get an update in by end of week...</div>

Miked0801 http://robowiki.net/w/index.php?title=Talk:Caligula&diff=19252 2011-05-07T23:31:05Z

<p>Miked0801: Congrats!</p> <hr /> <div>I really did not understood how I could have control in the first 10 rounds, but then if I calculated 100 rounds we ended equal!<br /> <br /> Until I read this page, and figured the things that happened on my screen were not a strange RC bug.<br /> <br /> I think this ramming tactic is brilliant! --[[User:Hapiel|Hapiel]] 19:15, 17 January 2011 (UTC)<br /> <br /> Thanks! As you examine more nanos and micros, you'll find that many of them start by using [[Stop And Go]] movement to defeat robots using [[Head-On Targeting]] and [[Linear Targeting]], and then switch to their main movement strategy to deal with everything else. Mine is the only one with ramming as its back-up strategy, though:-)--[[User:CrazyBassoonist|CrazyBassoonist]] 19:49, 17 January 2011 (UTC)<br /> <br /> Wow! You beat Moebius! I am completely impressed and will have to go check it out to see how you did it. LBB is kinda a cheap so I consider this a very, very good entry! We might have a game again. --[[User:Miked0801|Miked0801]] 23:31, 7 May 2011 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=Talk:WaveSim&diff=19142 2011-04-16T13:58:46Z

<p>Miked0801: </p> <hr /> <div>Still ironing out some issues here and there, but damn this is cool. =) Time to run normal battles, 20 seasons x 48 bots: 4.75 hours (on 2 threads). Time to run the same gun against the raw data: ~10 minutes. :-D Plus you don't have to hope randomness averages out over the battles - it's the same data every time. --[[User:Voidious|Voidious]] 23:37, 13 March 2010 (UTC)<br /> <br /> Neat stuff here! Actually, back when working on RougeDC, I once had something akin to this set up for quick testing, but I never really used it extensively or made it robust. I wonder if I should set up a robust framework for this for my future targeting experiments. --[[User:Rednaxela|Rednaxela]] 23:52, 13 March 2010 (UTC)<br /> <br /> I actually wondered if you ever had. =) It's a funny combination of &quot;wow this is so cool!&quot; and &quot;you know this is sooo nothing special.&quot; Back when I had access to MATLAB at school, I did play with a wave data set with some SVMs, but other than that I haven't explored testing my classification algorithms outside of Robocode. But I still have the desire to try a lot of clustering experiments, so taking a few days to set this up was well worth it! --[[User:Voidious|Voidious]] 23:59, 13 March 2010 (UTC)<br /> <br /> This has got me thinking. Since the earliest days of Ugluk, the design of the guns and movement have been 'pluggable'. Which is handy because I'd often throw a large set of both against opponents and simply stop using the ones that were least effective. Anyway.. digressing too much.. what I have not yet done is to make the tank completely independent of Robocode, such that with the right input you could run a simulation outside of the client. I can see the benefit of doing this with a recorded set of tank positions, directions, and speeds. Even putting aside the nagging problem of adaptive movements, you can quickly tell if your gun has gone horribly wrong. And of course when testing against non-adaptive movements, you can refine your punishment to squeeze the best point ratios out of your battles, which is what the scoring in the rumble is all about. Defeating good / adaptive bots is secondary. --[[User:Pedersen|Martin]] 21:11, 15 March 2010 (UTC)<br /> <br /> QT Clustering sounds interesting. Reminds me of my density suggestion, except without the normal distribution. I wonder if there is a way to dynamically determine the best threshold as well. I would guess 'the point where the density of point to distance becomes less than those nearer to the center' but that is a bit abstract and is useless for building clusters, since not all points or for that matter clusters (with real data) fit this kind of definition. --[[User:Chase-san|Chase]] 10:33, 20 March 2010 (UTC)<br /> <br /> My recent gun tests have been against a field of 47 mid-range bots I had in an old [[RoboResearch]] test bed. Last night before bed, I took 5 minutes and used [[User:Voidious/BedMaker|BedMaker]] to create a test bed of 250 bots that [[Diamond]] scores between 70% and 90% against, then started collecting 6 seasons of gun data (1500 battles) against them with [[User:Voidious/WaveSim#TripHammer_RES|TripHammer RES]]. I felt so cool! =) --[[User:Voidious|Voidious]] 16:15, 25 January 2011 (UTC)<br /> <br /> Interesting idea here. Might convince me to dust off my bots and give things another go. --[[User:Miked0801|Miked0801]] 13:58, 16 April 2011 (UTC)<br /> <br /> == Compression? ==<br /> <br /> Hmm, since you end up with huge CSV files with this, why not do some compression with GZIPOutputStream? Not only would it save disk space, but I have a feeling it could make WaveSim run faster due to reduced reading from disk. --[[User:Rednaxela|Rednaxela]] 06:18, 26 January 2011 (UTC)<br /> <br /> Good call, trying it now with some existing data. First run was 889 uncompressed, 904 gzip - hmm. Still worth keeping for the size, but no speed increase. Started to think just last night how unoptimized this code might be. I added regular MEA and corresponding regular GFs last night and then wrote a method to massage my existing data files into the new format. It was taking forever! Turns out a zillion string appends in a tight loop is bad, and StringBuilder is awesome. <br /> <br /> Now I'm wondering if there are some magical incantations for reading these files better. I was using BufferedReader(FileReader()), now it's BufferedReader(InputStreamReader(GZIPInputStreamReader(FileInputStream)))). I tried (when still uncompressed) FileInputStream and reading in the whole file at once, then parsing it, but that was slower.<br /> <br /> --[[User:Voidious|Voidious]] 13:35, 26 January 2011 (UTC)<br /> <br /> Oh, another issue might be appending to a compressed file. I append at the end of each round because I hit some issues storing up this huge file to write in one burst at the end of the battle. Maybe I'll try all this on a newer Robocode and see if I can figure that issue out too. --[[User:Voidious|Voidious]] 13:41, 26 January 2011 (UTC)<br /> <br /> I'd consider reading it all at once, to be expected to be slower. After all, when you only read it part at a time, it gives the hard disk a chance to do readahead while you're processing the data. I don't think the InputStreamReader+FileInputStream makes any difference vs FileReader.<br /> <br /> Regarding appending, I believe you can append gzip streams actually. The command line gzip tools seem happy with this anyway. When I do &quot;echo foo | gzip &gt;&gt; blah.gz&quot; and &quot;echo foo | gzip &gt;&gt; blah.gz&quot;, then try to read it with &quot;cat blah.gz | gzip -d&quot;, it outputs both just fine. I haven't tested, but I presume GZIPInputStream can handle appended streams too. Even if that appending doesn't work, why not just keep the file open across rounds, as a static variable? --[[User:Rednaxela|Rednaxela]] 13:59, 26 January 2011 (UTC)<br /> <br /> Cool, this seems to be working, just leaving the output stream open now. I was hitting a &quot;bad file descriptor&quot; after a few minimized rounds, but switching back to Apple JVM (from SoyLatte) fixed it. Some of my data files collected with RoboResearch are hitting an &quot;unexpected EOF&quot; when I process them, but haven't reproduced it with data collected through normal Robocode, so I'm not sure what's going on. It seems to be able to read the data up to that point though. (Using Apple JVM and Robocode 1.7.2.2 for both.) Gonna try to get all of this posted today - with compressed data, normal MEA / wall distance, and random movement in the collector bot, all of which are done but just need testing and polishing. --[[User:Voidious|Voidious]] 15:38, 26 January 2011 (UTC)<br /> <br /> Figured it out - my little &quot;go back to Apple JVM&quot; stuff in my RoboResearch shell script wasn't really working, since RoboResearch doesn't use the Robocode control API, it actually launches Java itself. And now I remember why I hate the Apple JVM for RoboResearch - it launches a new &quot;Java app&quot; thing in the dock every battle and steals the focus from your current app. Time to figure out how to tweak that... I hope... Good news is I think this is almost good to go. =) --[[User:Voidious|Voidious]] 16:49, 26 January 2011 (UTC)<br /> <br /> : Figured if out, if anyone cares: add &quot;-Dapple.awt.UIElement=true&quot; argument in BattleRunner.java. --[[User:Voidious|Voidious]] 18:11, 26 January 2011 (UTC)<br /> <br /> == Play-It-Forward ==<br /> <br /> Hmm... I think I might just want to use this framework to test some new targeting ideas... Though I will need to update it to support PIF also. Perhaps the best way to do it would be a single row at the top of the CSV file, listing self/enemy positions/velocities. When I modify it do support this, want me to send the code? :) --[[User:Rednaxela|Rednaxela]] 04:48, 27 January 2011 (UTC)<br /> <br /> Sure! I might even try it out myself if you do. =) --[[User:Voidious|Voidious]] 13:24, 27 January 2011 (UTC)<br /> <br /> It strikes me that _classifier.feed(wave); and _classifier.classify(wave); currently aren't set up an accurate way. It looks to me like the classifier is being fed *every* wave before the one it's classifying, but I'd say this is notably inaccurate, because not all of those waves have finished yet. This could affect the results noticeably I think. It'll take a little more refactoring than I expected to correct for factors like this. --[[User:Rednaxela|Rednaxela]] 14:21, 27 January 2011 (UTC)<br /> <br /> Hmm? It's not like that. Each wave also includes the ID of the last wave collected before it was aimed. So it only feeds the classifier the waves it had seen before trying to classify that wave. WaveReader stores two positions - the firing wave position and the reading/feeding position. --[[User:Voidious|Voidious]] 14:28, 27 January 2011 (UTC)<br /> <br /> Oh, well... that's what I get for skimming over the code in the early morning I suppose. Let's see how this goes... --[[User:Rednaxela|Rednaxela]] 00:25, 28 January 2011 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=Talk:Robocode&diff=18047 2011-01-07T23:46:51Z

<p>Miked0801: /* 10th Birthday */</p> <hr /> <div>''The following 2 comments are from the &quot;Robocode/Welcome&quot; talk page, before moving it to &quot;Robocode&quot;''.<br /> <br /> This article should be merged with [[Robocode Basics]]. --[[User:AaronR|AaronR]] 23:19, 12 November 2007 (UTC)<br /> <br /> * I agree, and thank you for doing the merge job. :-) I have just started putting stuff into this new Wiki, so I will continue extending the Robocode part of the Wiki with the old one provided here [http://robocode.sourceforge.net/help/ Robocode Online Help], but in a total updated version of course. My intension is that all the stuff I put in this new Wiki will contain all information about Robocode in the future, and then I will redirect the old web page to point on this new one, when it is finished. ;-) --[[User:FlemmingLarsen|FlemmingLarsen]]<br /> <br /> ==== The Wikipedia entry for Robocode ====<br /> Somebody should update the http://en.wikipedia.org/wiki/Robocode page for Robocode some day. :-) --[[User:FlemmingLarsen|Flemming N. Larsen]] 23:31, 13 November 2007 (UTC)<br /> <br /> == 1.7.1.2 ==<br /> <br /> I've been doing a bit of local testing, both with new and 'know problem' archaic bots (SandboxDT, SilverSurfer), and all the results seem to match 1.5.4. Also, it seems to run a LOT faster. I've been testing the rumble with UPLOAD=NOT and it also seems to match everything within what I would think is the margin of error. Can we have a consensus that 1.7.1.2 is safe for the rumble and challenges? --[[User:Skilgannon|Skilgannon]] 19:15, 14 May 2009 (UTC)<br /> <br /> I bet even 1.7.1.1 are ready for RoboRumble. I've been asked Darkcanuck about newer version and he said we should wait. One thing that change is survival score, 1.6.1.4 and earlier use 1st as survival score but 1.7.x use either survival or survival bonus score instead. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 23:32, 14 May 2009 (UTC)<br /> <br /> : Whoah, did the survival scoring really change? Man, I don't like that at all. I wouldn't support ''any'' scoring change being allowed into the RoboRumble. Where is there info about this?--[[User:Voidious|Voidious]] 02:40, 15 May 2009 (UTC)<br /> <br /> :: Indeed, the result doesn't change. (because it a percent) It just switch from 1st to survival bonus, which is the same for 1v1 battle (but not for melee rumble) Here are some result from my result file (1.7.1.1alpha)<br /> &lt;pre&gt;<br /> roborumble,35,800x600,Nat_1711,1239165160631,SERVER<br /> stelo.UnfoolableNano 1.0,2748,1475,900<br /> robar.nano.BlackWidow 1.3,2685,1479,850<br /> roborumble,35,800x600,Nat_1711,1239165163655,SERVER<br /> robar.nano.BlackWidow 1.3,4848,2290,1750<br /> sul.Pinkbot 1.1,640,640,0<br /> &lt;/pre&gt;<br /> The older version look like:<br /> &lt;pre&gt;<br /> roborumble,35,800x600,Nat,1242355746718,SERVER<br /> zyx.mega.YersiniaPestis 1.6.2.4,3746,1707,29<br /> ak.Fermat 2.0,1529,1102,6<br /> roborumble,35,800x600,Nat,1242355781553,SERVER<br /> darkcanuck.Gaff 1.34,3559,1612,28<br /> apv.AspidReloaded 0.6,2159,1638,7<br /> &lt;/pre&gt;<br /> Score in format &lt;code&gt;total score, bullet damage, survival&lt;/code&gt; &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 02:53, 15 May 2009 (UTC)<br /> <br /> ::: Ah, cool, thanks for that info. So it's just the representation that changed. I'll chill out now. =) --[[User:Voidious|Voidious]] 03:08, 15 May 2009 (UTC)<br /> <br /> He he, just found that 1.7.1.2 beta isn't ready yet, see http://robocode.svn.sourceforge.net/viewvc/robocode?view=rev&amp;revision=2983 for more detail. Be should wait for final release before make it a rumble client. And, as I wrote this many times already, 1.7 is a LOT faster for sure. I've once run it with UPLOAD=NOT and I ran 60 battle/minute! &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 23:41, 14 May 2009 (UTC)<br /> <br /> Thanks for pointing out the scoring change, I didn't know about that. Do you know why it was done? I'd still consider this to be a bug, since it does change functionality without apparent cause. If we want the survival bonus it should be reported as a separate value.<br /> <br /> 1.7.1.1 wasn't ready because there were known bugs (e.g. melee rumble broken). Some of the movement gurus out might want to take a close look at 1.7.1.2 because the movement formulas were changed slightly to fix the quirks that [[User:Simonton|Simonton]] had pointed out. Happily this new version does fix a problem with the rumble client that could cause mass removals and also adds smart battles for melee. --[[User:Darkcanuck|Darkcanuck]] 03:46, 15 May 2009 (UTC)<br /> <br /> : Oh! I am wrong, it is actually survival, not survival bonus. But we still can't use current beta for the bug that fixed in [http://robocode.svn.sourceforge.net/viewvc/robocode?view=rev&amp;revision=2983 r2983]. It's is your server now, you don't want the new way so it is a bug. I've a patch now, see if you want. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 04:41, 15 May 2009 (UTC)<br /> <br /> == Robot Entry Sorting (in Robocode) ==<br /> <br /> Regarding to [https://sourceforge.net/tracker/?func=detail&amp;aid=2890159&amp;group_id=37202&amp;atid=419486 this recent bug report I made], I want to ask you that, according to this issue (please refer to the comments on the report for detail, I don't want to repeat here), which solution do you prefer? Because I saw a lot of robots do like Diamond, and very few do like the current solution (like GrubbmGait's robots) --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 13:15, 5 November 2009 (UTC)<br /> <br /> {|border=&quot;1&quot; style=&quot;text-align:center&quot;<br /> ! Name !! Keep !! Change<br /> |-<br /> | [[User:Nat|Nat]] || || X<br /> |-<br /> | [[User:Rednaxela|Rednaxela]] || X || <br /> |}<br /> <br /> I'm afraid I have to be strongly in favor of 'keep', since I think versioning which keeps closer to what real numbers would sort to makes far more sense. I personally also think it's silly to use a designation scheme which restricts to 10 levels for any given level of versioning. I think more than 'very few' like the current solution, for a few examples see bots of: GrubbmGait, Skilgannon, Simonton, Wcsv, Mue, ABC, and myself. Also, many bots use versioning that ensures 'sane' ordering with either sorting (Shadow seems to), or simply don't have high enough versions to tell what the versioning scheme is. --[[User:Rednaxela|Rednaxela]] 13:36, 5 November 2009 (UTC)<br /> <br /> I personally prefer the current version, but feel that it does have a bug, in that if you append a letter to the end of a version name it messes the numerical section up. Eg it will sort in the following order:<br /> &lt;pre&gt;<br /> 1.1.1<br /> 1.1.10y<br /> 1.1.2<br /> 1.1.10<br /> &lt;/pre&gt;<br /> instead of<br /> &lt;pre&gt;<br /> 1.1.1<br /> 1.1.2<br /> 1.1.10<br /> 1.1.10y<br /> &lt;/pre&gt;<br /> As such, I don't support the change [[Nat]] proposed, but don't particularly support keeping it either, because I think there's a bug in it =) --[[User:Skilgannon|Skilgannon]] 14:27, 5 November 2009 (UTC)<br /> <br /> : Ahhh, I didn't realize that about lettering. Agreed :) --[[User:Rednaxela|Rednaxela]] 18:01, 5 November 2009 (UTC)<br /> <br /> Oh, that's how the current sorting works? =) I don't really care much either way. And I actually agree that the other (Mue/Skilgannon) style makes more sense, I just haven't decided how/when to change over to it in my bots. --[[User:Voidious|Voidious]] 15:54, 5 November 2009 (UTC)<br /> <br /> Actually... There's no reason code couldn't sort any mentioned version styles all correctly. I'll write code for this in a moment...--[[User:Rednaxela|Rednaxela]] 17:41, 5 November 2009 (UTC)<br /> * Wait, nevermind, I was being braindead. But... there IS actually no conflict WHEN people using Voidious-style versioning keep the number of digits constant, which they (almost?) always seem to do. --[[User:Rednaxela|Rednaxela]] 18:01, 5 November 2009 (UTC)<br /> <br /> I definitely prefer the current alpha-numerical ordering. However, it should be like the last/2nd example given by [[User:Skilgannon|Skilgannon]], not the first one, which seems to be a bug. I already have a fix for this one. But I will wait will fixing it, till I know if we should keep the current sorting. --[[User:FlemmingLarsen|Fnl]] 22:39, 5 November 2009 (UTC)<br /> <br /> == Just updated and.... ==<br /> <br /> &lt;pre&gt;SYSTEM: chase.na.Seraphim uses static reference to a robot with the following field(s):<br /> chase.na.Extension.bot, which points to a robocode.AdvancedRobot<br /> chase.na.Extension.bot, which points to a robocode.AdvancedRobot<br /> chase.na.Extension.bot, which points to a robocode.AdvancedRobot<br /> SYSTEM: Static references to robots can cause unwanted behaviour with the robot using these.<br /> SYSTEM: Please change static robot references to non-static references and recompile the robot.&lt;/pre&gt;<br /> What a fun error, probably my fault, and it is easy to fix, but assuming I assign it every<br /> round, how is this bad? Aside from the game not being able to dispose of the robot easily due<br /> to the java equivalence of a dangling pointer. &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 22:10, 24 June 2010 (UTC)<br /> <br /> Ever since some architecture changes, holding old instances caused more overhead than in old versions. If you assign it every round reliably it's probably not a problem in practice. The reason this warning was added was at least one or two robots who had old references hanging around in a problematic way were found. That answer your question? --[[User:Rednaxela|Rednaxela]] 23:00, 24 June 2010 (UTC)<br /> <br /> == Jikes vs. ECJ ==<br /> <br /> I know for a lot of the codesize restricted bots it was advantageous to compile with Jikes because it gave a slightly smaller codesize. Has anybody done any comparisons on the codesize of bots compiled ECJ vs. Jikes vs. Sun javac? I suspect Jikes still gives the smallest code... although I'd love for somebody to prove me wrong. I'm not on my usual computer or I'd be putting up some results myself =) --[[User:Skilgannon|Skilgannon]] 00:03, 29 June 2010 (UTC)<br /> <br /> Didn't think I'd have time for this, but here's what happens with Waylander:<br /> &lt;pre&gt;<br /> Code Class Class<br /> Nr size size files Location<br /> --------------------------------------------------------------------<br /> 1 742 3945 1 jk.Waylander_0.3.7jikes.jar<br /> 2 753 4828 1 jk.Waylander_0.3.7ecj.jar<br /> 3 756 5057 1 jk.Waylander_0.3.7sun.jar<br /> &lt;/pre&gt;<br /> So better than the sun 1.6.0 jdk, but worse than jikes. I'll tinker with this... I'm sure this still has debugging info in it. --[[User:Skilgannon|Skilgannon]] 00:22, 29 June 2010 (UTC)<br /> <br /> Personally what I think would be most interesting would be seeing exactly where the different sizes of each come from, using a java disassembler. Anyway, I'm pretty sure one can only use jikes when compiling against an old robocode version though. --[[User:Rednaxela|Rednaxela]] 01:40, 29 June 2010 (UTC)<br /> <br /> I am pretty sure that some tricks to reduce codesize only works for Jikes. Many of my nanobots compile on Jikes and Ejc have the same codesize. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 12:45, 29 June 2010 (UTC)<br /> <br /> I have waited as long as I could with replacing the Jikes compiler - especially due to Jikes ability to produce small code size. But unfortunately lots of users has made complaints in several years about Jikes giving strange compiling errors (I got one or two every week), and these users don't care about the code size. Hence, I suggest you still use Jikes for reducing the codesize. You can always set this up Jikes manually in Robocode, if you wish to - in fact any compiler you like. But I will only include one compiler into Robocode, and it has to be the best free &quot;stand-alone&quot; compiler, which I believe is currently ECJ. ECJ also provides much better compiler errors. :-) --[[User:FlemmingLarsen|Fnl]] 21:59, 29 June 2010 (UTC)<br /> <br /> == Bullet/Bullet intersection ==<br /> <br /> Having written the one in roboflight, I now find it interesting that bullets intersect each other as lines in Robocode, meaning their collision chance even when fired directly at each other, is a bit low. Of course firing bullets to intercept bullets is also difficult. I wonder what the game would of been like if the bullet interception routine looked like this.<br /> &lt;syntaxhighlight&gt;<br /> /**<br /> * Moving Circle test, reduced dimensionality version of the bullet/bullet intersection code in Roboflight.<br /> * Tests two moving circles s1r1 s2r2, with directional vectors &lt;s1x,s1y&gt; and &lt;s2x,s2y&gt;, over a give time.<br /> */<br /> public static final boolean testCircle(Point2D s1, double r1, Point2D s2, double r2,<br /> double s1x, double s1y, double s2x, double s2y, int time) {<br /> double rVx = s1x - s2x;<br /> double rVy = s1y - s2y;<br /> double a = rVx*rVx + rVy*rVy;<br /> double dx = s1.getX() - s2.getX();<br /> double dy = s1.getY() - s2.getY();<br /> double c = dx*dx+dy*dy;<br /> double rSum = r1 + r2;<br /> double rSumSqr = rSum * rSum;<br /> if(a &gt; 0.0) {<br /> double b = dx*rVx+dy*rVy;<br /> if(b &lt;= 0.0) {<br /> if(-time * a &lt;= b)<br /> return a * c - b * b &lt;= a * rSumSqr;<br /> return time * (time * a + 2.0 * b) + c &lt;= rSumSqr;<br /> }<br /> }<br /> return c &lt;= rSumSqr;<br /> }<br /> &lt;/syntaxhighlight&gt;<br /> <br /> &amp;#8212; &lt;span style=&quot;font-family: monospace&quot;&gt;[[User:Chase-san|Chase]]-[[User_talk:Chase-san|san]]&lt;/span&gt; 00:57, 29 June 2010 (UTC)<br /> <br /> I think it would be much different, and using bullets to shield would be much more common. Note though, even with current line-based collisions, one author has had a great deal of success with it via an interesting technique ([[BulletCatcher]]), not sure if you've seen that one or not. --[[User:Rednaxela|Rednaxela]] 01:52, 29 June 2010 (UTC)<br /> <br /> == 10th Birthday ==<br /> <br /> Hey, if Wikipedia is to be trusted, Robocode was first released in February 2001. So next month should be the 10th anniversary! But [[oldwiki:History]] says July. Anyone know for sure? ([http://web.archive.org web.archive.org] can probably help.)<br /> <br /> We should do something special! Or thing'''s''', even. Ideas? Make some &quot;Happy Birthday&quot; graphical bots? A concerted effort to clean up the wiki? Some revamped challenges? We all go visit [[User:FlemmingLarsen|Fnl]] or [[User:PEZ|PEZ]] and bring our favorite forms of alcohol (or juice, for the younglings)?<br /> <br /> Maybe I'll run a single-elimination tournament with top rumble bots and post results. Like top 64 or 128, seeded by rank, best of 7... I like the sound of that. =)<br /> <br /> --[[User:Voidious|Voidious]] 19:52, 6 January 2011 (UTC)<br /> <br /> : Btw, I found an archive of The Bot Exchange from August 19, 2001: [http://web.archive.org/web/20010819183801/http://home.covad.net/~gchomuk/RoboCode/]. It mentions the July 27, 2001 date, so I'm inclined to go with that unless someone has evidence otherwise. --[[User:Voidious|Voidious]] 01:09, 7 January 2011 (UTC)<br /> <br /> : Initial Robocode Development Log ([http://robocode.googlecode.com/svn/robocode/trunk/versions.txt here] and scroll all the way down) agrees with Wikipedia. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 11:31, 7 January 2011 (UTC)<br /> <br /> Wow, 10 years? Feels more like.. 10 years! :) Just checked my email DB, the oldest reference to robocode is an IBM newsletter from december 2001, that was probably where I first read about it. --[[User:ABC|ABC]]<br /> <br /> Have anyone think of a celebration? For all I know, it couldn't be a party unless someone would sponsor tickets ;). I can think of a special competition with special rules (Robot only; Perceptual Robot only etc.), but I much doubt number of current active robocoder... --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 11:31, 7 January 2011 (UTC)<br /> <br /> I think it would be fun to have a competition with a prize like IBM did back in the day. Maybe try to promote it a little bit. I also think it would be fun to revisit, what was it, RoboCode 2.0? I liked the idea of introducing some new features/strategy but I think the problem with that was that there were too many and not a lot of time was spent balancing them. How about RoboCode with mines or shields or oil slicks or something? --[[User:Alcatraz|Alcatraz]] 13:41, 7 January 2011 (UTC)<br /> <br /> Man, that makes me feel old. P-Robots had configurable robots with shields, fuel, speed, armor, mines, and even a cloak. It also had shots that exploded - you told it how far the missiles shot and detonated. It was a neat game --[[User:Miked0801|Miked0801]] 23:46, 7 January 2011 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=Talk:RobocodeRepository&diff=18024 2011-01-04T15:39:33Z

<p>Miked0801: </p> <hr /> <div>Looks like Robocode Repository is a little outdated. The last update seems to be from 2006... [[User:Urgood2|-- Josh S]] 14:54, 30 April 2010 (UTC)<br /> <br /> Supposedly a new version is being worked on, but nothing has been heard recently. This robocode-developers mailing list thread [http://groups.google.com/group/robocode-developers/browse_thread/thread/a8b8fedb6998d591/6a4aea8a21dc37e7 here] probably gives the best synopses of the current situation with it. --[[User:Rednaxela|Rednaxela]] 16:00, 30 April 2010 (UTC)<br /> <br /> I can't seem to get to the site..., is the server down? {{unsigned|Badchicken}}<br /> <br /> : I think so; but seems that nobody used it nowadays. I would suggest using Google Pages for hosting your robot, and check [[RoboRumble/Starting_With_RoboRumble|RoboRumble Superpack]] for any older robot. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 00:31, 3 January 2011 (UTC)<br /> <br /> : Lame, looks like I'll have to use Google from now on :) --[[User:Miked0801|Miked0801]] 15:39, 4 January 2011 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=Talk:LittleBlackBook&diff=18015 2010-12-31T05:07:54Z

<p>Miked0801: /* Bot Blog */</p> <hr /> <div>== Congrats! ==<br /> <br /> Congrats! It's nice to see some movement in the nano scene lately. I was pondering predefined data bots myself actually. I'm curious though, you say &quot;Any perfect dodge stop and go will kill it&quot;, which seems odd to me. It should be quite trivial for a distance/lateral segmented GF gun to hit that I'd think... --[[User:Rednaxela|Rednaxela]] 01:51, 15 June 2009 (UTC)<br /> : Math.signum() off e.velocity screws up 0 velocity checks and I have no velocity averaging. I'll check other bots for inspiration though. Has to be TINY though<br /> : What about... &lt;code&gt;static double foo = 1; foo = e.velocity + 0.01*foo; foo /= foo;&lt;/code&gt;? Not sure if that would be small enough, and I haven't checked it's codesize, but I think it's smaller than any others ways to handle that which come to my mind. I think it's smaller than &lt;code&gt;static double foo = 1; foo = (e.velocity == 0) ? foo : Math.signum(e.velocity);&lt;/code&gt; anyway, since conditionals and function calls are expensive if I remember right. I'd also suggest seeing if you can get rid of the need to normalize the value to 1/-1 all together, but that may not be possible in this case. --[[User:Rednaxela|Rednaxela]] 04:15, 15 June 2009 (UTC)<br /> :: Anything having to do with statics are expensive. Your above code is probably around 25 bytes or so. Math.signum(e.getVelocity()) is 6 or so. I can easily fix my problem by adding +1 to the e.getVelocity() check on the inside of the gun( for 2 bytes)... But! It will only hit perfect stop/go 50% of the time as it is setup to use the velocity to know how far to lead. Also, bots like FretNano who have good guns, but get stuck on walls randomly, would then be unhittable. I get 1 lead value per distance segment at the moment. I've got a few ideas on how to improve this, though it will double+ the size of my string table. I will adhere to the 200k max limit and with 1000 or so bots to profile, I have to be careful on size. --[[User:Miked0801|Miked0801]] 13:38, 15 June 2009 (UTC)<br /> <br /> Hi! Awesome results! Now that I looked at the code, I think there is one little problem with the overall concept: every time a new robot or a new version of a robot appears, you have to update the stats in your bot. --[[User:Robar|HUNRobar]] 10:31, 15 June 2009 (UTC)<br /> : And a decent problem it is. I'm going to review the string libraries today to see if I can find a &quot;closest to this name&quot; type function for my search. That'll at least handle versioning. The version in there right now is using default behavior against [[Pugio]] because my table is setup for 1.40. When all your other versions get cleared from the rumble, my rating will go up another .5 or so. --[[User:Miked0801|Miked0801]] 13:38, 15 June 2009 (UTC)<br /> :: &lt;code&gt;HashMap&lt;String, String&gt; enemyGF; enemyGF.get(e.getName().split(&quot; &quot;)[0]);&lt;/code&gt; =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 14:03, 15 June 2009 (UTC)<br /> ::: Um, wow. That does work: e.getName().split(&quot; &quot;)[0]. I rediscovered it myself and you had it here the whole time. I feel very stupid. Thanks for the advice! --[[User:Miked0801|Miked0801]] 06:13, 23 June 2009 (UTC)<br /> :::: No problem at all. =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 11:05, 23 June 2009 (UTC)<br /> <br /> Nice! I may re-release [[Ocnirp]] 1.0 to screw your stats =) Updated Wikipedia page for you now. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 12:00, 15 June 2009 (UTC)<br /> : Don't bother, I'm already using default values against that bot so it wouldn't make any difference so Nyaa Nyaa! :) --[[User:Miked0801|Miked0801]] 13:48, 15 June 2009 (UTC)<br /> :: Really? I don't think so. (default is 50-40-30-20-10-0, right?). Beside, I'm working on Nano adaptive movement (Mysterious is its fail attempt) =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 14:03, 15 June 2009 (UTC)<br /> ::: Ok, you win. There are quite a few bots taht got default cases though. For some reason I thought Ocnrip was one. And, yeah, nice string match there. I could fit that if, oh I don't know, I took out all my movement code ;) --[[User:Miked0801|Miked0801]] 14:20, 15 June 2009 (UTC)<br /> :::: That doesn't call fit, really. :P &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 14:53, 15 June 2009 (UTC)<br /> <br /> Thanks! Links and work email address removed. --[[User:Miked0801|Miked0801]] 15:27, 15 June 2009 (UTC)<br /> <br /> : He he, the revision system still have it. =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 15:32, 15 June 2009 (UTC)<br /> :: Yep - but at least basic spider bots won't pick it up and spam be about male enhancement products :) --[[User:Miked0801|Miked0801]]<br /> <br /> Ok, new version in the wild. I expect this release to be better against stronger bots, but I also expect some startlingly poor results against a few bots. These I can tune back to either the old values or a combo of new and old. Stelo.MirrorNano being an example. My next release will beat this bot 90/10, but now LBB is losing 45/55. No panic :) --[[User:Miked0801|Miked0801]] 02:04, 18 June 2009 (UTC)<br /> : Good result. My next update tomorrow is going to absolutely destroy the competition. This is going to be a 1900+ rating bot. --[[User:Miked0801|Miked0801]] 05:45, 18 June 2009 (UTC)<br /> <br /> == Bot Blog ==<br /> Seems like a decent place for random ramblings. The averaging code is doing its job, it just needs some table number TLC. Alas, it also screwed with some other scores that will need attention. I also commited a cut and paste errored with nat's SNG 1.0b bot resulting in a 6% score. Lame. I may try taking the averaging back out and using firepower control instead. It'd probably help me more overall to fire at 3.0 firepower at range 80 or 120 and closer against everyone. The Micro scores have been decent thus far with their first autogeneration pass. 19th is a good starting point and I know I can get to 15th or even 10th with some work there. I'll drop the mini scores in Tuesday or so and for another overall ranking boost. I still believe I can get this bot to a 2k points score with over 80%APS in nanos with a few revisits to lagging numbers.<br /> <br /> Wow, a good day. Found another 10 bytes by just re-arranging the stack vars. Used that space to try out variable move distances. Helps quite a bit against the weakest bots. Also fixed bugs with a few bots that came from typos. Finally, I fixed poorer results against rambots wehre I wasn't aiming right at range 40 and in. My scores are now approaching [[DrussGT]]'s against the low-end bots. Using that bot's scores gives me a reasonable target to short for. I'm also going to experiment with variable firepower as well, though for some reason I keep pushing back on that - dunno. Next release tomorrow night. Shooting for APS of 78ish in nanos. That would put me close to my goal of a 2k score. Hopefully, my micro score will get me top 15 there as well. I'll start running Minis by end of week to see if I can get top 25 there and perhaps top 100 overall (aiming real high, I know.) --[[User:Miked0801|Miked0801]] 03:38, 23 June 2009 (UTC)<br /> <br /> : You should to remember the [[Code Size/Cheat sheet|Code Size/Cheat sheet]]. The most important part is the vars-on-register, which is discover by Simonton I think. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 11:02, 23 June 2009 (UTC)<br /> :: I just rearrange them all until I get the smallest result :)<br /> <br /> Another good day, but I found a dumb bug I introduced to my table generation a few days ago which will require me to revisit all the nano values. Sigh. Good news though, found another 8 bytes or so by declaring the string table final (never changes so I should have done it ages ago) and by rearranging a few typecasts to make sure we got int on int math wherever possible. That means I now have both distance and firepower control in the table! It hurts by aim a touch from 80 pixels and in, but for 1 more free byte I could fix this. I'll keep looking. 8 more bytes and I get variable string matching, though if firepower or move control prove poor, I can always swap this in for the other. Because I have to do a table revisit, I'm pushing my release back one more day. Who'd have though a variable GF, variable firepower, variable move distance, variable turn control bot could be done through a silly string table. It's like the synthesis of all the best nanos in one place. Next release will have some bugs, but the one following will be absolutely epic. --[[User:Miked0801|Miked0801]] 18:48, 23 June 2009 (UTC)<br /> <br /> Bleh. Had to work late a few nights. I'm just now getting all my initial micro/nano runs complete. Good news is that only [[Moebius]] is currently able to consistantly beat me now in nanos. I'm going to experiment with distance control next as many bots are optimized for certain ranges and I expect I will do well at varying ranges against many bots. If it works well, I'll trade something off to get it. We'll see about a tomorrow release, work allowing. --[[User:Miked0801|Miked0801]] 07:39, 25 June 2009 (UTC)<br /> <br /> Played around with enemy distancing and found it helps (much) more than firepower control. But, my test cycle is too far along to scrap and start again so I'll go ahead with what I have. Besides, I believe I found a way to fit all 5 factors into this nano anyways - Fire Power, Chance to reverse direction, Min Distance to move, desired distance from enemy, and Guess Factors. It requires my tables to be created differently (again), but I'll go for that next version. This is why I haven't bothered with minis or megas yet - the tables flux dramatically with each version. It also means yet another multiplier when creating my tables. I'm already running 20+ versions per bot through roboresearch. Adding distance is another x4 or so. Yikes. Back to 1 good test run and cull, cull, cull so that I have time to balance what makes sense. At least my testing methods are improving so that this doesn't take too long. Just need 1 more set up data to finish up for the guess factors and then we'll put this bot back together again. --[[User:Miked0801|Miked0801]] 07:29, 26 June 2009 (UTC)<br /> <br /> Ok, version is up and we gained nearly another 2% APS in nanos and even more in Micros. Nice. There's still a few bots that came out a bit half baked, even with all the care I put into the tables before releasing. I'll revisit those for one last version 1.5x release and then go onto version 1.6x with distance control. Still shooting for 80+% APS, a perfect PL score in nanos, and 2k in ratings. 72 Glicko's to go. --[[User:Miked0801|Miked0801]] 02:59, 27 June 2009 (UTC)<br /> <br /> Hey, you've taken my micro's place in the microrumble! I really should do something right after I finished my flash game. ;) --[[User:Robar|HUNRobar]] 17:31, 27 June 2009 (UTC)<br /> <br /> Dang it. Screwed up robar.nano.Scytodes 0.3's table, which costed me 50-60 battle points and .33 APS in the Nano Rumble (.15 in micro). Savant values are weaker too, but that can be attributed a little to random luck. Beyond that, a very good update. Solidly in 11th now in Micros and 1.5% APS from 80 in nanos. That's only 260 battle % points and 50 of those are from my above mistake. But, without distance control, I'm running out of big gains. I can probably push this bot to 80% APS and 2k Glicko without distance, but it will take a lot of work. I made a lot of gain my swapping appropriate bots to 2.0 fire power. Some of those I can switch back to get some ground I lost between 1.52 and 1.53. I did tie for the PL score this time and would have had it if not for Scytodes. Next version I'll get it right. I think I'll release a 1.54 just to try for 10th/9th in the micros without distance help. --[[User:Miked0801|Miked0801]] 03:46, 29 June 2009 (UTC)<br /> <br /> Well fixed Scytodes and decided to alphabetize my list and lo and behold I had missed 4 other bots - all micros. Adding those gave a decent score increase for them as well and would probably challenge Jen for 10th. But, I went ahead and started the HUGE roboresearch database needed for my next release. We're talking around 1 Million battles to be run before all is ready. I'm guessing my computer running 24/7 will get through this info in around 3 days. Wow. The good news is that my previous run is compatible so I saved 150k battles or so. All this will put me over 80APS in Nanos and will put me well into top 10 in micros. I'll know for sure once I start seeing some comparison results against the micros. The top nanos appear to be weak against different ranges, but I'm not sure on Micros yet. I'll post tomorrow with some initial results. --[[User:Miked0801|Miked0801]] 21:30, 30 June 2009 (UTC)<br /> <br /> Test run about 15% complete. I'm tuning back to breadth of the first run to speed it up so I can play before next week. --[[User:Miked0801|Miked0801]] 02:18, 2 July 2009 (UTC)<br /> <br /> 33% done and I'm not patient enough to wait for it to go much further so I put together the next version - and had another awesome idea on how to make it do more for less. I now have distance control and! - all other factors also are available based on distance as well. This means variable firewpower on distance. This means I can change my move mode out of oscillation at those distances where I run into head-on shots (around 280 or so). I can even change my desired distance based on distance meaning I can ping-pong between values to help with multi-mode movers and to throw off pattern bots. That plus partial string matches and I'm sitting at exactly 249. That's enough tech for my goals. Now it's time to do my last pass through the nano/micros and see just how much pwnage will be wrought. 85+ nano APS isn't out of reach.<br /> <br /> Work, work work. My job is heating up to the point where things have been on hold for a bit. This will continue for a few more days - grr. --[[User:Miked0801|Miked0801]] 17:39, 8 July 2009 (UTC)<br /> <br /> And even more work. I'm in crunch mode now and barely have time for breathing. I've still got my next bot upgrade ready, jsut need to find a couple uninterrupted hours to fix a few minor things. I'm still alive guys :) --[[User:Miked0801|Miked0801]] 20:44, 27 August 2009 (UTC)<br /> <br /> Good to hear =) I'm also pretty snowed under, but it seems that when that happens Robocode becomes my outlet =) --[[User:Skilgannon|Skilgannon]] 20:55, 27 August 2009 (UTC)<br /> <br /> Project starting to wrap up - we'll see if life returns to normal soon... --[[User:Miked0801|Miked0801]] 16:30, 6 October 2009 (UTC)<br /> <br /> Project's done! Vacation is started. Updates to follow :) --[[User:Miked0801|Miked0801]] 16:28, 6 December 2009 (UTC)<br /> <br /> : Yay, welcome back! =) --[[User:Voidious|Voidious]] 17:18, 6 December 2009 (UTC)<br /> <br /> Ok, Nanos mostly refit. I want to find another 1.5% of APS then its back to micros. Mostly hand tuning at this point. --[[User:Miked0801|Miked0801]] 22:46, 17 December 2009 (UTC)<br /> <br /> Actually changed a little base code with this version. I removed the adjustTurnForGun() call and replaced it with a bit of randomness added to the range index. This results in slightly more random ranges when firing. It makes it easier to hit multi-modes, bullet catchers, and wave surfers, but hurts my score against really, really weak bots and the best nanos a bit. Still, seems like a decent upgrade. Broke 2 nano bot solutions with this chagne that I can easily retrofit back to pwnage. I will also be able to make a further micro pass to get above Jen on my next update. I beginning to believe that this might get top 5ish in micro before I'm done. --[[User:Miked0801|Miked0801]] 00:07, 9 January 2010 (UTC)<br /> <br /> FYI, this bot needs to be compiled with Sun's Java Compiler in order for it to remain byte size complient. Got bit with that today. Made a major pass through the tables using the top Mega bot's scores in comparison to mine for inspiration on who to fix. Found many, many bots that were improved 10% APS or more. This should be the version, barring bugs, that hits 80%APS or even 81% APS in nanos - and should also hit 2k Glicko. And there's still a bit (not much!) more tuning that can be done. There are countless ways of ordering my tables to get 1-5% individual APS tweaks that I probably need a seperate program to find. Overall, this has ben a wonderful experiment and mega contenders should take note. I'll continue to tune it a touch more, but I'm also going to investiage Lateral Velocity segmentation as well. If I get inspired, it may not cost too much :) --[[User:Miked0801|Miked0801]] 23:07, 13 January 2010 (UTC)<br /> <br /> Results looking very nice so far, though not sure if it'll quite end up getting past 2k Glicko. What I find most impressive is how you fit so many movement modes alongside a GF gun, in a nano, that's an awful lot of movement modes for a nano, particularly with the distance-based selection of them! :) --[[User:Rednaxela|Rednaxela]] 03:50, 14 January 2010 (UTC)<br /> : Thank you! I'm a rather proud parent of this bot and all comments make me grin :) --[[User:Miked0801|Miked0801]] 15:49, 14 January 2010 (UTC)<br /> <br /> BTW, the build system seems to be completely confused at the moment. Would it help if I released a 1.60 version to fix it? --[[User:Miked0801|Miked0801]] 15:49, 14 January 2010 (UTC)<br /> <br /> : What do you mean by &quot;build system&quot;? --[[User:Voidious|Voidious]] 16:24, 14 January 2010 (UTC)<br /> :: Was about to ask the same, nearly got edit conflict :) --[[User:Rednaxela|Rednaxela]] 16:33, 14 January 2010 (UTC)<br /> <br /> :: At the moment, the rumble is only running LBB 1.58 (retired), not LBB 1.59. I believe it is because 1.59 lost roughly 30ish nano battles whilst retaining the micro and up battles before I fixed an issue on my local client. I could upload the missing nano battles and that may fix it, but I wanted permission to do so first as I would need to edit the results.txt file manully to add the missing numbers. --[[User:Miked0801|Miked0801]] 17:42, 14 January 2010 (UTC)<br /> <br /> ::: &quot;... fixed an issue on my local client&quot;? Please don't edit results.txt or upload any old results! Best thing to do is delete all files in the roborumble/files and roborumble/temp folders and start fresh -- preferably with uploads disabled for the first run just to make sure. --[[User:Darkcanuck|Darkcanuck]] 21:27, 14 January 2010 (UTC)<br /> <br /> :::: Not what I did. I have 2 copies of Robo installed. I created 1.59 in version 1.6.1.4 and it was 256 bytes in size. oops. I then fixed the problem and recreated it in my other version of robocode, but stupidly called it the same thing. I then took this version and copied it to both builds. But, the codesize.txt never updated to the new, reduced size for the updated lbb. Therefore, it didn't record roughly 30ish nano battles. When i noticed this, I completely killed the cache, the local 1.59 file, and removed it from the codesize file so that it could recreate it. This worked, but those 30 or so nano battles were lost as has since confused the server quite a bit. Another side effect of this is that when you first run the client, it correctly runs version 1.59 of LBB, but further iterations always run the previous verion. Long story short, be careful about versioning of bots... --[[User:Miked0801|Miked0801]] 21:45, 14 January 2010 (UTC)<br /> <br /> :: This is weird... If you look at its roborumble details, 1.58 only has 3 battles: [http://darkcanuck.net/rumble/RatingsDetails?game=roborumble&amp;name=mld.LittleBlackBook%201.58]. Only 2 for mini, but lots for micro and nano. Not sure how that would happen... The server tries to run all pairings for each version (after a certain point), even if it's retired, so maybe that's what's going on. If you delete 1.58 from your rumble dir, it won't run 1.58 any more. (But anyone that has 1.58 will until it has all pairings, if that's the reason.) --[[User:Voidious|Voidious]] 18:51, 14 January 2010 (UTC)<br /> <br /> :: Wow... this is very weird... the &quot;Last Updated&quot; times for LittleBlackBook 1.58 keep going <br /> up in mega/mini (and different update times from mini/nano), but the battle count is only increasing in mini/nano! Something is broken on the server side I think.... because all clients with LBB 1.58 (like mine) are ONLY running LBB 1.58, but the Rumble isn't recording the mega/mini results so it looks like it'll go on forever... --[[User:Rednaxela|Rednaxela]] 19:46, 14 January 2010 (UTC)<br /> <br /> :: It should be fixed now. Looks like a concurrent retirement/reactivation. My guess is one client saw no battles for 1.58 in the last 4 hours and started to retire it, first for the general rumble then the mini. But then another client uploaded new battles (either due to old results not yet uploaded or an old priority file) while the retirements were in progress leading to the corrupted states. I have a permanent fix in mind, but it will require a lot of testing which I have yet to find time for... --[[User:Darkcanuck|Darkcanuck]] 21:27, 14 January 2010 (UTC)<br /> <br /> ::: Wow, 1.58 has 7963 battles in mega... yep... clients sure working away at it when things were messed up before... :) --[[User:Rednaxela|Rednaxela]] 03:55, 15 January 2010 (UTC)<br /> <br /> Today was a huge update! Managed to redo and find roughly 20ish more bytes!!! Desired distance from enemy table became approach angle table for a big savings. Found 2 bytes in the averaging code. Came up with a new way to do bullet detection that costs only a couple more bytes than my simple one from before. Added Ramming ability. Overall, this bot will be weaker as the dodging stuff was so tightly coupled into the random movement, but next version will keep the massive increases against the simpler, linear aim bots while improving the general movement. This bot could very well reach top 5 in Micros. I have also decided that my string tables will not exceed 200k as per the Rumble rules to make it fair. Right the tables are sitting at 100kish and won't get much bigger until I add the Minis some day. I am now awaiting the results to see which bots are now broken and need another revisit :) --[[User:Miked0801|Miked0801]] 01:33, 16 January 2010 (UTC)<br /> <br /> Tables, tables, tables. Fixed 30 or so bots thus far that I had weakened with the improved oscollation code. This put me above where I was at 1.59. I've got roughly 30 more bots to modify to get back to where 1.59 was against all bots. That's a good days work. Then, there's a revisit to change some bots from random movement back to oscollation for a nice boost. The new and improved energy detection code as made me weaker overall against PM bots. I'm working on a solution to this now. If I can find one, that's another 2APS overall or so and makes this a contender for the Micro crown. Then it would be on to the minis. Big talk though; gotta get there first! --[[User:Miked0801|Miked0801]] 19:15, 18 January 2010 (UTC)<br /> <br /> Reviewed the movement code a bit because it still felt heavy and figured out a way to do near perfect stop-n-go movement. Good enough to fool Smog 90/10. It requires a bit of table wrangling to do though so I'll wait for version 1.70 or so to do it. I've still got lots of bots to tweak before I add yet another movement mode for maybe 5% of my opponents. Actually, stop-n-go overlaps most of my current oscollator bots so I'll have to review which helps more. I could use my extra few bytes to improve my gun instead by increasing the random range it uses for the index a bit more. Or again, look perpendicular velocity segmentation which is still a bit out of reach. Lots of choices here. Perhaps it's time for some heavy roboresearch... --[[User:Miked0801|Miked0801]] 19:27, 20 January 2010 (UTC)<br /> <br /> Latest version I accidently bugged Fuatisha and lost 5aps on him. In addition, I removed the minor random added to the aim and lost .25 overall APS and gained back a bunch of bytes. Improved micros a ton though. Now, I'm sitting at 240 bytes and looking into its next improvement. It will cost 0 bytes to added near perfect stop'n'go, but I inherit another string table. That would give me another full overall APS though so I will probably do it. After that, it's time to look into improving aim with my extra bytes. I may finally be reaching the end of what I can do on movement alone. --[[User:Miked0801|Miked0801]] 16:32, 22 January 2010 (UTC)<br /> <br /> Added perfect stop n go with this version at the cost of 8 bytes. This, plus some TLC with some aim tables, has moved me up roughly 1 full APS in the rankings. I'm now #4 in micros and may hit #3 when things stablize - with a bugged ntc.Knowledge entry that cost me 40ish points in that battle. I also seem to have comfortably hit 2k Glicko in Nanos! Party! I'm also a hairs breath away from 2K in both rankings which would be a first. I found a new, flatter movement curve and randomized my aim a bit more on generic bots for a good overall catagory bump. The same pattern can be used to help my scores against the top micros next time around. Hopefully, no reds on the micro screen sometime in my future. Still have 4 or 5 nanos I just have a very hard time beating. I'll keep working at it though. [[Fuatisha]], you are an awesome bot. Next upload goal is 3rd in micros approaching 80 APS. We'll see if I can pull it off. --[[User:Miked0801|Miked0801]] 07:32, 27 January 2010 (UTC)<br /> <br /> Looks like 3rd in Micros is achieved. Also, this build may give me a perfect PL score in Nanos. [[Fuatisha]] is the only question mark right now. I actually found a movement pattern that confuses some of the string PM guns and gained a nice chunk off the top bots in nano land. That means next updated will be mostly concentrating on Micros to see if I can approach 81% in the Micro rumble. That will be difficult, but doable. If I get there, then I am a micro crown contendor with my silly little nano. I also have a new home computer coming online this weekend. Hopefully reobocode is 64-bit Windows 7 compatible. Should be. If so, I will have roughly 10x the computing power I have right now for roboresearch and should be able to put together a first pass on mini-bots sometime next week. If it goes smoothly, I may just setup some scripts and add all the bots just to see if I'm top 100 overall or not yet. That would be a trick. Wow this bot has come far... --[[User:Miked0801|Miked0801]] 22:51, 28 January 2010 (UTC)<br /> <br /> About 50% complete with first pass at minibot tables. I have good movement types for them all, now am porting across aim. Then, I test against distances. Then, rebuild with best distance and test. Should take another 2-3 hours. I might get to that tonight. I will also probably pass the nano/micros back through a test pass again as well, now that I have enough CPU power to do a decent pass in a couple hours as opposed to a couple of days. Next release, I will skip to 1.70 because I'll have updated roughly 20% of the tables. I have no idea where I'll land against the minis, but not top 10. Initial testing is showing just how strong the top 5 bots in that division are. --[[User:Miked0801|Miked0801]] 18:55, 2 February 2010 (UTC)<br /> <br /> Sigh - compiling with minibot data crashes the java compiler. My bot cannot get any bigger than micro with this technique. --[[User:Miked0801|Miked0801]] 05:47, 3 February 2010 (UTC)<br /> <br /> : Perhaps try a java bytecode disassembeler/assembler to hack the additional string length in? That might work to circumvent any compiler crashing unless it's a limitation inherent in the bytecode standard itself. --[[User:Rednaxela|Rednaxela]] 06:09, 3 February 2010 (UTC)<br /> <br /> Solved it! Too many character concats blowing up the compiler. How to fix? I just discovered how to put a unicode literal into a string &quot;\u008f&quot; becomes character 8f! This also has the added benefit of making many, many of my entries a much more readable single constant that I can static const final declare above. I will also be able to use a real IDE again as my current version crashes ecclipse and visual studio. Happy days for unicode literals! --[[User:Miked0801|Miked0801]] 16:20, 3 February 2010 (UTC)<br /> <br /> Learned some Java things the last few days:<br /> * \u000a, \u000c, and \u0022 (\r, \n, and &quot;), when put into a string literal, are treated as a raw symbol meaning you have to \ them or use a seperate symbol.<br /> * Non-aligned tables make for bugs that are very hard to find. Much debugging was needed to fix these bugs.<br /> * RoboResearch on broken bots doesn't help much in terms of strength judging.<br /> * The top minis are STRONG!<br /> I have 1 more day of tweaking and then an update. --[[User:Miked0801|Miked0801]] 05:26, 6 February 2010 (UTC)<br /> <br /> Chugging lots of numbers this weekend - ran roughly 100k battles over 2 days, testing ideal range from target from 100 to 380 units per opponent. The results of this tuning pass will appear as soon as I find 2 or so hours to comb through the results and adjust my range table. On average, I was getting a good 5-10% APS kick every 3rd robot or so, but I also know that with such a large update, I will accidently break a few bots as well. Still, when this pass is complete, I could be contending for micros overall. Minis - not sure where I'll land, but at least top 20. [[Fuatisha]], I may finally have a marginal (52/48) solution for, but that's too small to count on. --[[User:Miked0801|Miked0801]] 19:00, 8 February 2010 (UTC)<br /> <br /> BAH! 1.67 jar is partially corrupted so the source isn't available. Lame. It also has 10 or so bot bugs to fix. I'll get those taken care of tonight and get a new version reloaded. --[[User:Miked0801|Miked0801]] 18:16, 9 February 2010 (UTC)<br /> <br /> Just uploaded a test for initial movement vs no dodge against 0.1 bullets and yes dodge up to 3.9 power change. Also may stick to walls slightly more. I know that this helps against ram bots, but am curious if it helps elsewhere. I've also fixed the mess that was 1.67. When adding that many entries, mistakes will be made. With 1.69, I finally got 10% ahead of the nearest nano, an achievement in itself. I think I found 1 more byte in the aim code if I want to redo 1/2 the aim values. The typecast to short can be dropped if I change my negative aim values to 2*Pi - values as I'm normalizing my gun anyway. I'll do that if the intial movement change turns out decent and I want the slightly better dodging code back. Then I do another comb through for 1 more byte. Always 1 more byte :) I'm now also thining about PhoneBook, a micro bot based on the lessons this bot has taught me. I won't abuse string literals like I have with this bot as I'll have enough room to handle things more elegantly (at first!). I'm also going to make another pass through [[Infinity]] and [[DustBunny]], using my new tricks to save a ton of space. That may free up enough space for them to go on a new melee run. For fun, I've calculated what it would require to brute force the best possible bot with this technique and it would cost about (40^6 x 30 x 8 x 20 x 50 x 100) x numBots=800 x numSeasonsToGetGoodResult=10 or 7.86e20 battles run. Even at 1 battle per second, I don't think I have time to wait around for this result to appear. And this is with some culling already built in. Perhaps I'll check out JGAP or something for fun to see if a genetic algo comes up with better answers than what I've been doing. --[[User:Miked0801|Miked0801]] 22:59, 12 February 2010 (UTC)<br /> <br /> : Some rough calculation told me that even at 1000 battles/second, by the time the result appear, out sun will be White Dwarf for 2E10 year already ((7.86E20)/(86400*365*1000) - 5E9 approx. = 1.99E10, give or take leap year) --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 04:48, 13 February 2010 (UTC)<br /> <br /> Funny how taking out &quot;code improvments&quot; actually gained me between .25 and 1.0% APS in divisions. Now I'm sitting at 243 bytes with 6 bytes to spend on whatever. I also believe I may have figured out a cheap size way to get (averaged) lateral velocity segmentation in. If it works, I will be micro champion and will challenge for minis. Just need some time to see if it works - or I can go optimize some tables a bit to squeak out another 1.5% in micros and try to win that way. Either will work given some time. --[[User:Miked0801|Miked0801]] 08:16, 14 February 2010 (UTC)<br /> <br /> I've coded in average lateral velocity / distance segmenting on my local copy at the cost of only 2 bytes. I'm not happy with my data gathering method though. With simpler bots like el33tGangstar &lt;sp&gt; or [[Infinity]] or even [[spinbot]], I should be able to get a near 100% lock on rate with my gun and my test bot is currently not able to do this. I even added in a segment for acceleration/deceration/steady to see if perhaps that was the issue without luck thus far. Or am I being too perfect here? Amazingly enough, multiple segments isn't as easy as I thought it would be. Perhaps that's why there are so many different ways of doing this out there right now. If I can get my dataset cleaned up, I can test it against 10-20 bots and see how much of a difference it will make. It will fix my current weakness against multi-mode moving bots as well as make my data tables in general more efficient in space. I'll basically be trading 80% of my movement tables (which are mostly unused anyways) for additional aiming information which can be very useful. I can also explore segment size being controled via a more complex formula than e.distance() / CONSTANT to better pack my data into useful areas - with size cost being controlled. Perhaps something like a bell curve centered around 200ish distance. Perhaps even something like AmplitudeConstant * Math.sin(Math.min(e.getDistance * Constant, maxRange)). That costs around 27ish bytes so maybe I'll just stick with the original :) If I do get this to work, it means revisitng every stinking entry in the bot; AGAIN. Man that sucks --[[User:Miked0801|Miked0801]] 21:57, 16 February 2010 (UTC)<br /> <br /> It's been a while and I have been doing various experiments. I've now got my helper bot generating a profile based on acceleration, avg angular velocity, distance, and fire power. I've also calculated the math such that I have a very good idea if a particular GF bin or sets of bins actually hit the target or not. From that, I can compare the various fire power bins to get a points per tic calculation to determine what firepower is most effective at what range calculation. So, I now have a system to automate firepower at distance selection. Just that alone put into the current LBB framework would probably grab a full aps and perhaps more. But, I'll be adding an additional module to the test bot to iterate over the various movement profiles I've created. If it can alternate best movement check, best gun check, and iterate back and forth until both values agree, I've now automated most of the table creation process. Once that works, then I can use this new process to generate a set of tables for angular velocity vs distance vs firepower tables and perhaps even acceleration if I can find the code space. This of course is time consuming. Ambitious, but if successful, I'll have a very, very nice bot upgrade and a low labor path to adding all bots regardless of codesize catagory. I envision a time where adding a new bot is just a matter of running my test bot against it a few thousand times until the numbers stabilze. If I place the movement checks into an external xml or whatever table, then I have a way of adding new movement types at will without recompiling. A fully automated LBB table system. This of course could be used as a spring board for larger, more complex bots in the future. --[[User:Miked0801|Miked0801]] 18:07, 22 February 2010 (UTC)<br /> <br /> No work this last week - interest is waining and work is picking back up. I will make time in the near future to claim the micro crown though :) --[[User:Miked0801|Miked0801]] 19:15, 2 March 2010 (UTC)<br /> <br /> Work still going strong here. Interest renewing. I will get this bot to #1 micro some day when I have a few days to work on it... --[[User:Miked0801|Miked0801]] 18:57, 21 April 2010 (UTC)<br /> <br /> One work project complete, but another short timeline project started. Ugh. Still a few weeks at least until I can start thinking here again. I've got at least 5 new bots that would want to be added to my library. The there's finishing my last edit run on a new improved gun... --[[User:Miked0801|Miked0801]] 16:48, 8 June 2010 (UTC)<br /> <br /> Hooray, a new nano to the field that is strong! I look forward to seeing how far you can go Caligula! Still busy, busy at work, but still watching the action here --[[User:Miked0801|Miked0801]] 17:47, 7 September 2010 (UTC)<br /> <br /> Fighting the urge to play again over winter break :) --[[User:Miked0801|Miked0801]] 05:07, 31 December 2010 (UTC)<br /> <br /> == LBB Cheeze Factor ==<br /> <br /> I added PEZ's [[LittleEvilBrother]], because it also had a String based GF gun, I believe. There was some discussion about whether or not it was cheesy to load data for a bot not capable of saving data. Consensus at the time was that it was cheesy, but judging by how much better [[LittleBlackBook]] does, it seems like a pretty cool strategy that has a lot of room for experimentation. Plus there's been nothing new in nano-land for years! --[[User:Alcatraz|Alcatraz]] 03:09, 26 June 2009 (UTC)<br /> <br /> : I'd be of the opinion that it is cheesy, but don't object to keeping it around, at least till something particularly new happens in nano-land :) --[[User:Rednaxela|Rednaxela]] 04:26, 26 June 2009 (UTC)<br /> <br /> :: It's extremely cheesy an exploitive of a loophole in the codesize tool. Yet, I'm having some real fun with it right now (and this game is supposed to be fun! :). I literally believe I can get this bot as a top 10 in the micro competition as a nano. That's something that hasn't been done since just after we decided on weight classes. Right now, I'm still crunching a rather exhasutive set of numbers for firepower and movement types. Once that's done, I'll grab the numbers and give it a test run to see where it stands. Good chance it will go in tonight. --[[User:Miked0801|Miked0801]] 05:15, 26 June 2009 (UTC)<br /> <br /> ::: Well, I wouldn't call it &quot;exploitive of a loophole in the codesize tool&quot; exactly (unless someone makes a highly capable interpereter within nano size), since such preloading of data specific to certain bots is also cheesy for megabots. I think what's cheesey most fundumentally, is when a bot that looks up the enemy on a preloaded table based on bot names regardless of codesize. --[[User:Rednaxela|Rednaxela]] 13:11, 26 June 2009 (UTC)<br /> <br /> ::: I for one don't like this though, but it is acceptable for me. Unless, like Rednaxela, someone make a good enough nano-size compiler and fit DrussGT into nano. I'll not object, but I do think that when you fully tuned this robot to the top and have no more idea, you should retire this robot. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 13:30, 26 June 2009 (UTC)<br /> <br /> ::: Of course I agree that preloading data is kinda cheesy, but I think everyone understands that LBB is of a different ilk than other NanoBots. It's cool seeing how far you can go with it. To be honest, I think even hand-tuned segmentations are similar to pre-loading: with a different rumble population, different tunings would surely work better. We all take the rumble population into account when we write our bots; pre-loading is just a more explicit way of doing so. --[[User:Voidious|Voidious]] 14:10, 26 June 2009 (UTC)<br /> <br /> ::: Yep, it's cool to see how far LBB can go indeed. It is true that we all build our bots in way that considers the rumble population, but I don't think pre-loading itself is the cheesy thing. For one thing, I wouldn't consider it cheesy at all, if a GF gun preloads with the average data of a bunch of rumble bots, until it's learned enough about the specific enemy (hint, hint). I think tying pre-loaded data to a specific bot name is where the 'cheese' begins, but more general pre-loaded data is simply prudant rather than cheesy. --[[User:Rednaxela|Rednaxela]] 14:34, 26 June 2009 (UTC)<br /> <br /> ::: Personally, I think the only issue here is that pre-loading is used to get around the size class limits. A bot that saves its own data is fine by me, whether it's general or specific -- the 200k limit restricts how much you can really store anyway. LBB is a novel concept, but it would be disappointing to see it inspire a new generation of string table nanos/micros/minis. Now if you could make a nano that ''generates'' its own string tables, that would be really cool. You still have a few bytes left, right? ;) --[[User:Darkcanuck|Darkcanuck]] 15:02, 26 June 2009 (UTC)<br /> <br /> == AceSurf ==<br /> <br /> I noticed you make not of AceSurf being a problem. One possible solution (if you can fit it into the codesize) that would probably work well, would be having a special code in your data that says &quot;Aim at the last GF it went to&quot;. I'm kind of thinking that would probably eat too much codesize... but I think that's probably the simplest thing that could be done with the likes of AceSurf, besides random targeting anyway. --[[User:Rednaxela|Rednaxela]] 16:00, 20 June 2009 (UTC)<br /> <br /> : I'm not too worried. This bot just hit the 1900 club - the first ever in nanoland to do this. This is with untuned tables for 1/2 the bots. I will take a closer look at ace.surf results though and possibly setup alternating guess factors at every 40 pixels. This has been the best way recently to smash wave bots as it is nearly the same as 2 different guess factors every few shots. Wow I proud of this bot. I might be able to get it to the 2000 club when all is said and done. It just needs another 1000 percentage basis points or so. Plus, right after this bot was released, I figured out a way to better hit stop'n'go's without reducing accuracy against simpler bots who just get stuck. Next release will be fun! --[[User:Miked0801|Miked0801]] 16:06, 20 June 2009 (UTC)<br /> <br /> :: IIRC, The club score is base on ELO, not Glicko-2. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 16:13, 20 June 2009 (UTC)<br /> ::: then [[Toorkild]] isn't in the 2k club. I was pretty sure it was the Glicko. But, it all may be mute. I just realized how few battles it has run - only about 1 per bot. I'll therefore wait a bit before posting anything further on that :) --[[User:Miked0801|Miked0801]] 16:17, 20 June 2009 (UTC)<br /> ::: We're in a weird position with the clubs because it was based on ELO on the old server. ELO on Darkcanuck's server is way lower than it was on the old server, and Glicko-2 is a bit higher -- at least in MegaBot and MiniBot 1v1. As a point of reference, before the old RR server hit a few months of non-stop upwards drift, Dookious was about 2130 and Komarious was about 2085 in mini (prolly a few points higher now). Nevertheless, it's still easy to compare your bot to the competition, arbitrary rating systems aside. =) --[[User:Voidious|Voidious]] 16:26, 20 June 2009 (UTC)<br /> :::: The new server originally matched the old one, but ELO has drifted steadily downwards in the past few months. Why, I don't know. In late 2008, Glicko2 and ELO were in the same range, but now they're quite different. Maybe it's all the recent activity, plus some long-standing bots were removed earlier this year too. In any case, ELO is a relative ranking system so it's the difference between the scores that matters, not the absolute values. But it does leave the ELO clubs in a funny position. --[[User:Darkcanuck|Darkcanuck]] 17:34, 20 June 2009 (UTC)<br /> <br /> <br /> == Fuatisha==<br /> Well, it's nice to see that my nano is giving you so much trouble! Would you happen to have any idea why LBB seems to be having more trouble with it than other adaptive movement nanos? Of course, I wouldn't just be trying to figure out the best things to tweak in it......--[[User:CrazyBassoonist|CrazyBassoonist]] 03:34, 14 February 2010 (UTC)<br /> <br /> It's a number of things:<br /> * It really doesn't have a weakness in its good at any distance I can exploit. [[Moebius]] had a weakness at 260. <br /> * It's movement is adaptive - my gun is not. Plus it has a Very flat movement profile.<br /> * It's gun is just really, really good.<br /> * The opening stop/go movement has a signifigantly different GF profile than its later movements meaning I have to give up hit percentage later to get it out of its opening gambit.<br /> Basically, it is a better overall fighting bot than [[NeophytePattern]] and [[Moebius]], but does worse against weaker bots. If you were to tune anything, tune agaist the masses and you'll probably get #2 (and help me!) :) --[[User:Miked0801|Miked0801]] 05:27, 14 February 2010 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=Talk:LittleBlackBook&diff=17404 2010-09-07T17:47:15Z

<p>Miked0801: /* Bot Blog */</p> <hr /> <div>== Congrats! ==<br /> <br /> Congrats! It's nice to see some movement in the nano scene lately. I was pondering predefined data bots myself actually. I'm curious though, you say &quot;Any perfect dodge stop and go will kill it&quot;, which seems odd to me. It should be quite trivial for a distance/lateral segmented GF gun to hit that I'd think... --[[User:Rednaxela|Rednaxela]] 01:51, 15 June 2009 (UTC)<br /> : Math.signum() off e.velocity screws up 0 velocity checks and I have no velocity averaging. I'll check other bots for inspiration though. Has to be TINY though<br /> : What about... &lt;code&gt;static double foo = 1; foo = e.velocity + 0.01*foo; foo /= foo;&lt;/code&gt;? Not sure if that would be small enough, and I haven't checked it's codesize, but I think it's smaller than any others ways to handle that which come to my mind. I think it's smaller than &lt;code&gt;static double foo = 1; foo = (e.velocity == 0) ? foo : Math.signum(e.velocity);&lt;/code&gt; anyway, since conditionals and function calls are expensive if I remember right. I'd also suggest seeing if you can get rid of the need to normalize the value to 1/-1 all together, but that may not be possible in this case. --[[User:Rednaxela|Rednaxela]] 04:15, 15 June 2009 (UTC)<br /> :: Anything having to do with statics are expensive. Your above code is probably around 25 bytes or so. Math.signum(e.getVelocity()) is 6 or so. I can easily fix my problem by adding +1 to the e.getVelocity() check on the inside of the gun( for 2 bytes)... But! It will only hit perfect stop/go 50% of the time as it is setup to use the velocity to know how far to lead. Also, bots like FretNano who have good guns, but get stuck on walls randomly, would then be unhittable. I get 1 lead value per distance segment at the moment. I've got a few ideas on how to improve this, though it will double+ the size of my string table. I will adhere to the 200k max limit and with 1000 or so bots to profile, I have to be careful on size. --[[User:Miked0801|Miked0801]] 13:38, 15 June 2009 (UTC)<br /> <br /> Hi! Awesome results! Now that I looked at the code, I think there is one little problem with the overall concept: every time a new robot or a new version of a robot appears, you have to update the stats in your bot. --[[User:Robar|HUNRobar]] 10:31, 15 June 2009 (UTC)<br /> : And a decent problem it is. I'm going to review the string libraries today to see if I can find a &quot;closest to this name&quot; type function for my search. That'll at least handle versioning. The version in there right now is using default behavior against [[Pugio]] because my table is setup for 1.40. When all your other versions get cleared from the rumble, my rating will go up another .5 or so. --[[User:Miked0801|Miked0801]] 13:38, 15 June 2009 (UTC)<br /> :: &lt;code&gt;HashMap&lt;String, String&gt; enemyGF; enemyGF.get(e.getName().split(&quot; &quot;)[0]);&lt;/code&gt; =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 14:03, 15 June 2009 (UTC)<br /> ::: Um, wow. That does work: e.getName().split(&quot; &quot;)[0]. I rediscovered it myself and you had it here the whole time. I feel very stupid. Thanks for the advice! --[[User:Miked0801|Miked0801]] 06:13, 23 June 2009 (UTC)<br /> :::: No problem at all. =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 11:05, 23 June 2009 (UTC)<br /> <br /> Nice! I may re-release [[Ocnirp]] 1.0 to screw your stats =) Updated Wikipedia page for you now. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 12:00, 15 June 2009 (UTC)<br /> : Don't bother, I'm already using default values against that bot so it wouldn't make any difference so Nyaa Nyaa! :) --[[User:Miked0801|Miked0801]] 13:48, 15 June 2009 (UTC)<br /> :: Really? I don't think so. (default is 50-40-30-20-10-0, right?). Beside, I'm working on Nano adaptive movement (Mysterious is its fail attempt) =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 14:03, 15 June 2009 (UTC)<br /> ::: Ok, you win. There are quite a few bots taht got default cases though. For some reason I thought Ocnrip was one. And, yeah, nice string match there. I could fit that if, oh I don't know, I took out all my movement code ;) --[[User:Miked0801|Miked0801]] 14:20, 15 June 2009 (UTC)<br /> :::: That doesn't call fit, really. :P &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 14:53, 15 June 2009 (UTC)<br /> <br /> Thanks! Links and work email address removed. --[[User:Miked0801|Miked0801]] 15:27, 15 June 2009 (UTC)<br /> <br /> : He he, the revision system still have it. =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 15:32, 15 June 2009 (UTC)<br /> :: Yep - but at least basic spider bots won't pick it up and spam be about male enhancement products :) --[[User:Miked0801|Miked0801]]<br /> <br /> Ok, new version in the wild. I expect this release to be better against stronger bots, but I also expect some startlingly poor results against a few bots. These I can tune back to either the old values or a combo of new and old. Stelo.MirrorNano being an example. My next release will beat this bot 90/10, but now LBB is losing 45/55. No panic :) --[[User:Miked0801|Miked0801]] 02:04, 18 June 2009 (UTC)<br /> : Good result. My next update tomorrow is going to absolutely destroy the competition. This is going to be a 1900+ rating bot. --[[User:Miked0801|Miked0801]] 05:45, 18 June 2009 (UTC)<br /> <br /> == Bot Blog ==<br /> Seems like a decent place for random ramblings. The averaging code is doing its job, it just needs some table number TLC. Alas, it also screwed with some other scores that will need attention. I also commited a cut and paste errored with nat's SNG 1.0b bot resulting in a 6% score. Lame. I may try taking the averaging back out and using firepower control instead. It'd probably help me more overall to fire at 3.0 firepower at range 80 or 120 and closer against everyone. The Micro scores have been decent thus far with their first autogeneration pass. 19th is a good starting point and I know I can get to 15th or even 10th with some work there. I'll drop the mini scores in Tuesday or so and for another overall ranking boost. I still believe I can get this bot to a 2k points score with over 80%APS in nanos with a few revisits to lagging numbers.<br /> <br /> Wow, a good day. Found another 10 bytes by just re-arranging the stack vars. Used that space to try out variable move distances. Helps quite a bit against the weakest bots. Also fixed bugs with a few bots that came from typos. Finally, I fixed poorer results against rambots wehre I wasn't aiming right at range 40 and in. My scores are now approaching [[DrussGT]]'s against the low-end bots. Using that bot's scores gives me a reasonable target to short for. I'm also going to experiment with variable firepower as well, though for some reason I keep pushing back on that - dunno. Next release tomorrow night. Shooting for APS of 78ish in nanos. That would put me close to my goal of a 2k score. Hopefully, my micro score will get me top 15 there as well. I'll start running Minis by end of week to see if I can get top 25 there and perhaps top 100 overall (aiming real high, I know.) --[[User:Miked0801|Miked0801]] 03:38, 23 June 2009 (UTC)<br /> <br /> : You should to remember the [[Code Size/Cheat sheet|Code Size/Cheat sheet]]. The most important part is the vars-on-register, which is discover by Simonton I think. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 11:02, 23 June 2009 (UTC)<br /> :: I just rearrange them all until I get the smallest result :)<br /> <br /> Another good day, but I found a dumb bug I introduced to my table generation a few days ago which will require me to revisit all the nano values. Sigh. Good news though, found another 8 bytes or so by declaring the string table final (never changes so I should have done it ages ago) and by rearranging a few typecasts to make sure we got int on int math wherever possible. That means I now have both distance and firepower control in the table! It hurts by aim a touch from 80 pixels and in, but for 1 more free byte I could fix this. I'll keep looking. 8 more bytes and I get variable string matching, though if firepower or move control prove poor, I can always swap this in for the other. Because I have to do a table revisit, I'm pushing my release back one more day. Who'd have though a variable GF, variable firepower, variable move distance, variable turn control bot could be done through a silly string table. It's like the synthesis of all the best nanos in one place. Next release will have some bugs, but the one following will be absolutely epic. --[[User:Miked0801|Miked0801]] 18:48, 23 June 2009 (UTC)<br /> <br /> Bleh. Had to work late a few nights. I'm just now getting all my initial micro/nano runs complete. Good news is that only [[Moebius]] is currently able to consistantly beat me now in nanos. I'm going to experiment with distance control next as many bots are optimized for certain ranges and I expect I will do well at varying ranges against many bots. If it works well, I'll trade something off to get it. We'll see about a tomorrow release, work allowing. --[[User:Miked0801|Miked0801]] 07:39, 25 June 2009 (UTC)<br /> <br /> Played around with enemy distancing and found it helps (much) more than firepower control. But, my test cycle is too far along to scrap and start again so I'll go ahead with what I have. Besides, I believe I found a way to fit all 5 factors into this nano anyways - Fire Power, Chance to reverse direction, Min Distance to move, desired distance from enemy, and Guess Factors. It requires my tables to be created differently (again), but I'll go for that next version. This is why I haven't bothered with minis or megas yet - the tables flux dramatically with each version. It also means yet another multiplier when creating my tables. I'm already running 20+ versions per bot through roboresearch. Adding distance is another x4 or so. Yikes. Back to 1 good test run and cull, cull, cull so that I have time to balance what makes sense. At least my testing methods are improving so that this doesn't take too long. Just need 1 more set up data to finish up for the guess factors and then we'll put this bot back together again. --[[User:Miked0801|Miked0801]] 07:29, 26 June 2009 (UTC)<br /> <br /> Ok, version is up and we gained nearly another 2% APS in nanos and even more in Micros. Nice. There's still a few bots that came out a bit half baked, even with all the care I put into the tables before releasing. I'll revisit those for one last version 1.5x release and then go onto version 1.6x with distance control. Still shooting for 80+% APS, a perfect PL score in nanos, and 2k in ratings. 72 Glicko's to go. --[[User:Miked0801|Miked0801]] 02:59, 27 June 2009 (UTC)<br /> <br /> Hey, you've taken my micro's place in the microrumble! I really should do something right after I finished my flash game. ;) --[[User:Robar|HUNRobar]] 17:31, 27 June 2009 (UTC)<br /> <br /> Dang it. Screwed up robar.nano.Scytodes 0.3's table, which costed me 50-60 battle points and .33 APS in the Nano Rumble (.15 in micro). Savant values are weaker too, but that can be attributed a little to random luck. Beyond that, a very good update. Solidly in 11th now in Micros and 1.5% APS from 80 in nanos. That's only 260 battle % points and 50 of those are from my above mistake. But, without distance control, I'm running out of big gains. I can probably push this bot to 80% APS and 2k Glicko without distance, but it will take a lot of work. I made a lot of gain my swapping appropriate bots to 2.0 fire power. Some of those I can switch back to get some ground I lost between 1.52 and 1.53. I did tie for the PL score this time and would have had it if not for Scytodes. Next version I'll get it right. I think I'll release a 1.54 just to try for 10th/9th in the micros without distance help. --[[User:Miked0801|Miked0801]] 03:46, 29 June 2009 (UTC)<br /> <br /> Well fixed Scytodes and decided to alphabetize my list and lo and behold I had missed 4 other bots - all micros. Adding those gave a decent score increase for them as well and would probably challenge Jen for 10th. But, I went ahead and started the HUGE roboresearch database needed for my next release. We're talking around 1 Million battles to be run before all is ready. I'm guessing my computer running 24/7 will get through this info in around 3 days. Wow. The good news is that my previous run is compatible so I saved 150k battles or so. All this will put me over 80APS in Nanos and will put me well into top 10 in micros. I'll know for sure once I start seeing some comparison results against the micros. The top nanos appear to be weak against different ranges, but I'm not sure on Micros yet. I'll post tomorrow with some initial results. --[[User:Miked0801|Miked0801]] 21:30, 30 June 2009 (UTC)<br /> <br /> Test run about 15% complete. I'm tuning back to breadth of the first run to speed it up so I can play before next week. --[[User:Miked0801|Miked0801]] 02:18, 2 July 2009 (UTC)<br /> <br /> 33% done and I'm not patient enough to wait for it to go much further so I put together the next version - and had another awesome idea on how to make it do more for less. I now have distance control and! - all other factors also are available based on distance as well. This means variable firewpower on distance. This means I can change my move mode out of oscillation at those distances where I run into head-on shots (around 280 or so). I can even change my desired distance based on distance meaning I can ping-pong between values to help with multi-mode movers and to throw off pattern bots. That plus partial string matches and I'm sitting at exactly 249. That's enough tech for my goals. Now it's time to do my last pass through the nano/micros and see just how much pwnage will be wrought. 85+ nano APS isn't out of reach.<br /> <br /> Work, work work. My job is heating up to the point where things have been on hold for a bit. This will continue for a few more days - grr. --[[User:Miked0801|Miked0801]] 17:39, 8 July 2009 (UTC)<br /> <br /> And even more work. I'm in crunch mode now and barely have time for breathing. I've still got my next bot upgrade ready, jsut need to find a couple uninterrupted hours to fix a few minor things. I'm still alive guys :) --[[User:Miked0801|Miked0801]] 20:44, 27 August 2009 (UTC)<br /> <br /> Good to hear =) I'm also pretty snowed under, but it seems that when that happens Robocode becomes my outlet =) --[[User:Skilgannon|Skilgannon]] 20:55, 27 August 2009 (UTC)<br /> <br /> Project starting to wrap up - we'll see if life returns to normal soon... --[[User:Miked0801|Miked0801]] 16:30, 6 October 2009 (UTC)<br /> <br /> Project's done! Vacation is started. Updates to follow :) --[[User:Miked0801|Miked0801]] 16:28, 6 December 2009 (UTC)<br /> <br /> : Yay, welcome back! =) --[[User:Voidious|Voidious]] 17:18, 6 December 2009 (UTC)<br /> <br /> Ok, Nanos mostly refit. I want to find another 1.5% of APS then its back to micros. Mostly hand tuning at this point. --[[User:Miked0801|Miked0801]] 22:46, 17 December 2009 (UTC)<br /> <br /> Actually changed a little base code with this version. I removed the adjustTurnForGun() call and replaced it with a bit of randomness added to the range index. This results in slightly more random ranges when firing. It makes it easier to hit multi-modes, bullet catchers, and wave surfers, but hurts my score against really, really weak bots and the best nanos a bit. Still, seems like a decent upgrade. Broke 2 nano bot solutions with this chagne that I can easily retrofit back to pwnage. I will also be able to make a further micro pass to get above Jen on my next update. I beginning to believe that this might get top 5ish in micro before I'm done. --[[User:Miked0801|Miked0801]] 00:07, 9 January 2010 (UTC)<br /> <br /> FYI, this bot needs to be compiled with Sun's Java Compiler in order for it to remain byte size complient. Got bit with that today. Made a major pass through the tables using the top Mega bot's scores in comparison to mine for inspiration on who to fix. Found many, many bots that were improved 10% APS or more. This should be the version, barring bugs, that hits 80%APS or even 81% APS in nanos - and should also hit 2k Glicko. And there's still a bit (not much!) more tuning that can be done. There are countless ways of ordering my tables to get 1-5% individual APS tweaks that I probably need a seperate program to find. Overall, this has ben a wonderful experiment and mega contenders should take note. I'll continue to tune it a touch more, but I'm also going to investiage Lateral Velocity segmentation as well. If I get inspired, it may not cost too much :) --[[User:Miked0801|Miked0801]] 23:07, 13 January 2010 (UTC)<br /> <br /> Results looking very nice so far, though not sure if it'll quite end up getting past 2k Glicko. What I find most impressive is how you fit so many movement modes alongside a GF gun, in a nano, that's an awful lot of movement modes for a nano, particularly with the distance-based selection of them! :) --[[User:Rednaxela|Rednaxela]] 03:50, 14 January 2010 (UTC)<br /> : Thank you! I'm a rather proud parent of this bot and all comments make me grin :) --[[User:Miked0801|Miked0801]] 15:49, 14 January 2010 (UTC)<br /> <br /> BTW, the build system seems to be completely confused at the moment. Would it help if I released a 1.60 version to fix it? --[[User:Miked0801|Miked0801]] 15:49, 14 January 2010 (UTC)<br /> <br /> : What do you mean by &quot;build system&quot;? --[[User:Voidious|Voidious]] 16:24, 14 January 2010 (UTC)<br /> :: Was about to ask the same, nearly got edit conflict :) --[[User:Rednaxela|Rednaxela]] 16:33, 14 January 2010 (UTC)<br /> <br /> :: At the moment, the rumble is only running LBB 1.58 (retired), not LBB 1.59. I believe it is because 1.59 lost roughly 30ish nano battles whilst retaining the micro and up battles before I fixed an issue on my local client. I could upload the missing nano battles and that may fix it, but I wanted permission to do so first as I would need to edit the results.txt file manully to add the missing numbers. --[[User:Miked0801|Miked0801]] 17:42, 14 January 2010 (UTC)<br /> <br /> ::: &quot;... fixed an issue on my local client&quot;? Please don't edit results.txt or upload any old results! Best thing to do is delete all files in the roborumble/files and roborumble/temp folders and start fresh -- preferably with uploads disabled for the first run just to make sure. --[[User:Darkcanuck|Darkcanuck]] 21:27, 14 January 2010 (UTC)<br /> <br /> :::: Not what I did. I have 2 copies of Robo installed. I created 1.59 in version 1.6.1.4 and it was 256 bytes in size. oops. I then fixed the problem and recreated it in my other version of robocode, but stupidly called it the same thing. I then took this version and copied it to both builds. But, the codesize.txt never updated to the new, reduced size for the updated lbb. Therefore, it didn't record roughly 30ish nano battles. When i noticed this, I completely killed the cache, the local 1.59 file, and removed it from the codesize file so that it could recreate it. This worked, but those 30 or so nano battles were lost as has since confused the server quite a bit. Another side effect of this is that when you first run the client, it correctly runs version 1.59 of LBB, but further iterations always run the previous verion. Long story short, be careful about versioning of bots... --[[User:Miked0801|Miked0801]] 21:45, 14 January 2010 (UTC)<br /> <br /> :: This is weird... If you look at its roborumble details, 1.58 only has 3 battles: [http://darkcanuck.net/rumble/RatingsDetails?game=roborumble&amp;name=mld.LittleBlackBook%201.58]. Only 2 for mini, but lots for micro and nano. Not sure how that would happen... The server tries to run all pairings for each version (after a certain point), even if it's retired, so maybe that's what's going on. If you delete 1.58 from your rumble dir, it won't run 1.58 any more. (But anyone that has 1.58 will until it has all pairings, if that's the reason.) --[[User:Voidious|Voidious]] 18:51, 14 January 2010 (UTC)<br /> <br /> :: Wow... this is very weird... the &quot;Last Updated&quot; times for LittleBlackBook 1.58 keep going <br /> up in mega/mini (and different update times from mini/nano), but the battle count is only increasing in mini/nano! Something is broken on the server side I think.... because all clients with LBB 1.58 (like mine) are ONLY running LBB 1.58, but the Rumble isn't recording the mega/mini results so it looks like it'll go on forever... --[[User:Rednaxela|Rednaxela]] 19:46, 14 January 2010 (UTC)<br /> <br /> :: It should be fixed now. Looks like a concurrent retirement/reactivation. My guess is one client saw no battles for 1.58 in the last 4 hours and started to retire it, first for the general rumble then the mini. But then another client uploaded new battles (either due to old results not yet uploaded or an old priority file) while the retirements were in progress leading to the corrupted states. I have a permanent fix in mind, but it will require a lot of testing which I have yet to find time for... --[[User:Darkcanuck|Darkcanuck]] 21:27, 14 January 2010 (UTC)<br /> <br /> ::: Wow, 1.58 has 7963 battles in mega... yep... clients sure working away at it when things were messed up before... :) --[[User:Rednaxela|Rednaxela]] 03:55, 15 January 2010 (UTC)<br /> <br /> Today was a huge update! Managed to redo and find roughly 20ish more bytes!!! Desired distance from enemy table became approach angle table for a big savings. Found 2 bytes in the averaging code. Came up with a new way to do bullet detection that costs only a couple more bytes than my simple one from before. Added Ramming ability. Overall, this bot will be weaker as the dodging stuff was so tightly coupled into the random movement, but next version will keep the massive increases against the simpler, linear aim bots while improving the general movement. This bot could very well reach top 5 in Micros. I have also decided that my string tables will not exceed 200k as per the Rumble rules to make it fair. Right the tables are sitting at 100kish and won't get much bigger until I add the Minis some day. I am now awaiting the results to see which bots are now broken and need another revisit :) --[[User:Miked0801|Miked0801]] 01:33, 16 January 2010 (UTC)<br /> <br /> Tables, tables, tables. Fixed 30 or so bots thus far that I had weakened with the improved oscollation code. This put me above where I was at 1.59. I've got roughly 30 more bots to modify to get back to where 1.59 was against all bots. That's a good days work. Then, there's a revisit to change some bots from random movement back to oscollation for a nice boost. The new and improved energy detection code as made me weaker overall against PM bots. I'm working on a solution to this now. If I can find one, that's another 2APS overall or so and makes this a contender for the Micro crown. Then it would be on to the minis. Big talk though; gotta get there first! --[[User:Miked0801|Miked0801]] 19:15, 18 January 2010 (UTC)<br /> <br /> Reviewed the movement code a bit because it still felt heavy and figured out a way to do near perfect stop-n-go movement. Good enough to fool Smog 90/10. It requires a bit of table wrangling to do though so I'll wait for version 1.70 or so to do it. I've still got lots of bots to tweak before I add yet another movement mode for maybe 5% of my opponents. Actually, stop-n-go overlaps most of my current oscollator bots so I'll have to review which helps more. I could use my extra few bytes to improve my gun instead by increasing the random range it uses for the index a bit more. Or again, look perpendicular velocity segmentation which is still a bit out of reach. Lots of choices here. Perhaps it's time for some heavy roboresearch... --[[User:Miked0801|Miked0801]] 19:27, 20 January 2010 (UTC)<br /> <br /> Latest version I accidently bugged Fuatisha and lost 5aps on him. In addition, I removed the minor random added to the aim and lost .25 overall APS and gained back a bunch of bytes. Improved micros a ton though. Now, I'm sitting at 240 bytes and looking into its next improvement. It will cost 0 bytes to added near perfect stop'n'go, but I inherit another string table. That would give me another full overall APS though so I will probably do it. After that, it's time to look into improving aim with my extra bytes. I may finally be reaching the end of what I can do on movement alone. --[[User:Miked0801|Miked0801]] 16:32, 22 January 2010 (UTC)<br /> <br /> Added perfect stop n go with this version at the cost of 8 bytes. This, plus some TLC with some aim tables, has moved me up roughly 1 full APS in the rankings. I'm now #4 in micros and may hit #3 when things stablize - with a bugged ntc.Knowledge entry that cost me 40ish points in that battle. I also seem to have comfortably hit 2k Glicko in Nanos! Party! I'm also a hairs breath away from 2K in both rankings which would be a first. I found a new, flatter movement curve and randomized my aim a bit more on generic bots for a good overall catagory bump. The same pattern can be used to help my scores against the top micros next time around. Hopefully, no reds on the micro screen sometime in my future. Still have 4 or 5 nanos I just have a very hard time beating. I'll keep working at it though. [[Fuatisha]], you are an awesome bot. Next upload goal is 3rd in micros approaching 80 APS. We'll see if I can pull it off. --[[User:Miked0801|Miked0801]] 07:32, 27 January 2010 (UTC)<br /> <br /> Looks like 3rd in Micros is achieved. Also, this build may give me a perfect PL score in Nanos. [[Fuatisha]] is the only question mark right now. I actually found a movement pattern that confuses some of the string PM guns and gained a nice chunk off the top bots in nano land. That means next updated will be mostly concentrating on Micros to see if I can approach 81% in the Micro rumble. That will be difficult, but doable. If I get there, then I am a micro crown contendor with my silly little nano. I also have a new home computer coming online this weekend. Hopefully reobocode is 64-bit Windows 7 compatible. Should be. If so, I will have roughly 10x the computing power I have right now for roboresearch and should be able to put together a first pass on mini-bots sometime next week. If it goes smoothly, I may just setup some scripts and add all the bots just to see if I'm top 100 overall or not yet. That would be a trick. Wow this bot has come far... --[[User:Miked0801|Miked0801]] 22:51, 28 January 2010 (UTC)<br /> <br /> About 50% complete with first pass at minibot tables. I have good movement types for them all, now am porting across aim. Then, I test against distances. Then, rebuild with best distance and test. Should take another 2-3 hours. I might get to that tonight. I will also probably pass the nano/micros back through a test pass again as well, now that I have enough CPU power to do a decent pass in a couple hours as opposed to a couple of days. Next release, I will skip to 1.70 because I'll have updated roughly 20% of the tables. I have no idea where I'll land against the minis, but not top 10. Initial testing is showing just how strong the top 5 bots in that division are. --[[User:Miked0801|Miked0801]] 18:55, 2 February 2010 (UTC)<br /> <br /> Sigh - compiling with minibot data crashes the java compiler. My bot cannot get any bigger than micro with this technique. --[[User:Miked0801|Miked0801]] 05:47, 3 February 2010 (UTC)<br /> <br /> : Perhaps try a java bytecode disassembeler/assembler to hack the additional string length in? That might work to circumvent any compiler crashing unless it's a limitation inherent in the bytecode standard itself. --[[User:Rednaxela|Rednaxela]] 06:09, 3 February 2010 (UTC)<br /> <br /> Solved it! Too many character concats blowing up the compiler. How to fix? I just discovered how to put a unicode literal into a string &quot;\u008f&quot; becomes character 8f! This also has the added benefit of making many, many of my entries a much more readable single constant that I can static const final declare above. I will also be able to use a real IDE again as my current version crashes ecclipse and visual studio. Happy days for unicode literals! --[[User:Miked0801|Miked0801]] 16:20, 3 February 2010 (UTC)<br /> <br /> Learned some Java things the last few days:<br /> * \u000a, \u000c, and \u0022 (\r, \n, and &quot;), when put into a string literal, are treated as a raw symbol meaning you have to \ them or use a seperate symbol.<br /> * Non-aligned tables make for bugs that are very hard to find. Much debugging was needed to fix these bugs.<br /> * RoboResearch on broken bots doesn't help much in terms of strength judging.<br /> * The top minis are STRONG!<br /> I have 1 more day of tweaking and then an update. --[[User:Miked0801|Miked0801]] 05:26, 6 February 2010 (UTC)<br /> <br /> Chugging lots of numbers this weekend - ran roughly 100k battles over 2 days, testing ideal range from target from 100 to 380 units per opponent. The results of this tuning pass will appear as soon as I find 2 or so hours to comb through the results and adjust my range table. On average, I was getting a good 5-10% APS kick every 3rd robot or so, but I also know that with such a large update, I will accidently break a few bots as well. Still, when this pass is complete, I could be contending for micros overall. Minis - not sure where I'll land, but at least top 20. [[Fuatisha]], I may finally have a marginal (52/48) solution for, but that's too small to count on. --[[User:Miked0801|Miked0801]] 19:00, 8 February 2010 (UTC)<br /> <br /> BAH! 1.67 jar is partially corrupted so the source isn't available. Lame. It also has 10 or so bot bugs to fix. I'll get those taken care of tonight and get a new version reloaded. --[[User:Miked0801|Miked0801]] 18:16, 9 February 2010 (UTC)<br /> <br /> Just uploaded a test for initial movement vs no dodge against 0.1 bullets and yes dodge up to 3.9 power change. Also may stick to walls slightly more. I know that this helps against ram bots, but am curious if it helps elsewhere. I've also fixed the mess that was 1.67. When adding that many entries, mistakes will be made. With 1.69, I finally got 10% ahead of the nearest nano, an achievement in itself. I think I found 1 more byte in the aim code if I want to redo 1/2 the aim values. The typecast to short can be dropped if I change my negative aim values to 2*Pi - values as I'm normalizing my gun anyway. I'll do that if the intial movement change turns out decent and I want the slightly better dodging code back. Then I do another comb through for 1 more byte. Always 1 more byte :) I'm now also thining about PhoneBook, a micro bot based on the lessons this bot has taught me. I won't abuse string literals like I have with this bot as I'll have enough room to handle things more elegantly (at first!). I'm also going to make another pass through [[Infinity]] and [[DustBunny]], using my new tricks to save a ton of space. That may free up enough space for them to go on a new melee run. For fun, I've calculated what it would require to brute force the best possible bot with this technique and it would cost about (40^6 x 30 x 8 x 20 x 50 x 100) x numBots=800 x numSeasonsToGetGoodResult=10 or 7.86e20 battles run. Even at 1 battle per second, I don't think I have time to wait around for this result to appear. And this is with some culling already built in. Perhaps I'll check out JGAP or something for fun to see if a genetic algo comes up with better answers than what I've been doing. --[[User:Miked0801|Miked0801]] 22:59, 12 February 2010 (UTC)<br /> <br /> : Some rough calculation told me that even at 1000 battles/second, by the time the result appear, out sun will be White Dwarf for 2E10 year already ((7.86E20)/(86400*365*1000) - 5E9 approx. = 1.99E10, give or take leap year) --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 04:48, 13 February 2010 (UTC)<br /> <br /> Funny how taking out &quot;code improvments&quot; actually gained me between .25 and 1.0% APS in divisions. Now I'm sitting at 243 bytes with 6 bytes to spend on whatever. I also believe I may have figured out a cheap size way to get (averaged) lateral velocity segmentation in. If it works, I will be micro champion and will challenge for minis. Just need some time to see if it works - or I can go optimize some tables a bit to squeak out another 1.5% in micros and try to win that way. Either will work given some time. --[[User:Miked0801|Miked0801]] 08:16, 14 February 2010 (UTC)<br /> <br /> I've coded in average lateral velocity / distance segmenting on my local copy at the cost of only 2 bytes. I'm not happy with my data gathering method though. With simpler bots like el33tGangstar &lt;sp&gt; or [[Infinity]] or even [[spinbot]], I should be able to get a near 100% lock on rate with my gun and my test bot is currently not able to do this. I even added in a segment for acceleration/deceration/steady to see if perhaps that was the issue without luck thus far. Or am I being too perfect here? Amazingly enough, multiple segments isn't as easy as I thought it would be. Perhaps that's why there are so many different ways of doing this out there right now. If I can get my dataset cleaned up, I can test it against 10-20 bots and see how much of a difference it will make. It will fix my current weakness against multi-mode moving bots as well as make my data tables in general more efficient in space. I'll basically be trading 80% of my movement tables (which are mostly unused anyways) for additional aiming information which can be very useful. I can also explore segment size being controled via a more complex formula than e.distance() / CONSTANT to better pack my data into useful areas - with size cost being controlled. Perhaps something like a bell curve centered around 200ish distance. Perhaps even something like AmplitudeConstant * Math.sin(Math.min(e.getDistance * Constant, maxRange)). That costs around 27ish bytes so maybe I'll just stick with the original :) If I do get this to work, it means revisitng every stinking entry in the bot; AGAIN. Man that sucks --[[User:Miked0801|Miked0801]] 21:57, 16 February 2010 (UTC)<br /> <br /> It's been a while and I have been doing various experiments. I've now got my helper bot generating a profile based on acceleration, avg angular velocity, distance, and fire power. I've also calculated the math such that I have a very good idea if a particular GF bin or sets of bins actually hit the target or not. From that, I can compare the various fire power bins to get a points per tic calculation to determine what firepower is most effective at what range calculation. So, I now have a system to automate firepower at distance selection. Just that alone put into the current LBB framework would probably grab a full aps and perhaps more. But, I'll be adding an additional module to the test bot to iterate over the various movement profiles I've created. If it can alternate best movement check, best gun check, and iterate back and forth until both values agree, I've now automated most of the table creation process. Once that works, then I can use this new process to generate a set of tables for angular velocity vs distance vs firepower tables and perhaps even acceleration if I can find the code space. This of course is time consuming. Ambitious, but if successful, I'll have a very, very nice bot upgrade and a low labor path to adding all bots regardless of codesize catagory. I envision a time where adding a new bot is just a matter of running my test bot against it a few thousand times until the numbers stabilze. If I place the movement checks into an external xml or whatever table, then I have a way of adding new movement types at will without recompiling. A fully automated LBB table system. This of course could be used as a spring board for larger, more complex bots in the future. --[[User:Miked0801|Miked0801]] 18:07, 22 February 2010 (UTC)<br /> <br /> No work this last week - interest is waining and work is picking back up. I will make time in the near future to claim the micro crown though :) --[[User:Miked0801|Miked0801]] 19:15, 2 March 2010 (UTC)<br /> <br /> Work still going strong here. Interest renewing. I will get this bot to #1 micro some day when I have a few days to work on it... --[[User:Miked0801|Miked0801]] 18:57, 21 April 2010 (UTC)<br /> <br /> One work project complete, but another short timeline project started. Ugh. Still a few weeks at least until I can start thinking here again. I've got at least 5 new bots that would want to be added to my library. The there's finishing my last edit run on a new improved gun... --[[User:Miked0801|Miked0801]] 16:48, 8 June 2010 (UTC)<br /> <br /> Hooray, a new nano to the field that is strong! I look forward to seeing how far you can go Caligula! Still busy, busy at work, but still watching the action here --[[User:Miked0801|Miked0801]] 17:47, 7 September 2010 (UTC)<br /> <br /> == LBB Cheeze Factor ==<br /> <br /> I added PEZ's [[LittleEvilBrother]], because it also had a String based GF gun, I believe. There was some discussion about whether or not it was cheesy to load data for a bot not capable of saving data. Consensus at the time was that it was cheesy, but judging by how much better [[LittleBlackBook]] does, it seems like a pretty cool strategy that has a lot of room for experimentation. Plus there's been nothing new in nano-land for years! --[[User:Alcatraz|Alcatraz]] 03:09, 26 June 2009 (UTC)<br /> <br /> : I'd be of the opinion that it is cheesy, but don't object to keeping it around, at least till something particularly new happens in nano-land :) --[[User:Rednaxela|Rednaxela]] 04:26, 26 June 2009 (UTC)<br /> <br /> :: It's extremely cheesy an exploitive of a loophole in the codesize tool. Yet, I'm having some real fun with it right now (and this game is supposed to be fun! :). I literally believe I can get this bot as a top 10 in the micro competition as a nano. That's something that hasn't been done since just after we decided on weight classes. Right now, I'm still crunching a rather exhasutive set of numbers for firepower and movement types. Once that's done, I'll grab the numbers and give it a test run to see where it stands. Good chance it will go in tonight. --[[User:Miked0801|Miked0801]] 05:15, 26 June 2009 (UTC)<br /> <br /> ::: Well, I wouldn't call it &quot;exploitive of a loophole in the codesize tool&quot; exactly (unless someone makes a highly capable interpereter within nano size), since such preloading of data specific to certain bots is also cheesy for megabots. I think what's cheesey most fundumentally, is when a bot that looks up the enemy on a preloaded table based on bot names regardless of codesize. --[[User:Rednaxela|Rednaxela]] 13:11, 26 June 2009 (UTC)<br /> <br /> ::: I for one don't like this though, but it is acceptable for me. Unless, like Rednaxela, someone make a good enough nano-size compiler and fit DrussGT into nano. I'll not object, but I do think that when you fully tuned this robot to the top and have no more idea, you should retire this robot. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 13:30, 26 June 2009 (UTC)<br /> <br /> ::: Of course I agree that preloading data is kinda cheesy, but I think everyone understands that LBB is of a different ilk than other NanoBots. It's cool seeing how far you can go with it. To be honest, I think even hand-tuned segmentations are similar to pre-loading: with a different rumble population, different tunings would surely work better. We all take the rumble population into account when we write our bots; pre-loading is just a more explicit way of doing so. --[[User:Voidious|Voidious]] 14:10, 26 June 2009 (UTC)<br /> <br /> ::: Yep, it's cool to see how far LBB can go indeed. It is true that we all build our bots in way that considers the rumble population, but I don't think pre-loading itself is the cheesy thing. For one thing, I wouldn't consider it cheesy at all, if a GF gun preloads with the average data of a bunch of rumble bots, until it's learned enough about the specific enemy (hint, hint). I think tying pre-loaded data to a specific bot name is where the 'cheese' begins, but more general pre-loaded data is simply prudant rather than cheesy. --[[User:Rednaxela|Rednaxela]] 14:34, 26 June 2009 (UTC)<br /> <br /> ::: Personally, I think the only issue here is that pre-loading is used to get around the size class limits. A bot that saves its own data is fine by me, whether it's general or specific -- the 200k limit restricts how much you can really store anyway. LBB is a novel concept, but it would be disappointing to see it inspire a new generation of string table nanos/micros/minis. Now if you could make a nano that ''generates'' its own string tables, that would be really cool. You still have a few bytes left, right? ;) --[[User:Darkcanuck|Darkcanuck]] 15:02, 26 June 2009 (UTC)<br /> <br /> == AceSurf ==<br /> <br /> I noticed you make not of AceSurf being a problem. One possible solution (if you can fit it into the codesize) that would probably work well, would be having a special code in your data that says &quot;Aim at the last GF it went to&quot;. I'm kind of thinking that would probably eat too much codesize... but I think that's probably the simplest thing that could be done with the likes of AceSurf, besides random targeting anyway. --[[User:Rednaxela|Rednaxela]] 16:00, 20 June 2009 (UTC)<br /> <br /> : I'm not too worried. This bot just hit the 1900 club - the first ever in nanoland to do this. This is with untuned tables for 1/2 the bots. I will take a closer look at ace.surf results though and possibly setup alternating guess factors at every 40 pixels. This has been the best way recently to smash wave bots as it is nearly the same as 2 different guess factors every few shots. Wow I proud of this bot. I might be able to get it to the 2000 club when all is said and done. It just needs another 1000 percentage basis points or so. Plus, right after this bot was released, I figured out a way to better hit stop'n'go's without reducing accuracy against simpler bots who just get stuck. Next release will be fun! --[[User:Miked0801|Miked0801]] 16:06, 20 June 2009 (UTC)<br /> <br /> :: IIRC, The club score is base on ELO, not Glicko-2. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 16:13, 20 June 2009 (UTC)<br /> ::: then [[Toorkild]] isn't in the 2k club. I was pretty sure it was the Glicko. But, it all may be mute. I just realized how few battles it has run - only about 1 per bot. I'll therefore wait a bit before posting anything further on that :) --[[User:Miked0801|Miked0801]] 16:17, 20 June 2009 (UTC)<br /> ::: We're in a weird position with the clubs because it was based on ELO on the old server. ELO on Darkcanuck's server is way lower than it was on the old server, and Glicko-2 is a bit higher -- at least in MegaBot and MiniBot 1v1. As a point of reference, before the old RR server hit a few months of non-stop upwards drift, Dookious was about 2130 and Komarious was about 2085 in mini (prolly a few points higher now). Nevertheless, it's still easy to compare your bot to the competition, arbitrary rating systems aside. =) --[[User:Voidious|Voidious]] 16:26, 20 June 2009 (UTC)<br /> :::: The new server originally matched the old one, but ELO has drifted steadily downwards in the past few months. Why, I don't know. In late 2008, Glicko2 and ELO were in the same range, but now they're quite different. Maybe it's all the recent activity, plus some long-standing bots were removed earlier this year too. In any case, ELO is a relative ranking system so it's the difference between the scores that matters, not the absolute values. But it does leave the ELO clubs in a funny position. --[[User:Darkcanuck|Darkcanuck]] 17:34, 20 June 2009 (UTC)<br /> <br /> <br /> == Fuatisha==<br /> Well, it's nice to see that my nano is giving you so much trouble! Would you happen to have any idea why LBB seems to be having more trouble with it than other adaptive movement nanos? Of course, I wouldn't just be trying to figure out the best things to tweak in it......--[[User:CrazyBassoonist|CrazyBassoonist]] 03:34, 14 February 2010 (UTC)<br /> <br /> It's a number of things:<br /> * It really doesn't have a weakness in its good at any distance I can exploit. [[Moebius]] had a weakness at 260. <br /> * It's movement is adaptive - my gun is not. Plus it has a Very flat movement profile.<br /> * It's gun is just really, really good.<br /> * The opening stop/go movement has a signifigantly different GF profile than its later movements meaning I have to give up hit percentage later to get it out of its opening gambit.<br /> Basically, it is a better overall fighting bot than [[NeophytePattern]] and [[Moebius]], but does worse against weaker bots. If you were to tune anything, tune agaist the masses and you'll probably get #2 (and help me!) :) --[[User:Miked0801|Miked0801]] 05:27, 14 February 2010 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=Talk:LittleBlackBook&diff=16524 2010-06-08T16:48:04Z

<p>Miked0801: /* Bot Blog */</p> <hr /> <div>== Congrats! ==<br /> <br /> Congrats! It's nice to see some movement in the nano scene lately. I was pondering predefined data bots myself actually. I'm curious though, you say &quot;Any perfect dodge stop and go will kill it&quot;, which seems odd to me. It should be quite trivial for a distance/lateral segmented GF gun to hit that I'd think... --[[User:Rednaxela|Rednaxela]] 01:51, 15 June 2009 (UTC)<br /> : Math.signum() off e.velocity screws up 0 velocity checks and I have no velocity averaging. I'll check other bots for inspiration though. Has to be TINY though<br /> : What about... &lt;code&gt;static double foo = 1; foo = e.velocity + 0.01*foo; foo /= foo;&lt;/code&gt;? Not sure if that would be small enough, and I haven't checked it's codesize, but I think it's smaller than any others ways to handle that which come to my mind. I think it's smaller than &lt;code&gt;static double foo = 1; foo = (e.velocity == 0) ? foo : Math.signum(e.velocity);&lt;/code&gt; anyway, since conditionals and function calls are expensive if I remember right. I'd also suggest seeing if you can get rid of the need to normalize the value to 1/-1 all together, but that may not be possible in this case. --[[User:Rednaxela|Rednaxela]] 04:15, 15 June 2009 (UTC)<br /> :: Anything having to do with statics are expensive. Your above code is probably around 25 bytes or so. Math.signum(e.getVelocity()) is 6 or so. I can easily fix my problem by adding +1 to the e.getVelocity() check on the inside of the gun( for 2 bytes)... But! It will only hit perfect stop/go 50% of the time as it is setup to use the velocity to know how far to lead. Also, bots like FretNano who have good guns, but get stuck on walls randomly, would then be unhittable. I get 1 lead value per distance segment at the moment. I've got a few ideas on how to improve this, though it will double+ the size of my string table. I will adhere to the 200k max limit and with 1000 or so bots to profile, I have to be careful on size. --[[User:Miked0801|Miked0801]] 13:38, 15 June 2009 (UTC)<br /> <br /> Hi! Awesome results! Now that I looked at the code, I think there is one little problem with the overall concept: every time a new robot or a new version of a robot appears, you have to update the stats in your bot. --[[User:Robar|HUNRobar]] 10:31, 15 June 2009 (UTC)<br /> : And a decent problem it is. I'm going to review the string libraries today to see if I can find a &quot;closest to this name&quot; type function for my search. That'll at least handle versioning. The version in there right now is using default behavior against [[Pugio]] because my table is setup for 1.40. When all your other versions get cleared from the rumble, my rating will go up another .5 or so. --[[User:Miked0801|Miked0801]] 13:38, 15 June 2009 (UTC)<br /> :: &lt;code&gt;HashMap&lt;String, String&gt; enemyGF; enemyGF.get(e.getName().split(&quot; &quot;)[0]);&lt;/code&gt; =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 14:03, 15 June 2009 (UTC)<br /> ::: Um, wow. That does work: e.getName().split(&quot; &quot;)[0]. I rediscovered it myself and you had it here the whole time. I feel very stupid. Thanks for the advice! --[[User:Miked0801|Miked0801]] 06:13, 23 June 2009 (UTC)<br /> :::: No problem at all. =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 11:05, 23 June 2009 (UTC)<br /> <br /> Nice! I may re-release [[Ocnirp]] 1.0 to screw your stats =) Updated Wikipedia page for you now. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 12:00, 15 June 2009 (UTC)<br /> : Don't bother, I'm already using default values against that bot so it wouldn't make any difference so Nyaa Nyaa! :) --[[User:Miked0801|Miked0801]] 13:48, 15 June 2009 (UTC)<br /> :: Really? I don't think so. (default is 50-40-30-20-10-0, right?). Beside, I'm working on Nano adaptive movement (Mysterious is its fail attempt) =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 14:03, 15 June 2009 (UTC)<br /> ::: Ok, you win. There are quite a few bots taht got default cases though. For some reason I thought Ocnrip was one. And, yeah, nice string match there. I could fit that if, oh I don't know, I took out all my movement code ;) --[[User:Miked0801|Miked0801]] 14:20, 15 June 2009 (UTC)<br /> :::: That doesn't call fit, really. :P &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 14:53, 15 June 2009 (UTC)<br /> <br /> Thanks! Links and work email address removed. --[[User:Miked0801|Miked0801]] 15:27, 15 June 2009 (UTC)<br /> <br /> : He he, the revision system still have it. =) &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 15:32, 15 June 2009 (UTC)<br /> :: Yep - but at least basic spider bots won't pick it up and spam be about male enhancement products :) --[[User:Miked0801|Miked0801]]<br /> <br /> Ok, new version in the wild. I expect this release to be better against stronger bots, but I also expect some startlingly poor results against a few bots. These I can tune back to either the old values or a combo of new and old. Stelo.MirrorNano being an example. My next release will beat this bot 90/10, but now LBB is losing 45/55. No panic :) --[[User:Miked0801|Miked0801]] 02:04, 18 June 2009 (UTC)<br /> : Good result. My next update tomorrow is going to absolutely destroy the competition. This is going to be a 1900+ rating bot. --[[User:Miked0801|Miked0801]] 05:45, 18 June 2009 (UTC)<br /> <br /> == Bot Blog ==<br /> Seems like a decent place for random ramblings. The averaging code is doing its job, it just needs some table number TLC. Alas, it also screwed with some other scores that will need attention. I also commited a cut and paste errored with nat's SNG 1.0b bot resulting in a 6% score. Lame. I may try taking the averaging back out and using firepower control instead. It'd probably help me more overall to fire at 3.0 firepower at range 80 or 120 and closer against everyone. The Micro scores have been decent thus far with their first autogeneration pass. 19th is a good starting point and I know I can get to 15th or even 10th with some work there. I'll drop the mini scores in Tuesday or so and for another overall ranking boost. I still believe I can get this bot to a 2k points score with over 80%APS in nanos with a few revisits to lagging numbers.<br /> <br /> Wow, a good day. Found another 10 bytes by just re-arranging the stack vars. Used that space to try out variable move distances. Helps quite a bit against the weakest bots. Also fixed bugs with a few bots that came from typos. Finally, I fixed poorer results against rambots wehre I wasn't aiming right at range 40 and in. My scores are now approaching [[DrussGT]]'s against the low-end bots. Using that bot's scores gives me a reasonable target to short for. I'm also going to experiment with variable firepower as well, though for some reason I keep pushing back on that - dunno. Next release tomorrow night. Shooting for APS of 78ish in nanos. That would put me close to my goal of a 2k score. Hopefully, my micro score will get me top 15 there as well. I'll start running Minis by end of week to see if I can get top 25 there and perhaps top 100 overall (aiming real high, I know.) --[[User:Miked0801|Miked0801]] 03:38, 23 June 2009 (UTC)<br /> <br /> : You should to remember the [[Code Size/Cheat sheet|Code Size/Cheat sheet]]. The most important part is the vars-on-register, which is discover by Simonton I think. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 11:02, 23 June 2009 (UTC)<br /> :: I just rearrange them all until I get the smallest result :)<br /> <br /> Another good day, but I found a dumb bug I introduced to my table generation a few days ago which will require me to revisit all the nano values. Sigh. Good news though, found another 8 bytes or so by declaring the string table final (never changes so I should have done it ages ago) and by rearranging a few typecasts to make sure we got int on int math wherever possible. That means I now have both distance and firepower control in the table! It hurts by aim a touch from 80 pixels and in, but for 1 more free byte I could fix this. I'll keep looking. 8 more bytes and I get variable string matching, though if firepower or move control prove poor, I can always swap this in for the other. Because I have to do a table revisit, I'm pushing my release back one more day. Who'd have though a variable GF, variable firepower, variable move distance, variable turn control bot could be done through a silly string table. It's like the synthesis of all the best nanos in one place. Next release will have some bugs, but the one following will be absolutely epic. --[[User:Miked0801|Miked0801]] 18:48, 23 June 2009 (UTC)<br /> <br /> Bleh. Had to work late a few nights. I'm just now getting all my initial micro/nano runs complete. Good news is that only [[Moebius]] is currently able to consistantly beat me now in nanos. I'm going to experiment with distance control next as many bots are optimized for certain ranges and I expect I will do well at varying ranges against many bots. If it works well, I'll trade something off to get it. We'll see about a tomorrow release, work allowing. --[[User:Miked0801|Miked0801]] 07:39, 25 June 2009 (UTC)<br /> <br /> Played around with enemy distancing and found it helps (much) more than firepower control. But, my test cycle is too far along to scrap and start again so I'll go ahead with what I have. Besides, I believe I found a way to fit all 5 factors into this nano anyways - Fire Power, Chance to reverse direction, Min Distance to move, desired distance from enemy, and Guess Factors. It requires my tables to be created differently (again), but I'll go for that next version. This is why I haven't bothered with minis or megas yet - the tables flux dramatically with each version. It also means yet another multiplier when creating my tables. I'm already running 20+ versions per bot through roboresearch. Adding distance is another x4 or so. Yikes. Back to 1 good test run and cull, cull, cull so that I have time to balance what makes sense. At least my testing methods are improving so that this doesn't take too long. Just need 1 more set up data to finish up for the guess factors and then we'll put this bot back together again. --[[User:Miked0801|Miked0801]] 07:29, 26 June 2009 (UTC)<br /> <br /> Ok, version is up and we gained nearly another 2% APS in nanos and even more in Micros. Nice. There's still a few bots that came out a bit half baked, even with all the care I put into the tables before releasing. I'll revisit those for one last version 1.5x release and then go onto version 1.6x with distance control. Still shooting for 80+% APS, a perfect PL score in nanos, and 2k in ratings. 72 Glicko's to go. --[[User:Miked0801|Miked0801]] 02:59, 27 June 2009 (UTC)<br /> <br /> Hey, you've taken my micro's place in the microrumble! I really should do something right after I finished my flash game. ;) --[[User:Robar|HUNRobar]] 17:31, 27 June 2009 (UTC)<br /> <br /> Dang it. Screwed up robar.nano.Scytodes 0.3's table, which costed me 50-60 battle points and .33 APS in the Nano Rumble (.15 in micro). Savant values are weaker too, but that can be attributed a little to random luck. Beyond that, a very good update. Solidly in 11th now in Micros and 1.5% APS from 80 in nanos. That's only 260 battle % points and 50 of those are from my above mistake. But, without distance control, I'm running out of big gains. I can probably push this bot to 80% APS and 2k Glicko without distance, but it will take a lot of work. I made a lot of gain my swapping appropriate bots to 2.0 fire power. Some of those I can switch back to get some ground I lost between 1.52 and 1.53. I did tie for the PL score this time and would have had it if not for Scytodes. Next version I'll get it right. I think I'll release a 1.54 just to try for 10th/9th in the micros without distance help. --[[User:Miked0801|Miked0801]] 03:46, 29 June 2009 (UTC)<br /> <br /> Well fixed Scytodes and decided to alphabetize my list and lo and behold I had missed 4 other bots - all micros. Adding those gave a decent score increase for them as well and would probably challenge Jen for 10th. But, I went ahead and started the HUGE roboresearch database needed for my next release. We're talking around 1 Million battles to be run before all is ready. I'm guessing my computer running 24/7 will get through this info in around 3 days. Wow. The good news is that my previous run is compatible so I saved 150k battles or so. All this will put me over 80APS in Nanos and will put me well into top 10 in micros. I'll know for sure once I start seeing some comparison results against the micros. The top nanos appear to be weak against different ranges, but I'm not sure on Micros yet. I'll post tomorrow with some initial results. --[[User:Miked0801|Miked0801]] 21:30, 30 June 2009 (UTC)<br /> <br /> Test run about 15% complete. I'm tuning back to breadth of the first run to speed it up so I can play before next week. --[[User:Miked0801|Miked0801]] 02:18, 2 July 2009 (UTC)<br /> <br /> 33% done and I'm not patient enough to wait for it to go much further so I put together the next version - and had another awesome idea on how to make it do more for less. I now have distance control and! - all other factors also are available based on distance as well. This means variable firewpower on distance. This means I can change my move mode out of oscillation at those distances where I run into head-on shots (around 280 or so). I can even change my desired distance based on distance meaning I can ping-pong between values to help with multi-mode movers and to throw off pattern bots. That plus partial string matches and I'm sitting at exactly 249. That's enough tech for my goals. Now it's time to do my last pass through the nano/micros and see just how much pwnage will be wrought. 85+ nano APS isn't out of reach.<br /> <br /> Work, work work. My job is heating up to the point where things have been on hold for a bit. This will continue for a few more days - grr. --[[User:Miked0801|Miked0801]] 17:39, 8 July 2009 (UTC)<br /> <br /> And even more work. I'm in crunch mode now and barely have time for breathing. I've still got my next bot upgrade ready, jsut need to find a couple uninterrupted hours to fix a few minor things. I'm still alive guys :) --[[User:Miked0801|Miked0801]] 20:44, 27 August 2009 (UTC)<br /> <br /> Good to hear =) I'm also pretty snowed under, but it seems that when that happens Robocode becomes my outlet =) --[[User:Skilgannon|Skilgannon]] 20:55, 27 August 2009 (UTC)<br /> <br /> Project starting to wrap up - we'll see if life returns to normal soon... --[[User:Miked0801|Miked0801]] 16:30, 6 October 2009 (UTC)<br /> <br /> Project's done! Vacation is started. Updates to follow :) --[[User:Miked0801|Miked0801]] 16:28, 6 December 2009 (UTC)<br /> <br /> : Yay, welcome back! =) --[[User:Voidious|Voidious]] 17:18, 6 December 2009 (UTC)<br /> <br /> Ok, Nanos mostly refit. I want to find another 1.5% of APS then its back to micros. Mostly hand tuning at this point. --[[User:Miked0801|Miked0801]] 22:46, 17 December 2009 (UTC)<br /> <br /> Actually changed a little base code with this version. I removed the adjustTurnForGun() call and replaced it with a bit of randomness added to the range index. This results in slightly more random ranges when firing. It makes it easier to hit multi-modes, bullet catchers, and wave surfers, but hurts my score against really, really weak bots and the best nanos a bit. Still, seems like a decent upgrade. Broke 2 nano bot solutions with this chagne that I can easily retrofit back to pwnage. I will also be able to make a further micro pass to get above Jen on my next update. I beginning to believe that this might get top 5ish in micro before I'm done. --[[User:Miked0801|Miked0801]] 00:07, 9 January 2010 (UTC)<br /> <br /> FYI, this bot needs to be compiled with Sun's Java Compiler in order for it to remain byte size complient. Got bit with that today. Made a major pass through the tables using the top Mega bot's scores in comparison to mine for inspiration on who to fix. Found many, many bots that were improved 10% APS or more. This should be the version, barring bugs, that hits 80%APS or even 81% APS in nanos - and should also hit 2k Glicko. And there's still a bit (not much!) more tuning that can be done. There are countless ways of ordering my tables to get 1-5% individual APS tweaks that I probably need a seperate program to find. Overall, this has ben a wonderful experiment and mega contenders should take note. I'll continue to tune it a touch more, but I'm also going to investiage Lateral Velocity segmentation as well. If I get inspired, it may not cost too much :) --[[User:Miked0801|Miked0801]] 23:07, 13 January 2010 (UTC)<br /> <br /> Results looking very nice so far, though not sure if it'll quite end up getting past 2k Glicko. What I find most impressive is how you fit so many movement modes alongside a GF gun, in a nano, that's an awful lot of movement modes for a nano, particularly with the distance-based selection of them! :) --[[User:Rednaxela|Rednaxela]] 03:50, 14 January 2010 (UTC)<br /> : Thank you! I'm a rather proud parent of this bot and all comments make me grin :) --[[User:Miked0801|Miked0801]] 15:49, 14 January 2010 (UTC)<br /> <br /> BTW, the build system seems to be completely confused at the moment. Would it help if I released a 1.60 version to fix it? --[[User:Miked0801|Miked0801]] 15:49, 14 January 2010 (UTC)<br /> <br /> : What do you mean by &quot;build system&quot;? --[[User:Voidious|Voidious]] 16:24, 14 January 2010 (UTC)<br /> :: Was about to ask the same, nearly got edit conflict :) --[[User:Rednaxela|Rednaxela]] 16:33, 14 January 2010 (UTC)<br /> <br /> :: At the moment, the rumble is only running LBB 1.58 (retired), not LBB 1.59. I believe it is because 1.59 lost roughly 30ish nano battles whilst retaining the micro and up battles before I fixed an issue on my local client. I could upload the missing nano battles and that may fix it, but I wanted permission to do so first as I would need to edit the results.txt file manully to add the missing numbers. --[[User:Miked0801|Miked0801]] 17:42, 14 January 2010 (UTC)<br /> <br /> ::: &quot;... fixed an issue on my local client&quot;? Please don't edit results.txt or upload any old results! Best thing to do is delete all files in the roborumble/files and roborumble/temp folders and start fresh -- preferably with uploads disabled for the first run just to make sure. --[[User:Darkcanuck|Darkcanuck]] 21:27, 14 January 2010 (UTC)<br /> <br /> :::: Not what I did. I have 2 copies of Robo installed. I created 1.59 in version 1.6.1.4 and it was 256 bytes in size. oops. I then fixed the problem and recreated it in my other version of robocode, but stupidly called it the same thing. I then took this version and copied it to both builds. But, the codesize.txt never updated to the new, reduced size for the updated lbb. Therefore, it didn't record roughly 30ish nano battles. When i noticed this, I completely killed the cache, the local 1.59 file, and removed it from the codesize file so that it could recreate it. This worked, but those 30 or so nano battles were lost as has since confused the server quite a bit. Another side effect of this is that when you first run the client, it correctly runs version 1.59 of LBB, but further iterations always run the previous verion. Long story short, be careful about versioning of bots... --[[User:Miked0801|Miked0801]] 21:45, 14 January 2010 (UTC)<br /> <br /> :: This is weird... If you look at its roborumble details, 1.58 only has 3 battles: [http://darkcanuck.net/rumble/RatingsDetails?game=roborumble&amp;name=mld.LittleBlackBook%201.58]. Only 2 for mini, but lots for micro and nano. Not sure how that would happen... The server tries to run all pairings for each version (after a certain point), even if it's retired, so maybe that's what's going on. If you delete 1.58 from your rumble dir, it won't run 1.58 any more. (But anyone that has 1.58 will until it has all pairings, if that's the reason.) --[[User:Voidious|Voidious]] 18:51, 14 January 2010 (UTC)<br /> <br /> :: Wow... this is very weird... the &quot;Last Updated&quot; times for LittleBlackBook 1.58 keep going <br /> up in mega/mini (and different update times from mini/nano), but the battle count is only increasing in mini/nano! Something is broken on the server side I think.... because all clients with LBB 1.58 (like mine) are ONLY running LBB 1.58, but the Rumble isn't recording the mega/mini results so it looks like it'll go on forever... --[[User:Rednaxela|Rednaxela]] 19:46, 14 January 2010 (UTC)<br /> <br /> :: It should be fixed now. Looks like a concurrent retirement/reactivation. My guess is one client saw no battles for 1.58 in the last 4 hours and started to retire it, first for the general rumble then the mini. But then another client uploaded new battles (either due to old results not yet uploaded or an old priority file) while the retirements were in progress leading to the corrupted states. I have a permanent fix in mind, but it will require a lot of testing which I have yet to find time for... --[[User:Darkcanuck|Darkcanuck]] 21:27, 14 January 2010 (UTC)<br /> <br /> ::: Wow, 1.58 has 7963 battles in mega... yep... clients sure working away at it when things were messed up before... :) --[[User:Rednaxela|Rednaxela]] 03:55, 15 January 2010 (UTC)<br /> <br /> Today was a huge update! Managed to redo and find roughly 20ish more bytes!!! Desired distance from enemy table became approach angle table for a big savings. Found 2 bytes in the averaging code. Came up with a new way to do bullet detection that costs only a couple more bytes than my simple one from before. Added Ramming ability. Overall, this bot will be weaker as the dodging stuff was so tightly coupled into the random movement, but next version will keep the massive increases against the simpler, linear aim bots while improving the general movement. This bot could very well reach top 5 in Micros. I have also decided that my string tables will not exceed 200k as per the Rumble rules to make it fair. Right the tables are sitting at 100kish and won't get much bigger until I add the Minis some day. I am now awaiting the results to see which bots are now broken and need another revisit :) --[[User:Miked0801|Miked0801]] 01:33, 16 January 2010 (UTC)<br /> <br /> Tables, tables, tables. Fixed 30 or so bots thus far that I had weakened with the improved oscollation code. This put me above where I was at 1.59. I've got roughly 30 more bots to modify to get back to where 1.59 was against all bots. That's a good days work. Then, there's a revisit to change some bots from random movement back to oscollation for a nice boost. The new and improved energy detection code as made me weaker overall against PM bots. I'm working on a solution to this now. If I can find one, that's another 2APS overall or so and makes this a contender for the Micro crown. Then it would be on to the minis. Big talk though; gotta get there first! --[[User:Miked0801|Miked0801]] 19:15, 18 January 2010 (UTC)<br /> <br /> Reviewed the movement code a bit because it still felt heavy and figured out a way to do near perfect stop-n-go movement. Good enough to fool Smog 90/10. It requires a bit of table wrangling to do though so I'll wait for version 1.70 or so to do it. I've still got lots of bots to tweak before I add yet another movement mode for maybe 5% of my opponents. Actually, stop-n-go overlaps most of my current oscollator bots so I'll have to review which helps more. I could use my extra few bytes to improve my gun instead by increasing the random range it uses for the index a bit more. Or again, look perpendicular velocity segmentation which is still a bit out of reach. Lots of choices here. Perhaps it's time for some heavy roboresearch... --[[User:Miked0801|Miked0801]] 19:27, 20 January 2010 (UTC)<br /> <br /> Latest version I accidently bugged Fuatisha and lost 5aps on him. In addition, I removed the minor random added to the aim and lost .25 overall APS and gained back a bunch of bytes. Improved micros a ton though. Now, I'm sitting at 240 bytes and looking into its next improvement. It will cost 0 bytes to added near perfect stop'n'go, but I inherit another string table. That would give me another full overall APS though so I will probably do it. After that, it's time to look into improving aim with my extra bytes. I may finally be reaching the end of what I can do on movement alone. --[[User:Miked0801|Miked0801]] 16:32, 22 January 2010 (UTC)<br /> <br /> Added perfect stop n go with this version at the cost of 8 bytes. This, plus some TLC with some aim tables, has moved me up roughly 1 full APS in the rankings. I'm now #4 in micros and may hit #3 when things stablize - with a bugged ntc.Knowledge entry that cost me 40ish points in that battle. I also seem to have comfortably hit 2k Glicko in Nanos! Party! I'm also a hairs breath away from 2K in both rankings which would be a first. I found a new, flatter movement curve and randomized my aim a bit more on generic bots for a good overall catagory bump. The same pattern can be used to help my scores against the top micros next time around. Hopefully, no reds on the micro screen sometime in my future. Still have 4 or 5 nanos I just have a very hard time beating. I'll keep working at it though. [[Fuatisha]], you are an awesome bot. Next upload goal is 3rd in micros approaching 80 APS. We'll see if I can pull it off. --[[User:Miked0801|Miked0801]] 07:32, 27 January 2010 (UTC)<br /> <br /> Looks like 3rd in Micros is achieved. Also, this build may give me a perfect PL score in Nanos. [[Fuatisha]] is the only question mark right now. I actually found a movement pattern that confuses some of the string PM guns and gained a nice chunk off the top bots in nano land. That means next updated will be mostly concentrating on Micros to see if I can approach 81% in the Micro rumble. That will be difficult, but doable. If I get there, then I am a micro crown contendor with my silly little nano. I also have a new home computer coming online this weekend. Hopefully reobocode is 64-bit Windows 7 compatible. Should be. If so, I will have roughly 10x the computing power I have right now for roboresearch and should be able to put together a first pass on mini-bots sometime next week. If it goes smoothly, I may just setup some scripts and add all the bots just to see if I'm top 100 overall or not yet. That would be a trick. Wow this bot has come far... --[[User:Miked0801|Miked0801]] 22:51, 28 January 2010 (UTC)<br /> <br /> About 50% complete with first pass at minibot tables. I have good movement types for them all, now am porting across aim. Then, I test against distances. Then, rebuild with best distance and test. Should take another 2-3 hours. I might get to that tonight. I will also probably pass the nano/micros back through a test pass again as well, now that I have enough CPU power to do a decent pass in a couple hours as opposed to a couple of days. Next release, I will skip to 1.70 because I'll have updated roughly 20% of the tables. I have no idea where I'll land against the minis, but not top 10. Initial testing is showing just how strong the top 5 bots in that division are. --[[User:Miked0801|Miked0801]] 18:55, 2 February 2010 (UTC)<br /> <br /> Sigh - compiling with minibot data crashes the java compiler. My bot cannot get any bigger than micro with this technique. --[[User:Miked0801|Miked0801]] 05:47, 3 February 2010 (UTC)<br /> <br /> : Perhaps try a java bytecode disassembeler/assembler to hack the additional string length in? That might work to circumvent any compiler crashing unless it's a limitation inherent in the bytecode standard itself. --[[User:Rednaxela|Rednaxela]] 06:09, 3 February 2010 (UTC)<br /> <br /> Solved it! Too many character concats blowing up the compiler. How to fix? I just discovered how to put a unicode literal into a string &quot;\u008f&quot; becomes character 8f! This also has the added benefit of making many, many of my entries a much more readable single constant that I can static const final declare above. I will also be able to use a real IDE again as my current version crashes ecclipse and visual studio. Happy days for unicode literals! --[[User:Miked0801|Miked0801]] 16:20, 3 February 2010 (UTC)<br /> <br /> Learned some Java things the last few days:<br /> * \u000a, \u000c, and \u0022 (\r, \n, and &quot;), when put into a string literal, are treated as a raw symbol meaning you have to \ them or use a seperate symbol.<br /> * Non-aligned tables make for bugs that are very hard to find. Much debugging was needed to fix these bugs.<br /> * RoboResearch on broken bots doesn't help much in terms of strength judging.<br /> * The top minis are STRONG!<br /> I have 1 more day of tweaking and then an update. --[[User:Miked0801|Miked0801]] 05:26, 6 February 2010 (UTC)<br /> <br /> Chugging lots of numbers this weekend - ran roughly 100k battles over 2 days, testing ideal range from target from 100 to 380 units per opponent. The results of this tuning pass will appear as soon as I find 2 or so hours to comb through the results and adjust my range table. On average, I was getting a good 5-10% APS kick every 3rd robot or so, but I also know that with such a large update, I will accidently break a few bots as well. Still, when this pass is complete, I could be contending for micros overall. Minis - not sure where I'll land, but at least top 20. [[Fuatisha]], I may finally have a marginal (52/48) solution for, but that's too small to count on. --[[User:Miked0801|Miked0801]] 19:00, 8 February 2010 (UTC)<br /> <br /> BAH! 1.67 jar is partially corrupted so the source isn't available. Lame. It also has 10 or so bot bugs to fix. I'll get those taken care of tonight and get a new version reloaded. --[[User:Miked0801|Miked0801]] 18:16, 9 February 2010 (UTC)<br /> <br /> Just uploaded a test for initial movement vs no dodge against 0.1 bullets and yes dodge up to 3.9 power change. Also may stick to walls slightly more. I know that this helps against ram bots, but am curious if it helps elsewhere. I've also fixed the mess that was 1.67. When adding that many entries, mistakes will be made. With 1.69, I finally got 10% ahead of the nearest nano, an achievement in itself. I think I found 1 more byte in the aim code if I want to redo 1/2 the aim values. The typecast to short can be dropped if I change my negative aim values to 2*Pi - values as I'm normalizing my gun anyway. I'll do that if the intial movement change turns out decent and I want the slightly better dodging code back. Then I do another comb through for 1 more byte. Always 1 more byte :) I'm now also thining about PhoneBook, a micro bot based on the lessons this bot has taught me. I won't abuse string literals like I have with this bot as I'll have enough room to handle things more elegantly (at first!). I'm also going to make another pass through [[Infinity]] and [[DustBunny]], using my new tricks to save a ton of space. That may free up enough space for them to go on a new melee run. For fun, I've calculated what it would require to brute force the best possible bot with this technique and it would cost about (40^6 x 30 x 8 x 20 x 50 x 100) x numBots=800 x numSeasonsToGetGoodResult=10 or 7.86e20 battles run. Even at 1 battle per second, I don't think I have time to wait around for this result to appear. And this is with some culling already built in. Perhaps I'll check out JGAP or something for fun to see if a genetic algo comes up with better answers than what I've been doing. --[[User:Miked0801|Miked0801]] 22:59, 12 February 2010 (UTC)<br /> <br /> : Some rough calculation told me that even at 1000 battles/second, by the time the result appear, out sun will be White Dwarf for 2E10 year already ((7.86E20)/(86400*365*1000) - 5E9 approx. = 1.99E10, give or take leap year) --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 04:48, 13 February 2010 (UTC)<br /> <br /> Funny how taking out &quot;code improvments&quot; actually gained me between .25 and 1.0% APS in divisions. Now I'm sitting at 243 bytes with 6 bytes to spend on whatever. I also believe I may have figured out a cheap size way to get (averaged) lateral velocity segmentation in. If it works, I will be micro champion and will challenge for minis. Just need some time to see if it works - or I can go optimize some tables a bit to squeak out another 1.5% in micros and try to win that way. Either will work given some time. --[[User:Miked0801|Miked0801]] 08:16, 14 February 2010 (UTC)<br /> <br /> I've coded in average lateral velocity / distance segmenting on my local copy at the cost of only 2 bytes. I'm not happy with my data gathering method though. With simpler bots like el33tGangstar &lt;sp&gt; or [[Infinity]] or even [[spinbot]], I should be able to get a near 100% lock on rate with my gun and my test bot is currently not able to do this. I even added in a segment for acceleration/deceration/steady to see if perhaps that was the issue without luck thus far. Or am I being too perfect here? Amazingly enough, multiple segments isn't as easy as I thought it would be. Perhaps that's why there are so many different ways of doing this out there right now. If I can get my dataset cleaned up, I can test it against 10-20 bots and see how much of a difference it will make. It will fix my current weakness against multi-mode moving bots as well as make my data tables in general more efficient in space. I'll basically be trading 80% of my movement tables (which are mostly unused anyways) for additional aiming information which can be very useful. I can also explore segment size being controled via a more complex formula than e.distance() / CONSTANT to better pack my data into useful areas - with size cost being controlled. Perhaps something like a bell curve centered around 200ish distance. Perhaps even something like AmplitudeConstant * Math.sin(Math.min(e.getDistance * Constant, maxRange)). That costs around 27ish bytes so maybe I'll just stick with the original :) If I do get this to work, it means revisitng every stinking entry in the bot; AGAIN. Man that sucks --[[User:Miked0801|Miked0801]] 21:57, 16 February 2010 (UTC)<br /> <br /> It's been a while and I have been doing various experiments. I've now got my helper bot generating a profile based on acceleration, avg angular velocity, distance, and fire power. I've also calculated the math such that I have a very good idea if a particular GF bin or sets of bins actually hit the target or not. From that, I can compare the various fire power bins to get a points per tic calculation to determine what firepower is most effective at what range calculation. So, I now have a system to automate firepower at distance selection. Just that alone put into the current LBB framework would probably grab a full aps and perhaps more. But, I'll be adding an additional module to the test bot to iterate over the various movement profiles I've created. If it can alternate best movement check, best gun check, and iterate back and forth until both values agree, I've now automated most of the table creation process. Once that works, then I can use this new process to generate a set of tables for angular velocity vs distance vs firepower tables and perhaps even acceleration if I can find the code space. This of course is time consuming. Ambitious, but if successful, I'll have a very, very nice bot upgrade and a low labor path to adding all bots regardless of codesize catagory. I envision a time where adding a new bot is just a matter of running my test bot against it a few thousand times until the numbers stabilze. If I place the movement checks into an external xml or whatever table, then I have a way of adding new movement types at will without recompiling. A fully automated LBB table system. This of course could be used as a spring board for larger, more complex bots in the future. --[[User:Miked0801|Miked0801]] 18:07, 22 February 2010 (UTC)<br /> <br /> No work this last week - interest is waining and work is picking back up. I will make time in the near future to claim the micro crown though :) --[[User:Miked0801|Miked0801]] 19:15, 2 March 2010 (UTC)<br /> <br /> Work still going strong here. Interest renewing. I will get this bot to #1 micro some day when I have a few days to work on it... --[[User:Miked0801|Miked0801]] 18:57, 21 April 2010 (UTC)<br /> <br /> One work project complete, but another short timeline project started. Ugh. Still a few weeks at least until I can start thinking here again. I've got at least 5 new bots that would want to be added to my library. The there's finishing my last edit run on a new improved gun... --[[User:Miked0801|Miked0801]] 16:48, 8 June 2010 (UTC)<br /> <br /> == LBB Cheeze Factor ==<br /> <br /> I added PEZ's [[LittleEvilBrother]], because it also had a String based GF gun, I believe. There was some discussion about whether or not it was cheesy to load data for a bot not capable of saving data. Consensus at the time was that it was cheesy, but judging by how much better [[LittleBlackBook]] does, it seems like a pretty cool strategy that has a lot of room for experimentation. Plus there's been nothing new in nano-land for years! --[[User:Alcatraz|Alcatraz]] 03:09, 26 June 2009 (UTC)<br /> <br /> : I'd be of the opinion that it is cheesy, but don't object to keeping it around, at least till something particularly new happens in nano-land :) --[[User:Rednaxela|Rednaxela]] 04:26, 26 June 2009 (UTC)<br /> <br /> :: It's extremely cheesy an exploitive of a loophole in the codesize tool. Yet, I'm having some real fun with it right now (and this game is supposed to be fun! :). I literally believe I can get this bot as a top 10 in the micro competition as a nano. That's something that hasn't been done since just after we decided on weight classes. Right now, I'm still crunching a rather exhasutive set of numbers for firepower and movement types. Once that's done, I'll grab the numbers and give it a test run to see where it stands. Good chance it will go in tonight. --[[User:Miked0801|Miked0801]] 05:15, 26 June 2009 (UTC)<br /> <br /> ::: Well, I wouldn't call it &quot;exploitive of a loophole in the codesize tool&quot; exactly (unless someone makes a highly capable interpereter within nano size), since such preloading of data specific to certain bots is also cheesy for megabots. I think what's cheesey most fundumentally, is when a bot that looks up the enemy on a preloaded table based on bot names regardless of codesize. --[[User:Rednaxela|Rednaxela]] 13:11, 26 June 2009 (UTC)<br /> <br /> ::: I for one don't like this though, but it is acceptable for me. Unless, like Rednaxela, someone make a good enough nano-size compiler and fit DrussGT into nano. I'll not object, but I do think that when you fully tuned this robot to the top and have no more idea, you should retire this robot. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 13:30, 26 June 2009 (UTC)<br /> <br /> ::: Of course I agree that preloading data is kinda cheesy, but I think everyone understands that LBB is of a different ilk than other NanoBots. It's cool seeing how far you can go with it. To be honest, I think even hand-tuned segmentations are similar to pre-loading: with a different rumble population, different tunings would surely work better. We all take the rumble population into account when we write our bots; pre-loading is just a more explicit way of doing so. --[[User:Voidious|Voidious]] 14:10, 26 June 2009 (UTC)<br /> <br /> ::: Yep, it's cool to see how far LBB can go indeed. It is true that we all build our bots in way that considers the rumble population, but I don't think pre-loading itself is the cheesy thing. For one thing, I wouldn't consider it cheesy at all, if a GF gun preloads with the average data of a bunch of rumble bots, until it's learned enough about the specific enemy (hint, hint). I think tying pre-loaded data to a specific bot name is where the 'cheese' begins, but more general pre-loaded data is simply prudant rather than cheesy. --[[User:Rednaxela|Rednaxela]] 14:34, 26 June 2009 (UTC)<br /> <br /> ::: Personally, I think the only issue here is that pre-loading is used to get around the size class limits. A bot that saves its own data is fine by me, whether it's general or specific -- the 200k limit restricts how much you can really store anyway. LBB is a novel concept, but it would be disappointing to see it inspire a new generation of string table nanos/micros/minis. Now if you could make a nano that ''generates'' its own string tables, that would be really cool. You still have a few bytes left, right? ;) --[[User:Darkcanuck|Darkcanuck]] 15:02, 26 June 2009 (UTC)<br /> <br /> == AceSurf ==<br /> <br /> I noticed you make not of AceSurf being a problem. One possible solution (if you can fit it into the codesize) that would probably work well, would be having a special code in your data that says &quot;Aim at the last GF it went to&quot;. I'm kind of thinking that would probably eat too much codesize... but I think that's probably the simplest thing that could be done with the likes of AceSurf, besides random targeting anyway. --[[User:Rednaxela|Rednaxela]] 16:00, 20 June 2009 (UTC)<br /> <br /> : I'm not too worried. This bot just hit the 1900 club - the first ever in nanoland to do this. This is with untuned tables for 1/2 the bots. I will take a closer look at ace.surf results though and possibly setup alternating guess factors at every 40 pixels. This has been the best way recently to smash wave bots as it is nearly the same as 2 different guess factors every few shots. Wow I proud of this bot. I might be able to get it to the 2000 club when all is said and done. It just needs another 1000 percentage basis points or so. Plus, right after this bot was released, I figured out a way to better hit stop'n'go's without reducing accuracy against simpler bots who just get stuck. Next release will be fun! --[[User:Miked0801|Miked0801]] 16:06, 20 June 2009 (UTC)<br /> <br /> :: IIRC, The club score is base on ELO, not Glicko-2. &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 16:13, 20 June 2009 (UTC)<br /> ::: then [[Toorkild]] isn't in the 2k club. I was pretty sure it was the Glicko. But, it all may be mute. I just realized how few battles it has run - only about 1 per bot. I'll therefore wait a bit before posting anything further on that :) --[[User:Miked0801|Miked0801]] 16:17, 20 June 2009 (UTC)<br /> ::: We're in a weird position with the clubs because it was based on ELO on the old server. ELO on Darkcanuck's server is way lower than it was on the old server, and Glicko-2 is a bit higher -- at least in MegaBot and MiniBot 1v1. As a point of reference, before the old RR server hit a few months of non-stop upwards drift, Dookious was about 2130 and Komarious was about 2085 in mini (prolly a few points higher now). Nevertheless, it's still easy to compare your bot to the competition, arbitrary rating systems aside. =) --[[User:Voidious|Voidious]] 16:26, 20 June 2009 (UTC)<br /> :::: The new server originally matched the old one, but ELO has drifted steadily downwards in the past few months. Why, I don't know. In late 2008, Glicko2 and ELO were in the same range, but now they're quite different. Maybe it's all the recent activity, plus some long-standing bots were removed earlier this year too. In any case, ELO is a relative ranking system so it's the difference between the scores that matters, not the absolute values. But it does leave the ELO clubs in a funny position. --[[User:Darkcanuck|Darkcanuck]] 17:34, 20 June 2009 (UTC)<br /> <br /> <br /> == Fuatisha==<br /> Well, it's nice to see that my nano is giving you so much trouble! Would you happen to have any idea why LBB seems to be having more trouble with it than other adaptive movement nanos? Of course, I wouldn't just be trying to figure out the best things to tweak in it......--[[User:CrazyBassoonist|CrazyBassoonist]] 03:34, 14 February 2010 (UTC)<br /> <br /> It's a number of things:<br /> * It really doesn't have a weakness in its good at any distance I can exploit. [[Moebius]] had a weakness at 260. <br /> * It's movement is adaptive - my gun is not. Plus it has a Very flat movement profile.<br /> * It's gun is just really, really good.<br /> * The opening stop/go movement has a signifigantly different GF profile than its later movements meaning I have to give up hit percentage later to get it out of its opening gambit.<br /> Basically, it is a better overall fighting bot than [[NeophytePattern]] and [[Moebius]], but does worse against weaker bots. If you were to tune anything, tune agaist the masses and you'll probably get #2 (and help me!) :) --[[User:Miked0801|Miked0801]] 05:27, 14 February 2010 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=Talk:DustBunny&diff=16497 2010-06-04T16:39:59Z

<p>Miked0801: /* Wall Avoidance */</p> <hr /> <div>If you manage to fit that Random/Linear gun into it, will you entered it to NanoRumble (not melee)? This bot may kill the DoctorBob records!! &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 14:52, 1 June 2009 (UTC)<br /> <br /> It fits :) - I just need to find 2 more bytes to enter it into the normal rumble due to it no longer being able to call getBattleFieldWidth() and Height(). The other problem being random/linear is poor for melee - linear reduction linear is better ([[Infinity]] style.) To make it melee proof will require another 4 bytes or so. Hmmm --[[User:Miked0801|Miked0801]] 15:36, 1 June 2009 (UTC)<br /> <br /> : OMG, I found my 2 bytes. I had e.distance() cached in a register, but wasn't using it. Next release will have random linear gun with battleField sizes taken into account. Going for overall best rating next. --[[User:Miked0801|Miked0801]] 17:06, 2 June 2009 (UTC)<br /> <br /> Congrats on the Nano crowns! =) That didn't take very long. --[[User:Voidious|Voidious]] 15:45, 2 June 2009 (UTC)<br /> <br /> Great work! Number one in both... very impressive, especially in a nano! --[[User:Skilgannon|Skilgannon]] 16:10, 2 June 2009 (UTC)<br /> <br /> Good job man! --[[User:Zyx|zyx]] 20:57, 2 June 2009 (UTC)<br /> <br /> Awesome stuff! I really should try more nano and more melée --[[User:Rednaxela|Rednaxela]] 23:07, 2 June 2009 (UTC)<br /> <br /> <br /> == Wall Avoidance ==<br /> <br /> I recently saw this code from DustBunny:<br /> &lt;pre&gt;<br /> // Use a very simple running average system. /2 is as cheap as I can get this<br /> xForce = xForce *.9 - Math.sin(absoluteBearing) / distance;<br /> yForce = yForce *.9 - Math.cos(absoluteBearing) / distance;<br /> <br /> // Get our turn angle - factor in distance from each wall every time so we get<br /> // pushed towards the center when close to the walls. This took a long time to come up with.<br /> setTurnRightRadians(Utils.normalRelativeAngle(Math.atan2(xForce + 1/getX() - 1/(getBattleFieldWidth() - getX()), <br /> yForce + 1/getY() - 1/(getBattleFieldHeight() - getY()))<br /> - getHeadingRadians()) );<br /> &lt;/pre&gt;<br /> I was wondering... what's up with the 1/getX() - 1/(getBattleFieldWidth()-getX()), and the same with the Y? {{unsigned|Abalabazn}}<br /> <br /> It is a [[Anti-Gravity Movement]] system. If you want to learn about this more, I don't suggest your to learn from NanoBot, because they are obfuscated to gain as much codesize possible. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 13:06, 2 June 2010 (UTC)<br /> <br /> I completely understand the antigrav movement.<br /> I just don't get the relationship that the<br /> 1/getX and 1/getBFWidth-getX has.{{unsigned|Abalabazn}}<br /> <br /> Well, we can start with how Math.atan2 works in Robocode's coordinates. For instance:<br /> &lt;pre&gt;<br /> public double absoluteBearing(Point2D.Double target) {<br /> return Math.atan2(target.x - sourceLocation.x, target.y - sourceLocation.y);<br /> }<br /> &lt;/pre&gt;<br /> So it produces an angle based on delta x and delta y like that. <br /> <br /> In this case, &lt;code&gt;(1/getX() - 1/(getBattleFieldWidth()-getX()))&lt;/code&gt; produces a positive value if your bot's along the left wall (say, x=50), 0 near the center, and negative along the right wall. Similarly with y. Adding a positive value to the first argument of Math.atan2 will produce a more positive angle, so when you're along the left wall, you'll turn to the right. So I think this will cause a bot to turn right along the bottom and left walls, left along the right and top walls? How much it affects the turn depends on its size relative to xForce and yForce, which I'm not familiar with. But I can definitely see it as some semblance of wall avoidance that would fit in a nano. --[[User:Voidious|Voidious]] 17:31, 2 June 2010 (UTC)<br /> <br /> It is indeed wall avoidance. It doesn't work well enough though without the setMaxVelocity line which slows me down (to speed up turn rate) if I need to turn a bunch. The idea behind the &lt;code&gt;(1/getX() - 1/(getBattleFieldWidth()-getX()))&lt;/code&gt; code is to create a force to push you hard away from the edge of the board as you get close to it. There are 2 force terms being added 1/getX() positive and 1/(getBattleFieldWidth()-getX()) negative. Each of these terms gets large enough to quickly effect the overall rolling average of force as the position approaches 0 or getBattleFieldWidth(). These forces then act to push the bot back towards the center, yet as the force is a 1/x type force, it backs off very quickly as you get away from the edge. It also has a harmonic frequency unfortunately that makes DustBunyy orbit in the corner opposite of its opponent at the end of the match - a very inefficient movement pattern that gets its trounced. That's why some version add an additional random number to the mix each tic. It makes the circle larger and much less hittable at the cost of a few more wall collisions and/or closer to the center movement.<br /> <br /> I can discuss any portion of the code you'd like at length. Just ask. DustBunny is one of my favorite bots. --[[User:Miked0801|Miked0801]] 00:06, 3 June 2010 (UTC)<br /> <br /> <br /> Thanks for the detailed explanation. <br /> In these lines of code:<br /> &lt;pre&gt;<br /> Math.atan2((-5 * Math.sin(absoluteBearing) / distance) + 1/getX() - 1/(getBattleFieldWidth() - getX()), <br /> (-5 * Math.cos(absoluteBearing) / distance) + 1/getY() - 1/(getBattleFieldHeight() -getY()))<br /> - getHeadingRadians()) );<br /> <br /> and <br /> <br /> setMaxVelocity( 12 / getTurnRemainingRadians() );<br /> &lt;/pre&gt;<br /> What is the significance of -5 in the antigrav calculation, and what is the significance of 12 in the maxVelocity statement?<br /> How would changing these values affect the robot?<br /> {{unsigned|Abalabazn}}<br /> <br /> Both are somewhat arbitrary tuning values. The -5 just scales it relative to the wall-avoidance factors. If it was -1 for instance, it would avoid the walls more strongly I believe. The 12 is the attempted velocity if the remaining turn in radians is 1, but since velocity caps at 8, it only takes effect once the remaining turn is 1.5 radians or greater. The 12 basically affects how much the robot slows when doing tight turns, decrease it to make it slow down more when turning. That make sense? --[[User:Rednaxela|Rednaxela]] 05:01, 3 June 2010 (UTC)<br /> <br /> Yeah, it makes sense now. Thanks. But there still must be SOME rationale as to why you would use the exact values -5 and 12? --[[User:Abalabazn|Abalabazn]] 05:27, 3 June 2010 (UTC)<br /> <br /> The exact values? Well the general area of those numbers happens to tune the tradeoffs reasonably well I'd guess, but as for why those exact numbers.... that they're integers perhaps? Integers take less codesize which is good for restricted nanobots like DustBunny. --[[User:Rednaxela|Rednaxela]] 12:24, 3 June 2010 (UTC)<br /> <br /> -5 is cheaper than mul by 0.2 on the flip side of the ratio and 12 Rednaxela is completely correct on. They are literally trial and error numbers I've placed in there to tune behavior. The -5 turns the rolling average force to be more important than the wall pushing force. It is cheaper to multply my this constant than to use a decimal. 12 is interesting. If I make it smaller, the bot hits the walls less often because it turns quicker, but it also tends to move slower which gets it hit more often. Making it larger means it hits walls more often - especially corners, but it does better getting away from enemies as it moves faster overall. I wish there was more magical signifigance to these numbers, but they are just trial and error entries. If I get the time, I may setup a new sim where I vary these numbers across lots of battles and see if they can be slightly improved. --[[User:Miked0801|Miked0801]] 16:39, 4 June 2010 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=Talk:DustBunny&diff=16496 2010-06-04T16:39:23Z

<p>Miked0801: /* Wall Avoidance */</p> <hr /> <div>If you manage to fit that Random/Linear gun into it, will you entered it to NanoRumble (not melee)? This bot may kill the DoctorBob records!! &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 14:52, 1 June 2009 (UTC)<br /> <br /> It fits :) - I just need to find 2 more bytes to enter it into the normal rumble due to it no longer being able to call getBattleFieldWidth() and Height(). The other problem being random/linear is poor for melee - linear reduction linear is better ([[Infinity]] style.) To make it melee proof will require another 4 bytes or so. Hmmm --[[User:Miked0801|Miked0801]] 15:36, 1 June 2009 (UTC)<br /> <br /> : OMG, I found my 2 bytes. I had e.distance() cached in a register, but wasn't using it. Next release will have random linear gun with battleField sizes taken into account. Going for overall best rating next. --[[User:Miked0801|Miked0801]] 17:06, 2 June 2009 (UTC)<br /> <br /> Congrats on the Nano crowns! =) That didn't take very long. --[[User:Voidious|Voidious]] 15:45, 2 June 2009 (UTC)<br /> <br /> Great work! Number one in both... very impressive, especially in a nano! --[[User:Skilgannon|Skilgannon]] 16:10, 2 June 2009 (UTC)<br /> <br /> Good job man! --[[User:Zyx|zyx]] 20:57, 2 June 2009 (UTC)<br /> <br /> Awesome stuff! I really should try more nano and more melée --[[User:Rednaxela|Rednaxela]] 23:07, 2 June 2009 (UTC)<br /> <br /> <br /> == Wall Avoidance ==<br /> <br /> I recently saw this code from DustBunny:<br /> &lt;pre&gt;<br /> // Use a very simple running average system. /2 is as cheap as I can get this<br /> xForce = xForce *.9 - Math.sin(absoluteBearing) / distance;<br /> yForce = yForce *.9 - Math.cos(absoluteBearing) / distance;<br /> <br /> // Get our turn angle - factor in distance from each wall every time so we get<br /> // pushed towards the center when close to the walls. This took a long time to come up with.<br /> setTurnRightRadians(Utils.normalRelativeAngle(Math.atan2(xForce + 1/getX() - 1/(getBattleFieldWidth() - getX()), <br /> yForce + 1/getY() - 1/(getBattleFieldHeight() - getY()))<br /> - getHeadingRadians()) );<br /> &lt;/pre&gt;<br /> I was wondering... what's up with the 1/getX() - 1/(getBattleFieldWidth()-getX()), and the same with the Y? {{unsigned|Abalabazn}}<br /> <br /> It is a [[Anti-Gravity Movement]] system. If you want to learn about this more, I don't suggest your to learn from NanoBot, because they are obfuscated to gain as much codesize possible. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 13:06, 2 June 2010 (UTC)<br /> <br /> I completely understand the antigrav movement.<br /> I just don't get the relationship that the<br /> 1/getX and 1/getBFWidth-getX has.{{unsigned|Abalabazn}}<br /> <br /> Well, we can start with how Math.atan2 works in Robocode's coordinates. For instance:<br /> &lt;pre&gt;<br /> public double absoluteBearing(Point2D.Double target) {<br /> return Math.atan2(target.x - sourceLocation.x, target.y - sourceLocation.y);<br /> }<br /> &lt;/pre&gt;<br /> So it produces an angle based on delta x and delta y like that. <br /> <br /> In this case, &lt;code&gt;(1/getX() - 1/(getBattleFieldWidth()-getX()))&lt;/code&gt; produces a positive value if your bot's along the left wall (say, x=50), 0 near the center, and negative along the right wall. Similarly with y. Adding a positive value to the first argument of Math.atan2 will produce a more positive angle, so when you're along the left wall, you'll turn to the right. So I think this will cause a bot to turn right along the bottom and left walls, left along the right and top walls? How much it affects the turn depends on its size relative to xForce and yForce, which I'm not familiar with. But I can definitely see it as some semblance of wall avoidance that would fit in a nano. --[[User:Voidious|Voidious]] 17:31, 2 June 2010 (UTC)<br /> <br /> It is indeed wall avoidance. It doesn't work well enough though without the setMaxVelocity line which slows me down (to speed up turn rate) if I need to turn a bunch. The idea behind the &lt;code&gt;(1/getX() - 1/(getBattleFieldWidth()-getX()))&lt;/code&gt; code is to create a force to push you hard away from the edge of the board as you get close to it. There are 2 force terms being added 1/getX() positive and 1/(getBattleFieldWidth()-getX()) negative. Each of these terms gets large enough to quickly effect the overall rolling average of force as the position approaches 0 or getBattleFieldWidth(). These forces then act to push the bot back towards the center, yet as the force is a 1/x type force, it backs off very quickly as you get away from the edge. It also has a harmonic frequency unfortunately that makes DustBunyy orbit in the corner opposite of its opponent at the end of the match - a very inefficient movement pattern that gets its trounced. That's why some version add an additional random number to the mix each tic. It makes the circle larger and much less hittable at the cost of a few more wall collisions and/or closer to the center movement.<br /> <br /> I can discuss any portion of the code you'd like at length. Just ask. DustBunny is one of my favorite bots. --[[User:Miked0801|Miked0801]] 00:06, 3 June 2010 (UTC)<br /> <br /> <br /> Thanks for the detailed explanation. <br /> In these lines of code:<br /> &lt;pre&gt;<br /> Math.atan2((-5 * Math.sin(absoluteBearing) / distance) + 1/getX() - 1/(getBattleFieldWidth() - getX()), <br /> (-5 * Math.cos(absoluteBearing) / distance) + 1/getY() - 1/(getBattleFieldHeight() -getY()))<br /> - getHeadingRadians()) );<br /> <br /> and <br /> <br /> setMaxVelocity( 12 / getTurnRemainingRadians() );<br /> &lt;/pre&gt;<br /> What is the significance of -5 in the antigrav calculation, and what is the significance of 12 in the maxVelocity statement?<br /> How would changing these values affect the robot?<br /> {{unsigned|Abalabazn}}<br /> <br /> Both are somewhat arbitrary tuning values. The -5 just scales it relative to the wall-avoidance factors. If it was -1 for instance, it would avoid the walls more strongly I believe. The 12 is the attempted velocity if the remaining turn in radians is 1, but since velocity caps at 8, it only takes effect once the remaining turn is 1.5 radians or greater. The 12 basically affects how much the robot slows when doing tight turns, decrease it to make it slow down more when turning. That make sense? --[[User:Rednaxela|Rednaxela]] 05:01, 3 June 2010 (UTC)<br /> <br /> Yeah, it makes sense now. Thanks. But there still must be SOME rationale as to why you would use the exact values -5 and 12? --[[User:Abalabazn|Abalabazn]] 05:27, 3 June 2010 (UTC)<br /> <br /> The exact values? Well the general area of those numbers happens to tune the tradeoffs reasonably well I'd guess, but as for why those exact numbers.... that they're integers perhaps? Integers take less codesize which is good for restricted nanobots like DustBunny. --[[User:Rednaxela|Rednaxela]] 12:24, 3 June 2010 (UTC)<br /> <br /> -5 is cheaper than mul by 0.02 and 12 Rednaxela is completely correct on. They are literally trial and error numbers I've placed in there to tune behavior. The -5 turns the rolling average force to be more important than the wall pushing force. It is cheaper to multply my this constant than to use a decimal. 12 is interesting. If I make it smaller, the bot hits the walls less often because it turns quicker, but it also tends to move slower which gets it hit more often. Making it larger means it hits walls more often - especially corners, but it does better getting away from enemies as it moves faster overall. I wish there was more magical signifigance to these numbers, but they are just trial and error entries. If I get the time, I may setup a new sim where I vary these numbers across lots of battles and see if they can be slightly improved. --[[User:Miked0801|Miked0801]] 16:39, 4 June 2010 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=Talk:DustBunny&diff=16477 2010-06-03T00:06:09Z

<p>Miked0801: </p> <hr /> <div>If you manage to fit that Random/Linear gun into it, will you entered it to NanoRumble (not melee)? This bot may kill the DoctorBob records!! &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 14:52, 1 June 2009 (UTC)<br /> <br /> It fits :) - I just need to find 2 more bytes to enter it into the normal rumble due to it no longer being able to call getBattleFieldWidth() and Height(). The other problem being random/linear is poor for melee - linear reduction linear is better ([[Infinity]] style.) To make it melee proof will require another 4 bytes or so. Hmmm --[[User:Miked0801|Miked0801]] 15:36, 1 June 2009 (UTC)<br /> <br /> : OMG, I found my 2 bytes. I had e.distance() cached in a register, but wasn't using it. Next release will have random linear gun with battleField sizes taken into account. Going for overall best rating next. --[[User:Miked0801|Miked0801]] 17:06, 2 June 2009 (UTC)<br /> <br /> Congrats on the Nano crowns! =) That didn't take very long. --[[User:Voidious|Voidious]] 15:45, 2 June 2009 (UTC)<br /> <br /> Great work! Number one in both... very impressive, especially in a nano! --[[User:Skilgannon|Skilgannon]] 16:10, 2 June 2009 (UTC)<br /> <br /> Good job man! --[[User:Zyx|zyx]] 20:57, 2 June 2009 (UTC)<br /> <br /> Awesome stuff! I really should try more nano and more melée --[[User:Rednaxela|Rednaxela]] 23:07, 2 June 2009 (UTC)<br /> <br /> <br /> == Wall Avoidance ==<br /> <br /> I recently saw this code from DustBunny:<br /> &lt;pre&gt;<br /> // Use a very simple running average system. /2 is as cheap as I can get this<br /> xForce = xForce *.9 - Math.sin(absoluteBearing) / distance;<br /> yForce = yForce *.9 - Math.cos(absoluteBearing) / distance;<br /> <br /> // Get our turn angle - factor in distance from each wall every time so we get<br /> // pushed towards the center when close to the walls. This took a long time to come up with.<br /> setTurnRightRadians(Utils.normalRelativeAngle(Math.atan2(xForce + 1/getX() - 1/(getBattleFieldWidth() - getX()), <br /> yForce + 1/getY() - 1/(getBattleFieldHeight() - getY()))<br /> - getHeadingRadians()) );<br /> &lt;/pre&gt;<br /> I was wondering... what's up with the 1/getX() - 1/(getBattleFieldWidth()-getX()), and the same with the Y? {{unsigned|Abalabazn}}<br /> <br /> It is a [[Anti-Gravity Movement]] system. If you want to learn about this more, I don't suggest your to learn from NanoBot, because they are obfuscated to gain as much codesize possible. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 13:06, 2 June 2010 (UTC)<br /> <br /> I completely understand the antigrav movement.<br /> I just don't get the relationship that the<br /> 1/getX and 1/getBFWidth-getX has.{{unsigned|Abalabazn}}<br /> <br /> Well, we can start with how Math.atan2 works in Robocode's coordinates. For instance:<br /> &lt;pre&gt;<br /> public double absoluteBearing(Point2D.Double target) {<br /> return Math.atan2(target.x - sourceLocation.x, target.y - sourceLocation.y);<br /> }<br /> &lt;/pre&gt;<br /> So it produces an angle based on delta x and delta y like that. <br /> <br /> In this case, &lt;code&gt;(1/getX() - 1/(getBattleFieldWidth()-getX()))&lt;/code&gt; produces a positive value if your bot's along the left wall (say, x=50), 0 near the center, and negative along the right wall. Similarly with y. Adding a positive value to the first argument of Math.atan2 will produce a more positive angle, so when you're along the left wall, you'll turn to the right. So I think this will cause a bot to turn right along the bottom and left walls, left along the right and top walls? How much it affects the turn depends on its size relative to xForce and yForce, which I'm not familiar with. But I can definitely see it as some semblance of wall avoidance that would fit in a nano. --[[User:Voidious|Voidious]] 17:31, 2 June 2010 (UTC)<br /> <br /> It is indeed wall avoidance. It doesn't work well enough though without the setMaxVelocity line which slows me down (to speed up turn rate) if I need to turn a bunch. The idea behind the &lt;code&gt;(1/getX() - 1/(getBattleFieldWidth()-getX()))&lt;/code&gt; code is to create a force to push you hard away from the edge of the board as you get close to it. There are 2 force terms being added 1/getX() positive and 1/(getBattleFieldWidth()-getX()) negative. Each of these terms gets large enough to quickly effect the overall rolling average of force as the position approaches 0 or getBattleFieldWidth(). These forces then act to push the bot back towards the center, yet as the force is a 1/x type force, it backs off very quickly as you get away from the edge. It also has a harmonic frequency unfortunately that makes DustBunyy orbit in the corner opposite of its opponent at the end of the match - a very inefficient movement pattern that gets its trounced. That's why some version add an additional random number to the mix each tic. It makes the circle larger and much less hittable at the cost of a few more wall collisions and/or closer to the center movement.<br /> <br /> I can discuss any portion of the code you'd like at length. Just ask. DustBunny is one of my favorite bots. --[[User:Miked0801|Miked0801]] 00:06, 3 June 2010 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=Talk:DustBunny&diff=16476 2010-06-02T23:53:17Z

<p>Miked0801: </p> <hr /> <div>If you manage to fit that Random/Linear gun into it, will you entered it to NanoRumble (not melee)? This bot may kill the DoctorBob records!! &amp;raquo; &lt;span style=&quot;font-size:0.9em;color:darkgreen;&quot;&gt;[[User:Nat|Nat]] | [[User_talk:Nat|Talk]]&lt;/span&gt; &amp;raquo; 14:52, 1 June 2009 (UTC)<br /> <br /> It fits :) - I just need to find 2 more bytes to enter it into the normal rumble due to it no longer being able to call getBattleFieldWidth() and Height(). The other problem being random/linear is poor for melee - linear reduction linear is better ([[Infinity]] style.) To make it melee proof will require another 4 bytes or so. Hmmm --[[User:Miked0801|Miked0801]] 15:36, 1 June 2009 (UTC)<br /> <br /> : OMG, I found my 2 bytes. I had e.distance() cached in a register, but wasn't using it. Next release will have random linear gun with battleField sizes taken into account. Going for overall best rating next. --[[User:Miked0801|Miked0801]] 17:06, 2 June 2009 (UTC)<br /> <br /> Congrats on the Nano crowns! =) That didn't take very long. --[[User:Voidious|Voidious]] 15:45, 2 June 2009 (UTC)<br /> <br /> Great work! Number one in both... very impressive, especially in a nano! --[[User:Skilgannon|Skilgannon]] 16:10, 2 June 2009 (UTC)<br /> <br /> Good job man! --[[User:Zyx|zyx]] 20:57, 2 June 2009 (UTC)<br /> <br /> Awesome stuff! I really should try more nano and more melée --[[User:Rednaxela|Rednaxela]] 23:07, 2 June 2009 (UTC)<br /> <br /> <br /> == Wall Avoidance ==<br /> <br /> I recently saw this code from DustBunny:<br /> &lt;pre&gt;<br /> // Use a very simple running average system. /2 is as cheap as I can get this<br /> xForce = xForce *.9 - Math.sin(absoluteBearing) / distance;<br /> yForce = yForce *.9 - Math.cos(absoluteBearing) / distance;<br /> <br /> // Get our turn angle - factor in distance from each wall every time so we get<br /> // pushed towards the center when close to the walls. This took a long time to come up with.<br /> setTurnRightRadians(Utils.normalRelativeAngle(Math.atan2(xForce + 1/getX() - 1/(getBattleFieldWidth() - getX()), <br /> yForce + 1/getY() - 1/(getBattleFieldHeight() - getY()))<br /> - getHeadingRadians()) );<br /> &lt;/pre&gt;<br /> I was wondering... what's up with the 1/getX() - 1/(getBattleFieldWidth()-getX()), and the same with the Y? {{unsigned|Abalabazn}}<br /> <br /> It is a [[Anti-Gravity Movement]] system. If you want to learn about this more, I don't suggest your to learn from NanoBot, because they are obfuscated to gain as much codesize possible. --[[User:Nat|&lt;span style=&quot;color:#099;&quot;&gt;Nat&lt;/span&gt;]] [[User talk:Nat|&lt;span style=&quot;color:#0a5;&quot;&gt;Pavasant&lt;/span&gt;]] 13:06, 2 June 2010 (UTC)<br /> <br /> I completely understand the antigrav movement.<br /> I just don't get the relationship that the<br /> 1/getX and 1/getBFWidth-getX has.{{unsigned|Abalabazn}}<br /> <br /> Well, we can start with how Math.atan2 works in Robocode's coordinates. For instance:<br /> &lt;pre&gt;<br /> public double absoluteBearing(Point2D.Double target) {<br /> return Math.atan2(target.x - sourceLocation.x, target.y - sourceLocation.y);<br /> }<br /> &lt;/pre&gt;<br /> So it produces an angle based on delta x and delta y like that. <br /> <br /> In this case, &lt;code&gt;(1/getX() - 1/(getBattleFieldWidth()-getX()))&lt;/code&gt; produces a positive value if your bot's along the left wall (say, x=50), 0 near the center, and negative along the right wall. Similarly with y. Adding a positive value to the first argument of Math.atan2 will produce a more positive angle, so when you're along the left wall, you'll turn to the right. So I think this will cause a bot to turn right along the bottom and left walls, left along the right and top walls? How much it affects the turn depends on its size relative to xForce and yForce, which I'm not familiar with. But I can definitely see it as some semblance of wall avoidance that would fit in a nano. --[[User:Voidious|Voidious]] 17:31, 2 June 2010 (UTC)<br /> <br /> It is indeed wall avoidance. It doesn't work well enough though without the setMaxVelocity line which slows me down (to speed up turn rate) if I need to turn a bunch. --[[User:Miked0801|Miked0801]] 23:53, 2 June 2010 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=Talk:Anarchy&diff=16362 2010-05-24T15:18:12Z

<p>Miked0801: </p> <hr /> <div>Head on Targeting will not get you far at all in Nano land anymore. Even with awesome movement, there are too many bots that know how to stop and go dodge head on targeting and prevent you from scoring. Same for straight linear targeting. Then again, it depends on what you are trying to accomplish. The best RAM bots use head on gun targeting, but linear leading for Ramming purposes :) --[[User:Miked0801|Miked0801]] 15:16, 24 May 2010 (UTC)<br /> <br /> Doh! Didn't realize this was a melee specialist. I take back most of what I said. HOT targeting can work in melee as long as you are firing at either very close or very, very far range. Then it's just a matter of not getting stuck in the middle and getting destroyed by corner bots or Doctor Bob. --[[User:Miked0801|Miked0801]] 15:18, 24 May 2010 (UTC)</div>

Miked0801 http://robowiki.net/w/index.php?title=Talk:Anarchy&diff=16361 2010-05-24T15:16:03Z

<p>Miked0801: Quick comment for you</p> <hr /> <div>Head on Targeting will not get you far at all in Nano land anymore. Even with awesome movement, there are too many bots that know how to stop and go dodge head on targeting and prevent you from scoring. Same for straight linear targeting. Then again, it depends on what you are trying to accomplish. The best RAM bots use head on gun targeting, but linear leading for Ramming purposes :) --[[User:Miked0801|Miked0801]] 15:16, 24 May 2010 (UTC)</div>

Miked0801