Multiplayer in Dyson Sphere Program lets multiple players cooperate on the same star system and coordinate production across planets and systems using Interstellar Logistics Stations (ILS), remote logistics, and naming/grouping tools. It is primarily about sharing resources, assigning priorities for transfer, and organizing stations for efficient transport.
Basic multiplayer concepts
Multiplayer sessions use the same game systems as single-player but add networked interaction: players share the same universe, can build together, and can transfer items between planets and systems via Interstellar Logistics Stations (ILS).
Coordination is done through ILS configuration: each station exposes local and remote storage/supply/demand roles, point-to-point transports, and membership in groups that determine priority and routing.
Each ILS can be configured per-item with a role that determines how that ILS treats that item:
Local Storage: keep the item at this station for belt output on the same planet; the item will not be requested from or sent to other stations on the same planet.
Local Supply: make the item available to other stations on the same planet via logistics drones.
Local Demand: request the item from other stations on the same planet; drones will bring the item to this ILS.
Remote Storage: keep the item at this station for belt output on this planet; do not request or send items to stations on other planets.
Remote Supply: make the item available to stations on other planets via interstellar logistics vessels.
Remote Demand: request the item from stations on other planets; logistics vessels will bring the item to this ILS.
Use Local settings when you intend to limit transfers to the same planet and Remote settings when you want transfers between planets or systems.
Priority system: Point-to-Point, Groups, and default routing
ILS handles priority in layers. From highest to lowest priority:
Point-to-Point Transports
Groups
Default/global matching between supply and demand
Point-to-Point Transports: You can set a highest-priority direct transport between two named ILS. Both stations must share the same name before you can assign a point-to-point transport. Configure transports via the ILS interface: click Configure or the blue pair count to view, add, or remove transports. Adding a transport by name immediately adds the corresponding transport entry to the remote ILS you are interacting with. If multiple remote ILS share the same name, all such stations are added at that time; later-created stations with that same name are not automatically included. Deleting a transport removes it from both participating ILS; if multiple identically named stations existed, only the specific transport clicked is removed on each side.
Groups: Groups are a flexible mid-level priority mechanism. An ILS can belong to any number of groups. To place an ILS in a group, click the group number in the Group panel. To inspect other stations in any shared group, click the blue Stations number: the UI shows configured items, distance in AU, and group assignments for each station that shares any group with the local ILS.
Default/global routing: when no point-to-point or group priority applies, supplies and demands are matched by the normal logistics algorithm across available stations respecting their Remote/Local supply/demand settings.
Naming conventions and tips
Station names are used for point-to-point matching. Name stations deliberately and consistently if you intend to create direct transport links.
If you give the same name to multiple ILS before creating a point-to-point transport, adding a transport by that name will include all currently existing stations with that name. Later stations given the same name are not automatically included.
Use names to create role-based networks (for example: "Iron Hub - PlanetA") when you want specific bilateral routes.
Practical multiplayer workflows
Shared hubs: designate one or more ILS as planet or system hubs using Remote Supply to make produced items available off-planet, and Remote Demand on consumer planets to pull resources in.
Export-only nodes: mark a production ILS as Remote Supply for exported goods; set Local Storage for items you do not want shipped off-planet.
Import-only nodes: set Remote Demand on consumer stations so logistics vessels will deliver needed items from Remote Supply stations elsewhere.
Point-to-point for priority lanes: create point-to-point transports between major producer and consumer stations to ensure direct, high-priority shipping that bypasses intermediate matches.
Groups for categories: group stations by resource category or region (e.g., “metals”, “chemicals”, or “outer-ring”) to ensure grouped supplies are routed before unrelated stations.
Inspecting and managing transports
Use the Configure UI on an ILS to see active transports, groups, and per-item roles.
The Stations list in a Group view shows configured items, interstellar distance in AU, and group assignments for other stations sharing any group with the current ILS.
Removing a transport from one station removes the corresponding transport entry from the paired station as well.
Multiplayer coordination etiquette
Communicate naming and group conventions before building to avoid accidental routing conflicts.
Decide who controls shared hub ILS configuration to prevent unintended supply/demand changes.
Use point-to-point transports for explicit bilateral supply agreements when coordinating multiple players.
This covers the multiplayer logistics features you will use most: per-item local/remote roles, point-to-point transports, and groups for multi-station priority management.
