[Lou][2.0.28] Placing quality building over common building ghost removes module slot requests.

This subforum contains all the issues which we already resolved.
sben
Long Handed Inserter
Long Handed Inserter
Posts: 57
Joined: Sat Nov 23, 2024 5:33 pm
Contact:

[Lou][2.0.28] Placing quality building over common building ghost removes module slot requests.

Post by sben »

Given I have a blueprint including common big mining drills with modules and I place this blueprint.
If I place quality (uncommon) big mining drills over the common big drill ghosts, the module slot request get lost.
kittykammings
Factorio Staff
Factorio Staff
Posts: 14
Joined: Mon Nov 04, 2024 12:34 pm
Contact:

Re: [2.0.28] Placing quality building over common building ghost removes module slot requests.

Post by kittykammings »

thank you for report.

could reproduce with assembling machine as well 2.0.28
User avatar
Lou
Factorio Staff
Factorio Staff
Posts: 255
Joined: Mon Nov 30, 2020 10:50 am
Contact:

Re: [Lou][2.0.28] Placing quality building over common building ghost removes module slot requests.

Post by Lou »

Once again thanks for the report. Fixed for 2.0.39
avenger
Burner Inserter
Burner Inserter
Posts: 8
Joined: Tue Mar 25, 2025 1:56 am
Contact:

Re: [Lou][2.0.28] Placing quality building over common building ghost removes module slot requests.

Post by avenger »

I have been noticing this issue the last few days. And once I upgraded to latest (2.0.42) I paid attention whether it was working fine.

Well, it sort of is... right? It keeps the module request slots but even within personal/logistic range the request is never responded to. The bots simply ignore it.

I reproduced this with an assembling machine 3 (uncommon, hereby calling AM3) blueprint with 4x quality MK2 modules. I only had Rare AM3s in inventory/logistic network. Ctrl+c the uncommon one, ctrl+v, then place over the rare one. The module requests are there, but they simply are never attended to. In my scenario I tried this in Gleba. Once I move to other planets I will most likely test this again, again, and over again again so I will post an update here.

Edit: this was reported on a dedicated issue Mar 17 and has been fixed in 2.0.43 (127575)
Post Reply

Return to “Resolved Problems and Bugs”