Debugging tutorial is overcomplicated about spongedocs

[simon816]

That won't give you source code or the ability to set breakpoints in sponge/minecraft code.

[XakepSDK]

This will give source code and ability to set breakpoints up SF or SV code.
This won't give you deobfuscated names or ability to set breakpoints in MC or Forge code.
If don't know how can you debug code in JVM, i'm sure you don't need setting breakpoints in MC codebase or wanting deobfuscated names.

[gabizou]

This tutorial is completely wrong!

Your opinion. If someone does want to get a workspace with full code access, the docs are 100% right.

What I think the correct solution to the issue is:
Split up full vs "beginning to debug" docs and call it a day.

[zhourui123]

A lot of forge code gets mixin , can't be debugged(The line number is incorrect for debugging), Further setup is required for normal debugging

[gabizou]

can't be debugged(The line number is incorrect for debugging)

Debugs just fine in intellij with the MinecraftDev plugin:
https://youtu.be/JQAnCC-ZDng

[XakepSDK]

If you're using mixins, then you are using ForgeGradle too. FG has out of box run configs for IDE's, so current tutorial and this tutorial are unnecessary and confusing.