Quick issue while Reopening BPs+ctrl

[joraanpe]

Heya, lately ive found one of my makers dying oftern but could not really spot the reason as it used to happen by Serversave, but i think ive finally found why.

The relogger basically logs you back, sets targetting, cavebot etc off untill he is able to re-open all backpacks and then activate all the engines back, this doesnt use to take more than 10 seconds....
but sometimes seems like it gets stuck trying to open the next backpack, showing the open next container windows but not performing any action, just stuck there (the one you get when do ctrl+click over container to open/look etc)........ Then it never opens the needed amount of bps and there for doesnt reactivate engines. Also if im not wrong, nowdays the bot doesnt try to use any pots if they are not visible, right? so there it goes.

Here are some screen shots i got that could help over there:







If there is any practical solution on my side that could be implemented, would be appreciated as well.

[Lucas Terra]

Thanks. I will work on it.

[BUgWT]

For now,

use "confirm menu"

[Lucas Terra]

Can you paste the results of the Debug Log?

[joraanpe]

I though the issue was fixed with update 1.2.8 but seems like it persist, happened last night again in one of my mcs, once again by serversave si i wasnt able to get any debug message or whatever... by other side i was using 1.2.8, havent had it updated at that moment, duno if u had made any improvements related to this on that version.

[Lucas Terra]

No, there's no improvements related to this in 1.2.9.
I still need your Debug Console messages to try to figure it out. And I need as much details as you can get. So enable the "Details" checkbox and "Debug Events". You can disable "HUDs" and "Navigation".

[joraanpe]

Ok ill try to keep this on at all my bots to see what can we catch. Do i need to keep debug consoles open to allow them keep tracking or does it continue working even if closed after enabling?


Also by other side, i just opened the bot to run these tests, just loaded the script, activated the console and manually loed char out to "try to force" the issue, obviusly didnt work, but happened that old issue i told you about the other day that "freezes" the options in the bot, do you remember? The console kept track of all the actions, dunno if it provides you any usefull info related to this case of the freeze but ill post here as well just in case. Here it is:


13:54:17.447 a General INFO Render Time: 1.724970 ms, Update Time: 0.390193 ms 13:55:15.414 Event 1 issued. Type: Connect, Connect
13:55:15.414 Event 1 started.
13:55:15.414 Event step changed to 13.
13:55:15.414 Pressed 13 1 1
13:55:15.616 Released 13 1 1
13:55:16.222 Event step changed to 10.
13:55:16.648 Event 1 ended with status code 1 at step 10.
13:55:16.666 Event 2 issued. Type: Close Windows, Type:
13:55:16.666 Event 2 started.
13:55:16.666 Event step changed to 5.
13:55:16.666 Event 2 ended with status code 1 at step 5.
13:55:16.688 Event 3 issued. Type: Open Item, ItemId: 2854
13:55:16.688 Event 3 started.
13:55:16.688 Event step changed to 1.
13:55:17.060 Event step changed to 3.
13:55:17.248 Event step changed to 9.
13:55:17.248 Event 3 finished successfully.
13:55:18.160 Event 4 issued. Type: Open Item, ItemId: 5949
13:55:18.161 Event 4 started.
13:55:18.161 Event step changed to 1.
13:55:18.307 Event step changed to 5.
13:55:18.307 Pressed 162 1 1
13:55:18.448 Event step changed to 4.
13:55:18.591 Released 162 1 1
13:55:18.603 Event step changed to 7.
13:55:18.747 Event step changed to 8.
13:55:18.879 Event step changed to 9.
13:55:18.879 Event 4 finished successfully.
13:55:19.419 Event 5 issued. Type: Close Windows, Type:
13:55:19.420 Event 5 started.
13:55:19.420 Event step changed to 1.
13:55:19.657 Event step changed to 2.
13:55:19.775 Event step changed to 3.
13:55:19.879 Event step changed to 4.
13:55:20.001 Event step changed to 1.
13:55:20.155 Event step changed to 2.
13:55:20.276 Event step changed to 3.
13:55:20.384 Event step changed to 4.
13:55:20.513 Event step changed to 5.
13:55:20.513 Event 5 ended with status code 1 at step 5.
13:55:20.535 Event 6 issued. Type: Open Item, ItemId: 7342
13:55:20.536 Event 6 started.
13:55:20.536 Event step changed to 1.
13:55:20.644 Event step changed to 5.
13:55:20.644 Pressed 162 1 1
13:55:20.788 Event step changed to 4.
13:55:20.910 Event step changed to 7.
13:55:20.927 Released 162 1 1
13:55:21.015 Event step changed to 8.
13:55:21.167 Event step changed to 9.
13:55:21.167 Event 6 finished successfully.
13:55:22.077 Event 7 issued. Type: Open Item, ItemId: 2867
13:55:22.077 Event 7 started.
13:55:22.077 Event step changed to 1.
13:55:22.222 Event step changed to 5.
13:55:22.222 Pressed 162 1 1
13:55:22.376 Event step changed to 4.
13:55:22.505 Event step changed to 7.
13:55:22.525 Released 162 1 1
13:55:22.607 Event step changed to 8.
13:55:22.769 Event step changed to 9.
13:55:22.769 Event 7 finished successfully.
13:55:23.574 Event 8 issued. Type: Close Windows, Type:
13:55:23.575 Event 8 started.
13:55:23.575 Event step changed to 1.
13:55:23.788 Event step changed to 2.
13:55:23.934 Event step changed to 3.
13:55:24.045 Event step changed to 4.
13:55:24.158 Event step changed to 1.
13:55:24.291 Event step changed to 2.
13:55:24.401 Event step changed to 3.
13:55:24.546 Event step changed to 4.
13:55:24.695 Event step changed to 5.
13:55:24.695 Event 8 ended with status code 1 at step 5.
13:55:26.984 Going to Waypoint #1
13:55:27.013 Going to Waypoint #2
13:55:27.023 Going to Waypoint #0
13:55:27.043 Going to Waypoint #1
13:55:27.053 Going to Waypoint #2
13:55:27.071 Going to Waypoint #3
13:55:27.081 Going to Waypoint #4
13:55:27.093 Going to Waypoint #5
13:55:27.098 Pressed 296 1 1
13:55:27.278 Pressed 296 1 1
13:55:27.335 Event 9 issued. Type: Key,
13:55:27.335 Event 9 started.
13:55:27.335 Event 9 finished successfully.
13:55:27.335 Pressed 27 1 1
13:55:27.437 Released 27 1 1
13:55:27.475 Event 10 issued. Type: Key,
13:55:27.475 Event 10 started.
13:55:27.475 Event 10 finished successfully.
13:55:27.475 Pressed 27 1 1
13:55:27.483 Released 296 1 1
13:55:27.578 Released 27 1 1

[joraanpe]

By other side, thinking about the main topic issue opening bps, isnt it possible to add something like a lifetime inside your bp opener, and/or if it didnt accomplish to fully execute it, press esc? i bet that way it would close the window and allow continue retrying with bps opening

[Lucas Terra]

Thanks for the info @joraanpe. I will investigate it.

[joraanpe]

Finally, i think i got the debug console message with the issue i was having with the menu, opening bps after relogin inside spawn.
In some part of the "testing" i tryed enabling a small hotkey i had made, which was supposed to be a fix for this but didnt work, so i disabled it again.
The debug console goes untill i allowed it to try several times reopening bps closing the menu by clicking anywhere, so it could re try, and did like 3 stucks on the menu before accomplishing it.

The hotkey i had made to see if it helped was enabled after a sometime inside the debug console, and also disabled again sometime liter so it might show it its activity only in a part of it maybe. This is what i used:
auto(300) if $openmenutime >= 2000 then
press('[ESC]')
end



Here is the log, saved it on pastebin as post's limit wont let me add it here

http://pastebin.com/xZMSVdsV


Let me know if it has any usefull info about the issue in it.