[2.0.72] Buffer/Requester chests disabled by circuit make one request when placed by blueprint or ctrl+v

[nekizalb]

1. What did I do?
When placing a requester or buffer chest with active requests, but the chest is disabled by circuit condition, the chest will still make 1 request before being disabled by the circuit condition.

2. What happened?
In the attached example, I have a requester and buffer chest requesting Artillery shells, disabled by circuit [Iron Plate] > 0. The chests correctly show disabled and do not request the shells.

12-31-2025, 14-06-56.png (304.55 KiB) Viewed 139 times

However, if you copy paste them, or place the blueprint in the character's inventory, the newly placed chests will each receive some shells before requesting is disabled. In this image, you can see the copied chests on the right received shells, but the buffer and requester both show disabled, and are no longer requesting more shells.

12-31-2025, 14-09-26.png (1.49 MiB) Viewed 139 times

3. What did I expect to happen?
As the chests were blueprinted with a circuit that could never be active, I expected no deliveries to occur until the signal changed. In my original world, I had an actual control that would enable the chests when appropriate. For the demo world, I just set a condition that could not possibly be true to limit possibilities.

4. Does it happen always, once, or sometimes?
I have noticed while writing this report that not always both chests get deliveries when pasting two chests. But most often, both chests receive the items. And I always observed at least one of the chests being delivered to.

[Rseding91]

Thanks for the report however this is simply how circuit logic works for entities. It takes one tick for values to propagate to the entity and apply any enable or disable logic.

[nekizalb]

Appreciate the fast reply. That make sense in principal, however, I do have one follow-up. If I paste a circuit disabled inserter, shouldn't it also make one swing if valid source and target on the first tick too?

For example, if I cut and paste this inserter, since it doesn't get disabled until tick after placement, shouldn't it move one shell before being disabled? Or do inserters just have a difference here?

12-31-2025, 14-52-24.png (73.08 KiB) Viewed 115 times

If I hook up a pushbutton, I can see that a single tick of enabled condition is enough for a full swing, so I'm just confused on the behavior difference in this case, if the entity is enabled on the first tick. Unless inserters don't try to swing on the tick they're placed?

Thank you again for replying!