Can't LogoutToTitleScreen when session invalid

[kodwim]

when there are auth issue, bot will try to logout and exit the exile bot. but it don't logout at all, just like click "ESC" and then stop there.
I'm ok that auth issue happens, but for a game like POE, you will lost a lot of experience when you die, so, please please, log me out, even a "Alt-F4" is ok for me!!!!
following is the logout part log. a full log is also attached.


2014-10-04 09:12:25,995 [7] INFO  (null) - Invalid Session
2014-10-04 09:12:26,000 [7] INFO  (null) - The bot is now logging out the client due to an auth issue.
2014-10-04 09:12:26,008 [7] DEBUG LokiPoe (null) - [ActivateEscapeState] !IsEscapeStateActive. Attempting to open it.
2014-10-04 09:12:26,277 [33] INFO ExampleRoutine (null) - [Logic] Now moving towards the monster Mortality Experimenter because [canSee: False][pathDistance: 40.44433][blockedByDoor: False]
2014-10-04 09:12:26,768 [33] INFO ExampleRoutine (null) - [Logic] Now moving towards the monster Mortality Experimenter because [canSee: False][pathDistance: 29.08392][blockedByDoor: False]
2014-10-04 09:12:27,202 [33] INFO ExampleRoutine (null) - [Logic] Now moving towards the monster Mortality Experimenter because [canSee: False][pathDistance: 29.12615][blockedByDoor: False]
2014-10-04 09:12:28,325 [33] DEBUG StuckDetection (null) - [StuckDetection] {492, 868} => 2
2014-10-04 09:12:28,326 [33] DEBUG StuckDetection (null) - [StuckDetection] {457, 691} => 2
2014-10-04 09:12:28,327 [33] DEBUG StuckDetection (null) - [StuckDetection] bounds: {241, 279}
2014-10-04 09:12:28,328 [33] DEBUG StuckDetection (null) - [StuckDetection] TimeInInstance: 00:00:27.8683718
2014-10-04 09:12:28,328 [33] DEBUG StuckDetection (null) - [StuckDetection] TimeInArea: 00:00:27.8690979
2014-10-04 09:12:29,042 [7] DEBUG  (null) - LogoutToTitleScreen returned None.

 

[pushedx]

Please attach a full unmodified log rather than snippets in the future.

There's two things I can do to address this:
1. Checking over the code, the auth thread doesn't properly acquire a frame before calling API functions, so that might be the issue you saw. Input methods are not 100% reliable in this game though.
2. I can add a terminate process on auth error setting for 100% certainty the client will get exited.

I'll get these worked into the next version.

 

[kodwim]

here we are, a full log

Please attach a full unmodified log rather than snippets in the future.

There's two things I can do to address this:
1. Checking over the code, the auth thread doesn't properly acquire a frame before calling API functions, so that might be the issue you saw. Input methods are not 100% reliable in this game though.
2. I can add a terminate process on auth error setting for 100% certainty the client will get exited.

I'll get these worked into the next version.

 

[pushedx]

The latest Beta, #921, contains the fixes. Please download and give the Beta a try to see if the issue is fixed for you.

You'll want to enable the new setting from the Global Settings tab. You should uncheck the logout option if you want to use the exit process method. Testing should be pretty easy as well, since you can start the bot in a low level safe area, and just kill your session via BuddyAuth.

 

[kodwim]

thank you ! I'll try the beta 921