It seems that ApplyFileDefaults() goes through FlightGlobals.Bodies in one pass and applying config immediately.
So if the new parent body (I have Dres) of the body (Minmus, now a moon of Dres) is later in the list (and Dres seems to be), the orbit will be faulty if the parent body GeeASL (mass) is changed.
Suggestion:
Read up all the config files and order the bodies in a tree (or at least an ordered list by depth) of the parent-child relation. Then apply the configs starting from the root.
It seems that ApplyFileDefaults() goes through FlightGlobals.Bodies in one pass and applying config immediately. So if the new parent body (I have Dres) of the body (Minmus, now a moon of Dres) is later in the list (and Dres seems to be), the orbit will be faulty if the parent body GeeASL (mass) is changed.
Suggestion:
Read up all the config files and order the bodies in a tree (or at least an ordered list by depth) of the parent-child relation. Then apply the configs starting from the root.