Closed gabfv closed 1 year ago
The zip support through that extension was always a little iffy, and i'm planning to rip it out and redo it from scratch soon, because i too have gotten fed up with it inexplicably just not working sometimes. In the mean time, you'll probably find it much more reliable if you unzip the mods you're interested in!
I think I have fixed it. There was two factorioPath (although it was the same value) in different vscode's project config files.
Explanation: In my mods folder, where I open vscode into, there what two files that contained the factorio.versions element in the json files. One settings.json and the other mods.code-workspace. I'm not sure how the second file got made but it had the exact same factorio.versions (with the same values and everything). Once I deleted mods.code-workspace, the breakpoints started to work again (including the breakpoints in zip files).
I'm trying to debug some factorio mod and I'm unable to make it stop for any breakpoints. I've followed the instructions and launch using "Factorio Mod Debug (Settings & Data)". Every time I launch it that way, the breakpoints become "Unverified breakpoints" shortly after launching.
The mod I was trying to debug was Constructron, and it seems to load just fine according to the log (full log at the end of the post):
But any breakpoints inside (or any other mods) using Zip File Explorer does not work at all. I've also tried to extract the zip file, rename the folder so it loads correctly (from Constructron-Continued-main to Constructron-Continued) and delete the _Constructron-Continued1.0.68.zip, but still no breakpoints seems to work (still "Unverified").
My launch.json is just the default one:
And my settings.json:
Here's the startup log for Factorio: