[2.0.76] Cloning belts doesn't respect control behavior

[Puke]

04-30-2026, 22-07-17.png (267.58 KiB) Viewed 206 times

04-30-2026, 22-07-22.png (246.07 KiB) Viewed 206 times

The belt is disabled, the circuit configuration is the following :

04-30-2026, 22-07-48.png (270.62 KiB) Viewed 206 times

But when the belt is cloned, the item on the belt moves.
I would expect the item to NOT move since the belt that is cloned is supposed to be disabled by circuit control.
There is no way that I'm aware of to stop / "disable" the belt before cloning.

[Loewchen]

89035

[boskid]

At a first glance i think this behavior is due to active state not being cloned so it takes 1 tick for the new belt to update the behavior and make it disabled. Given that a default state of a belt is to be active, in that 1 tick the item is allowed to move. I am feeling uneasy on this because attempting to clone active state could fail in so many weird ways, for example by cloning a belt in a way that does not preserve wires (because entity at the other end of a wire is not included in a clone) would need to be correctly handled by not copying active state since there would be no notifications for wire removed (there was no wire added to be removed) and the behavior would never update (since it would never need to) and so active state clone would need to be heavily guarded. Fixing this would require some heavy thinking as to not introduce new bugs.