"Dry run" mode for Assembling Machines via "No Item" signal
Posted: Mon Apr 20, 2026 12:10 pm
I suggest allowing Assembling Machines to accept the "No Item" signal (the internal "Null" item) as a valid recipe via the Circuit Network. This would enable a "test mode" or "dry run" for assemblers without requiring actual ingredients or producing outputs.
Details:
Trigger: When "Set Recipe" is enabled and the assembler receives a "No Item" signal.
Behavior: The machine enters a working state and consumes electricity as if it were crafting. No resources are consumed, and no items are produced.
Circuit Interaction: The machine should still output signals like "Read working status" and "Read recipe finished."
Use Cases & Benefits:
Currently, it is difficult to accurately count the total number of functional assemblers in a large-scale build using only the Circuit Network, as machines are often idle due to resource bottlenecks or full outputs.
Implementing this "dry run" would allow for:
Fault Detection: Automatically detecting if a machine has been destroyed or disconnected (e.g., "Expected 30 active signals, but only receiving 29").
Scalability Management: Checking if a new production block is correctly wired before providing it with expensive resources.
Throughput Analysis: Measuring theoretical maximum power consumption or timing logic cycles without wasting materials.
This feature would significantly enhance vanilla automation for megabases and complex Space Age logistics without the need for external mods.
p.s. also Fully Automated Production Analysis: This allows for the creation of universal circuit controllers that can be connected to any unknown sub-factory to automatically calculate its potential capacity and identify idle machines without any manual oversight or external mods.
Trigger: When "Set Recipe" is enabled and the assembler receives a "No Item" signal.
Behavior: The machine enters a working state and consumes electricity as if it were crafting. No resources are consumed, and no items are produced.
Circuit Interaction: The machine should still output signals like "Read working status" and "Read recipe finished."
Use Cases & Benefits:
Currently, it is difficult to accurately count the total number of functional assemblers in a large-scale build using only the Circuit Network, as machines are often idle due to resource bottlenecks or full outputs.
Implementing this "dry run" would allow for:
Fault Detection: Automatically detecting if a machine has been destroyed or disconnected (e.g., "Expected 30 active signals, but only receiving 29").
Scalability Management: Checking if a new production block is correctly wired before providing it with expensive resources.
Throughput Analysis: Measuring theoretical maximum power consumption or timing logic cycles without wasting materials.
This feature would significantly enhance vanilla automation for megabases and complex Space Age logistics without the need for external mods.
p.s. also Fully Automated Production Analysis: This allows for the creation of universal circuit controllers that can be connected to any unknown sub-factory to automatically calculate its potential capacity and identify idle machines without any manual oversight or external mods.