[Kovarex] [2.0.16] non-parameter variables changing in blueprint

[moodwrench]

Hi... Im not sure if this is a bug or if Im doing something wrong. Ive been playing with the parameters on the blueprints.. After way too long troubleshooting, I found a weird behavior and I'm not sure what I'm doing wrong.. To replicate, create a constant combinator with 2 static items (lets say copper and iron). set a separate count for each so that the parameters see them as different variables (lets say copper-1, iron-2). I want copper to be 1 always, but iron to be a variable. I set iron to variable, and change the 2 to a 1 (default needs to be 1, but i needed to make it 2 to make it a separate variable (if you follow me)). when I deploy the blueprint, It asks me for the variable for iron and I set it to 5 for example. when it gets placed, iron is set properly to 5, but copper is changed even though its not a parameter. same result if I make it a separate combinator. Again, I'm sorry if this is not a bug and I'm just too stupid for this game.

[boskid]

Given that this bug report is about numbers in parameters, i am considering this a duplicate of 117000. TL;DR: same numbers are grouped and replaced in one go.

[moodwrench]

The duplicate you posted while it does describe the problem, the work around of using separate values for every item will not work for me as I want the defaults to be the same for more then one of the items. The UI allows this, but the functionality is not working. Maybe if numbers that match values of static objects or other variables, the UI should block you from creating the parameter or atleast give a warning to tell you that unexpected behavior may occur

[robot256]

The issue described in 121110 may be playing a part here.

[moodwrench]

just a note to clarify.. the work-around in 121110 would work if every parameter had a different default, but I need several to default to "1"

[moodwrench]

The issue described in 121110 may be playing a part here.

It's definitely the same issue as 117000, but that issue was closed as will not fix with a work-around that does not work if you want 2 parameters to have the same default

[robot256]

121110 describes a blueprint with two "variables" (not just values) that share the same default value like you want. Not sure how they produced said blueprint, but modifying either value to make them *different* makes one of them disappear. So that's a different but I guess.