I ran into a strange issue with the 66th long variable in one of my scripts. It compiles fine in MWEdit but is giving me either a run time "set expression error" or causing the script to stop without warning when used for simple "set <66th_local_long> to " statement(s). Adding a dummy 66th local long variable and using the 67th with everything else the same including the same variable name works fine. I have another script with >66 long variables I didn't notice any issue with so probably it's context dependent. I know the 34th variable bug is well documented which MWEdit nicely warns about.. but I don't recall and can't find any mention of the 66th. Anyways, just curious if anyone else has more experienced input on this topic. Thanks in advance.

Well, if you're using >66 variables then the script is likely massive. There's other known limitations that you might be reaching, covered in the "Limits of the Script Editor" section of MSFD.

I made a test script using 66 variables and things seemed to work fine.