Is the LOCK state preserved across CALL's at all, like INST is?

[PuppyPi]

The INST state is preserved by pushing it to a stack of some kind across CALL's and restoring it when the CALL completes, but what about the LOCK state?

[Vermidia]

If you mean that if the current script is in a CALLed script, yeah the caller script can't be interrupted if it was LOCKed before. If you mean can the CALLed script be interrupted if the caller script was LOCKed first, it seems yes. If the CALLed script is interrupted, the CALL doesn't end, it still waits for the current instance to end.

[PuppyPi]

Wow that's interesting, thanks so much!
Hmmmmm,
So..

• A CALLed script always starts UNLK'ed?

• What if it calls UNLK explicitly? The CALLer's LOCK state isn't affected? Meaning it keeps a record of whether each script in a CALL stack was in a LOCK state separately, instead of just keeping in like a single hidden agent-wide variable? (That's what I meant with my confusingly-worded question ^^' )

If the CALLed script is interrupted, the CALL doesn't end, it still waits for the current instance to end.

• So wait you mean if you MESG or the game sends an Event, that it will interrupt the CALLed script with the new script, but when that script is done, it will return to the CALLer script?! (That's wild if true! :o )

[Vermidia]

1. DBG# says 0 when checking LOCK, so yes
2. Somehow I'm unable to replicate my previous results(I seem to be able to run the CALLer during a CALLed script if it's during a WAIT), but calling UNLK on the CALLed script does not affected the CALLer.(I'm currently not sure how I got the first results, I might need to mess around with that bit more, I've been using mesg to test this stuff so I'll mess around more)
3. Yes

[PuppyPi]

Goooood to know!
Thanks so much for taking the time to check these things! :D

I mentioned it in—Oh well thanks GitHub, isn't that nifty! XD