[kovarex] [0.17.1] "'Item' is in the way" message should not appear for the same item placed

[wahming]

e.g. if you're placing transport belts, and you click on another belt in the same facing, you get the floating error message "Transport belt is in the way". This is unnecessary and irrelevant information. As a general rule, if whatever is in the way is the same object and the exact same positioning as what you're trying to place, skip the error message.

[kovarex]

Yes, I agree, that in this case, it shouldn't make the message.

[gamestefan]

I noticed that the same happens when pasting a blueprint over existing items using the new copy-paste features. Placing the blueprint holding shift does not give a floating message.

[BlueTemplar]

Should this be happening ?

[catpig]

Should this be happening ?

I think I would prefer it would let you overwrite in that situation, like with real belt placing.

[Reika]

Should this be happening ?

I think I would prefer it would let you overwrite in that situation, like with real belt placing.

Agreed.

[kovarex]

Should this be happening ?

I think I would prefer it would let you overwrite in that situation, like with real belt placing.

Agreed.

Ghost building tweaks like this is one of the bigger tasks for later

[Solinya]

e.g. if you're placing transport belts, and you click on another belt in the same facing, you get the floating error message "Transport belt is in the way". This is unnecessary and irrelevant information. As a general rule, if whatever is in the way is the same object and the exact same positioning as what you're trying to place, skip the error message.

In general I would agree, but there are some cases it's useful. For example, when building a stone wall through a forest, the tree sprites cover up tiles above them, so it can be hard to tell if there's a wall underneath all the trees. In this case, seeing "a wall is in the way" actually helped confirm I had a solid wall present as there's no way (afaik) to rotate the camera or see under the trees without removing them.

It's also been a little helpful when trying to upgrade e.g. red belt to yellow belt on belts full of items in the middle of a multi-belt bus, where it can be hard to tell which type is under the mess. Same with items where it can be hard to tell if they're a blueprint ghost or not (such as small power poles).

[TruePikachu]

I'm just curious, is there any particular reason why this is stickied?

[tehfreek]

It's probably one of those important-but-not-trivial fixes, so its visibility needs to be high.

[kovarex]

Acknowledged problem that isn't fixed right away, so it stays on the top and is not reported repeatadly.

[wahming]

Acknowledged problem that isn't fixed right away, so it stays on the top and is not reported repeatadly.

I suppose that means it'll be fixed next week instead of this week.

[Ultros]

Should this be happening ?

I think I would prefer it would let you overwrite in that situation, like with real belt placing.

+1 to the agree. This also applies to replacing a non-ghost entity with a ghost entity, which I think should also be allowed. Without modding reach, it is annoying to have to run over to rotate an item when your workflow deals with mostly remote bot placement.

[TruePikachu]

Should this be happening ?

I think I would prefer it would let you overwrite in that situation, like with real belt placing.

+1 to the agree. This also applies to replacing a non-ghost entity with a ghost entity, which I think should also be allowed. Without modding reach, it is annoying to have to run over to rotate an item when your workflow deals with mostly remote bot placement.

I'm not quite sure about directly replacing non-ghosts with ghosts, as it can mess up some workflows e.g. copy/pasting chunks of belt to extend busses. Maybe using a modifier key (Ctrl? Shift doesn't feel like a proper fit for this in all situations).

[bobingabout]

Place a gate over a wall (or wall over a gate) and it works fine.
Do the same with a ghost, error, cannot place gate, wall is in the way.

[kovarex]

Thanks for the report, it is solved for the next release.

[NickKsh]

Yes! Finally! Thank you kovarex <3