[2.0.13] Parameterized constants are force-merged with other constants based on default value

[Theikkru]

Not quite sure if outright bug or missing functionality, but feels broken: currently, it seems impossible to set the default value for a parameterized constant to any value used elsewhere in the blueprint without causing those other instances of the value to also become parameterized.
For example, consider the following setup:

4.png (607.17 KiB) Viewed 143 times

1.png (282.18 KiB) Viewed 143 times

2.png (55.5 KiB) Viewed 143 times

3.png (50.56 KiB) Viewed 143 times

Let's say I want to set the default value for the parameter 0 in the constant combinator to 1:

5.png (555.57 KiB) Viewed 143 times

As soon as I apply this change, that parameterized value is force-merged with the constant 1 in the other two combinators, effectively breaking the blueprint:

6.png (633.87 KiB) Viewed 143 times

[Loewchen]

viewtopic.php?f=58&t=117000

[Theikkru]

Reposted as an idea/suggestion.