What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Feedback + Bug Report

KayJay

New Member
Joined
Oct 16, 2014
Messages
3
Reaction score
0
Hi guys,

First things first: currently TankLeader is unusable, because it simply doesn't work for a couple of maps (see below). This will get you banned eventually.

But actually I really like your product. I'm a software developer myself and I can see how much effort you put into this. All the complex stuff like process injection etc. works flawlessly, so it's a bit hard to understand, why those tiny bugs prevent TankLeader from being a decent bot.

I've started using TL a few days ago and just let it run. Observed a few games, everything seemed to run well. But later on I got logged out of WoT twice ("spam protection") and also observed a few "disciplinary afk penalties" (those pop-ups will disappear once the bot starts the next battle), which made me curious. So I've watched TL playing and noticed that the bot just sits at spawn and does nothing for a few maps.

It's pretty hard to observe all issues while playing random battles, so I've tried to use TL in a training room (together with my primary account) and it actually worked! Nice touch! ;)

So I've spent almost a day playing all 65 maps for both teams (130+ battles). Guess this is worth a life time TL subscription. ;)

These are the results, ordered from "unacceptable, will cause ban" to "don't care too much". All of these tests are perfectly reproducible (and also observable in random battles).

Unacceptable, will cause ban:
"47_canada_a" (regular battle)
Bot sits at spawn and does nothing (team 1).​
"83_kharkiv" (regular battle)
Bot sits at spawn and does nothing (team 1+2).​
"84_winter" (regular battle)
Bot sits at spawn and does nothing (team 1+2).​
"86_himmelsdorf_winter" (regular battle)
Bot sits at spawn and does nothing (team 1+2).​

For working maps the log usually shows:
[Objectives] Found 2 objective(s) for map 1413463521.
Poi set to Objective. Reason: Moving to complete objective

But for above maps "Poi set to Objective. Reason: Moving to complete objective" is missing. Tried to create custom profiles for above maps, but they don't work either. Profiles work fine for other maps though.

Can live with these, but bot behaviour will be spotted by other players:
"01_karelia" (regular battle)
Bot missed cap point by a few meters (team 1+2).​
"02_malinovka" (regular battle)
Bot missed cap point by a few meters (team 1).​
"10_hills" (regular battle)
Bot missed cap point by a few meters (team 1).​
"11_murovanka" (regular battle)
Stupid objective (missed cap completely) (team 1+2).​
"14_siegfried_line" (regular battle)
Bot missed cap point by a few meters (team 1).​
"15_komarin" (regular battle)
Tank gets stuck by an obstacle (team 1+2).​
"22_slough" (regular battle)
Bot missed cap point by a few meters (team 1).​
"31_airfield" (regular battle)
Bot missed cap point by a few meters (team 2).​
"33_fjord" (regular battle)
Bot missed cap point by a few meters (team 1).​
"39_crimea" (regular battle)
Bot missed cap point by a few meters (team 2).​
"43_north_america" (regular battle)
Bot missed cap point by a few meters (team 1+2).​
"53_japan" (regular battle)
Bot missed cap point by a few meters (team 1+2).​
"63_tundra" (regular battle)
Bot missed cap point by a few meters (team 1+2).​
"73_asia_korea" (regular battle)
Bot missed cap point by a few meters (team 1).​
"85_winter" (regular battle)
Bot missed cap point by a few meters (team 1).​

Don't care too much (because encounter battles can be disabled):
"02_malinovka" (encounter battle)
Stupid objective (missed cap completely) (team 1+2).​
"04_himmelsdorf" (encounter battle)
Stupid objective (missed cap completely) (team 1+2).​
"05_prohorovka" (encounter battle)
Stupid objective (missed cap completely) (team 1+2).​
"06_ensk" (encounter battle)
Stupid objective (missed cap completely) (team 1+2).​
"07_lakeville" (encounter battle)
Stupid objective (missed cap completely) (team 1+2).​
"08_ruinberg" (encounter battle)
Stupid objective (missed cap completely) (team 1+2).​
"10_hills" (encounter battle)
Stupid objective (missed cap completely) (team 1+2).​
"11_murovanka" (encounter battle)
Stupid objective (missed cap completely) (team 1+2).​
"14_siegfried_line" (encounter battle)
Stupid objective (missed cap completely) (team 1+2).​
"28_desert" (encounter battle)
Stupid objective (missed cap completely) (team 1+2).​
"29_el_hallouf" (encounter battle)
Stupid objective (missed cap completely) (team 1+2).​
"34_redshire" (encounter battle)
Stupid objective (missed cap completely) (team 1+2).​
"35_steppes" (encounter battle)
Stupid objective (missed cap completely) (team 1+2).​
"73_asia_korea" (encounter battle)
Stupid objective (missed cap completely) (team 1+2).​
"86_himmelsdorf_winter" (encounter battle)
Bot sits at spawn and does nothing (team 1+2).​
"87_ruinberg_on_fire" (encounter battle)
Stupid objective (missed cap completely) (team 1+2).​
"96_prohorovka_defense" (regular battle)
Bot does some stupid 360s in the middle of the map (team 1+2). Were you drunk when doing the way points? ;)
"96_prohorovka_defense" (encounter battle)
Bot sits at spawn and does nothing (team 1+2).​

Of course I also have the logs (diagnostic) for all games played. Let me know if you need them.

Looking forward to seeing at least those crucial bugs getting fixed!

-- KayJay
 
Hi guys,

First things first: currently TankLeader is unusable, because it simply doesn't work for a couple of maps (see below). This will get you banned eventually.

But actually I really like your product. I'm a software developer myself and I can see how much effort you put into this. All the complex stuff like process injection etc. works flawlessly, so it's a bit hard to understand, why those tiny bugs prevent TankLeader from being a decent bot.

~snip~

Of course I also have the logs (diagnostic) for all games played. Let me know if you need them.

Looking forward to seeing at least those crucial bugs getting fixed!

-- KayJay

It's actually interesting to see that the bot isn't picking up objectives on those maps. That's something that'll need looking into. As for the bot missing the cap by a few meters, that may have to do with the precision or with WarGaming actually changing stuff around on their end. Thanks for the report, and the log wouldn't hurt.
 
It's actually interesting to see that the bot isn't picking up objectives on those maps. That's something that'll need looking into.

Thanks for the swift response.

I've just replayed the 4 maps and the good news is that "47_canada_a" (team 1) is actually working. Don't know what happened the first time.

But for the other 3 maps it's the same result as before.

Here's the log:
View attachment 2014-10-21 23.52.txt

As for the bot missing the cap by a few meters, that may have to do with the precision or with WarGaming actually changing stuff around on their end.

All right, but don't you think that you should be changing stuff around your end when WarGaming is changing stuff around their end? ;)

-- KayJay
 
First things first: currently TankLeader is unusable, because it simply doesn't work for a couple of maps (see below). This will get you banned eventually.

Today my account got suspended for 14 days. Last game was 13 days ago.

@Aevitas
Any news on the reported map bugs?

-- KayJay
 
Back
Top