Started by GitHub push by lamont-granquist1452e508df10b26d436dd69b4fef29c85f6d72198dade508df10b26d436dd69b4fef29c85f6d72198dadrefs/remotes/origin/deve508df10b26d436dd69b4fef29c85f6d72198dade508df10b26d436dd69b4fef29c85f6d72198dadrefs/remotes/origin/deve508df10b26d436dd69b4fef29c85f6d72198dade508df10b26d436dd69b4fef29c85f6d72198dadrefs/remotes/origin/devhttps://github.com/MuMech/MechJeb2.gitMechJeb2-2.14.3.0-1452.zipMechJeb2-2.14.3.0-1452.zipMechJeb2-2.14.3.0-1452.zipfalse#14521980621549MechJeb2-Dev #14521452falsefalse14522121SUCCESS1747873191941https://ksp.sarbian.com/jenkins/user/kerbas-ad-astra/my-views/view/All/job/MechJeb2-Dev/1452/MechJeb2/MechJebCore.cs5e920def6bdf12e4d6832948e277ee283704b9691747606284000https://ksp.sarbian.com/jenkins/user/mrev1995mrev1995mrev1995@gmail.comFix saving and loading of vessel-specific settings When loading a craft file in the Editor, there's no vessel name available; thus, all vessel-specific settings (those with persistent pass TYPE) get loaded at their default values. A few seconds later, those get saved (with the ship name at the top of the screen), overwriting any previously vessel-specific settings with their default values. Since there's no way to get a ship name in the OnLoad method (it gets called before the Editor has set the name from the .craft file), the best option is to simply not save the settings from inside the editor at all. 2025-05-19 00:11:24 +02005e920def6bdf12e4d6832948e277ee283704b969Fix saving and loading of vessel-specific settingseditMechJeb2/MechJebCore.csgithttps://ksp.sarbian.com/jenkins/user/mrev1995mrev1995