Client java version

Jump to navigation Jump to search

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 (32).

In the log above, there are 25 lines of "Hit by a wave that was not being correctly tracked", indicating MoxieBot losing energy. That would be consistent with MoxieBot stalling and MyFirstRobot getting a 100% hitrate on it. MyFirstRobot fires 1.0 power bullets, which cause 4.0 damage, and 100 / 4 = 25 hits to kill = 25 log messages.

I also made a video of MoxieBot vs. TrackFire on that computer. It stalls for 2 rounds, but works on the other 8. It doesn't seem so bad when not minimized.

I wonder if the bug is that MoxieBot loses its radar lock and cannot regain it, which wouldn't be that hard of a fix...

MultiplyByZer0 (talk)‎02:37, 5 September 2017
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"