Changing Assembler Speed can lead to inserters deadlocking

BloodStainedCrow
Manual Inserter
Manual Inserter
Posts: 1
Joined: Wed Jun 10, 2026 2:03 pm
Contact:

Changing Assembler Speed can lead to inserters deadlocking

Post by BloodStainedCrow »

The maximum output an assembler crafts to depends on its crafting speed, and inserters will only insert items when the output is less that the maximum output on all crafting outputs:
06-10-2026, 16-27-56.png
06-10-2026, 16-27-56.png (1.1 MiB) Viewed 333 times
The bug is that, if the speed modifier on the assembler changes after the fact (e.g. by placing a beacon, or adding a module), while the output limit gets increased, the waiting input inserters do not get woken up:
06-10-2026, 16-21-28.png
06-10-2026, 16-21-28.png (808.37 KiB) Viewed 333 times
Note that the output inserter here is limited to full swings like this:
06-10-2026, 16-22-24.png
06-10-2026, 16-22-24.png (80.22 KiB) Viewed 333 times
A newly placed inserter *will* still insert items, showing the inconsistency:
06-10-2026, 16-23-20.png
06-10-2026, 16-23-20.png (693.25 KiB) Viewed 333 times
As soon as the output changes (either by other inserters filling the input or by manually changing anything) the previously stuck inserter will wake back up.

Annoyingly this issue can happen without adding new beacons/modules when the power drops low, reducing beacon speed modifier. Then the inserters might get stuck, and even when the power returns will not go back to running normally. (This is what happened to @Bamckup who originally encountered this issue)

My guess is that the change in assembler output limit does not wake up any waitlisted input inserters waiting on this slot changing. Ensuring this wakeup would fix this issue.
Rseding91
Factorio Staff
Factorio Staff
Posts: 16863
Joined: Wed Jun 11, 2014 5:23 am
Contact:

Re: Changing Assembler Speed can lead to inserters deadlocking

Post by Rseding91 »

Thanks for the report. After thinking about this one more (this issue has come up in the past without a nice fix) we found a solution and this is now fixed for 2.1.
If you want to get ahold of me I'm almost always on Discord.
Post Reply

Return to “Fixed for 2.1”