
But at that point I already had reflown until Minmus. Turns out, I probably could have been able to salvage the save file. The First and Official Amino Community about the Kerbal Space Program. Apparently, the docking port part changed state mid flight.

The tug in question can be found by doing a Ctrl+F search for Rosie. Sometimes only one of them has the undock option. Let me know if attaching anything would help. I should point out that I am able to undock tug+s2 at the s2's terminating port, but not tug by itself from the tug command module's shielded port. After hitting it a few times I get "No Target" and nothing happens. The shielded docking port gives no option to undock or uncouple, and the s2-side medium port doesh ave undock, but it does nothing. So it will mark references to generated symbols unresolvable. By default, IntelliJ IDEA or other IDEs don't know about the generated code.
KSP NO UNDOCK OPTION FREE
If you're using KSP 1.0.9 or newer and don't need to make the IDE aware of generated resources, feel free to skip this section. After docking the tug and the s2 module, I could not undock the tug. Generated source files are registered automatically since KSP 1.8.0-1.0.9. Then grabbed the s2 module and flew back to the station to dock it in the d1 spot.

Unhooked s2, floats away, attached my tug to d1, and after some fancy moves docked it in the spot s2 was in. s1/s2 are solar arrays terminated with medium docking ports, and d1 and d2 are, respectively, a couple of docking adapters terminated with medium ports, and medium port/large port. I brought a tug ship with a shielded docking port up to my space station that was laid out like so.
