IntelliJ - Attaching debugger and hitting breakpoints - ForgeGradle

Heliarco

Posted November 11, 2020

TItle says it all really. I have a project setup via gradles genIntellijRuns task open in intelliJ. I can run the runClient task just fine and i get log output, but any breakpoints set in the debugger are not hit.

What am i missing here? I am not particularly at home with either java or intellij yet, so bear with me if i missed something obvious, (though extensive googling got me nothing).

Quote

DaemonUmbra

Posted November 12, 2020

You need to use the runconfigs to get debugging to work properly, not the gradle tasks.

Quote

This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy.

As the most common issue I feel I should put this outside the main bulk:

The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge.

If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan.

For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety.

Reveal hidden contents

Logs (Most issues require logs to diagnose):

Reveal hidden contents

Please post logs using one of the following sites (Thank you Lumber Wizard for the list):

https://gist.github.com/: 100MB Requires member (Free)

https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$)

https://hastebin.com/: 400KB

Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads.

What to provide:

...for Crashes and Runtime issues:

Minecraft 1.14.4 and newer:

Post debug.log

Older versions:

Please update...

...for Installer Issues:

Post your installer log, found in the same place you ran the installer

This log will be called either installer.log or named the same as the installer but with .log on the end

Note for Windows users:

Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension

Where to get it:

Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs.

Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:

Reveal hidden contents

or alternately,

Fallback ("No logs are generated"):

If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft

Server Not Starting:

Reveal hidden contents

Reporting Illegal/Inappropriate Adfocus Ads:

Reveal hidden contents

Posting your mod as a GitHub Repo:

Reveal hidden contents

[Workaround line, please ignore]

Heliarco

Posted November 12, 2020

Author

Posted November 12, 2020

That worked perfectly. Thanks

Quote

Sign In

IntelliJ - Attaching debugger and hitting breakpoints

Recommended Posts

Heliarco

DaemonUmbra

Heliarco

Join the conversation

Announcements

Recently Browsing

Posts

Topics

Who's Online (See full list)

Browse

Activity

Important Information