[2.0.44] Pasting Assembler Settings in Editor does not immediately overwrite Recipe

[eugenekay]

On today's episode of "Editor mode shenanigans", I found a (very small) difference in how Assembling Machines (or derivatives) receive/handle Settings Pasting while the Game is not Ticking. This is probably another intended corner-case; but as it was so surprising I am raising my hand to ask if this is a Bug or not.

What did you do?

0eNqVUsFOwzAM/ZXIJ5DSaV0pYuXIlRMcOGxoSlNvs9YmxUnZpqn/jrsxAQIh7RIlfn4vT88+QFl32DK5CMUBKgyWqY3kHRTw4Nu9WrJv1BOt1lFFrx5xGdVVWRu3uS6UevG8CcqEBHct2ojV3P1BekAXkdVVy5gEjEKcwzNG9YSWWpyDoqCsbwmre6Vsxyz9n+AAOR+VrdEwVqCBrHcBitkBAq2cqQfbzjQofk0I2JQ1uVXSGLsmh0kGvVBchTso0v5Vg0hTJDwpHB/7heuaElka9L9KGlof6JTNAUQwuRvlGvZQ5KO87/Uvvcmletk3PQ18TEDYW+8rdIldY4hwri/eOlPLb4I7z40E8YeD7EIH6Q8DknRkXy9KXJt38jw0yfwWZ2ORO+yHULfEx0RnqU71RKeveianzuQmKEVsxMHXommoTYkyOfgc8rAzUn1HDkcv+e1kejOd5rfZ+GY6nvT9BwKr4ig=

Copy blueprint

• New Scenario (or Load Attachment)
• Place three Assemblers, connected by a Circuit Network (or use Blueprint)
• Leave one unconfigured (Left)
• Configure a Recipe on one of them (Middle)
• Configure "set Recipe" on the last (Right)
• Shift+Right-Click the Right assembler --> Shift+Left-Click Left/Center assembles

What happened?
Middle machine accepts "Set Recipe" toggle, but the Recipe stays set until the Tick Once button is used.

Screenshot 2025-04-09 120404.png (313.62 KiB) Viewed 486 times

What did you expect to happen instead? It might be obvious to you, but do it anyway!
Recipe would instantly un-set if the machine is Empty and Idle (which it is, since this map has never Ticked).

Screenshot 2025-04-09 120425.png (344.51 KiB) Viewed 486 times

Does it happen always, once, or sometimes?

• When the game is not Ticking
• When a Recipe has already been manually set on the Pasted machine

I strongly suspect that the "Update" of the middle Assembler is being deferred until the next Tick, to permit an Inventory check, etc.... but this does not seem necessary to Defer since this Update can be made by the player anyway by clicking the "Change Recipe" button! This action instantly transfers any items to the Editor-Controller's inventory - so it is not 100% clear what is/is not able to be changed without a Tick occurring.

I have searched for "Set Recipe"; the previous results/reports which seemed similar are for actual Gameplay issues with unexpected Recipes. I hope it's not a duplicate!

Thank you for reading!

[boskid]

Thanks for the report however there are no bugs here. Copy settings does not change recipe of assembler if the machine has a recipe set by control behavior. This is intentional because if you would be copying settings between two machines that see different signals on the input, if the recipe would be copied then for 1 tick the machine with settings pasted would have wrong recipe set.

[eugenekay]

Copy settings does not change recipe of assembler if the machine has a recipe set by control behavior

For clarity, does "set by control behavior" mean "Player/Blueprint set the Recipe" (which is the case here), or is it referring to "changed by Circuit" (which did not happen; as no Tick occurred) ? I am just trying to grok what this means.


Thank you, I did not expect this to be a real Bug - it did/does seem inconsistent (even if only in my understanding of the Update/Tick cycle).

[boskid]

For clarity, does "set by control behavior" mean "Player/Blueprint set the Recipe" (which is the case here), or is it referring to "changed by Circuit" (which did not happen; as no Tick occurred) ?

When assembler has any circuit wires connected and the "set recipe" checkbox is set, then assembler is considered as having recipe set by control behavior and copy settings will not attempt changing recipe.

[eugenekay]

For clarity, does "set by control behavior" mean "Player/Blueprint set the Recipe" (which is the case here), or is it referring to "changed by Circuit" (which did not happen; as no Tick occurred) ?

When assembler has any circuit wires connected and the "set recipe" checkbox is set, then assembler is considered as having recipe set by control behavior and copy settings will not attempt changing recipe.

Ahhh OK, you are referring to the source of the copy/paste operation, as being in "Set by control behavior" state, so that's why it isn't being Copied over... I was thinking about things in terms of the Destination entity.

[boskid]

To be accurate, it is the copy target that rejects changing recipe. In this case copy settings consists of 2 separate pieces being copied: first is control behavior which will copy the "set recipe" checkbox from source to target assembler, and once this is set the recipe is copied if target has recipe not set by control behavior. You may observe this by copying settings from assembler with wires and "set recipe checked" onto an assembler that has no wires: "set recipe" will be copied but it will remain hidden and ineffective due to lack of wires, however the current recipe from the source assembler will get copied even if it was set by control behavior.