Finding your logs

When in the Pixelmon Discord Server, you may be asked to send your logs if you're experiencing crashes or other issues. Logs are very important for diagnosing issues, since they contain a lot of information on what the game was doing at the time, as well as telling us the environment the game is running in.

In order to find your logs, you will need to follow these steps according to your launcher:

Minecraft/TLauncher

Windows

1. In Windows Search type in %appdata%
2. Hit Enter.
3. Open the folder named .minecraft.
4. If you were experiencing a crash, open crash-reports. For other issues, open logs.
5. Find either the newest crash report file, or the file named latest.log. The latter file may also show up as just latest.
6. Battle logs (captured by doing /battlelog while in battle) can also be found in logs folder, in the battlelog folder.
7. Drag and drop the file into the #📤logs-and-screenshots chat.

MacOS

1. Open Finder on your Mac.
2. Navigate to your user's home directory.
3. Click on Library.
4. Click on Application Support.
5. Click on minecraft.
6. If you were experiencing a crash, open crash-reports. For other issues, open logs.
7. Find either the newest crash report file, or the file named latest.log. The latter file may also show up as just latest.
8. Battle logs (captured by doing /battlelog while in battle) can also be found in logs folder, in the battlelog folder.
9. Drag and drop the file into the #📤logs-and-screenshots chat.

Linux

1. Open your user's home directory.
2. Open the folder named .minecraft. (If you cannot find a .minecraft folder in your home directory, find the setting which is similar to View Hidden Files. On Ubuntu, this is the Ctrl+H keyboard shortcut.)
3. If you were experiencing a crash, open crash-reports. For other issues, open logs.
4. Find either the newest crash report file, or the file named latest.log. The latter file may also show up as just latest.
5. Battle logs (captured by doing /battlelog while in battle) can also be found in logs folder, in the battlelog folder.
6. Drag and drop the file into the #📤logs-and-screenshots chat.

CurseForge

1. Right-click on the modpack.
2. Click on Open Folder.
3. If you were experiencing a crash, open crash-reports. For other issues, open logs.
4. Find either the newest crash report file, or the file named latest.log. The latter file may also show up as just latest.
5. Battle logs (captured by doing /battlelog while in battle) can also be found in logs folder, in the battlelog folder.
6. Drag and drop the file into the #📤logs-and-screenshots chat.

Technic Launcher

1. Click on Modpack Options
2. At the install folder click on Open
3. If you were experiencing a crash, open crash-reports. For other issues, open logs.
4. Find either the newest crash report file, or the file named latest.log. The latter file may also show up as just latest.
5. Battle logs (captured by doing /battlelog while in battle) can also be found in logs folder, in the battlelog folder.
6. Drag and drop the file into the #📤logs-and-screenshots chat.

ATLauncher

1. Click Instances.
2. Click Open Folder on your chosen Pack.
3. If you were experiencing a crash, open crash-reports. For other issues, open logs.
4. Find either the newest crash report file, or the file named latest.log. The latter file may also show up as just latest.
5. Battle logs (captured by doing /battlelog while in battle) can also be found in logs folder, in the battlelog folder.
6. Drag and drop the file into the #📤logs-and-screenshots chat.

The latest.log file contains information from the most recent session. Restarting the game will overwrite this file. Older files are repacked into an archive with the date as the name.