[2.0.21] Number of Missing Construction Materials Keeps Changing

[IsaacOscar]

Bassically, I wanted to upgrade all my express belts to turbo belts on Nauvis, but before shipping them over from Vulcanus, I want to count how many I need.
So I used an upgrade planner to upgrade all the belts to turbo.
Now as I haven't got any turbo belts, underground belts, or splitters on nauvis I expected to get an alert for missing construction materials like so:

Screenshot 2024-11-26 175828.png (105.22 KiB) Viewed 526 times

Unfortunately the number keeps rapidly changing, for example a few seconds later:

Screenshot 2024-11-26 175832.png (90.26 KiB) Viewed 526 times

If I take a blueprint of the area however, it does show a fixed count (4.6k belts, 474 underground belts, 98 splitters).

I'm also experiencing the "Not A Bug" 122131, which may be the cause of the numbers changing.

[Loewchen]

It's not showing the number of missing items, it's showing the number of alerts for missing items. Alerts are only generated if the game tries to place an item and fails and then persist for a few seconds, if it has not tried to place any specific item for a while there will not be an alert for it.

[IsaacOscar]

It's not showing the number of missing items, it's showing the number of alerts for missing items. Alerts are only generated if the game tries to place an item and fails and then persist for a few seconds, if it has not tried to place any specific item for a while there will not be an alert for it.

Ahh I see.
When I have a much smaller number of construction jobs, the number remains constant, which is why I was confused here.
I still think this behaviour isn't very good, but I understand if it would be very slow for it to try and keep an accurate count. (i.e. every tick, try and assign every job?)

[IsaacOscar]

Also, the listed number of "entities missing construction materials" does stay constant, so maybe it wouldn't be too hard to fix.

[Loewchen]

Also, the listed number of "entities missing construction materials" does stay constant, so maybe it wouldn't be too hard to fix.

Because it's a function of construction job allocation frequency and alert timeout, the faster you check and the longer the timeout the more alerts can be shown at one time. There is not way to fix it unless you globally limit how many ghosts can exist otherwise you can simply place one more ghost to "unfix" it.