Any output NodePort can have multiple connections, even though some of them should only be able to have one.
Cause
By default the [Output] attribute's connectionType is set to ConnectionType.Multiple
This should be set to ConnectionType.Override for any output that isn't a List.
Workaround
Currently if two things are connected to a node that is only expecting one, when you export the moveset, the node that was connected FIRST is the one that is exported. The others are ignored.
Bug
Any output NodePort can have multiple connections, even though some of them should only be able to have one.
Cause
By default the
[Output]
attribute'sconnectionType
is set toConnectionType.Multiple
This should be set toConnectionType.Override
for any output that isn't a List.Workaround
Currently if two things are connected to a node that is only expecting one, when you export the moveset, the node that was connected FIRST is the one that is exported. The others are ignored.