Show logistic range for ghost robotports

[Charidan]

• The problem
  • Placing multiple roboport ghosts is very frustrating as the ghost roboport does not emit a coverage prediction, making it impossible to tell how far to place the next roboport to make a max-range connected network without memorizing distances.
• The solution
  • Ghost roboports should display logistic coverage, at least while the hand-object is a logistics entity.

[SupplyDepoo]

+1

[Madman666]

Please do this, i so hoped 2.0 would have this feature. I know we can use blueprints to place roboports with connecting logibot network coverage, but its incredibly inconvenient, when you dont use that trick.

[IsaacOscar]

This isn't limited to roboports though, everything with a range: asteroid collectors, minjng drills, power poles, turrets, etc.

This is why I usually wait for them to be built before making another ghost, but this is impractical on space platforms....

[pinecoffin]

I'm really surprised this issue is still in the game. It's really frustrating!
Please please please change this Wube.

[BraveCaperCat]

Show entity "ranges" for entity ghosts, please!
This can even include lightning rod and gun turret ranges, mistakes in which could be very hard on the average player. This is in comparison to not so difficult to fix problems like Roboport ranges.

Think about a scenario where someone has been constructing a Nauvis base when they accidentally mis-place a ghost of a gun turret (which later gets built) or even worse - builds the wrong quality ghost of a gun turret (which later gets built) then realises that biters broke through their defences because of a single (or few) mis-clicks. However, while the issue may be harder to diagnose for the roboport issue, the result of not fixing it isn't as bad.

[fazol]

+1

[picklock]

+1

[BraveCaperCat]

+1,000,000?

[Meehael]

+1

[FatCat0]

+1

[mr_abomination]

+1 this would be very nice