Camaro'
2010-09-29 06:27:11
As shown here:
http://villavu.com/forum/showpost.php?p=739898&postcount=238It ran over night the script, but my players were both True and the script was logged out, did it not detect that it had failed?
Was it still running or had it executed?
Coh3n
2010-09-29 13:05:45
It may have lost connection. We have a function to handle it, but I'm sure it doesn't work EVERY time.
Camaro'
2010-09-29 20:27:08
From: Coh3n
It may have lost connection. We have a function to handle it, but I'm sure it doesn't work EVERY time.
The script it self was still running, both players were set to true, and i was logged out. It happened another time too.
Coh3n
2010-09-29 21:53:21
[QUOTE=Camaro';740019]The script it self was still running, both players were set to true, and i was logged out. It happened another time too.[/QUOTE]
Where were the characters? Were they in randoms? I was just thinking that if something went wrong and SRL set Players.Active to False, we don't ever check to see if it was changed and therefore MSI_Players.Active would have never been updated.
Just a thought though.
Camaro'
2010-09-30 07:21:42
From: Coh3n
Where were the characters? Were they in randoms? I was just thinking that if something went wrong and SRL set Players.Active to False, we don't ever check to see if it was changed and therefore MSI_Players.Active would have never been updated.
Just a thought though.
One of the characters failed draynor fish walking - My fault though. Other one was woodcutting at draynor.
Coh3n
2010-09-30 12:51:48
[QUOTE=Camaro';740139]One of the characters failed draynor fish walking - My fault though. Other one was woodcutting at draynor.[/QUOTE]
So the one should have been set to false because it failed the walking. There may be something buggy in the color walking functions. Afterall, they haven't been tested nearly as much as the reflection ones.
As for the other one, the only thing I can this of is that it lost connection, but even then it should have set your player to false. Perhaps it got caught in the endless loop in SRL? I know there's one somewhere and I'm still not sure why it's there…
E: I added a check in the newest revision that will hopefully fix this.