xlog() bugging client

[Wesker]

11:56:33.232 Event 1 issued. Type: Connect, Connect11:56:33.232 Event 1 started.
11:56:33.232 Event step changed to 13.
11:56:33.232 Pressed 13 1 0
11:56:33.432 Released 13 1 0
11:56:33.732 Event step changed to 10.
11:56:34.488 Event 1 ended with status code 1 at step 10.

auto(5000)

if $connected then

wait(1300,2300)

xlog()

end

auto(5000)

if not $connected then

wait(3000)

connect(acc,pass,char) ----strings

end

theres a malfunction around the code


you can also do it manually doesnt matter xlog() will bug the client eventually or at the first attempt theres no way to predict it


------
on a different matter theres also a bug or malfunction with waypoints, its hard to tell where or how or when it will appear but the way to solve it is making more waypoints, beetween areas i think that you should fix that asap, its anoying

http://tpforums.org/forum/threads/34...ll=1#post33191 (outdated api example)

[Leonardo]

I have no clue about the error, did you tried keyevent ? keyevent(CTRL + L) for logout (both in hex values). Not that will fix this but at least will help you connect again, maybe.

[Wesker]

yeah but the issue is that i need to force the logout while im caveboting, i triend the logout() instead sometimes it does logout sometimes ss logs me out and if that happens the screen on tibia will froze and i wont be able to log in again, didnt find a solution yet, makign a waypoint to logout is not what i have in mind