Client java version

Jump to navigation Jump to search

I do not think that above report indicates that MoxieBot is broken. Actually, the log indicates that the bot was working and was reporting sensible things. The part about 

SYSTEM: ncj.MoxieBot 1.0 has died

is due to its logic: MoxieBot does not fire when there are no bullets in the air. If the other bot runs out of energy, then they both wait and robocode gives an energy penalty kick after certain "no fire" timeout. Eventually they both killed by penalty energy drain, which is reported as "has died".

I played MoxieBot in the GUI it gives similar log entry while it is moving and firing.

Beaming (talk)‎01:31, 5 September 2017

You do not have permission to edit this page, for the following reasons:

  • The action you have requested is limited to users in the group: Users.
  • You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

You can view and copy the source of this page.

Return to Thread:Talk:RoboRumble/Client java version/reply (36).

Edited by author.
Last edit: 04:44, 5 September 2017

Yep. This is what I see as well. It seems to be a bug in the MoxieBot logic. Not in the robocode.

By the way ThreadDeath is also there. Looks like I need to try java7 or earlier and see if ThreadDeath related losses are there.

Beaming (talk)‎04:37, 5 September 2017

I also checked the historical robocode 1.8.3, MoxieBot has the same buggy behaviour.

Beaming (talk)‎04:41, 5 September 2017
 
 
 
Retrieved from "http://robowiki.net/wiki/Thread:Talk:RoboRumble/Client_java_version/reply_(32)#Client_java_version_5573"