Post by AtomHeartDragon on Feb 7, 2018 20:49:25 GMT
Between ships (half covertly) missing crucial modules like radiators, engines and powerplants, core stuff happily mixing with workshop items in common namespace, like one huge, deeply dysfunctional family (whose family tree contains cycles), no version viability tracking and component designs happily overwriting each other in one big free-for-all, so that what you put into your missile one day as a long, skinny 10kg fluorine tank, will return to haunt you as a stubby, bloated one the next day, happily propagating across your dependency tree and adorning your most cherished designs with red exclamation marks while turning them into bloated monstrosities, the Workshop is pretty much unusable in its current state.
What is really needed:
Tracking each single item, down to individual modules by workshop ID and uniquely identifying it by one
Keeping track of the game version the ship or module was built with
Keeping track of external dependencies and enforcing them
Allowing quick deletion from within the game
Separation of core stuff from workshop stuff just like the core stuff is already separated from user designs
Any workarounds and user side remedies I could apply are welcome as well.
I think we really need three distinct identifiers for parts, and we only have the least useful one currently. I would ideally like:
Part label: "small drone". Should not need to be unique; currently it does, which is the core of all our problems. Part unique identifier: "b5bb9d8014a0f9b1d61e21e796d78dccdf1352f23cd32812f4850b878ae4944c". (Use the sha256sum of the complete part definition less identifiers other than name) Part family identifier: "Version 3 ea0cc42e3f0045bdc73002c4f291be75d69088c1967f6bc8a8bcad7a3c5b3f9b" (where the latter string is the part unique identifier of the first version)
In the designer, you would need another toggle specifying whether you wanted parts to update to the latest versions, or maybe to let you do that in a semi-automated fashion.