[2.0.66] Roboport appears to read logistic requests from other networks

[falstro]

I don't know if this is a bug or intended, but I couldn't find any documentation, and it appears at least inconsistent.

I have perimeter defense outposts that I wanted to leverage using buffer chests to both distribute resources and control the inserters unloading the resupply train by reading active requests in the outpost network. This logistic network is completely separated from the logistic network of the main base (although it does share an electrical network, if that matters for trouble shooting).

Setting the Roboport circuit connection to "Read logistic network requests" appears to read the requests from the main base (in addition to the outpost network), whereas the "Read logistic network contents" only reads contents from the current network, as expected.

I'll work around this by using other mechanisms, I just thought it was odd, and I couldn't find anything talking about it.

[Genhis]

Thanks for the report. Please mark places where this issue can be observed and share your save file.

[sushi_eater]

I have roboports with separate logistic networks on the same power grid, with overlapping construction range. "Read logistic network requests" works correctly and is isolated to the separate logistic networks.

[falstro]

As I was collecting screenshots and save file I was able to pinpoint the source of the requests, and indeed it was not from the main base, but rather from my tank that was parked within the network that was using a logistics group that was also used in the main base. So that _is_ a request within the network, and this is not a bug at all. My mistake!