[Kovarex] [2.0.10] Named Parameterised Fields Dissapearing

[Necandum]

What did you do?

TL;DR - In blueprint parameterisation, naming two numerical fields, then setting them to the same value, then making them different, causes one of the fields to disappear.

Step by step:

Create constant combinator with two signals:
X - set to 1
Y - set to 2

Create blueprint of the above.
Go into blueprint parameterisation, and create name for both values
Value 1 - labelled as x
Value 2 - labelled as y

Confirm changes. Save blueprint.

Now, open blueprint editor, edit parameterisation, and change value y to 1. Confirm changes. Place, works as expected, both X and Y signals are 1.
Re-open blueprint editor and parameterisation editing, both fields are still present. Change field y to 5. Confirm changes. Re-open parameterisation editing. Field y now gone.

What happened?
Field y disappeared without warning or explanation.

I surmise that the logic for parameterisation keeps track of numerical fields purely by their value, and does not allow a field to be edited twice (otherwise changing all 4s to 5s, and 5s to 6s would have unexpected behaviour). I also presume the editing happens every time, even if the value is the same. When two fields have the same value and further parameterisation is attempted changing one of the values, the first listed field performs an edit, and thus the second listed field, looking for the same value, finds none that hasn't already been edited and is deleted.

What did you expect to happen instead? It might be obvious to you, but do it anyway!
I would expect named fields to persist as distinct entities, even if they are at one point set to the same value.
If this is not possible, I would expect a warning or other notification that what I am about to do will result in the loss of a named field. I would also expect the field to disappear when it is set to the same value as another, rather than persist and disappear when it is changed to a different value.

Does it happen always, once, or sometimes?
I reproduced this numerous times, following the above steps, so seems consistent.

[kovarex]

Hello, you can't have two numerical fields with the same value, just skip the step of changing the value of y to 1, and keep it as 2 and they will be kept distinct.
The value is the primary indicator of the blueprint parametrisation, so no trick like this can go around it.

[Necandum]

Thank you for the reply.

I sadly suspected there wasn't an easy workaround, but my reason for the report was that it 'feels' janky: the fields disappears without warning and its disappearance is not linked to the action which causes the disappearance.

Given that, it might benefit some users to have a warning (such as a red highlight) appear when setting two fields to be the same value in the parameterisation menu, to warn them that one of the fields will be deleted.

Thanks for making a great game!