Difference between revisions of "Finding your logs"
From Pixelmon Wiki
(Fixed grammar/spelling, more details. TODO: Other platforms.) |
SwitzerLad (talk | contribs) (Added missing Launchers and paths for other Operating Systems) |
||
Line 1: | Line 1: | ||
When in the [[Discord server|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. | When in the [[Discord server|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: | + | In order to find your logs, you will need to follow these steps according to your launcher: |
− | + | ==Minecraft/TLauncher== | |
− | + | ===Windows=== | |
− | + | # In Windows Search type in <code>%appdata%</code> | |
− | + | # Hit Enter. | |
− | + | # Open the folder named <code>.minecraft</code>. | |
− | + | # If you were experiencing a crash, open <code>crash-reports</code>. For other issues, open <code>logs</code>. | |
− | + | # Find either the newest crash report file, or the file named <code>latest.log</code>. The latter file may also show up as just <code>latest</code>. | |
+ | # Drag and drop the file into the <code>#📤logs-and-screenshots</code> chat. | ||
+ | |||
+ | ===MacOS=== | ||
+ | # Open <code>Finder</code> on your Mac. | ||
+ | # Navigate to your user's '''home directory'''. | ||
+ | # Click on <code>Library</code>. | ||
+ | # Click on <code>Application Support</code>. | ||
+ | # Click on <code>minecraft</code>. | ||
+ | # If you were experiencing a crash, open <code>crash-reports</code>. For other issues, open <code>logs</code>. | ||
+ | # Find either the newest crash report file, or the file named <code>latest.log</code>. The latter file may also show up as just <code>latest</code>. | ||
+ | # Drag and drop the file into the <code>#📤logs-and-screenshots</code> chat. | ||
+ | |||
+ | ===Linux=== | ||
+ | # Open your user's '''home directory'''. | ||
+ | # Open the folder named <code>.minecraft</code>. (''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.'') | ||
+ | # If you were experiencing a crash, open <code>crash-reports</code>. For other issues, open <code>logs</code>. | ||
+ | # Find either the newest crash report file, or the file named <code>latest.log</code>. The latter file may also show up as just <code>latest</code>. | ||
+ | # Drag and drop the file into the <code>#📤logs-and-screenshots</code> chat. | ||
+ | |||
+ | ==CurseForge== | ||
+ | # Right-click on the modpack. | ||
+ | # Click on <code>Open Folder</code>. | ||
+ | # If you were experiencing a crash, open <code>crash-reports</code>. For other issues, open <code>logs</code>. | ||
+ | # Find either the newest crash report file, or the file named <code>latest.log</code>. The latter file may also show up as just <code>latest</code>. | ||
+ | # Drag and drop the file into the <code>#📤logs-and-screenshots</code> chat. | ||
+ | |||
+ | ==Technic Launcher== | ||
+ | # Click on Modpack Options | ||
+ | # At the install folder click on <code>Open</code> | ||
+ | # If you were experiencing a crash, open <code>crash-reports</code>. For other issues, open <code>logs</code>. | ||
+ | # Find either the newest crash report file, or the file named <code>latest.log</code>. The latter file may also show up as just <code>latest</code>. | ||
+ | # Drag and drop the file into the <code>#📤logs-and-screenshots</code> chat. | ||
+ | |||
+ | ==ATLauncher== | ||
+ | # Click <code>Instances</code>. | ||
+ | # Click <code>Open Folder</code> on your chosen Pack. | ||
+ | # If you were experiencing a crash, open <code>crash-reports</code>. For other issues, open <code>logs</code>. | ||
+ | # Find either the newest crash report file, or the file named <code>latest.log</code>. The latter file may also show up as just <code>latest</code>. | ||
+ | # Drag and drop the file into the <code>#📤logs-and-screenshots</code> 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. | 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. |
Revision as of 08:32, 31 May 2022
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:
Contents
Minecraft/TLauncher
Windows
- In Windows Search type in
%appdata%
- Hit Enter.
- Open the folder named
.minecraft
. - If you were experiencing a crash, open
crash-reports
. For other issues, openlogs
. - Find either the newest crash report file, or the file named
latest.log
. The latter file may also show up as justlatest
. - Drag and drop the file into the
#📤logs-and-screenshots
chat.
MacOS
- Open
Finder
on your Mac. - Navigate to your user's home directory.
- Click on
Library
. - Click on
Application Support
. - Click on
minecraft
. - If you were experiencing a crash, open
crash-reports
. For other issues, openlogs
. - Find either the newest crash report file, or the file named
latest.log
. The latter file may also show up as justlatest
. - Drag and drop the file into the
#📤logs-and-screenshots
chat.
Linux
- Open your user's home directory.
- 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.) - If you were experiencing a crash, open
crash-reports
. For other issues, openlogs
. - Find either the newest crash report file, or the file named
latest.log
. The latter file may also show up as justlatest
. - Drag and drop the file into the
#📤logs-and-screenshots
chat.
CurseForge
- Right-click on the modpack.
- Click on
Open Folder
. - If you were experiencing a crash, open
crash-reports
. For other issues, openlogs
. - Find either the newest crash report file, or the file named
latest.log
. The latter file may also show up as justlatest
. - Drag and drop the file into the
#📤logs-and-screenshots
chat.
Technic Launcher
- Click on Modpack Options
- At the install folder click on
Open
- If you were experiencing a crash, open
crash-reports
. For other issues, openlogs
. - Find either the newest crash report file, or the file named
latest.log
. The latter file may also show up as justlatest
. - Drag and drop the file into the
#📤logs-and-screenshots
chat.
ATLauncher
- Click
Instances
. - Click
Open Folder
on your chosen Pack. - If you were experiencing a crash, open
crash-reports
. For other issues, openlogs
. - Find either the newest crash report file, or the file named
latest.log
. The latter file may also show up as justlatest
. - 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.