lisa wrote:I've been thinking about this for a little while, I think waitForLoadingScreen should have a limit, even if made 20 seconds which is very long but it would atleast put a cap on the loop.
Any thoughts Rock?
I've explained previously why I don't put a limit. What happens if users do the usual
Code: Select all
walk into portal
waitForLoadingScreen()
got to next waypoint.
and it doesn't teleport? It will try to walk in a straight line to the next waypoint with, most likely, disasterous results.
As it is now it will get stuck in a loop. No harm done.
If a user thinks "I don't want it getting stuck", then they add a max time (which, let's face it can vary HUGELY between users) and take steps if it fails.
eg.
Code: Select all
walk into portal
if not waitForLoadingScreen(20) then
goto previous waypoint to try and approach again
end
got to next waypoint.
There's no point in waitForLoadingScreen to time out unless there are steps to deal with it failing.