This bug occurs when clicking save/sync/run on an inactive script.
+ load both scripts into open script editors and configure so that temp.script is the active script
+ in the script editor for temp2, change line 152 to this
GMAT x = 55;
+ Click save/sync/run for temp2
+ When pop occurs asking to load temp2 into GUI, click yes
+ Go to the mission sequence and open the dialog box for ScriptEvent1
notice it says: GMAT x = 7.7;
+ If you click close on script editor for temp2 you get a message saying there are unsaved changes.
This shows that GMAT did not save and load the changes, it ran the old script.