All, Been seeing more frequent crashes on the RebornBuddy bot while running ExFateBot and OrderBot. Attached is the most recent log running ExFateBot when I was fate grinding. It appears before the crash I get "too many packets sent". Not sure what that means. Please assist. Thank you in advance!
Looks like it's the usual flying crash due to object collision with EnableFlight. This is where you can see that something went wrong in your log: Code: [17:01:02.137 V] [FlightNav] Moving to next hop: <-535.8045, 193.7974, 204.0768> (Moving to fate) D: 6.493577 [17:01:02.435 V] [FlightNav] Moving to next hop: <-540.1885, 192.2935, 199.6365> (Moving to fate) D: 6.963018 [17:01:02.761 V] [FlightNav] Moving to next hop: <-544.5724, 190.5441, 195.1962> (Moving to fate) D: 6.999569 [17:01:03.106 V] [FlightNav] Moving to next hop: <-548.9564, 188.5592, 190.7558> (Moving to fate) D: 6.543608 [17:01:03.435 V] [FlightNav] Moving to next hop: <-553.3404, 186.3504, 186.3155> (Moving to fate) D: 6.585804 [17:01:03.731 V] [FlightNav] Moving to next hop: <-557.7244, 183.9301, 181.8752> (Moving to fate) D: 7.360249 [17:01:04.096 V] [FlightNav] Moving to next hop: <-562.1083, 181.3119, 177.4349> (Moving to fate) D: 6.818413 [17:01:04.436 V] [FlightNav] Moving to next hop: <-566.4923, 178.5105, 172.9946> (Moving to fate) D: 6.868016 [17:01:04.764 V] [FlightNav] Moving to next hop: <-570.8763, 175.5414, 168.5543> (Moving to fate) D: 7.200677 [17:01:05.102 V] [FlightNav] Moving to next hop: <-575.2603, 172.421, 164.114> (Moving to fate) D: 7.479609 [17:01:05.138 N] [FlightNav] Collision detected! Generating new path! [17:01:05.160 D] Requesting path on 399 from <-571.2393, 175.3701, 168.1866> to <-605.9482, 147.8599, 133.0317> [17:01:05.225 D] Generated path to <-605.9482, 147.8599, 133.0317> in 00:00:00.0647731 ms [17:01:05.594 D] Finished checking gear in 00:00:00.0016835 [17:01:06.634 D] Moving to next hop: <-588.5856, 170.3661, 163.2297> (Moving to fate) D: 6.616094 [17:01:07.293 D] Navigation reached current destination. Within 41.58434 [17:01:07.339 D] Requesting path on 399 from <-588.4584, 170.3118, 163.1845> to <-605.9482, 147.8599, 133.0317> [17:01:07.421 D] Generated path to <-605.9482, 147.8599, 133.0317> in 00:00:00.0820612 ms [17:01:07.664 D] Navigation reached current destination. Within 41.3008 [17:01:07.699 D] Requesting path on 399 from <-587.2511, 170.2544, 162.2969> to <-605.9482, 147.8599, 133.0317> [17:01:07.760 D] Generated path to <-605.9482, 147.8599, 133.0317> in 00:00:00.0606628 ms [17:01:07.764 D] Navigation reached current destination. Within 41.35821 [17:01:07.805 D] Requesting path on 399 from <-586.453, 170.3153, 161.8332> to <-605.9482, 147.8599, 133.0317> [17:01:07.864 D] Generated path to <-605.9482, 147.8599, 133.0317> in 00:00:00.0589394 ms [17:01:07.871 D] Moving to next hop: <-586.3134, 170.3661, 161.6659> (Moving to fate) D: 0.3527279 [17:01:07.894 D] Navigation reached current destination. Within 41.37668 If you don't catch this pretty much immediately, it will lead to an RB crash when you've been kicked from the nav server due to the request spam. If your game client is recoverable from the RB crash, that does help and you just need to fire up RB again. Here's a quick list of steps to take if you catch the issue before RB closes when your game client changes to Not Responding while flying: Press Stop in the RB window => Wait for RB to stop => Close RB Ctrl + Alt + Del => Task Manager Wait until the game client responds again. You may get a 90k error for being d/c'd - if not, just land manually away from obstacles or TP to a nearby Aetheryte. If you did get d/c'd, log back into your character - if you get a 5k error when trying to log back in, the game client will close and you will need to start it again and log in to your character. Start RB => Select your CR (if applicable) => Press Start in the RB window
