Restricting script save/load [done in 3314]

[utunnels]

I realized a problem of current script save file issue.

That is not all kinds of variables are saved properly:

1. Integers, decimals

They shouldn't have any problems.

2. Pointers

They can be save/load normally. But since the pointers are changed in a new game, so saving them is really pointless.

3. Strings

Due to current string cache mechanic, they can't be loaded properly because the cache is gone if you close the program.



In this case I have another idea to save the script variable other than dumping the memory into disk.
All global variables should be saved in a script file which can be load and executed.

The script file should looks like this:

Code: [Select]

void main(){
   setglobalvar("newname", "Frankenstein");
   setglobalvar("charlevel", 99);
   setglobalvar("defense", 0.46);

   setindexedvar(3, 85);
   setindexedvar(9, 66);


}
A side effect of this is the player can hack this easier than the binary save.

[Damon Caskey]

Are you sure you want to worry about this? The filestream functions already allow controllable persistence by reading/writing text files if a modder so chooses.

DC

[utunnels]

The default save function should at least work properly, otherwise all user have to write their own save/load functions. Text format is easier to handle and keeps its functionality even if script variable changes its structure.