The Number 1 Problem: Disconnection (often)

[vampayne]

Yes, tankleader may be very buggy but it is still usable and worth the price in my opinion. Your tank may afk in base once in a while but it resumes after the match ends or when you are dead. Yes your tank may not shoot perfectly (what do u expect from a bot). Yes, your tank may be stuck in front of a steep slope or a kerb/wall but it resumes normal functioning after that particular match ends. I think people are wasting their energy by focusing their complains on the wrong stuff.

The number 1 problem I faced is disconnection!! There are three kinds of disconnection.
First also the rarest, the game, WOT client disappear/closes automatically.
Second, you were transferred to the login screen with a normal you-have-been-disconnected pop up message.
Third, you were transferred to the login screen with "Protection from multiple "client-server" calls" pop up message.

I had never experienced disconnection when playing the game for a long period (whole day) with my hands instead of using a bot.
Disconnection happens very frequently, from my experience, about 70%. Leaving the bot on for 10 nights, you will get about 7 disconnections out of the 10 nights.

For example, Tankleader bot for 1 hour after you left your computer on for 10 hours really sucks. What's the point of botting when you have to sit in front of your computer in case of disconnection?

I hope the staffs can solve this great problem and have lots of customers. Thank you.

 

[Aevitas]

I'll add some throttling to the tank selection process. It could slow it down, but it will most likely reduce the amount of disconnects. Hit me up with your Skype in a PM and you can test it if you want to.

 

[vampayne]

From my experience, the weird thing was, once you were not disconnected for the first few hours, your bot session is safe from disconnection until you restart the bot.
For example, you bot for 3 hours without disconnection, most probably you can continue the bot session for another 10 hours without disconnection. Hence, every time when I intended to bot for long hours (say 10 hours), I will run the bot early and check on the bot during the first few hours to make sure that there was no disconnection. This may be a solution to my disconnection problem. Not 100% sure though.

Changing the amount of tanks in the garage and the wait time between queueing for battles do not seem to help.

A tip for new user: The start button can only be used once most probably. To start your botting again, close the program (tankleader) and start the program again.

 

[vampayne]

Tankleader seriously need auto login. Botting often end up doing nothing at the login screen of WOT client.

Left the bot for 10 hours yesterday and it bots for 1 hour. wth

 

[flairdevil]

Bump for "still an issue!"

Ongoing complaint all over the forums. One Dev said its not related to the bot, one Dev is looking at how to fix it. Time will tell. I was entertaining making an AutoIT script that clicked the <OK> button location to get rid of the the Clent-Server error message then the <Login> button, and have it cycle once every 30 minutes, so at WORST you would be down for like a half hour. lol

FOr the most part I agree with the OP, it's a little rough around the edges, and worth the money - absolutely! But, it really does need some love, and it could actually turn into a money maker for them. Right now lots of people get scared off by all the bad press it gets. It's all the little things, like for instance.... Firing. It locks on, fires its first shot. Reloads, Sits there like a potato. If the bot is locked onto something it should be SPAMMING THE SHIT out of the fire button.... just like we would be doing. I know, I know if it cannot see the entore tank it won't shoot. Screw that. Let her spam her heart out and the accuracy will take care of the rest. Hell at least its SHOOTING lol.... #1way to kill this bot? Just shot it your turret hull down. It will just stare at you lolz Ive done it. ;-)

~Flair

 

[Aevitas]

Bump for "still an issue!"

Ongoing complaint all over the forums. One Dev said its not related to the bot, one Dev is looking at how to fix it. Time will tell. I was entertaining making an AutoIT script that clicked the <OK> button location to get rid of the the Clent-Server error message then the <Login> button, and have it cycle once every 30 minutes, so at WORST you would be down for like a half hour. lol

It is actually a game thing, but the bot definitely has a part in it. I'm looking into adding a "slow mode" option for TankLeader to see if the problem still occurs when TL takes a chill pill and doesn't query the game as often. However, that'll greatly reduce the overall speed the bot queues up with, leaves battles, etc.

 

[Gigaflat]

The disconnection problem is related to the speed of the PC.

My i7 runs TL2 without any problem (probably 1 disconnection per 24hrs).

My Pentium IV disconnects every 20min.


On my Pentium IV, I increased the "Time to wait between battles" from 5sec to 15sec and for the time being there is no more disconnects (still testing).

One more thing: always run without any mods (I rename my 0.9.1 mods directory and create an empty 0.9.1 and, I rename the xvm directory) and with minimum graphics.

 

[vampayne]

Pretty sure pc speed is not my problem. My CPU can handle WoT and TL2 with little effort. Unless you are saying my computer is too fast/good and causing the disconnection. When I'm in front of my computer, my computer is running WoT, TL2, Hearthstone, Hearthbuddy, Google Chrome 20 tabs or web pages and Injustice: Gods Among Us. I do not experience any lag when I ran 3 games together + some random stuff.

 

[Gigaflat]

Interesting!

I am having lost connections on my Pentium IV because the hard disk is too slow.

In your case, it may be the handling of the network card or your router?

On my i7 I am running only WOT (without mods, min graphics) and the only disconnection I experience is if WOT reset their server.

So, I am pretty sure that it is the PC that may cause the problem but, it may as well be the handling of the network traffic by your router/gateway. Do you have a cheap router?

Easy way to test this would be running only WOT & TL for a few hours and see if disconnections continue.