In space, "connect to logistic network" should read the Hub

[Klips]

The "connect to logistic network" button currently has no function in space. However, there are many things to be read from the Hub, and platforms often end up with a clutter of red/green wires. Using the Hub as a logistic network would help simplify this situation.

It would be nice if it was possible to send Hub info such as Speed etc as well through this.

[Muche]

Surface conditions are a gameplay limitation, not an engine limitation.
So one could make a modded roboport + logistic chests placeable on a platform. The hub would then had to act as a logistic chest as well to be able to report its contents.

Other hub info (route, speed, damage) requires circuit signals to work.

The bigger issue is that platform hub's storage is primarily a passive storage used to transport stuff between planets.
It does not make much sense to control whether a turret is enabled based on the amount of Foundries carried.

[Klips]

It might cause conflicts in mods, that's fair; I didn't want to go too much into possible constraints and other options and ideas, as it would just make the suggestion vague and unclear.

I hope the central point -- to be able to read the Hub without needing a big mess of wires -- comes across.

[Green Cat]

Since we don't have logistic network to connect to, why can't it be the main hub's storage? As in, no need for circuit cables, since we can just read what exist in the hub

In case people are not aware, when you open an inserter or belt (or really, anything), look at top right, press the icon that looks like a signal or wifi. That will allow said ententy to read what exist in the network. One exemple is when I build stuff. I don't connect the inserter to the storage via circuit, but to the network. Why? to avoid overproduction. Because if i place a Storage Chest (the yellow one) with a certain item, this mean all the items will come to that storage... unless it's full due to overproduction. Plus, due to unpredicted events, some might be stored in other location. So even without a request chest, you can cap how many you produce while still having more then enought. Plus they work with parameters, aka you only need one blueprint.

And just like this, we could use it for so many other instances. Like the fluids. You connect them to a radar via circuit. And the radar will send that signal to the network. So by placing radar and if the hub is a network, we can massivly reduce the need of wierd looking circuit connections while still having tons of control.

[crimsonarmy]

This seems like it would add confusion. "why is there a logistic system on my space platform? I don't have any roboports there" kind of thing

[Sad_Brother]

Hub and platform are the logistic network itself. Any item can be moved to hub or from hub via platform.
Fully support this suggestion.

Liquid tank storage can be added even if it is not hub. There are no chests on the platform anyway.

[sczsne]

Since, 2.0, I've gotten used to using the logistics connection to control my machines - it's great for limiting production of things when you already have enough of something stored across the network.

However, this functionality is entirely null on space platforms - there's no logistics network to connect to, because you can't build bot hubs, nor storage in space.

Thus, my simple suggestion - make any entity on a space platform treat the contents of the hub as a logistics network, which all of the entities on the platform can use for setting logistics connection conditionals.

[eugenekay]

Previously

[Koub]

[Koub] Merged several threads with a similar suggestion.