[2.0.73] plant on gleba not being marked for deconstruction in force-build

[jimga150]

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:

01-26-2026, 20-59-02.png (1.64 MiB) Viewed 420 times

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:

manual_deconstruct_plant.gif (407.9 MiB) Viewed 420 times

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

[Lou]

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.

[jimga150]

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.

[Lou]

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.

[jimga150]

Ah, i think i found the issue.

After i remove the roboport and the three landfill ghosts:

If i then force build just a roboport, it gets marked for deconstruction.

If i go into the blueprints (see "gleba roboport outpost") and force build that such that the roboport is where the ghost used to be, it also marks the plant for deconstruction.

However, the way i placed it was by using a copied set of 4 roboports + power lines. The save should have it in the clipboard, hopefully: use paste and line up the pasted buildings with where the ghost was, then force build. In my test, this did NOT mark the plant for deconstruction.

[Lou]

..
However, the way i placed it was by using a copied set of 4 roboports + power lines. The save should have it in the clipboard, hopefully: use paste and line up the pasted buildings with where the ghost was, then force build. In my test, this did NOT mark the plant for deconstruction.

I followed your instructions but the plant was marked for deconstruction every time. (Which would be in line with my expectation since clipboard is just a blueprint). If can still reproduce this, can you maybe make a video or more detailed steps?

[jimga150]

I tried getting a video of it, but on both my machines (one windows 10 and one mac OS 26) the bug suddenly stopped happening. I'm still on 2.0.73. I'm not sure why it stopped occurring now.

I'm quite certain i didnt manually un-mark the plant for deconstruction, but without being able to reproduce it naturally I can't demonstrate it.

I suspect that this plant was in an unexplored chunk when i pasted the clipboard, which may have to do with why this state happened in the first place. I'm having trouble recreating those conditions though since my last permanent save is too far back to reliably hit the same spot with this object.

Sorry to give you the runaround, thank you for your help!