We learned in Kerbal that using raw names or strings for part IDs is a bad idea.
From an engineering perspective: Human readable strings as object identifiers does not a robust architecture make.
Yes, I've been bitten by this problem before.
Before the community gets too deep in the weeds with mods, this game needs a better ID system.
Generating GUIDs is cheap, decentralized, and the most common approach used in heterogeneous databases.
EDIT: Just add a Version attribute to define an object version, and an optional UseVersion attribute where an object is referenced. If UseVersion is not specified, it is the same as UseVersion = "latest".
That way, players can have multiple major revisions of the same mod installed (under different folder names), and all existing parts can still load and function. This also provides an unambiguous way to mark older mod versions as deprecated without having to modify the text or any other maintenance-intensive work.
From an engineering perspective: Human readable strings as object identifiers does not a robust architecture make.
Yes, I've been bitten by this problem before.
Before the community gets too deep in the weeds with mods, this game needs a better ID system.
EDIT: Just add a Version attribute to define an object version, and an optional UseVersion attribute where an object is referenced. If UseVersion is not specified, it is the same as UseVersion = "latest".
That way, players can have multiple major revisions of the same mod installed (under different folder names), and all existing parts can still load and function. This also provides an unambiguous way to mark older mod versions as deprecated without having to modify the text or any other maintenance-intensive work.
Last edited:
Upvote
0