I had this idea, and thought it might be a good idea, for an individual program or for an added feature to a future DCS release (if Kerm finds more room or decides to go up one page).
A kind of "Safe Mode" RunProg option. While active, when running a program, you are asked whether to run program in normal or safe mode. If run in safe mode, all saferam areas and RAM programs are copied to Archive, and a copy of any data this program writes to is saved in archive. When the program resolves, or if a crash occurs, DoorsCS analyzes the save file, returns variables copied into Archive back into RAM, and restores all saferam areas to their original states and restores any data changed by this program to its original state. Likely alot harder to implement, but a worthy idea, this "Safe Mode" preserves saferam, RAM variables, and undoes corruption. Perhaps, you can allow a user to select what tasks to do in safe mode, like don't save saferam, but do everything else.
A kind of "Safe Mode" RunProg option. While active, when running a program, you are asked whether to run program in normal or safe mode. If run in safe mode, all saferam areas and RAM programs are copied to Archive, and a copy of any data this program writes to is saved in archive. When the program resolves, or if a crash occurs, DoorsCS analyzes the save file, returns variables copied into Archive back into RAM, and restores all saferam areas to their original states and restores any data changed by this program to its original state. Likely alot harder to implement, but a worthy idea, this "Safe Mode" preserves saferam, RAM variables, and undoes corruption. Perhaps, you can allow a user to select what tasks to do in safe mode, like don't save saferam, but do everything else.
