Thread history

Seems something is wrong, ScalarN is suddenly first in mini, micro and nano rumble ! And ofcourse second in roborumble, which in itself is quite an accomplishment.

Just removed ScalarN d.160

The only related change in d.160 is experimenting lambda expressions

And it seems that codesize.jar cannot analyze bots with lambda expressions and returning non-valid results

We should disable 1.9.3.3 and wait for codesize fix along with my melee pairing fix.

I submitted an issue: https://github.com/robo-code/codesize/issues/3

The codesize utility currently uses BCEL 5.2 which cannot handle Java 6, 7, 8 features properly. And the roborumble client has a logical bug that treats codesize calc failure as codesize 0 and allowing it to participant in even nano. The correct logic should be treating codesize calc failure as infinity, only allowing it to participant in MegaRumble.

I will definitely have to fix codesize as I have not touched it for many years. :O

Also notice that it will be faster to write to me a mail at fnl (at) users.sourceforge.net in order to have me fix as many issues related to RoboRumble as possible (this has a high priority to me). Just tell me to look on this discussion, if all details are already provided. This way you'll not have to wait for me updating Robocode, Codesize, RoboRumble etc. :-) And thank you for providing me with patches for RoboRumble. It is a great help to all of us.

Thanks for the contact info ;) And it is my pleasure to help as well.

Codesize 1.2 for Java 7, 8, 9 (Experimental) is ready.

Do we need to fix other stuff for RoboRumble before I make another release?

Sure, the meleerumble pairing algorithm also needs a fix. I’ll send you a patch then.

The melee pairing fix is now fully tested and available as a pull request:

https://github.com/robo-code/robocode/pull/13

discussions:

http://robowiki.net/wiki/Thread:Talk:RoboRumble/Upgrade_client_version/reply_(2)