How to find your Logs & Error Reports

Having an issue on the server or with your game? This guide will help you find the logs you may need so we can assist you!

On our wiki, we use the following icons when features are restricted in some way. Below are the icons and what they mean:

• Blaze Modpack Required

• Discord Server Exclusive

• Cobblemon Server Exclusive

• Pixelmon Server Exclusive

When something goes wrong — a crash, a disconnect, an error in chat, or heavy lag — your game writes down what happened in a few different files. Sending us the right file is the fastest way for Staff to work out what went wrong.

All of these files live inside your instance folder (the folder your modpack is installed in):

Folder	What it's for	When we'll ask for it
./logs/	A record of everything that happened during your play session	Almost every Support Ticket
./crash-reports/	A report written when the game crashes	Your game closed or crashed
./debug/	A report written when you unexpectedly disconnect from the server	Network Protocol Errors and other server-caused disconnects

Pick the mod you play below to find your instance folder, then jump to What's in each folder to see which file to send.

Don't relaunch the game before grabbing your logs! The main log file (latest.log) is replaced every time you start the game. If you've already restarted, see Older logs below.

Pixelmon

CurseForge

1

Open the CurseForge app

Launch the CurseForge app, select Minecraft on the left-hand side and go to My Modpacks.

2

Open your modpack's folder

Right-click your Pixelmon modpack and select Open Folder.

You can also open the modpack, click the ⋮ (three dots) button next to Play and select Open Folder.

3

Open the folder you need

Your file explorer will open on the modpack's instance folder. Open logs, crash-reports or debug depending on what you've been asked for.

If a folder isn't there, it just means the game hasn't needed to create it yet — for example, crash-reports only appears after your first crash.

Cobblemon

CurseForge

1

Open the CurseForge app

Launch the CurseForge app, select Minecraft on the left-hand side and go to My Modpacks.

2

Open your modpack's folder

Right-click your Cobblemon modpack and select Open Folder.

You can also open the modpack, click the ⋮ (three dots) button next to Play and select Open Folder.

3

Open the folder you need

Your file explorer will open on the modpack's instance folder. Open logs, crash-reports or debug depending on what you've been asked for.

If a folder isn't there, it just means the game hasn't needed to create it yet — for example, crash-reports only appears after your first crash.

Modrinth

1

Open the Modrinth App

Launch the Modrinth App and click Library on the left-hand side.

2

Open your instance's folder

Right-click your Cobblemon instance and select Open folder.

You can also open the instance, click the ⋯ button next to Play and select Open folder.

The Modrinth App also has a Logs tab on the instance page where you can read your logs inside the app. When sending them to Staff, please still send the actual file from the logs folder.

3

Open the folder you need

Your file explorer will open on the instance folder. Open logs, crash-reports or debug depending on what you've been asked for.

Can't open the folder from the app?

You can browse to the instance folder yourself. These are the default locations — replace <name> with your modpack or instance name:

Launcher	Windows	macOS
CurseForge	C:\Users\<you>\curseforge\minecraft\Instances\<name>	~/Documents/curseforge/minecraft/Instances/<name>
Modrinth App	%APPDATA%\ModrinthApp\profiles\<name>	~/Library/Application Support/ModrinthApp/profiles/<name>

On Windows, you can paste a path containing %APPDATA% straight into the File Explorer address bar or the Run box (Win + R). Older Modrinth App installs may use com.modrinth.theseus instead of ModrinthApp. If you changed your install location in the launcher's settings, look there instead.

What's in each folder

./logs/

Client Logs are what we require most often with Support Tickets. They show every error, command, chat message, and broadcast that occurred during your session.

File	What it is	When we need it
latest.log	The log for your current or most recent play session	Almost always — errors, disconnects, missing items, things not working as expected
debug.log	A much more detailed version of the same session. Created by Forge/NeoForge, so you'll have it on Pixelmon (and NeoForge Cobblemon packs) but usually not on Fabric	When Staff ask for more detail than latest.log gives
YYYY-MM-DD-#.log.gz	Older sessions, compressed and named by the date they started	When the issue happened before your last restart

Older logs

Every time you launch the game, the previous latest.log is compressed and renamed to the date it was created — for example 2026-10-01-2.log.gz is the second session started on 1st October 2026. If the problem happened in an earlier session, find the file with the matching date and send that one. You don't need to unzip it.

./crash-reports/

When the game crashes, Minecraft tries to write a crash report explaining what caused it. These are named with the date and time of the crash, for example crash-2026-10-01_15.42.10-client.txt.

When we need it: any time your game crashes or closes unexpectedly. Send the report with the date and time that matches your crash — it's usually the newest file in the folder. Please send your latest.log along with it, as the two together tell us much more than either one alone.

No crash report? If the game closed without writing one, check the instance folder itself for a file named hs_err_pid followed by a number (e.g. hs_err_pid12345.log). This is written when Java itself crashes — send that along with your latest.log.

./debug/

This folder holds disconnect errors (often called Network Protocol Errors) that are generated when you unexpectedly disconnect from a server due to a bug. It will be empty or missing unless you've had this happen.

When we need it: if you are being disconnected by an issue on the server's side, this may help us figure out what the problem is so we can try and fix it.

Sending your files to Staff

• Attach the file directly to your Support Ticket. Please don't copy and paste the contents into a message — logs are usually far too long and get cut off.

• If a file is too large to attach, upload it to mclo.gs and send us the link instead.

• Don't rename or edit the files — the names and timestamps help us match them to your issue.

• Tell us roughly when the issue happened, so we know where to look in the log.

Logs can include your Minecraft username and chat messages from your session. Only share them through Support Tickets or with Staff members — never post them publicly.