-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
part:uid changes every time I load a craft #782
Comments
The old part UID was removed from the api a few KSP releases ago. When that happened I reimplemented it with a generic hashcode which changes every time because I thought it would be enough to be unique in a mission. You could use the part:tag value. As it does not change. |
Because I'll have to set part:tag using a script and there is no easy way of making part:tag unique i ksp saved game. Also: I sort of want to use part:tag for other purposes than just storing a unique identifier. |
You don't have to set it with a script. You can set it with the right click menu in the VAB. |
@erendrake This has mostly come up because I was writing a script (with assistance from @abenkovskii ) that tried to link volumes to their respective parts (without going through and doing it all by hand). The script in its current state runs fine until you reload the vessel its running on, in which case it goes into a boot loop.
exec.ks:
boot_control.ks:
By setting the tag of 1 core to Edit: |
@TDW89 In the dev version part:tag is settable. |
@abenkovskii ok your rover idea should be able to handle everything then since it can just clock up a variable in a log on it's volume and assign that as a tag for every core as it launches. |
What the title says. According to this page KSP API exposes a part id that never changes and is stored in the save file. It would be nice to have part:uid that never changes.
The text was updated successfully, but these errors were encountered: