set-customizable-object-node-property pin fallback cannot link object reference assets

[softdaddy-o]

Description

When a property name does not match a UPROPERTY on a CustomizableObject node, the bridge falls back to writing the pin's DefaultValue string. For pins of category 'materialAsset' or other object-reference categories, setting DefaultValue with the asset path string does not actually create a linked-asset default — the pin remains visibly empty and downstream compile complains 'Could not generate a mesh section because it didn't have a material selected'. The bridge should detect object-reference pin categories and write Pin->DefaultObject = LoadedAsset instead of (or in addition to) DefaultValue.

Steps to Reproduce

1. Add a node with a materialAsset input pin, e.g. CustomizableObjectNodeMaterial. 2) Call set-customizable-object-node-property with properties.{PinName}={asset_path_string}. 3) Inspect the pin with include_node_properties=true.

Expected Behavior

The pin's default object reference is set to the loaded asset, and downstream compile finds the material.

Actual Behavior

Tool returns success but pin default_value remains empty (or holds an unresolved string); compile produces 'Could not generate a mesh section' warning.

System Information

• CLI version: 1.25.4
• Python: 3.14.4
• OS: Windows-11-10.0.26200-SP0
• Bridge: reachable

[softdaddy-o]

Fixed in v1.27.0. Install with pip install soft-ue-cli==1.27.0. CustomizableObject property pin fallback now supports object reference assets through soft-ue-cli set-co-node-property <asset> <node> --properties <json>.