[Blueprints][Parameters] Differents Signals in a Blueprint merge together when they share the same value

[Sin_K]

Hello there

I'm here to report a bug that completly break blueprints' paramaters.

Here is the video

https://youtu.be/ectko3hPbG0

Here is the save file (Editor 1)

Here is the blueprint (Blueprint Test 1)

It is important to note that the video was recorded the 2025/06/08 on the public version of Factorio Space Age

With a LTN mod that was up to date at said day.

It is also important to note that while this bug was found while using LTN, the problem lies in Factorio Blueprint Paramaters and I believe a similar issue can be found in a vanilla use case.


Now, the lenghy explication, it's also possible to just watch the video instead but here it is anyway :


Basicaly, I want 3 different signals :
Network ID,
Limit Train,
Min Train Lenght

To all be prompted when placing a blueprint. The prompt shouldn't ask for the nature of the signal, which is what Param0 does and it used for defining the filters of the inserters, but instead, on afore-mentionned signals, to prompt them and ask them their value.

The problem appear because I want all three different signals to have the same default value of 1, but I still want the prompt to pop and individualy ask me if I want to change any of theses values.

The problem is that the different signals, upon having the same value, merge together, as you can see beetwin 1:05 and 1:16.

Once the merging is done, the blueprint is basicaly unrecoverable.

The blueprint is pretty simple, but I imagine meeting this problem on a larger blueprint can make a grown man cry.

After the merging, the prompt that worked before STAYS as GHOST paramaters that don't actualy do anything.

You know a paramater is a ghost based on two facts :

When mousing over them in the parameter window, the tooltip doesn't pop up (visible beetwin 1:40 and 1:55)

If you change the value when the prompt pop up, it doesn't do anything (visible beetwin 1:20 and 1:40)


To rub salt on the wound, I realized while writing this post that it's even worse than just useless, ghost parameters.

The new, merged parameter, doesn't work either.

You can see at 1:44 that when I mouse over "Network ID", the paramater shows that it impact 4 signals, yet it doesn't work.
At 1:26, I placed the blueprint down and CHANGED in the PROMPT Networkd ID value to be 2, yet nothing actualy happened and the values stayed at 1.


I'm open to answer any question and help however I can to have this issue fixed ASAP.

Even if having multiple signals indepedently carry the same base value wasn't part of the feature plan, right now, it's a big mess.