What happens if you call for a single update inside the "normal state", and that update then calls another to continue the looping process

BUT then before the update event happens the script goes to the "busy state" ?

Do we need to do this in the busy state to prevent the update loop from getting "stuck" in the busy state:

Huh?

So you have something like this in your script

;Normal StateEvent OnUpdate()    ;do stuff    RegisterForSingleUpdate(1.0)endEvent

And then somewhere you may enter the "BusyState" where you don't want anything to happen, except that you want to make sure that updates will continue after leaving the "BusyState"?

That solution you posted would probably work, or maybe even something like this?

Scriptname _test_testscript extends Quest   ;Normal StateEvent OnUpdate()    ;do stuff    RegisterForSingleUpdate(1.0)endEventEvent OnBeginState()    RegisterForSingleUpdate(1.0) ;or simply call OnUpdate()endEventState BusyState    Event OnUpdate()        ;chill out - stop the update loops    endEventendState

Thank you very much mojo22.

I try to avoid update loops but I am forced to use them sometimes. So I looked thru all the rest of my scripts and lucky for me NO OTHER script had this gotcha in it. I do have some with updates but the updates were in the "nul state" between the busy and normal states where everything runs no mater what the script state is.