Possible cause of many bugs: attachedPartGuid vs AttachedPartGuid under attachNodeStates

[jclovis3]

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes 
OS: Windows 10 Home 22H2 | CPU: AMD Ryzen 7 7800X3D | GPU: MSI Gaming GeForce RTX 4080 16GB GDDR6X PCI Express 4.0 | RAM: 128 GB DDR5-6000

 

While trying to figure out what state my docking ports are in when they fail to dock, I noticed in the json files under attachNodeStates there are a couple of lines that look like they could cause some problems with a capitalization error:

"attachNodeStates": [
              {
                "nodeId": "top",
                "IsDynamic": false,
                "attachedPartGuid": null,
                "AttachedPartGuid": {
                  "Guid": "00000000-0000-0000-0000-000000000000",
                  "DebugName": null
                }
 

Not sure if this is the result of changes made in parts along the way that weren't all updated correctly across newer parts but it does look suspicious to me. Feel free to downgrade this as not a bug if I am mistaken.

 

Included Attachments:

quicksave_16.json

Edited January 5 by DibzNr

[DibzNr]

@jclovis3 This feels like more of a discussion subject than a bug report, so I moved this post to the discussion page

[Mutex]

They really need to decide whether field names start with a capital letter or not.

[cheese3660]

The lowercase field is obsolete and not used anywhere

As such it cannot be the cause of these bugs