-
-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debugging tutorial is overcomplicated #806
Comments
That won't give you source code or the ability to set breakpoints in sponge/minecraft code. |
This will give source code and ability to set breakpoints up SF or SV code. |
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: |
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 |
Debugs just fine in intellij with the MinecraftDev plugin: |
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. |
https://docs.spongepowered.org/stable/en/plugin/debugging.html
This tutorial is completely wrong! You don't need to clone any sponge source code to just debug, everything you need is server jar and your plugin jar, that's all!
Replace or remove it.
if you don't do this, your project directory will be littered with sponge/forge/minecraft files
The text was updated successfully, but these errors were encountered: