The VSCode launch.json generated by ModDevGradle is incorrect.

[miss-programgamer]

The VM args in all launch configurations try to pass bin/main as the mod folder, but that directory doesn't exist, as it doesn't get generated. It's also not what gets passed to the VM in any of the "run" tasks, nor the launch configs in IDEA. In fact, copying the mod folder arguments from the IDEA launch configs make the VSCode ones work. Only problem is, the launch.json file gets regenerated every time I change my gradle files/properties, so that's not a permanent solution.

// .vscode/launch.json
"vmArgs": [
  "@C:\\Users\\Mireille\\Source\\Minecraft\\MBA\\build\\moddev\\clientRunVmArgs.txt",
  // This is wrong:
  "-Dfml.modFolders\u003dmba%%C:\\Users\\Mireille\\Source\\Minecraft\\MBA\\bin\\main"
],

<!-- .idea/workspace.xml -->
<option
  name="VM_PARAMETERS"
  value="@C:\\Users\\Mireille\\Source\\Minecraft\\MBA\\build\\moddev\\clientRunVmArgs.txt -Dfml.modFolders=mba%%C:\\Users\\Mireille\\Source\\Minecraft\\MBA\\build\\classes\\java\\main;mba%%C:\\Users\\Mireille\\Source\\Minecraft\\MBA\\build\\resources\\main"
/>

[shartte]

There are multiple different sets of plugins for vs code as far as we know. The ones that are eclipse based will compile to bin/, while build/ is relevant for building with Gradle itself.

[miss-programgamer]

So, what now? Should/can ModDevGradle detect what set of extensions I'm running or should I adjust my setup? And if so, which extensions should I add/remove?

[miss-programgamer]

Did some investigating and it seems like it's the gradle extension made by microsoft specifically causing things to behave the "gradle" way rather than the "eclipse" way. I don't know how you'd go about detecting that, but it's a lead at least.

Alternatively, there could be a setting that prevents clobbering the launch.json file, that way users could configure things appropriately to their dev environment.