Factorio Forums

On Gleba, at -468, -1680, i have this ghost building i force-built that for some reason isnt marking the plant next to it for deconstruction:
the plant is well within the construction zone of the next roboport.

Manually deconstructing the plant causes the roboport ghost to be assigned and built right away:
This has happened before a couple times, only on gleba. I don't know if its the same plant causing it each time.

Save below:

https://drive.google.com/file/d/1_IzH1d ... sp=sharing

Thanks for the report.

Is it possible, that you unmarked the plant for deconstruction? There is a known bug fixed for 2.1 that causes colliding tile ghosts not to be removed when unmarking the plant for deconstruction (131087).

If you manage to figure out a different reproduction, let me know.

Not manually, i didn't. You can reproduce it in this save if you manually remove the ghost roboport and re-build it without touching the offending plant.

This bug (linked in 131087) looks like the one i'm experiencing:
130907

If 2.1 fixes this issue on my save, then this is for sure resolved.

The roboport itself does not collide with the plant, so removing only the roboport ghost and rebuilding it shouldn't mark the plant for deconstruction - the issue is, it is already in wrong state, because of the tile ghosts (which need to be revived for the roboport to be buildable) colliding with the plant and the plant not being marked for deconstruction.

If you remove both the roboport ghost and the tile ghost, can you reproduce it from that state? I tried and the only way I managed was the one I meantined.