You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just to be sure, when a script is interrupted by a MESG or an engine Event (not by CALL), its running state is completely trashed, right?, not paused and resumed when the new script finishes?
Though according to Verm in #31, any higher script running states on the CALL stack are not affected! :o
(As for stopping a script rather than interrupting, see #30 )
(And as for a script err'ing, see #41 )
The text was updated successfully, but these errors were encountered:
Just to be sure, when a script is interrupted by a MESG or an engine Event (not by CALL), its running state is completely trashed, right?, not paused and resumed when the new script finishes?
Though according to Verm in #31, any higher script running states on the CALL stack are not affected! :o
(As for stopping a script rather than interrupting, see #30 )
(And as for a script err'ing, see #41 )
The text was updated successfully, but these errors were encountered: