Thread history

From RoboWiki
From Talk:RoboRumble/Participants/Melee
Viewing a history listing
Jump to: navigation, search
descTime User Activity Comment
16:56, 16 August 2017Beaming (Talk | contribs)New reply created (Reply to apc.Caan 1.0)
09:41, 16 August 2017Cb (Talk | contribs)New reply created (Reply to apc.Caan 1.0)
19:17, 15 August 2017Beaming (Talk | contribs)New reply created (Reply to apc.Caan 1.0)
21:06, 14 August 2017Cb (Talk | contribs)New thread created 

Has anybody else noticed the strange results of Caan, especially when you look at the KNNPBI scores? https://literumble.appspot.com/BotDetails?game=meleerumble&name=apc.Caan%201.0&order=KNNPBI

It seems like it depends on who executes the battles. If I let Caan fight some melee battles on my computer, it is a relatively strong bot, but in the meleerumble it has 15.40 APS? Maybe it depends on the Java version? Maybe on other computers Caan just doesn't move at all and dies?

I would like to fix this because the rankings are distorted by this issue and a single bot can make a big difference if you are fighting for every APS point ;)

Cb (talk)21:06, 14 August 2017

I am not sure that we can put this bot to a strong category. I looked at a few battles with it. It has worse hit rate than HawkOnFire with its head on targeting. Also, its motion does not look strong as well. However, it might perform well against several bots if its gun somehow tuned to hit them, than KNNPBI would be abnormal.

Beaming (talk)19:17, 15 August 2017

Yes, it is a mediocre bot. When I put it in a battle with some random bots, it usually ends up somewhere in the middle. But in the rumble Caan has 15.22 APS, which makes him the third worst bot in total, just before SittingDuck and WasteOfAmmo. This can't be right.

Furthermore, if you order Caan's scores by number of battles (like this), you see that those high KNNPBI scores only happen with new bots with less than 50 battles.

This means that in a lot of old battles Caan was probably disabled and didn't move at all like a sitting duck, whereas in new battles it performs normally.

Cb (talk)09:41, 16 August 2017

I see now.

While ago back, when java switched from version 6 to 7, this bot was probably compiled with java 7, and whoever ran battles (very likely me, since I was mainly the only rumbles runner for a couple of years) probably used 6. In this case, such bot was disabled.

We about to experience it again with java switching from 7 to 8.

Maybe Skilgannon can somehow check not only the rumble client version but also the java's jdk version at the LiteRumble server side.

Beaming (talk)16:56, 16 August 2017
 
 
 
Personal tools