1nsert_brain

I'm a bit confused, the first post in the first page of this thread states: Dependencies Kerbal Space Program 2 Contract Configurator (only on KSP 1.8.1+) Either 3 Module Manager /L Module Manage The same is in the github/curseforge/spacedock pages of the mod linked in the OP. Also the following exception, as well as some more errors later, are generated in the player.log file if contract configurator is not present. I assumed CKAN was not pulling CC because ScrapYard doesn't support it explicitly, so the dependency got dropped somewhere in the chain. I don't see mention of magicore. I think I'm missing something. Thanks for replicating it. My limited knowledge of ksp doesn't really allow me to go beyond that, so gl to whoever decides to look into this

This info is in the post above: Install Details: Steam install, no DLCs, launched from the KSP_x64.exe file, scrapyard installed through ckan (pulled MM as well), contract configurator manually. MM is the stock one, not the fork by Lisias Regardless, how scrapyard is installed does not change the outcome in this case. Testing with the curseforge download and manual installation produces the same result, see log file attached here. I re-uploaded the player.log file below for both kspcf and scrapyard as well, which has all the info about versions and system setup. Everything is the latest version, anyway. I have never stated it is ScrapYard fault, merely that what was stated before is 100% correct: you can replicate the bug on a clean install with only the latest ScrapYard and MM. Moreover, it does not have anything to do with KSPCF, contrary to what was stated above. The player.log was attached, as asked in the OP for bug reports. No save was provided by me because it was not requested and there is nothing in the game: I re-downloaded it from steam from scratch, installed the mod, and put a single stock vessel on the pad. No KSPCF, only ScrapYard + MM (not your fork). Contract Configurator was installed since it is a requirement of Scrap Yard, so the install would be exactly as specified in the OP. The behavior happens regardless of Contract Configurator and has nothing to do with it, as I replicated both with and without it. Anyway, you can see proof of all the above in the player.log files below. KSPCF Player.log and ScrapYard Player.log

@Lisias [snip] what was said is 100% right. All that is needed to replicate the bug is: 1 - get clean stock ksp 2- install ScrapYard, MM, Contract Configurator 3- enter VAB, load a craft (I loaded the stock AeroEquus) 4- press launch, get FlowGraph error spam on launchpad (no staging/ignition necessary) Install Details: Steam install, no DLCs, launched from the KSP_x64.exe file, scrapyard installed through ckan (pulled MM as well), contract configurator manually. I have just did this myself, see attached ksp.log. Nothing installed except the above, see the log. I have made an account specifically for this after years of lurking because I have noticed this spam problem in another, heavily modded install, and stumbled upon this "discussion" between you, machine and zer0kerbal. [snip] Anyway, @zer0Kerbal above you have the steps to replicate, and below the log file if you want to check it out. [snip] Player.log file here for both scrapyard-only and kspcf-only installs