Alek pls fix very nub programmer cant make helloworld.c

 

 

erm erm i mean what I meant to say was basically, if you were recently in combat and then you call stop() it will try to log out but if it doesnt succeed (i.e. 10 second cooldown didnt end yet) it will just stop the script anyway, leaving your player logged in. 

 

I have the script designed to run from combat, but it still hasn't finished the 10 second cool down yet. Obviously I could make it work for this by waiting before calling stop() but I think this should be handled API sided to protect this from happening in other scripts. 

 

 

 

 

Pls fix alek I luv u 

 

 

Please read the API documentation.

 

stop(boolean logout)

Please read the API documentation.

 

stop(boolean logout)

 

 

No I want it to logout, but what I am saying is that basically if it fails to log out like for example, I was in combat within the last 10 seconds, it tries to logout, fails and then the script stops.

 

Meaning, it tried to logout, like it should, it failed to logout because 10 seconds had not passed since last in combat, then it proceeded to kill the script thread even though it was not logged out yet.

No I want it to logout, but what I am saying is that basically if it fails to log out like for example, I was in combat within the last 10 seconds, it tries to logout, fails and then the script stops.

 

Meaning, it tried to logout, like it should, it failed to logout because 10 seconds had not passed since last in combat, then it proceeded to kill the script thread even though it was not logged out yet.

which then your character is left alone in you dont know where

 

edit:

 

isnt stop() the same as stop(true)

Edited April 9, 201511 yr by josedpay

which then your character is left alone in you dont know where

 

edit:

 

isnt stop() the same as stop(true)

 

 

Yea I think I was just unclear on my first post so alek misunderstood what I said. 

This should be logic handled by the scripter. What if you are at constant aggro monsters?

This should be logic handled by the scripter. What if you are at constant aggro monsters?

Is there any A-OK that tells us if we need to wait 10 seconds.

Is there any A-OK that tells us if we need to wait 10 seconds.

 

Message Listener and game state

Message Listener and game state

In my opinion fleeing combat should be done by the scripter, which I do. But I feel like when you call log out it should try more than one time to log out. All I'm asking if for logout to have a check, if the log out fails one time, wait 15 secs, try again? I don't feel like I'm asking much

Again, this isn't really just for me, but for everyone using the api Who might not know this happens.

Ps ily alek pls?

love u long time

Edited April 10, 201511 yr by Mysteryy

The more methods we add to the API which can be handled by the scripter, the more we open ourselves up to something breaking. As of now, I'm only interested in stabilizing existing API and fixing bugs.