Bug #18331

VESSELNAMING data not being added to ships created before 1.4

Added by jclovis3 about 3 years ago. Updated over 2 years ago.

Target version:
Start date:
% Done:


Core Game, Making History
English (US)
Mod Related:
Arrow u r green
Arrow d r red


In the 1.4 update, the ability to control vessel naming was assigned with priority levels to each control pod or probe core, and this was great, however, any vessel created before this update has no such data and will not revert to their previous name after docking and undocking from a vessel with this new feature. As a result, ship names keep getting cloned.

I recommend adding code to add a VESSELNAMING tag in the ship data when the player manually renames a vessel from one of its parts, as well as allow reconfiguration of the priority level during flight and not just during build time.


#1 Updated by TriggerAu about 3 years ago

  • Status changed from New to Ready to Test
  • Assignee set to TriggerAu
  • Target version set to 1.4.2
  • % Done changed from 0 to 80

You are able to add vesselnaming in flight if you adjust one of the settings in the config file.


You can read up about the feature here:

If you wanna add it to parts other than chair/command modules theres some extra editing, but its documented there - see how you go

#2 Updated by jclovis3 about 3 years ago

Made edit to ..\Kerbal Space Program\settings.cfg with the recommended change while the game was not running. Restarted and tried renaming an old vessel from within the tracking station. The option to set naming priorities was not available there, which was to be expected because you're not identifying a specific part to set this on.

Selected to fly the vessel and selected the most common module I use for renaming. There is both a rename option and a configure renaming option. This may lead to confusion, but at least this workaround works. Recommend incorporating this change into future releases as I see no reason you shouldn't be able to update this in flight.

Not changing status out of "Ready to Test" because I don't know if you need to test this on the next release first to clear this. Thank you for the quick fix though just the same.

#3 Updated by jclovis3 about 3 years ago

I am unable to test this as I no longer have any older vessels that haven't already been fixed manually. Might just move this one to Mute now.

#4 Updated by TriggerAu almost 3 years ago

  • Status changed from Ready to Test to Resolved
  • % Done changed from 80 to 100

#5 Updated by joshua.collins over 2 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF