Modify Parameters UI incorrectly shows TriggerSequence pin delays

[ghramsey]

Staging. Non-Steam version with EGS.

Tech Comms. The default parameters are request unload on several of these proxies and the lists are absent on the
Proxy nor on the base entity on the link dialog. But on the parameter list they are present.

[MattFiler]

To explain what's happening here: pin delays (shown in the flowgraph UI as numbers next to the pin) are actually added on entities as parameters. In your old non-flowgraph UI they should be visible in the parameter list, but otherwise in the new UI they should only be visible on the node pins. TriggerSequences produce some complexity here as they support custom pins.

So your example presents some edge cases where this is failing - the pin delays should be visible in all UIs if flowgraph mode is not supported (including, when proxied), however if it's supported, they should be visible in none of the UIs - however for TriggerSequences this also isn't working due to the nature of how the custom TriggerSequence pins are added.

I should use the Triggers list on the TriggerSequence itself to know which _finished and _relay parameters are actually pins, and handle them accordingly.

Thanks for flagging!

[ghramsey]

I see what you mean about the flowgraphs. On an unaltered file the pins look to be there as they are supposed to be.

I don't know why this UI was in fallback. I thought I'd used a vanilla Tech Comms file at the time.
I was helping someone who wanted to have internalComms section accessible during Mission 16.
When experimenting with things like this I usually would. It seems I did not though. You can close
ticket. The issue seems solved and was actually 'between the keyboard and the chair' ... user error.

[MattFiler]

No it's defo an edge case, I'll get it fixed 👍