What did you do?
Place any assembling machine (anything that takes in a recipe)
Set a logistic network condition of Parameter 0 < 250, or anything involving a parameter
Create a blueprint of this and attempt to parameterize it.
What happened?
The parameterization screen only recognized other uses of the parameter 0. When pasting the blueprint the logistic network enable condition is empty.
What did you expect to happen instead?
Parameterization screen to recognize and allow control of the parameter used in the logistic network enable condition.
Does it happen always, once, or sometimes?
Sometimes it doesn't recognize the parameter and sometimes it does. It doesn't seem fully random, but chaotic, stuff that seems like shouldn't impact it do
[2.1.9] Parameterization of Logistic Network Enable Condition not Recognized
-
NotTheWaffle
- Manual Inserter

- Posts: 4
- Joined: Sun Jul 05, 2026 3:29 pm
- Contact:
[2.1.9] Parameterization of Logistic Network Enable Condition not Recognized
- Attachments
-
- factorio-current.log
- log file
- (15.82 KiB) Downloaded 7 times
Re: [2.1.9] Parameterization of Logistic Network Enable Condition not Recognized
Thanks for the report however I am not able to reproduce any such issue when I test. Can you show a video of the steps you're doing? I think there's something missing that I'm not doing.
If you want to get ahold of me I'm almost always on Discord.
-
NotTheWaffle
- Manual Inserter

- Posts: 4
- Joined: Sun Jul 05, 2026 3:29 pm
- Contact:
Re: [2.1.9] Parameterization of Logistic Network Enable Condition not Recognized
Of course. Attached is a video of me showcasing the bug.
- Attachments
-
- loginetParameterization.mp4
- (22.38 MiB) Downloaded 17 times
Re: [2.1.9] Parameterization of Logistic Network Enable Condition not Recognized
I see. You’re placing the recipe parameter 0 in the item-condition. Since the logistic condition only works with items it ignores the recipe parameter.
The intended way is to make a blueprint and in the GUI you enable parameter for both the condition and recipe - separately.
The GUI probably shouldn’t let you place the recipe parameter in the condition.
The intended way is to make a blueprint and in the GUI you enable parameter for both the condition and recipe - separately.
The GUI probably shouldn’t let you place the recipe parameter in the condition.
If you want to get ahold of me I'm almost always on Discord.
-
NotTheWaffle
- Manual Inserter

- Posts: 4
- Joined: Sun Jul 05, 2026 3:29 pm
- Contact:
Re: [2.1.9] Parameterization of Logistic Network Enable Condition not Recognized
Oh, that explains why it would work sometimes and not others.
Thank you for clearing up my confusion.
Thank you for clearing up my confusion.
-
k1ngjulien
- Manual Inserter

- Posts: 3
- Joined: Wed Sep 24, 2025 11:41 am
- Contact:
Re: [2.1.9] Parameterization of Logistic Network Enable Condition not Recognized
This still works when the (0) is set in "Enable If" with Circuits, and has worked in previous version with the logistic connection.Rseding91 wrote: Sun Jul 05, 2026 10:25 pm I see. You’re placing the recipe parameter 0 in the item-condition. Since the logistic condition only works with items it ignores the recipe parameter.
The intended way is to make a blueprint and in the GUI you enable parameter for both the condition and recipe - separately.
The GUI probably shouldn’t let you place the recipe parameter in the condition.
I just stumbled across this because my logi bot mall assembler blueprint seems to have broken in 2.1! I can share the blueprints if you'd like
-
k1ngjulien
- Manual Inserter

- Posts: 3
- Joined: Wed Sep 24, 2025 11:41 am
- Contact:
Re: [2.1.9] Parameterization of Logistic Network Enable Condition not Recognized
ok its much stranger, i recreated the blueprint and now it works again...
broken version, copied from old save:
^^ here i think it puts it in circuits instead of logistics, maybe?
recreated version, should be pretty much identical apart from maybe parameter names:
broken version, copied from old save:
Code: Select all
0eNrFlttymzAQhl9Fo8sOZGwOacK0V3mF3jUZRsBiqwaJ6JDE4+Hdu8JA40DsOG3H4xsjrfb7d7VaaUezykKjuDA02dECdK54Y7gUNKG5YqXhYkW4JrkURsmqgoJkW1LJFdeG50SAeZZq002DMPpelLaqtoRZI2vmLJTMJGFaQ51VoDzyy2pDGp5viFkD4QZqspWWPDNhiJGkY17diw1AozuTTL6QNatK4jx7RAGuR0GMZLYsQZFSqg7i4NSjHKVomvzcUc1XglUuLMFqwHicVSOVoS2aiQJeaLJsvRnDXi6G7tcsX3MBfvhqUdA+eBSj5YbDHtV9bFNh6wwUevWOevJoIzXfJ3lH0eF1eBV7dEuTaHEVI0dBzhu3vGEK/RhQ/oIOw+mjZRXScFpIVaNwF8MbBcGoILPVxudCg0I3M+hgQAcdut/nNIM1e+JSObOcq9xyk4JguIcFTYyy4I3DuKQYXZZcaZNOMvo6kD1FG+ZqLlgs3GftDIzD0W+9gYDcpEamQ62lfa0N+HH8gH/CczuTq3DMlUY7tgI/X2ORHctV2G/To0XDtOQVRqadlUbRfCjAocY8OlocjM7kxqOT3X0TxPduwLoI0QWvXUGnpZK1W8HsE9e0fcDfTKDRh4siOiyKgqt9XDS5mfEbj377jGAo76Uw+s8pXP6jFHojJZihBOdRgtOUcIYSnkcJT1OiGUp0HiU6TYlnKPF5lPhIaXvUKKbXqZAmHQqub0qtmx2h+2Ix266V8oKOsn5IcufumcTdF8V7R9A/aCynxXdHrqf1R8Mb/iQU29EfAXcuyoS+WtDJe6Nl+Rda3GW1UlBwPKu+LCct+IhSh8VLtbYVc8sWKV9+WTrxBTSAO+z2p0v2cfXBZdQHE/XBZ9SHl1EfTtSHn1EfXUZ9NFEffUZ9fBn18UR9fEr9iWPO6np/0Kc+sE+5t6+7i8cHOL5pWAb4bOreNt0benw44+QTdrQuEfF1cBtHQXRz+/UmCuO2/Q1UsvYZ
recreated version, should be pretty much identical apart from maybe parameter names:
Code: Select all
0eNq1Vs2O2jAQfpVqjpWzgsRuIWoPVV+ht2oVGWJgtImdtR1ahPLuHSeQ7ZIsbEQrLmEy8/14ZgxHWBW1qixqD+kRcG20g/TnERxutSxCTMtSQQrSOVWuCtTbqJTrHWoVJdAwQJ2r35DOm0cGSnv0qDqE9ssh03W5UpYS2BlpVRdPEWqnrKcXDCrjqMroQEZIyfJBMDhAGvHkQRADafLWFNlK7eQejQ15FNNq7TNvssJs0XlcZ1r5X8Y+QeptrRj0ccrNe4INWuezgbtKWnogPdEMOkrnZTiTeDYLX8uQ4AM3fIGmadjAX9z7c5Qntypa75TzV/3FrT+rnmvKzDZYkAAX0hx5w3MrzifMoM94FR2xwOC5lgXJo7g2tiSvFy6+toE6WCQILCtjSYE1ZaiQ9R4dNI/0GXGasKszMTDMZ71hcTK8xmoouQtnA+UjEvh7h4nPL4YpR9udLaSLEWDRA5+6Qtre6ONf0P+pj/N/1EfWs8QjLPE0lvg2SzLCkkxjSW6z8BEWPo2F32YRIyxiGou4sl8MvJVul2njs/PE5d0N1oS3PWk3LP7Q7g3m0Mv6YT58t3LjUwpR/PIqe11zkRAGjJbXqhxpDyKzmVYe31ee3FfO7ysX7y8/XQ7s/JAC/Sq8dOBbWYZGp9dLwllvaFTqQgamWYbzj0FDripFoxYGpe36VdoBRjwZIxlgJJMx+ACDT8YQAwwxikFLgF6FtXn5p8JgTxvRXsXiU7wUPOaL5ecFT0TT/AE1XeuS
-
NotTheWaffle
- Manual Inserter

- Posts: 4
- Joined: Sun Jul 05, 2026 3:29 pm
- Contact:
Re: [2.1.9] Parameterization of Logistic Network Enable Condition not Recognized
I ran into it while updating my mall blueprints too.
Mine before
Mine After updating them
Yea, I think that 2.0 probably in some capacity supported logistic network conditions by recipes, which seems to have been removed. IMO a good change.
I would love some more standardization of what types of virtual signals can be placed where. Like limiting which signals are choosable for a parameter based on its usage (currently you can make fluid level conditions on trains with non fluids)
I think that the circuit system in Factorio is both amazing and terrifying. I would really love a way to say "this parameter is a recipe" or "this parameter is a fluid" in the parameterization screen. Additionally, changing which fields (like the currently available p0_i0, p0_i1, p0_t) are accessible based on the parameter type would be nice. Maybe a mod idea but it seems a bit more integral to the engine rather than something implementable with a mod.
Mine before
Mine After updating them
Yea, I think that 2.0 probably in some capacity supported logistic network conditions by recipes, which seems to have been removed. IMO a good change.
I would love some more standardization of what types of virtual signals can be placed where. Like limiting which signals are choosable for a parameter based on its usage (currently you can make fluid level conditions on trains with non fluids)
I think that the circuit system in Factorio is both amazing and terrifying. I would really love a way to say "this parameter is a recipe" or "this parameter is a fluid" in the parameterization screen. Additionally, changing which fields (like the currently available p0_i0, p0_i1, p0_t) are accessible based on the parameter type would be nice. Maybe a mod idea but it seems a bit more integral to the engine rather than something implementable with a mod.
