Hey,
I am trying to build a parametrized Blueprint for an Assembler with requester / passive Provider Chest. The contents of the requester Chest are supposed to be set based on the selected recipe, while the recipe is supposed to be chosen when placing.
This is my setup:
I am using the automatically available parameters pN_i1 etc which are supposed (my understanding at least) to give the item counts per craft for ingredient1, ingredient2 etc.
So with the formulas in the image I would expect to have a requester chest with all ingredients set to 2 cycles worth. However placing this always sets all counts to the count of the first ingredient in the list. Using a Mk1 Assembler gets this result:
Expected Result would have been to get:
18 Iron Plates
10 Iron Gears
6 Green Circuits
The blueprint string:
0eNrNlk2PmzAQhv/Kao6VWQXzoYLUQ//BHvZWrZABJ7EKhrVN1DTiv3fM124Sa7ulFy4JceznfWc8Y3yBvOp4q4Q0kF5AFI3UkP64gBYHySo7JlnNIQWmNa/zSsiDV7PiKCT3KPQEhCz5L0j9/oUAl0YYwUfC8OOcya7OucIJZCblXfXTE1JzZfAPAm2jcVUjrRiSaOg/RgTOkEbRY4QKpVC8GCeEPbkD0wWs+GvHNUK94ojfLjS9Rk8rsr2ocJm20/SoNcYwB0dgmXE1Ogm3TOGDFfZR9LVjFRrEcdmoGpNIoGhqO8c06Be+DQOdzfjOxjPhqANH1+MCBy5YjwsduHA9LnLgovW42IGL/xX3YkvYKKaPmWxMNldTCalRHe8dpfeWY2d33NdfkMz1F0/1V4j22vYO5uHszr3Dwtu+7Jk2n2ur+LatfOogv98ircWJe61qTqL8VHuNEjmz/WnTusQ3dpA5D1GLEiH4cRv/FLiHp1G5CPx9L4ct+gDt/wfaHnQHxUuBWfKa/Y3ld8JT+sj8kIKNaI/crmJ22S4T/hdbHCVvOZavLb6hwD42T7dinq4wH2zFfLDCfLgV8+EK89FWzEcrzMdbMR87zeO5Jgyv7ZVmuUQRqFjO8eIET6OcEr95+fBMH76Pr4hB6oQH4RBKFNMkTJLoqx8kyS7s+z+hGCnN
[2.0.72] Parameters (pN_i1, PN_i2 etc) in Blueprint do not calculate correctly
-
Trommelbohne
- Manual Inserter

- Posts: 1
- Joined: Thu Dec 25, 2025 10:09 pm
- Contact:
Re: [2.0.72] Parameters (pN_i1, PN_i2 etc) in Blueprint do not calculate correctly
The issue is that you've assigned all request counts the same value; give them all distinct values and the replacement will work as expected.
Fixed blueprint:
(Could the parametrization UI check and point out that some rows use the same value and will be merged / have no effect when pressing confirm?)
Fixed blueprint:
(Could the parametrization UI check and point out that some rows use the same value and will be merged / have no effect when pressing confirm?)
