Does each mission start with a fresh scripting environment?
I was wondering if it would be worth updating gameOverMessage() to have an additional 'allowSave' param, which if 'true' would show the save game option.
This would mean that for a single map, all missions on that map could be done with a single set of scripts.
This could then be used in challenge games, allowing a challenge to act like a mini-campaign with several missions on the one map and the option to save between each mission.
How come setScrollParams() isn't being used?
I imagine the accessible area of the map is still being controlled by some weirdness in a .slo or .vlo file somewhere (or some other strange file that I'm yet to discover). Surely it would be better to use labels that define the area of the map available for each mission, and then have the camXy.js script use setScrollParams() to limit the visible area of the map to the area object associated with the label?
We could also update setScrollParams() to accept different parameter formats - eg. allow a label name or area object to be passed in.
What gets persisted between missions?
I imagine there will come a point where we want to persist variables between missions, so stuff that happened in a previous mission can affect a future mission.
Is there some info on what currently gets retained from one mission to the next?
