bott will always leave battle once your tank is destroyed no matter if winning or losing. The bot's sole purpose is to spam battles as quickly as possible to farm exp/credits not improve battle performance and stats
[BETA] TankLeaderBETA - With new navigation
- Thread starter Aevitas
- Start date
bott will always leave battle once your tank is destroyed no matter if winning or losing. The bot's sole purpose is to spam battles as quickly as possible to farm exp/credits not improve battle performance and stats
Aevitas
Well-Known Member
- Joined
- Mar 2, 2010
- Messages
- 2,307
- Reaction score
- 36
I've just released a beta update which introduces a new way of doing the entire waypoint thing, and it should actually move out of the base and work towards completing the objective. Let me know how it works out, and if you run into any problems!
ska51
New Member
- Joined
- Jun 14, 2010
- Messages
- 26
- Reaction score
- 0
Started a match with a KV-1S, but halfway trough TL disconnected. Last message in the LOG says "[16:15:00.041] Tank: Light Tank AMX 13 75 - Kills: 0" before it crashed:
Code:
[16:12:26.260] Queueing for battle with with Heavy Tank KV-1S.
[16:12:40.695] [Debug] Obtaining waypoints for team 1 on 33_fjord.
[16:12:40.745] [Debug] Received waypoint: TankLeader.Waypoint
[16:12:40.786] Waiting for players.
[16:12:40.800] Status: WaitingForPlayers
[16:12:40.800] New state: WaitingForPlayers
[16:12:40.864] Waiting for players.
[16:12:46.848] Waiting for battle to start.
[16:12:46.860] Status: WaitingForGameStart
[16:12:46.860] New state: WaitingForGameStart
[16:12:46.943] Waiting for battle to start.
[16:13:16.885] New Objective: Search and destroy!
[16:13:16.885] [Debug] Hotspot changed! Previous: <-430.372, 73.68882, 137.0987> - New: <177.3365, 7.695407, -52.26821> - Expiry: 00:01:16
[16:13:16.887] [Debug] Moving to: <177.3365, 7.695407, -52.26821>
[16:13:16.938] Status: Moving
[16:13:16.938] New state: Moving
[16:13:16.974] [Debug] Generated path to <177.3365, 7.695407, -52.26821> in 58.07 ms
[16:13:16.991] [Debug] Moving to: <177.3365, 7.695407, -52.26821>
[16:13:26.102] [Debug] Generated path to <177.3365, 7.695407, -52.26821> in 65.17 ms
[16:13:26.155] [Debug] Moving to: <177.3365, 7.695407, -52.26821>
[16:13:35.118] [Debug] Generated path to <177.3365, 7.695407, -52.26821> in 54.34 ms
[16:13:35.212] [Debug] Moving to: <177.3365, 7.695407, -52.26821>
[16:13:35.990] Status: Camping
[16:13:35.990] New state: Camping
[16:13:36.041] New Objective: Search and destroy!
[16:13:36.041] [Debug] Hotspot changed! Previous: <177.3365, 7.695407, -52.26821> - New: <-366.0083, 0.04844693, 90.51399> - Expiry: 00:01:16
[16:13:36.043] [Debug] Moving to: <-366.0083, 0.04844693, 90.51399>
[16:13:36.056] Status: Moving
[16:13:36.056] New state: Moving
[16:13:38.164] [Debug] Generated path to <-366.0083, 0.04844693, 90.51399> in 62.67 ms
[16:13:38.166] [Debug] Moving to: <-366.0083, 0.04844693, 90.51399>
[16:13:47.257] [Debug] Generated path to <-366.0083, 0.04844693, 90.51399> in 64.88 ms
[16:13:47.267] [Debug] Moving to: <-366.0083, 0.04844693, 90.51399>
[16:13:56.369] [Debug] Generated path to <-366.0083, 0.04844693, 90.51399> in 58.88 ms
[16:13:56.423] [Debug] Moving to: <-366.0083, 0.04844693, 90.51399>
[16:14:01.189] We're stuck! Attempting unstuck maneuvre at <126.3094, 10.34237, -35.26707>.
[16:14:01.210] Status: Stuck
[16:14:01.210] New state: Stuck
[16:14:14.236] Status: Moving
[16:14:14.236] New state: Moving
[16:14:14.288] [Debug] Generated path to <-366.0083, 0.04844693, 90.51399> in 59.62 ms
[16:14:14.295] [Debug] Moving to: <-366.0083, 0.04844693, 90.51399>
[16:14:23.395] [Debug] Generated path to <-366.0083, 0.04844693, 90.51399> in 69.55 ms
[16:14:23.406] [Debug] Moving to: <-366.0083, 0.04844693, 90.51399>
[16:14:27.691] [Debug] Generated path to <-366.0083, 0.04844693, 90.51399> in 55.91 ms
[16:14:27.745] [Debug] Moving to: <-366.0083, 0.04844693, 90.51399>
[16:14:30.747] [Debug] Generated path to <-366.0083, 0.04844693, 90.51399> in 59.36 ms
[16:14:30.755] [Debug] Moving to: <-366.0083, 0.04844693, 90.51399>
[16:14:33.785] [Debug] Generated path to <-366.0083, 0.04844693, 90.51399> in 62.13 ms
[16:14:33.797] [Debug] Moving to: <-366.0083, 0.04844693, 90.51399>
[16:14:36.814] [Debug] Generated path to <-366.0083, 0.04844693, 90.51399> in 70.94 ms
[16:14:36.909] [Debug] Moving to: <-366.0083, 0.04844693, 90.51399>
[16:14:39.888] [Debug] Generated path to <-366.0083, 0.04844693, 90.51399> in 55.91 ms
[16:14:39.897] [Debug] Moving to: <-366.0083, 0.04844693, 90.51399>
[16:14:42.929] [Debug] Generated path to <-366.0083, 0.04844693, 90.51399> in 63.09 ms
[16:14:42.936] [Debug] Moving to: <-366.0083, 0.04844693, 90.51399>
[16:14:45.954] [Debug] Generated path to <-366.0083, 0.04844693, 90.51399> in 58.25 ms
[16:14:45.963] [Debug] Moving to: <-366.0083, 0.04844693, 90.51399>
[16:14:49.015] [Debug] Generated path to <-366.0083, 0.04844693, 90.51399> in 67.54 ms
[16:14:49.017] [Debug] Moving to: <-366.0083, 0.04844693, 90.51399>
[16:14:52.071] [Debug] Generated path to <-366.0083, 0.04844693, 90.51399> in 59.66 ms
[16:14:52.078] New Objective: Search and destroy!
[16:14:52.078] [Debug] Hotspot changed! Previous: <-366.0083, 0.04844693, 90.51399> - New: <42.73141, 6.685561, -73.99716> - Expiry: 00:01:16
[16:14:52.080] [Debug] Moving to: <42.73141, 6.685561, -73.99716>
[16:14:55.144] [Debug] Generated path to <42.73141, 6.685561, -73.99716> in 65.25 ms
[16:14:55.146] [Debug] Moving to: <42.73141, 6.685561, -73.99716>
[16:14:58.230] [Debug] Generated path to <42.73141, 6.685561, -73.99716> in 60.11 ms
[16:14:58.247] [Debug] Moving to: <42.73141, 6.685561, -73.99716>
[16:15:00.041] Tank: Light Tank AMX 13 75 - Kills: 0
[16:15:00.041] ErrorMay I suggest everyone setup the wait 20 to 30 seconds before moving from base so everyone dont bump into each other. Also can you put the options for waiting 5, 10,15,20 seconds before moving? Bc if you sit there for 20 to 30 seconds people may report you for being idle and once reported they cant take it back when you move.
_Hausi
New Member
- Joined
- Jan 15, 2010
- Messages
- 691
- Reaction score
- 0
Nice idea /vote
Aevitas
Well-Known Member
- Joined
- Mar 2, 2010
- Messages
- 2,307
- Reaction score
- 36
Aevitas
Well-Known Member
- Joined
- Mar 2, 2010
- Messages
- 2,307
- Reaction score
- 36
Should be all good again.
(latest beta) stopped moving all together.. doesnt see the fight started anymore.. ie says queing, when i die it ques for the next etc.. no action anymore
_Hausi
New Member
- Joined
- Jan 15, 2010
- Messages
- 691
- Reaction score
- 0
"Running" fine but behavior is really ugly. There is alot to do for let this bot looks human like.
Had some freezes ingame, but cant say thats the bot.
What can i (we) do to help you, to get it fast stable and smooth?
Pp.s.: Which targeting is your favorite? Ive tried many, but there often mad. Tank zig zags between the targets :-(
Had some freezes ingame, but cant say thats the bot.
What can i (we) do to help you, to get it fast stable and smooth?
Pp.s.: Which targeting is your favorite? Ive tried many, but there often mad. Tank zig zags between the targets :-(
Last edited:
ska51
New Member
- Joined
- Jun 14, 2010
- Messages
- 26
- Reaction score
- 0
It would really help me if you would put a version index/list on the main post of this topic, so we know when it's updated. That information now seems scattered over several posts.
Code:
[16:49:41.404] [Debug] Moving to: <176, 1.692035, 176>
[16:49:44.499] [Debug] Could not generate path to <0, 0, 0> (@ FindPath)
[16:49:44.504] [Debug] Moving to: <176, 1.692035, 176>
[16:49:47.602] [Debug] Could not generate path to <0, 0, 0> (@ FindPath)
[16:49:47.621] [Debug] Moving to: <176, 1.692035, 176>
[16:49:50.691] [Debug] Could not generate path to <0, 0, 0> (@ FindPath)
[16:49:50.711] [Debug] Moving to: <176, 1.692035, 176>
[16:49:53.780] [Debug] Could not generate path to <0, 0, 0> (@ FindPath)
[16:49:53.794] [Debug] Moving to: <176, 1.692035, 176>
[16:49:56.840] [Debug] Could not generate path to <0, 0, 0> (@ FindPath)
[16:49:56.853] [Debug] Moving to: <176, 1.692035, 176>thats why it does not move..