You can find your Minecraft client logs and crash reports in a few different places depending on which launcher you use, whether that's the vanilla launcher, CurseForge, or Modrinth. These logs record everything the game does when it launches, including errors and crashes, and they're helpful for diagnosing a problem.
Vanilla Launcher Logs
On Windows, logs are found at:
%appdata%\.minecraft\logs
On Mac, they're at:
~/Library/Application Support/minecraft/logs
The most recent session is saved as latest.log. Older sessions are compressed into dated .log.gz files in the same folder.

Crash Reports
If the game crashed rather than just showing an error, check the crash-reports folder in the same .minecraft directory. Each crash generates a separate timestamped .txt file with the full error and a stack trace.
CurseForge App Logs
- Open the CurseForge app and select your modpack under My Modpacks.

- Click the three dots next to the modpack and choose Open Folder.

- Logs are in the
logsfolder, and crash reports are incrash-reports, both inside that modpack's own instance folder rather than a shared.minecraftfolder.
Modrinth App Logs
- Open the Modrinth App and select your Modpack.

- Click the three dots and choose Open Folder, or use the in-app Logs tab if your version has one.

- Logs and crash reports are stored per-instance, the same way as CurseForge.
What to Share with Support
When sending a log to Wabbanode support, send the full latest.log or crash report file rather than a screenshot, since the full file includes details a screenshot usually cuts off. A site like mclo.gs lets you paste a log and share a link instead of attaching the whole file.
Server-side logs, from your Wabbanode server rather than your own PC, are found separately through the panel's Files tab, in the server's root logs folder.
You now know where to find your Minecraft logs, whichever launcher you're using.

