to keep it short, how well does the engine keep track of locals in global or targetted scripts when the script starts/stops infrequently? are the locals saved to the savegame? is there loading/reloading consequences? what about savegame cleaning effects?

i'm trying to gauge if using the locals of a global script is reliable in the long run, or if i should use globals instead for integrity.

for example, the scripts i'm using tracks when the player casts spells while an item is equipped. a targetted script is started when the sound effect plays, and the targetted script keeps track of counters and cast tallies, as well as fires the 'effect'. i'm wondering if the counters and tallies should rather be globals incase the script isn't reliable when saved.

so does anyone have any good info on this at all?

The state of variables in a global script will be saved in save games as long as the the script has run at least once since the game was loaded.

interesting, that's good to know. so these scripts can break of someone loads, saves, and reload nearly immediately. maybe i need to replan this.

I hope this isn't considered rude by net-iquette, but I resurrected this post from before cuz I read it and had a question about what I read.

abyssal terror wrote "interesting, that's good to know. so these scripts can break of someone loads, saves, and reload nearly immediately..."

So, lets say I have some global script variables I must keep track of. This suggests to me that if I don't want to lose the info, I have to run the scripts upon load to preserve the variable every time a game is loaded?

ST

As long as we're talking about local variables of a global script: yes. If that information is so valuable, I'd probably resort to using a global variable, though.