You could still have regular movescripts. Like I said, just treat them like special scripts. The 'EntityMove' function could take either a script name or a string with a literal script
inside.

And how 'bout this: you can customize literal movescripts. So you could assign a script to any character sequence in system.vc, before you do anything else, and then use those special sequences in move scripts:

System.vc:

#movescript Cwc% ClockwiseCircle
#movescript Ccwc% CounterClockwiseCircle

...

Some map script:

EntityMove(guardEnt, "Cwc4Cwc4Ccwc4Ccwc4R");

Scripts could be used in all kinds of other places, too. You're probably right about vecna ever implementing this, though.

#movescript wouldn't be a define, but a separate
preprocessor macro.

I might try to implement this coroutine idea as a preprocessor. Adding it to the engine itself would probably involve lots of redesign, but it shouldn't be too hard to translate scripts into functions and global variables.

Comments and suggestions welcome!