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

Arty on the run

Devster

New Member
Joined
Jun 23, 2012
Messages
34
Reaction score
0
Whats up with the bot thinking SPG is a light tanks, running ahead and suiciding?
My AMX 13 F3 AM just rushed enemy spawn point on Sand River. Seriously??
 
bump this thread, because arty botting seems doesn't work anymore.
 
Looking into it.

Edit: I couldn't find the culprit. Does this only happen on higher tier artillery vehicles, only french ones, etc?
 
Last edited:
Just tested with Lorr 155 50 on El Halluf (standard) and it started rushing for hill. Screenshot attached.


I'll check with a non-french SPG soon.



EDIT: btw, does the bot need LoS when playing SPG?

shot_006.webp
 
Last edited:
Tested with Hummel.
Abbey seemed ok. Camped not too far from spawn point, but it still drove a bit too far in my opinion.


Then Sand River came up....

shot_007.webp
 
Thanks, that indicates an issue with the artillery camp points for that map rather than anything else. Also, no, artillery does not require line of sight in order to fire; wouldn't be very effective if it did. :p
 
Also, no, artillery does not require line of sight in order to fire; wouldn't be very effective if it did. :p

I've had several occasions where the bot (when playing SPG) just aims, without firing. Does TL's targeting mode have any influence on this behaviour? Or was the target simply behind cover?
 
I've had several occasions where the bot (when playing SPG) just aims, without firing. Does TL's targeting mode have any influence on this behaviour? Or was the target simply behind cover?

While artillery doesn't require line of sight on the target in order to fire at it, the marker (the circle when you aim) needs to be within a certain dispersion tolerance before it will fire. Similar, battle tanks won't fire if they can't hit the dead center of the enemy tank. It's a way to make sure your tank doesn't go around wasting shells on things it can't hit; better be safe than sorry is what we figured.
 
Yeah I figured it was something like that :)

Thanks for the replies! :)
 
Nah the bot does that on any tier arty. Im grinding my Hummel so I have a grille to get exp with, and it keeps playing suicidal as well.
 
Nah the bot does that on any tier arty. Im grinding my Hummel so I have a grille to get exp with, and it keeps playing suicidal as well.

If you could give me the name of the map and the game mode, I could update those maps for you.
 
почему арта стреляет без shift почему так? как исправить? плохо работает арта...
 
what arty dosent work? I have leveled up to su-8 now without any problem!?
 
did go bananas and suicided rushed on Elenberg (spelling?) like the tank was going to a WP on the other team side :D
Tank SU-8
se log;

[22:38:45.803] [Debug] Refreshing garage vehicles..
[22:56:35.787] [Debug] CheckForCaptcha concluded, no challenge.
[22:56:35.810] [Debug] Refreshing garage vehicles..
[22:56:47.633] [Debug] GetProfileBytesAsync called.
[22:56:47.633] [Debug] Invoking GetProfileBytes.
[22:56:47.633] [Debug] Callback registered.
[22:56:47.633] [Debug] GetProfileBytes invoked.
[22:56:47.893] [Debug] Callback reached.
[22:56:47.893] [Debug] Finishing invoke.
[22:56:47.893] [Debug] Result size: 68
[22:56:47.893] [Debug] Throwing event.
[22:56:47.893] [Debug] Loading profile.
[22:56:47.894] [Debug] OnProfileLoaded caught! Done!
[22:57:26.815] [Debug] Moving to: <314.3208, 13.41294, -23.40953>
[22:57:26.823] [Debug] Creating operation.
[22:57:26.823] [Debug] Invoking GetServerPath.
[22:57:26.823] [Debug] Callback registered.
[22:57:26.823] [Debug] Waiting for callback..
[22:57:26.823] [Debug] Generated path to <314.3208, 13.41294, -23.40953> in 277,10 ms
[22:57:26.906] [Debug] Moving to: <314.3208, 13.41294, -23.40953>
[22:57:27.278] [Debug] Callback hit.
[22:57:27.278] [Debug] Ending Invoke on GetServerPath.
[22:57:27.278] [Debug] Invoke ended. Result: <Start: (<65.15312, 1.799871, -385.1044>) / End: (<314.3208, 13.41294, -23.40953>)>
[22:57:27.278] [Debug] Unlocking sync lock.
[22:57:27.278] [Debug] Sync locked: False
[22:57:27.278] [Debug] Throwing event.
[22:57:27.278] [Debug] Setting CurrentPath.
[22:57:27.278] [Debug] CurrentPath: <Start: (<65.15312, 1.799871, -385.1044>) / End: (<314.3208, 13.41294, -23.40953>)>
[22:57:27.278] [Debug] OnPathGenerated fetched! Path generation done!
[22:57:27.342] [Debug] Moving to: <314.3208, 13.41294, -23.40953>


-----
Normal log
22:56:35.072] Queue priority: (0) SPGs SU-8, (1) Tank Destroyers SU-100, (2) Medium Tank T-43,
[22:56:35.805] Status: Queueing
[22:56:35.805] New state: Queueing
[22:56:35.997] Queueing for battle with with SPGs SU-8.
[22:56:47.902] Waiting for players.
[22:56:47.913] Status: WaitingForPlayers
[22:56:47.913] New state: WaitingForPlayers
[22:56:47.987] Waiting for players.
[22:56:56.723] Waiting for battle to start.
[22:56:56.737] Status: WaitingForGameStart
[22:56:56.737] New state: WaitingForGameStart
[22:56:56.813] Waiting for battle to start.
[22:57:26.747] Artillery waypoint set to <314.3208, 13.41294, -23.40953>!
[22:57:26.823] Moving to artillery spot <314.3208, 13.41294, -23.40953>
[22:57:26.852] Status: Moving
[22:57:26.852] New state: Moving
[22:57:26.910] Moving to artillery spot <314.3208, 13.41294, -23.40953>
[22:58:35.943] Status: Aiming
[22:58:35.943] New state: Aiming
[22:58:47.492] Fire!
[22:58:47.539] Status: Firing
[22:58:47.539] New state: Firing
[22:58:47.948] Fire!
[22:58:49.221] Status: Dead
[22:58:49.221] New state: Dead
[22:58:49.227] Kills: 0
[22:58:49.239] We're dead! Leaving battle!
 
Arty doesn't use "Artillery View" when botting, because of the way WoT works.

Indeed, artillery view is the same as "not in game", as you're watching the game from above, which is a different entity in the game. While you're in this view, the game engine says you're not in game, and TankLeader interprets that as if you're dead. Nothing we can do about it.
 
Back
Top