[Kovarex] [2.0.9] Parameterized Blueprint: Variables with same default value are not working as intended

[Hares]

Parameterized blueprints with variables having same default value, when deployed, use the given value of the last one for both.

See blueprint:

0eNrtV11v2jAU/SuWH6ZNcmgcCKjRqknVXvYwqU97aSfkJA6xltiZ7cBYxX/fdQKB8lXoqq6T+oAgN9f3HPvce0LucVzUvNJC2nGs1A8c3a8jBke3G5funpGs8qzyJlqk7voXjkKC5zjqLwgWiZLtGiMmkhUuQbKS4wgzY3gZF0JOvJIluZDcC7BbIlMONeiCbC6y88otmgpta4iQVZU2wxOWl17FNAQt1xtlgsV3grm0wgreEmku5mNZlzFkRpQcJURwpQwsVnK5N9prdwffgKJ5IhpiHbbn41V4/BOoAhbclkqXQNvtaQs/6PCFVtJLcm7sLupgA3VPkX5XJGPGekIart057NTpP2CfCiDa3qXAA7SyWhXjmOdsKpR2axKhk1rYMZcsLjgIbHXNSReGJWlXPxPa2PGO0JtHs2hQjGWud2jou8vSJVgHhz/ixcIJNgNiTq3bgASkT4LvEOvKtDIuGwJ6rtv7F2gC1MSJi28jd2uWp0ZWPyIMTLbKJKoGio6Lay2Irnue4ILFHHaIb1b1xW+eoq+scI05BYbNgYTD4HJweRkOfEppf7TuSd9xOW2Ghs85Qzt60AeDQs4H6D8CsJk7ePFJpE+dxFc9RHRriPy9Q3TMI/7CaAZP1GhwSKPgPI3CczUa/BONgocaBadqNDxLI7e3vW5JbkP4NTzLN+kB56SPOKfv7xRaeic5DBYcAAuOgwU7YMFpRv1Z1SBq49DoPVD2oNKHk7yavnn1m1c/m1eHb1792r36ZI3+Q68OX9Crd8Ge5NWh78HnNK8O9lX2mnfYdfnreuJROqLBKELfmBasiLkBZjIrRGKRkOjm+gbyU24SLapWyq1/+uvXYTQTNkdTVwdIG+R6VE6QgWSU8ozVhYW7kE7QLOcSYlWh5jwlqDYc2ZyjiZhCvMlBKmtCBYwLUpKjTGkUK5v37uSdzK2tTHRxAcG6NL2MJdCeQvWgVy+mgs+sqkTSq/LqU3Y1emev2k3io8+krVez7lEE5wjlgdl49cpy5PwXfwDTB1pw

Copy blueprint

Steps to reproduce:

1. Import blueprint book
2. Paste blueprint 1 ("Parameterized Mall") with some values -> Works OK
3. Paste blueprint 2 ("Double Mall (100-200)") with different values -> Works OK
4. Paste blueprint 3 ("Double Mall (150-150)") with different values
   • Expected: Different conditions on the inserters
   • Actual: Same condition values on the inserters

[kovarex]

Hello, this is weird, as the two 150 numbers should get merged into one field anyway, as the system doesn't allow to have two numbers parametrised into two different numbers, it just isn't built that way.

So the question is, how did you even make such a blueprint, as the two numbers shouldn't be separate.

[Hares]

So the question is, how did you even make such a blueprint, as the two numbers shouldn't be separate.

I've changed the default values.

[Darkestnoir]

Yeah, the system needs a way to set a extra default value for user editable fields.

I have a blueprint where you can set the request stack size of a bunch of ingredients.
But i have to use as default values 2-6 and 21-25 which are to low/high for the purpose.

[Hares]

Yeah, the system needs a way to set a extra default value for user editable fields.

I have a blueprint where you can set the request stack size of a bunch of ingredients.
But i have to use as default values 2-6 and 21-25 which are to low/high for the purpose.

BTW, you can refer to the stack size of item in formulas, so only one extra input variable is needed (usually) - a common multiple.

11-02-2024, 03-09-17.png (552.21 KiB) Viewed 325 times

But having to set all those values by hand at first (when creating the BP) is yet annoying.
And you can never change the "value" inside this editor to be the same as for other parameter (that's what this bug report is about).