I decided to get with the scripting now that the syntax is settled (mostly).

If there was a command that one could place in a KSP script that would simply allow you to save a .txt file with a file name, then the “make_ persistent” variables and arrays could be stored in that file for any script. To recall a preset, hit a button “load preset”, select the text file, and it reads in the variables and arrays and displays the filename (which is also the preset name).
Is there a flaw in my logic here?
Seems like N.I could easily do this in a 2.1.2 update no?
Can we jump on them to do this?