Planetary P2P Pairing

What problem does this mod solve?

Dyson Sphere Program's ordinary local logistics treats every eligible supplier on a planet as an equivalent source. This can cause consumers to import material from general-purpose stations while a nearby byproduct station remains full.

A common example is hydrogen. A fire-ice production line can stall because its byproduct hydrogen storage is full, while a fractionator or deuterium production line simultaneously draws hydrogen from an interstellar import buffer.

Planetary P2P Pairing lets you tell the local drone network which station should be used first. The preferred station is drained before ordinary local suppliers are allowed to provide the remaining deficit.

What does this mod do?

The mod extends the existing Priority Settings > Point-to-Point interface to same-planet logistics.

• Pair any same-planet PLS or ILS with another PLS or ILS.
• Prefer the paired station for every item with matching Local Supply and Local Demand settings.
• Fall back to ordinary local logistics when the paired station cannot provide a valid shipment.
• Apply the priority regardless of whether the supplier's or demander's drones initiate the trip.
• Preserve vanilla interplanetary ILS point-to-point, route, and group behavior.
• Save local pairings through DSPModSave.

Pairings are bidirectional for priority purposes and station-wide rather than per-item. A pair affects only items for which one endpoint is explicitly configured as Local Supply and the other as Local Demand. Remote Supply, Remote Demand, and Storage settings are not treated as local supply or demand.

Configuring a local pair

1. Give both stations names.
2. Open either station and select Priority Settings.
3. Under Point-to-Point, select Configure.
4. Search for the other station by name and select Add.

A PLS search contains only named PLS and ILS stations on the current planet. An ILS search also retains vanilla remote ILS candidates. Local pairing rows display the paired station's building icon to distinguish PLS and ILS endpoints.

Dispatch Log

Every PLS and ILS window includes a Dispatch Log button beside the Control Panel button. The side panel records recent departures involving the selected station and shows:

• In-game dispatch time
• Drone or vessel
• Source and destination
• Item and scheduled amount
• Scheduler reason: local, local P2P, remote P2P, planet route, star route, group, or remote fallback

The log is intended for diagnostics. It uses a bounded 512-entry in-memory history, shows the newest matching entries first, and is cleared when a save is loaded or changed. It is not written to the save file.

Is it compatible with Nebula Multiplayer?

No. Planetary P2P Pairing is currently single-player only.

Its custom pair data and local dispatch filtering are not synchronized between Nebula peers. The mod also does not currently detect Nebula or disable itself automatically. Do not enable it in a Nebula multiplayer profile; doing so may cause logistics behavior to diverge between host and clients.

Installation

Required dependencies:

• BepInEx 5 for Dyson Sphere Program
• CommonAPI-DSPModSave

When installing manually, place PlanetaryP2PPairing.dll in:

BepInEx/plugins/PlanetaryP2PPairing/

Launch the game through the mod manager's Start modded option. BepInEx should report Planetary P2P Pairing 0.3.2 during startup.

Compatibility and tested version

• Mod version: 0.3.2
• Tested DSP version: 0.10.34.28529
• Existing vanilla remote ILS P2P routes, interplanetary routes, and groups remain available.
• Removing the mod does not make the vanilla save unloadable; saved local pairs simply stop affecting logistics.

Back up important saves before testing any mod release.

Current limitations

• Local point-to-point priority only; no local groups or local routes.
• Pairing is station-wide, not per-item.
• No exclusive mode: ordinary local logistics is used as fallback.
• Both endpoints must be named to locate them through the pairing search.
• The Dispatch Log covers departures recorded during the current loaded session only.

Troubleshooting

Check BepInEx/LogOutput.log and confirm that the expected version loaded. Search for:

Planetary P2P Pairing
samox.dsp.local-priority-pairing

When validating priority behavior, allow previously dispatched drones to finish first. Orders created before a pairing was added or changed remain in flight.