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

TankLeader 2.0.280.136

Aevitas

Well-Known Member
Joined
Mar 2, 2010
Messages
2,307
Reaction score
36
This thread elaborates on some of the changes in the latest version of TankLeader more in-depth than the changelog does.

There's been a couple of nasty bugs that have been fixed in the last two releases, I'll explain those below and explain what has changed and why.

Aimbot mode has been completely reworked. It was a hackish mess which didn't work reliably, the latest changes have changed the way the bot behaves when it is in aimbot mode, and it should now work every single time you enable it and press start. Whenever you enable it the bot won't queue and won't drive for you, but it'll keep shooting for you if it can find a target to hit. Do note that this requires a direct line of sight with the enemy, so sniping cupolas and turrets won't happen; though you can still do that yourself.

Pressing start after adding vehicles to your queue should no longer cause TankLeader to crash and forcing you to restart. The same goes for adding a bunch of vehicles to your queue, TankLeader should now just queue up as normal.

Keep the gun pointing forwards has been removed from the UI until we properly implement the functionality to support it. It was previously disabled as in you couldn't check the checkbox, but for now I've hidden it from the UI entirely.

Leaving battle after death should now work properly as well, though in certain rare circumstances the game prevents us from actually leaving, I'm looking into that further.

CPU intensity should be lowered a fair bit. Note that TankLeader is actually CPU intensive as is the nature of the bot, there's no real way around that, but we're tweaking and optimizing it as good as we can.

Thanks for your precious feedback regarding these bugs, they have enabled us to actually trace them and properly address them.
 
Keep the gun pointing forwards has been removed from the UI until we properly implement the functionality to support it. It was previously disabled as in you couldn't check the checkbox, but for now I've hidden it from the UI entirely.

We need this back! It makes the bot so obvious when the turret is pointing behind while its moving forward at the start of the match.
 
Bot not work. How disable [Aimbot]? I click "Start" and:

[09:34:40.609 N] Initialisation completed. Have fun!
[09:35:31.765 D] Start/Stop button clicked!
[09:35:31.781 N] Starting the bot!
[09:35:31.843 D] Added new hook [Death] e4613fed-7e0b-480b-a8cd-0d9af030337b
[09:35:31.843 D] Added new hook [PreBattle] a396e142-c1ad-4e60-b05e-72b0520ced2f
[09:35:31.843 D] Added new hook [Battle] e499c894-43e3-4fb8-92dd-a2d316392708
[09:35:31.843 D] Added new hook [AfterBattle] 82c78721-cc73-442c-8911-bea72a24ffda
[09:35:31.859 D] Replaced hook [GameBehaviour] bc681260-268d-4c3e-afe5-4ce7078330b7
[09:35:31.875 D] Replaced hook [GarageBehaviour] d59a420b-7f4d-41fb-a98a-c62fbb4a1b54
[09:35:31.875 N] Loading custom profiles...
[09:35:31.875 N] [ProfileManager] Reloading profiles from disk.
[09:35:50.234 N] Finished loading profiles; found 31 profiles in total.
[09:35:50.406 N] Profiles loaded. 31 custom profiles found.
[09:35:50.406 N] [Aimbot] Starting the bot in Aimbot mode; you'll need to manually queue up and drive, and the bot does the shooting.
[09:35:50.406 D] Replaced hook [GarageBehaviour] 852e9ddb-4f40-4903-be63-e02f6f702cf7
[09:35:50.406 D] [Routine] Current routine changed to Aimbot Routine.
[09:35:50.406 N] [Aimbot] Enabled, driving is done by the player, TankLeader handles combat.
[09:35:50.406 N] [Targeting] Provider changed to Default Targeting
[09:35:50.484 D] ObjectiveManager cleared.
[09:35:50.484 N] Stuck Provider changed to Default Obstacle Targeting.
[09:35:50.484 N] Poi set to None. Reason: Starting up.
[09:35:50.531 N] Attempting to connect to the server.
[09:35:50.640 D] Successfully connected to remote host.
[09:37:04.546 D] Start/Stop button clicked!
[09:37:04.546 N] Waiting for ExecutionState to become available for BotMain.Stop.
[09:37:04.656 N] Stopping the bot! Remote client requested stopping the bot.
[09:37:04.656 N] Poi set to None. Reason: The bot was stopped.
[09:37:04.671 D] All hooks cleared!
[09:37:06.578 N] Gracefully shutting down..

how to start?
 
Aimbot mode has been completely reworked. It was a hackish mess which didn't work reliably, the latest changes have changed the way the bot behaves when it is in aimbot mode, and it should now work every single time you enable it and press start. Whenever you enable it the bot won't queue and won't drive for you, but it'll keep shooting for you if it can find a target to hit. Do note that this requires a direct line of sight with the enemy, so sniping cupolas and turrets won't happen; though you can still do that yourself.

I still dont understand that aimbot mode its not usefull in high tier battles not usefull at low tier battles it just automaticly lock on target but you can do that by your self
 
Back
Top