*sigh* When using fabric, it dosnt care much about the java version you use to run most of it, if the loom version is newer, and you just register stuff in registries and done. Nice, easy, just pleasant to work with.

Then you run forge. It cries because it dosnt like you query blocks immeadiately after you register them, it dosnt even like it when you register certain stuff (loot table functions & conditions just dosnt work like at all), hangs when you use one java version, cries when you use another and only starts *somewhat* working in a VERY SPECIFIC java version and even need to downgrade loom so it starts working.

If not for the fact that forge (espc for older MC versions) was the defacto standard...

Sadly neoforged only starts with MC 1.20 and I'm currently working with 1.16 for my OpenComputers continuation / rewrite...

#minecraft #modding #java #fabric #forge #neoforged #programming

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

Ich versuche mich mal selbst an #MinecraftModding. Ich werde mich ein bisschen mit #Neoforge beschäftigen. Ich habe es auch schon mal mit #Fabric und #Quilt versucht, aber bei den beiden brach das #Java Environment schon zusammen, weil ich einfach nur das Template umbenannt habe und #Neoforged funktioniert bereits mit #Minecraft 1.20.6.

#Minecraft #Modding #Gaming #Programming

#Minecraft Forge split info #NeoForged: https://neoforged.net/news/theproject/, by @cpw

#MinecraftForge