This is what I copy
This is what is pasted
This can be recreated in a fresh map using /cheat
Am I doing something wrong or is this a bug? It definitely obliterates my workflow.
[2.1.8] Quality configs lost in copy paste
-
darklich14
- Long Handed Inserter

- Posts: 96
- Joined: Sat Feb 24, 2018 3:07 am
- Contact:
Re: [2.1.8] Quality configs lost in copy paste
Are you using any mods?
If you want to get ahold of me I'm almost always on Discord.
Re: [2.1.8] Quality configs lost in copy paste
Similar issue, no mods.
The logistic connection condition gets the right parameter set to same value as the left one on BP copy-paste.
(steel > iron -> steel > steel)
This happens with logistic connection, circuit connection gets transferred properly.
Copying config by SHIFT+click works as expected, via BP copy-paste corrupts the second parameter.
Constant as second parameter seems unaffected.
The logistic connection condition gets the right parameter set to same value as the left one on BP copy-paste.
(steel > iron -> steel > steel)
This happens with logistic connection, circuit connection gets transferred properly.
Copying config by SHIFT+click works as expected, via BP copy-paste corrupts the second parameter.
Constant as second parameter seems unaffected.
Re: [2.1.8] Quality configs lost in copy paste
Thanks for the report. Issue is now fixed for 2.1.9.
Turns out that when i was fixing a different bug report (it was possible to parametrise blueprints in a way that puts fluids inside of logistic condition), i did a copy-paste mistake and when right slot in this condition has a signal, it was getting value of first signal.
Turns out that when i was fixing a different bug report (it was possible to parametrise blueprints in a way that puts fluids inside of logistic condition), i did a copy-paste mistake and when right slot in this condition has a signal, it was getting value of first signal.
-
darklich14
- Long Handed Inserter

- Posts: 96
- Joined: Sat Feb 24, 2018 3:07 am
- Contact:
Re: [2.1.8] Quality configs lost in copy paste
I figured there was some copy paste update due to 2.1.8 stuff that has some lonely conditional branch which is now being met again for 2.1.9 - any slated date for it yet?

