[2.0.34] Placement color for manual placing should reflect colors for blueprint placement

Bugs that are actually features.
Ashier
Burner Inserter
Burner Inserter
Posts: 8
Joined: Sun Jan 26, 2025 11:03 pm
Contact:

[2.0.34] Placement color for manual placing should reflect colors for blueprint placement

Post by Ashier »

Hello!

There are inconsistencies for placing items over existing items.
As shown below, when hovering to place an item over an item that already exists, it is marked as red. This also happens with ghosts.
02-18-2025, 21-32-58.png
02-18-2025, 21-32-58.png (35.63 KiB) Viewed 285 times
02-18-2025, 21-33-35.png
02-18-2025, 21-33-35.png (55.79 KiB) Viewed 285 times
However, when attempting to paste a blueprint, they show up as blue.
02-18-2025, 21-33-49.png
02-18-2025, 21-33-49.png (36.76 KiB) Viewed 285 times
02-18-2025, 21-34-09.png
02-18-2025, 21-34-09.png (37.7 KiB) Viewed 285 times
They should follow the blue rule always in my opinion. Red should mean "cannot place here" and blue should mean "already exists here". I understand the code for blueprints and manual placement is not-interconnected, but would it be possible to just change the highlight color when the item is the same as existing, to blue?
Rseding91
Factorio Staff
Factorio Staff
Posts: 15712
Joined: Wed Jun 11, 2014 5:23 am
Contact:

Re: [2.0.34] Placement color for manual placing should reflect colors for blueprint placement

Post by Rseding91 »

This is not a bug. Please do not post suggestions in the bug reports section.
If you want to get ahold of me I'm almost always on Discord.
Ashier
Burner Inserter
Burner Inserter
Posts: 8
Joined: Sun Jan 26, 2025 11:03 pm
Contact:

Re: [2.0.34] Placement color for manual placing should reflect colors for blueprint placement

Post by Ashier »

Rseding91 wrote: Wed Feb 19, 2025 10:49 am This is not a bug. Please do not post suggestions in the bug reports section.
I'm so sorry! I figured it wasn't intentional and was a bug, that's my bad. I will recreate the topic in the suggestions forum.
Post Reply

Return to “Not a bug”