[Kovarex] [2.0.31] Blueprint parameter can remain unset after placing

[elmbald]

There is some weird behavior when placing parameterized blueprints, where if you set a parameter, then click somewhere outside of the parameter box (I have frequently done this because of muscle memory to double-click to select item at current quality in other screens, and sometimes my mouse will register a single click as 2), the parameter will not be set, and the blueprint will place in a different spot than expected when the checkmark is selected.

What did I do? Placed a blueprint, set the parameter and value for a signal, then double-clicked outside of the parameter screen before accepting the parameterized build.

What happened? A new, empty, parameterized build UI got 'stacked' (only showed one, but this can be chained and will break on every layer other than the top of the stack of requests). When the top parameterized screen is accepted or escaped out of, the parameters initially set show on the screen that came before, but are only set as their default values (ie. set signal as [A] with value of 1, but default is signal [p0] and value 0, the blueprint is placed with signal [p0] = 0)

What would I expect to happen? I would expect that the parameter UI holds priority until confirmed or escaped out of. If the intended behavior is to stack the UIs on top of each other, I would expect the values that are set through those UIs to be respected. Additionally, I would expect visual feedback of where blueprints along this stack will be placed to decide if that is an intended placement or not. There is a related crash I found testing this bug, which I will link separately.

These combinators were placed with the same parameter requests: left first, then right.

01-19-2025, 11-56-34.png (22.52 KiB) Viewed 383 times

I used this blueprint to reproduce, but as far as I can tell it is reproducible anywhere that parameters are supported (buildings, vehicles, belts, combinators, etc.)
0eNqFUdtKxDAQ/ZVlntNlWzcLDfjiFwiKLyJL2kYN5FKTdLGU/Lsz3W1FRSUvkzkzc86cmaAxg+qDdgnEBLr1LoJ4nCDqFycN5Zy0CgQQkqRLRetto51MPkBmoF2n3kGU+YmBckknrc4D5s94dINtVMAC9tcgBr2P2OsdMeK8oirLLWcwgjjsthyJsC0Fb46NepUnjT1YGFVLPfFrjOSLKgbP2iQVvmcvUnoZMEC82KGEt0EalIx554PF5YnUUg1JFHA9JwZyCtfFl2npdcaZI409TdYdrCx3s5Wbe0IYIb8QoyGuW034X03ObOW72MyWQED5Q8CDxFMDadZJWcx/np6BkY3Cc8ONjLrd3C76EDnharMmfqjqfV1zvudVfVXm/AHrrL+t

factorio-current.log

(11.11 KiB) Downloaded 36 times

[kovarex]

Hello, this is all related to the same bug of clicking outside the bogs starting a new build, this have been fixed for the next release.