In KSP multiscript, “stop_wait” stops working— and $NI_CALLBACK_ID returns a negative number

KeithRamsey

I wrote a KSP multiscript for Kontakt which uses stop_wait to cut short the wait times I've applied to other events.

For the most part, the script works as I want it to. But every now and then, out of the blue, it stops working. (It ceases to stop the wait of the other events.) I was debugging it and noticed that while the script normally gives a positive number for for the $NI_CALLBACK_ID, when it stops functioning properly the script gives a negative number for the $NI_CALLBACK_ID-- (that is, a number with a hyphen in front of it.)

Right now, the only way I know to fix it is to quit VE Pro (unloading some 90 GB of ram in the process) and then reloading. This is rather time consuming. Any ideas what the problem might be and how to fix it?

(I tried a shot in the dark and tried storing the NI callback ID as its absolute value, but that didn't fix it.)