Hi,
I’ve been testing migration from Transport_Drones_Continued to Transport_Drones_Continued_Fixed on a large existing save and ended up building a small migration bridge plus a target-side patch for 2.0.106.

The bridge preserves the existing road network, depot configuration and running transport state across the mod-ID change. I also extended the current fork migration to handle more depot types and added cleanup for orphaned drone entities.

This has now been tested successfully on a save with ~2000 depots and ~5000 drones. After migration, the save could be switched back to the unmodified 2.0.106 and continued normally.

If you are interested, I can provide the bridge mod, the 2.0.106 patch/diff, and a short technical summary of what was changed and tested.
Greetings
MoSII2710

I'm curious what you did.

Drop the checksum here and put the zip in this dropbox folder
https://www.dropbox.com/scl/fo/4kvpv2849zyljoldky1nb/AGBddBSRs3BodCofA6rs5vk?rlkey=4qvv6p6w00ggyfcfpismp396v&st=5nbz2z7m&dl=0

Hey Hellwatcher,

thanks for taking a look at this. I’ve put everything related to the migration proof-of-concept into one package so you can review and verify it independently.

The package contains the bridge mod, the local 2.0.108 test build based on 2.0.106, the patch/diff, full documentation, a quick command reference, reference hashes for the original base files, and screenshots from the real-save test.

For verification, here are the SHA-256 hashes:

e8312156ac6dbca60ff78b23bb8f55ce1af73c01b47cbfa975735b2eaf411409 Transport_Drones_Migration_Author_Package_2026-08-31.zip

4e800c3d560f5d1a8cc757a259cc68ee2f485654caadcf4203014b8bd88579ae COMMAND_QUICK_REFERENCE.txt
3543565e05f7b1f7fecb2cb7df05a158c208fb553a3c1442ea93e2d75a5c2eb7 MANIFEST.txt
4ecfdfd239d158427daf19fbab4be2ab1ea6b2496ed8195b8d63cd3b30ee5a71 README_AUTHOR_EN.md
4581a02053dff7b8ac9adf99f3d5188c3f02e0df559cacd54e86287e5ff8d5eb REFERENCE_BASE_HASHES.txt

29dcf66be12eda19009c3d0cf45ee5ae553f2313bd0865dda248464b4f76f188 Transport_Drones_Continued_Fixed_2.0.106_to_2.0.108_live-bridge-test.patch
44c50dbdc4cd9873814836ca359c840e248f11356b0a0604020076556deb81af Transport_Drones_Continued_Fixed_2.0.108_LOCAL_BRIDGE_TEST.zip
ee250edbb88fa5c1c1804b32ee49d81861efd28300b6fc94452d943bfafc71cb Transport_Drones_Migration_Bridge_0.2.1.zip

428cf0ebe6216bd3b251c2890fab00a9e26a956ab08f3559228bafa4fdea3f9a evidence/01_orphan_scan_273.jpg
3360f021719eb0628736ab44f2bc30f502dc78d360e5f9a8177689241505271c evidence/02_orphan_cleanup_273_to_0.jpg
9be36850d03a4e435737a0bfdb361e8fe68989493a81b4d361a263fcb1b87f12 evidence/03_final_scan_orphan_0.jpg

The real-save migration was performed on a fairly large network with more than 2,000 request depots and roughly 5,000 drones. The migration itself succeeded, including the later downgrade back to the unchanged 2.0.106.

During post-migration testing we found one additional issue with orphaned physical drone entities. The cleanup detected 273 of them, removed all 273 with failed=0, and the final verification showed:

registered=1251
physical=1251
ORPHAN=0

The documentation explains the complete procedure, the bridge architecture, the changes made on the Continued Fixed side, the handling of live transports, the remaining limitations, and the exact commands used during testing.

I hope this is useful. If you are interested in integrating any part of it upstream, I’d be happy to provide more details or help test further changes.

+1 for this landing upstream. I'm on a large Pyanodon save still on Transport Drones Continued and I hit the fluid max storage bug fixed in 2.0.88, so I want to move over.

Holding off until this resolves though. I'd rather migrate once than adopt depots now and redo it later.

Hi memiczny,

just as a practical data point: on my large existing save, the migration itself went surprisingly smoothly. I had a few orphaned drone entities afterwards, but the bridge already includes scan/cleanup tools for exactly that case, so those were easy to remove.

The one thing I would definitely check carefully after migrating is the circuit network. Red/green wire connections can be hard-disconnected because Continued Fixed changed some of the depot circuit connection points. Those links therefore need to be checked and, where affected, reconnected manually.

Apart from that, I was able to migrate the save, verify the transport network, and even return to the unmodified 2.0.106 afterwards without rebuilding the road network or depots.

So from my test, the migration path is already quite usable — the circuit connections are currently the main manual cleanup item to keep in mind.

greetings

Thanks for the upload. I'll take a good look at things this weekend.

Yeah, the wires were not done all that well. The 107 build I've been working on has taken a lot of time trying to get them to work how I want.

The one thing I would definitely check carefully after migrating is the circuit network. Red/green wire connections can be hard-disconnected because Continued Fixed changed some of the depot circuit connection points. Those links therefore need to be checked and, where affected, reconnected manually.

I too Encountered this, I have several Supply Depots with wires attached to various feed mechanisms to fill the Depots with limited amounts of stuff. I had to rush through the game and reattach them before they filled up with way too much and clogged up the feed lines... But other than that....

Ok, I was able to integrate this into what I had already built into .107. I think it's working right. Let me know if I didn't understand and messed things up.