Can a vessel id be changed?

[linuxgurugamer]

I have a problem which is caused by a vessel keeping the same vessel id after undocking and then redocking.

Would it be a problem if the vessel id was changed?

The problem arises when a vessel undocks into two.  One vessel gets a new id, the other keeps the same id.  

I'm trying to preserve certain information in the command pod for each vessel when undocked, but share new information when docked.  I'm currently using the vessel id for this. The issue is when redocking, since the original vessel id is the same, data which was supposed to be private to each command pod is shared from the original vessel to the newly-docked vessel.  I think that if I ensured that the vessel id of undocked vessels gets replaced, the problem would be resolved.

Thanks, and Happy New Year to all

[peteletroll]

Maybe you can put a timestamp on the stored information, and use it to know if an item is shared or not, without messing with the vessel IDs?

[linuxgurugamer]

2 hours ago, peteletroll said:

Maybe you can put a timestamp on the stored information, and use it to know if an item is shared or not, without messing with the vessel IDs?

Already does, but I think I will go about this a slightly different way

[JPLRepo]

Changing the vesselId would create other issues, hence there is no public method for doing that.

You can remove and add a vessel/vesselId but that also will create unwanted issues for you as that fires events and other processing.. as removing it - means it's being removed.

You could try that. but I can't say that you won't have other side effects.

Feels to me you should be tracking your data based on the command pod/root part persistentId and then sharing the data between them if they are part of the same vessel.

[linuxgurugamer]

5 minutes ago, JPLRepo said:

Changing the vesselId would create other issues, hence there is no public method for doing that.

You can remove and add a vessel/vesselId but that also will create unwanted issues for you as that fires events and other processing.. as removing it - means it's being removed.

You could try that. but I can't say that you won't have other side effects.

Feels to me you should be tracking your data based on the command pod/root part persistentId and then sharing the data between them if they are part of the same vessel.

Thanks, I've already moved past that.  I found I was able to do it a different way.

[Souptime]

On 1/12/2021 at 5:29 PM, JPLRepo said:

Changing the vesselId would create other issues, hence there is no public method for doing that.

that makesit sound like a secret thing only top tier hackers know