[2.1] Roboports should report ghost entities

[worph]

TL;DR

There should be a way to read unbuilt entities/ghosts from the roboports.

What

Currently, I don't know of a way to get which items are scheduled to be build but missing the actual item.
The ghost entity in the following example image, does not show up anywhere in the circuit output of the roboport.

grafik.png (721.32 KiB) Viewed 206 times

I would expect some way to show these like pictured below.
Now that we can separate outputs to red/green wires this is a prime implementation to use this feature with.

grafik.png (211.96 KiB) Viewed 206 times

Why

First of all, it's cool to tell your automall which items need to be built on demand.
But the more likely and better application is Aquilo (or any other planet that should be supplied by a mall in orbit).
Currently, especially on Aquilo, one has to keep at least one of every item on the planet surface and resupply that item once it's used, if you don't want to handle this stuff manually.

With this change, and some circuitry magic, I can cue up a large batch of buildings and the Cargo Landing Pad should eventually, if I programmed it correctly, request and fulfill all the projected items eventually.


(*edit: In case you are wondering: Changing the settings from "Read ... contents" to "Read ... requests" on the roboport changes nothing. I knew that before taking the screenshots, but I should have selected that option)

[robot256]

Previously:
viewtopic.php?t=133812 (in Outdated/not implemented)
viewtopic.php?t=39474 (very long thread where all the suggestions of the same kind were merged, except the one that was moved to outdated/not implemented)

[worph]

Missed those, mea culpa. The one from 2017 is a bit old anyway. But the one from last month is not only recent but pretty clear.
It begs the question though, how the game cannot know these things, but I digress.

[eugenekay]

It begs the question though, how the game cannot know these things

The Number of Ghosts in range of a given Construction RoboNetwork can be counted, but this is a potentially expensive operation as it requires searching through all Entities on a surface; potentially each Tick if you want to have an accurate Circuit output. More complexity comes from the fact that Construction RoboNetworks can overlap where there is not an overlap of Logistics Networks (which are merged into a single Network) - leading to inaccurate/duplicated Ghost Counts on both Circuits. Trying to add/remove a "running Total" each time a Ghost is placed/cancelled/Revived would require careful logic handling everywhere that Ghosts are interacted-with (Robots, Planners, Scripts, Events...) to ensure it stays accurate; or set you back to performing a potentially-slow "sweep" as above.

The current implementation scans "a few" Ghosts each Tick, and then creates a timed Notification. It performs well with tens-of-thousands of Entities pending.

[worph]

I don't think implementing an accurate list of those entities is in and of itself a hugely complicated problem. Sure you need to find all the edge cases and test it thoroughly. It's probably just too much work for relatively little benefit. I can totally see that.

[Ruuttu]

I understand providing an accurate list in real time would be expensive, but I also don't think it would be necessary. The robots take their time to work through the list of ghosts, and it makes intuitive sense that those with missing materials would be "discovered" at some point. A list which tracks and cross-references all the items and requests across the entire network in real time would seem like magic.

The roboport could provide a list which updates infrequently, and which isn't perfectly accurate even when it does, and I would still be perfectly happy. I can't imagine a legitimate use case where the signals for the ghosts would have to reflect changes immediately.