Working on an minecraft mod and wanting debugging it in vscode and it only fails over it's own feets.
Not only does it generate & use it's own build cache (bin/... instead of gradle's build/...), in doing so it just copies all resources and dosn't executes the processResources step correctly which messes up my mod metadata (i use expansion in it for version numbers) so the loader interprets ${minecraft_version} as an version requirement it obviously can't validate, like ever.
Fixing that took a while, but then it dosn't even finds LWJGL anymore. Looking further through the 108 entry classpath (cries in java), I've found out for some idiotic reason, does vscode picks up TWO instances of lwjgl! 3.2.2 AND 3.3.2. And only the later is the the correct one! So I've now also need to filter out all wrong lwjgl components from the classpath before putting it back together. Espc hart since the arguments are given to the exec command as a file.
So yeah, time for another hastly thrown together ruby script to sort this mess...
#java #minecraft #fabricmc #neoforged #gradle #lwjgl
