btw super-force-select for deconstruction planner allows you to mark entities, tiles, hidden tiles and tiles with supported entities in one fell swoop.

Thanks for the report, added the instruction to the tooltip for 2.1.0.

After some reevaluation I am moving this to minor -> it is a relatively minor issue with possible remification of the fixes.

This seems to have been solved some time ago, at least as of 2.0.71 I don't observe the undesired behaviour

Thanks for the report, fixed for 2.1

If i was correct and the cause of it was cancelling deconstruction of plants not removing player's colliding tile ghosts, then it is fixed for 2.1

The 1st and 3rd photo looks to be the issue mentioned, I don't think the 2nd is as well. I think I found the cause of the second one, but if you have a save or video I could confirm.

Thanks for the report, the issue is fixed for 2.1.0.

The cause was that we were incorrectly detecting collisions for tileghosts and obstacles which just "touch" the tile.

Thanks for the reports, fixed for 2.1.0.

Thank you for the report.

This was fixed since 2.0.45, I just forgot to resolve this report, sorry.

Fixed for 2.0.67. Thanks for the report.

Thank you for the report, fixed for 2.0.67

From 2.0.67 this should no longer happen, however ghosts that were never built in existing saves will not be affected, those you still have to fix manually.

Thank you for the reports. I think tracked down the cause, while we work on proper fix, you can "fix" your save by removing unconstructable elevated rail signals (like in the picture and on 4 more places). Let me now if it works for you or if the issues remain.

Ah. The previous fix was not working on rail-ghosts. This is now fixed for 2.0.65. Thanks for bringing it back up.

Thanks for the reports. It no longer happens in 2.0.65, most likely was the same cause as 129388

I cannot reproduce this on internal 2.0.61.

If I understand this correctly, it is the same issue as 128978

I see. Currently assembling machines are being treated (by default) as if they do not have direction (even for the purposes of LuaEntity::lueWriteDirection ). The exceptions to this as of now are if any of the following:

has asymmetrical collision box
has active fluid manager
its energy source ...

Thanks for making the report. Since 2.0.56 blueprints including spidertrons should be rotatable again.