Hello everyone, we talked about bots and now, we talked about what they can do and today, we will have a look at how they can screw you. This replay came from St0rmshadow and shows a typical situation, but with a twist. But let’s start first with getting the tools you are going to need to fight this. Tools of the Trade You will need the Freecam tool. It is a mod, that allows you to use free camera in replays (and ONLY in replays). Yes, this is legal. Without it, you won’t be able to see the botting behavior. You can get it here: http://www.ulozto.net/xJP6mdPh/avatar-input-handler-xml Installation – simple: just copy the file you downloaded into your World of Tanks\res_mods\0.8.10\Gui folder (it’s possible there is no Gui folder in the 0.8.10 folder, in such a case just create it) How to operate it – it’s very simple: - start the replay - wait for the countdown to finish (!) - press left mouse button once to “unlock” the camera - press CAPS+F3 to activate the free camera mod - control free camera with classic WSAD, mouse wheel changes your “altitude” 2 Bots, 1 Cup Battle Okay, now for the replay – you can download it here. So, what do we have here: Dramatis personae: Rostam_ (Churchill III) – a Tankleader bot EYESOFNIGHT (KV-1) – a Tankleader bot That’s right – there are TWO FUCKING BOTS on ONE team on TWO highest tiers. When you look at the replay, you can follow either of them around. Both of them get killed early in the battle (no surprise there), screwing the entire team in the process – still think a bot is a good idea? How do you recognize them as bots? - a very telling is the “gun drop” when they move. Basically, until he “finds a target” a bot just aims into the ground and drives around like that. As soon as he loses the target (and doesn’t switch to any other target), the gun goes back down into the “idle” position - very twitchy turret movement (notice that on the KV-1) - very specific movement pattern – notice, how when the bot runs into an obstacle, he immediately reverses, traverses the hull a bit and goes forward, when he runs into the obstacle again, he repeats it. It can be illustrated by this picture: St0rmshadow said, regarding this replay: “KV-1 starts with a gundrop, that is typical for the Tankleader bot. Be aware though – gundrop might not always mean it’s a bot, it can happen during disconnects also, but it is usually a bot sign, especially when the bot is moving. Just to clarify: a gundrop is when the battle starts and the gun immediately goes to its maximum depression. Shortly after, he rammed a teammate and very typical Tankleader bot behavior happens: the bot backs down a few meters, rotates the hull by 30 degrees to the side and starts moving forward again. If he runs into an obstacle once more, it does the same thing again. After that, the bot stays in the forest for a while, as if AFK – after that, he suddenly drives into the field for no reason, its gun is pointed always in the same direction. It doesn’t react until it has a clear line of view of its target, that is another typical sign of a Tankleader bot. It doesn’t even react on being shot – a human player would try to take cover, or would at least turn its turret to face the enemy. The second bot (ROSTAM_) has exactly the same signs of being a bot. In this case, the problem is the bot drove out of the rendering distance.” There you have it. Two bots, one battle, same team. Either the guy who submitted it was extremely unlucky, or the problem is much worse than Wargaming claims. You be the judge of that…

More...