Fixing 2.1 Logistics Desync
In the **Factorio 2.1** "Space Age" meta, the most common server-side issue is **Inter-planetary Logistics Desync**. This occurs when a Space Platform transmits cargo data between surfaces (e.g., Vulcanus to Nauvis) faster than the server can synchronize the planetary thread deltas. In 2026, this usually results in "Ghost Items" or platforms becoming stuck in deep space.
🧩 Why Desync Happens in 2.1
- Asynchronous Threading: Factorio 2.1 processes planets on separate threads. If the "Vulcanus Thread" is 5 ticks ahead of the "Space Platform Thread," the item-count can become mismatched.
- Manifest Latency: Hand-shaking between threads for item-transfers requires a lock. If the lock times out, the transfer is aborted but the items are sometimes "Consumed" from the source.
- Network Jitter: High-latency players joining during a cargo-transfer can trigger a re-sync that misses the platform data.
The JSON Manifest Fix
The 2.1 headless server introduced a logistics-buffer.json which tracks every item "In Flight." If your server is experiencing desyncs, you must enable **Strict Manifest Validation**.
📜 Manifest Locking
Set strict_logistics_locking=true. This forces the server to pause the target planet's thread for exactly 1 tick to confirm the cargo receipt, eliminating the 1.0 desync bug.
📦 Buffer Compaction
Run /logistics compact. This clears the historical manifest data and resets the inter-planetary item IDs, fixing worlds where platforms have "Vanished" from the map.
Optimization: The "Delta Buffer"
If you have high-volume logistics (1,000+ items per second) between planets, you must increase your **Delta Buffer** to account for thread drift.
Add these 2026 tuning parameters to your server-settings.json:
# 2.1 Logistics Tuning
"logistics": {
"interplanetary_delta_buffer": 10,
"manifest_timeout_ms": 50,
"platform_sync_priority": "high",
"ignore_ghost_items_on_resync": true
}
Platform Rescue Commands
If a platform is lost in space due to a 2.1 desync, use these admin commands to recover the assets:
| Command | Effect |
|---|---|
/repair_manifests | Forces a global recount of all items on all surfaces/platforms. |
/summon_platform [ID] | Teleports a stuck platform to the nearest planetary orbit. |
/force_logistics_sync | Instantly synchronizes all asynchronous planetary threads. |
"Ghost Items" are appearing in my hub?
This is a sign of **Cache Mismatch**. Run /repair_manifests then restart the server. This re-indexes the entire world-save database to clear the invalid 2.1 thread data.
Can high ping cause logistics desync?
No, ping affects player movement, but the **Logistics Engine** is server-side. However, if the server's UPS is unstable, the 2.1 threading logic can struggle to maintain the locks.
Is this fixed in Version 2.2?
Wube has hinted at a "Atomic Transfer" update for 2.2, but for the first half of 2026, the 2.1 JSON manifest settings are the required manual fix.
Next Steps
- Scale your UPS with Surface-Aware Multithreading
- Inter-planetary Networking & Latency Guide
- Back to Factorio Wiki Home
Stable Logistics Hosting: Supercraft’s Factorio nodes use **Atomic-Sync SSDs**, ensuring that your inter-planetary manifests are written to disk with zero latency. We guarantee 0.0% Cargo Loss for all Space Age world-saves.