[2.1.9] Upgrade planner requests wrong modules for assembling machine

[Nwing]

0eNrVU9tqwzAM/Rc9J9CmSZca9iVjFNdROoNvs5WyEvLvk8nCWiiMbE8DP8g650g6Ao0whHOUHR6Dkc5hBDFCQiLtzinHVoaAkcOXEfrobc7RNSAIQEearlCAkzb/ZUpoT4aVpZXqTTsst4y+D9JkngDno5WGU8rbIKMkz+3gGaYCyK8rvGPU+m4weEzG0zzfFz1EBhTpCxcpZxK3+AnO75Un0a7DDxCbrFhvuPo/hv8C3yyqzdw7N5rQfnvBvtdKo1M3xRfttnqw5Xv5g/a/XPKKsfazwSwQy4GUy4EUcOGD0N6BaPbVoamruj08tfWumaZPHg8jaQ==

Copy blueprint

when the above upgrade planner blueprint is used on an assembly machine 1 or 2 the modules are set to productivity 1's every time. expected behavior is for empty slots to be efficiency 1's and productivity 2's to be efficiency 1's.

Steps to reproduce:
1. use the above blueprint on any assembly machine 1 or 2 (existing modules are irrelevant for assembly machine 2) and the shown output and actual output are an assembling machine 3 with all modules as productivity 1's.

The upgrade planner blueprint works as expected when used on an assembling machine 3.

[Loewchen]

The specifically set module loadout in the entity not being overwritten by the general empty module slot upgrade is clearly intended, you can simply not define modules in the entity if you don't want them.

[Nwing]

My apologies, I figured it out. I previously had set the modules in the To field and forgot I had set them. When I looked at the blueprint later I didn't realize the module slots under entity settings were configured.

I also learned that the module slots under entity settings have precedent over the empty module slot to something else regardless of placement order in the blueprint.