[1.3.1] Upgrade Editor - Choose upgrades for each engine/RCS in VAB or SPH.

Through a combination of storing the names of all upgrades that should be disabled in a single string separated by commas, processed by the code every time a craft is first loaded through a public override void OnStart(StartState state), it's done, and finally the critical feature of persistence is in:

Version 0.32.5:

https://drive.google.com/open?id=1NLNZ3O65bHJKk8FkIi2PScZW2ouEYIwQ

Creating persistent settings in saved vessels was a much higher priority than improving the code so workarounds won't be needed. Now it's mostly functional for engines and RCS. Tested it with 5 parts including an engine with two modes like the Stock RAPIER with each mode had its own specific upgrade changes and there were no issues, but it may lag a bit when loading crafts with tons of parts featuring upgrades. A version that just reads correctly from the original Part config without upgrades for any module will(or more honestly may) be done later.

I'm not going to re-license as a matter of respect. As for the license choice, every time you release anything under the GNU GPL, you receive a blessing.[1.3.1] Upgrade Editor - Choose upgrades for each engine/RCS in VAB or SPH.

---------------------------------------------------------------------------
Visit this link to stop these emails: http://zpr.io/nfAVj