[2.0.20] Placing identical ghosts over entities marked for deconstruction doesn't cancel deconstruction

[IsaacOscar]

I don't know whether this is a bug or a feature request, but I think I recall it behaving differently sometimes.

1. If you mark something for deconstruction, e.g.

   

   11-19-2024, 14-27-19.png (861.96 KiB) Viewed 138 times

2. Then place a ghost of exactly the same thing on top of it (e.g. by pressing q from remote view then click in place), e.g.

   

   11-19-2024, 14-27-43.png (508.32 KiB) Viewed 138 times

3. It is still marked for deconstruction, e.g.

   

   11-19-2024, 14-28-05.png (280.69 KiB) Viewed 138 times

The above also happens if you go ctrl-x on the entity and then click it's current location (i.e. 'moving' it to it's current location).

Assuming you don't have another copy of the entity in storage, a robot will then come to the entity, and then the deconstruction and ghost will be cancelled (i.e. put it back to how it was before).

If on the other hand, you do have another copy in storage, a robot will come and take the entity away, whilst another one comes to put a new one in it's place.

I would expect the deconstruction to simply be canceled (which I seem to recall it doing in the past, but my memory is not perfect).

I guess replacing the entity with a fresh one might make sense if it's health is damaged, but it's really annoying when placing blueprints when some of the entities already exist, or when trying to cancel a move (instead of going q + ctrl-z, I often just move the entity back to where it was if I decide not to move it after all).

[Genhis]

Thanks for the report. At the moment this works as intended.