The current method will not stop until you've successfully logged out, could you please update the logout method to exit it's loop if it detects that it's in combat?

The current method will not stop until you've successfully logged out, could you please update the logout method to exit it's loop if it detects that it's in combat?

this please

The current method will not stop until you've successfully logged out, could you please update the logout method to exit it's loop if it detects that it's in combat?

 

i agree 100%

Not only that, but other things as well that may keep it from logging out such as an open interface.

Not only that, but other things as well that may keep it from logging out such as an open interface.

this too

LogoutTab.logout() doesn't use a loop, so I'm assuming you're referring to Script.stop()?

LogoutTab.logout() doesn't use a loop, so I'm assuming you're referring to Script.stop()?

Well I wasn't actually using the logout() method specifically. I was using WorldHopper.hopWorld(int world) I just assumed it had that method inside it. Anyways, hopWorld() does use a loop, and it causes some issues.

Well I wasn't actually using the logout() method specifically. I was using WorldHopper.hopWorld(int world) I just assumed it had that method inside it. Anyways, hopWorld() does use a loop, and it causes some issues.

 

Should it just break the loop after 3-4 seconds? The scripter would have to be ready to handle any failure of course.

Should it just break the loop after 3-4 seconds? The scripter would have to be ready to handle any failure of course.

That would be great. That or 2 - 3 unsuccessful log-out attempts.

 

Also, un-related but are you guys aware that the underAttack() method is broken?

Edited February 1, 201412 yr by Deffiliate

That would be great. That or 2 - 3 unsuccessful log-out attempts.

 

Also, un-related but are you guys aware that the underAttack() method is broken?

 

It'll be after 3ish seconds, so fixed on my copy.

And no, I was not. What's happening with it?

It'll be after 3ish seconds, so fixed on my copy.

And no, I was not. What's happening with it?

I think it pretty much always returns false. Here's a script with more info: http://osbot.org/forum/topic/34377-recent-runescape-update/

 

Swizzbeat said it has something to do with incorrectly grabbing the logout timer.

I think it pretty much always returns false. Here's a script with more info: http://osbot.org/forum/topic/34377-recent-runescape-update/

 

Swizzbeat said it has something to do with incorrectly grabbing the logout timer.

 

I just tested it on guards and it triggered fine o.O

I just tested it on guards and it triggered fine o.O

and you're on client version .76? There's definitely something wrong with it, me and a bunch of other scripters have been getting complaints because of it.

and you're on client version .76? There's definitely something wrong with it, me and a bunch of other scripters have been getting complaints because of it.

 

Yea, I see the issue now. It should be pushed out next update.

Yea, I see the issue now. It should be pushed out next update.

Thank you very much