Difference between revisions of "Finding your logs"
From Pixelmon Wiki
(Fixed grammar/spelling, more details. TODO: Other platforms.) |
Yumetama829 (talk | contribs) |
||
(3 intermediate revisions by 3 users not shown) | |||
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>. | |
+ | # Battle logs (captured by doing <code>/battlelog</code> while in battle) can also be found in <code>logs</code> folder, in the <code>battlelog</code> folder. | ||
+ | # Drag and drop the file into the <code>#📤logs-and-screenshots</code> chat. | ||
+ | ===MacOS=== | ||
+ | # Click on your desktop and go to menu bar ( by default at top of your screen), click on <code>Go</code>. | ||
+ | # Hold <code>option</code> key on your keyboard and 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>. | ||
+ | # Battle logs (captured by doing <code>/battlelog</code> while in battle) can also be found in <code>logs</code> folder, in the <code>battlelog</code> folder. | ||
+ | # 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>. | ||
+ | # Battle logs (captured by doing <code>/battlelog</code> while in battle) can also be found in <code>logs</code> folder, in the <code>battlelog</code> folder. | ||
+ | # 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>. | ||
+ | # Battle logs (captured by doing <code>/battlelog</code> while in battle) can also be found in <code>logs</code> folder, in the <code>battlelog</code> folder. | ||
+ | # 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>. | ||
+ | # Battle logs (captured by doing <code>/battlelog</code> while in battle) can also be found in <code>logs</code> folder, in the <code>battlelog</code> folder. | ||
+ | # 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>. | ||
+ | # Battle logs (captured by doing <code>/battlelog</code> while in battle) can also be found in <code>logs</code> folder, in the <code>battlelog</code> folder. | ||
+ | # Drag and drop the file into the <code>#📤logs-and-screenshots</code> chat. | ||
+ | |||
+ | ==Prism Launcher== | ||
+ | # Choose The Pixelmon Modpack instance and click <code>Edit</code> on the side menu bar. | ||
+ | # In the Console Window which you just opened, go to <code>Minecraft Log</code> tab, click <code>upload</code>. If you just had a crash, this window would show up automatically. If you want to find an old log or battle log, go to <code>Other logs</code> tab, and select the log there then click <code>upload</code>. | ||
+ | # Paste the link by pressing <code>command</code> and <code>V</code> together on your keyboard into the <code>#📤logs-and-screenshots</code> chat. | ||
+ | |||
+ | ==Other Options== | ||
+ | ===ResPack Folder Workaround=== | ||
+ | # Enter the <code>Resource Packs...</code> settings from Minecraft's <code>Options...</code> menu. | ||
+ | # Click <code>Open Pack Folder</code> at the bottom of that screen. | ||
+ | # In the window that opens, navigate one layer up. | ||
+ | # 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>. | ||
+ | # Battle logs (captured by doing <code>/battlelog</code> while in battle) can also be found in <code>logs</code> folder, in the <code>battlelog</code> folder. | ||
+ | # Drag and drop the file into the <code>#📤logs-and-screenshots</code> chat. | ||
+ | |||
+ | This workaround will lead you to the correct log folder(s) regardless of the operating system or launcher you're using. | ||
+ | ==Notes== | ||
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. |
Latest revision as of 06:36, 5 August 2024
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
. - Battle logs (captured by doing
/battlelog
while in battle) can also be found inlogs
folder, in thebattlelog
folder. - Drag and drop the file into the
#📤logs-and-screenshots
chat.
MacOS
- Click on your desktop and go to menu bar ( by default at top of your screen), click on
Go
. - Hold
option
key on your keyboard and click onLibrary
. - 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
. - Battle logs (captured by doing
/battlelog
while in battle) can also be found inlogs
folder, in thebattlelog
folder. - 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
. - Battle logs (captured by doing
/battlelog
while in battle) can also be found inlogs
folder, in thebattlelog
folder. - 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
. - Battle logs (captured by doing
/battlelog
while in battle) can also be found inlogs
folder, in thebattlelog
folder. - 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
. - Battle logs (captured by doing
/battlelog
while in battle) can also be found inlogs
folder, in thebattlelog
folder. - 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
. - Battle logs (captured by doing
/battlelog
while in battle) can also be found inlogs
folder, in thebattlelog
folder. - Drag and drop the file into the
#📤logs-and-screenshots
chat.
Prism Launcher
- Choose The Pixelmon Modpack instance and click
Edit
on the side menu bar. - In the Console Window which you just opened, go to
Minecraft Log
tab, clickupload
. If you just had a crash, this window would show up automatically. If you want to find an old log or battle log, go toOther logs
tab, and select the log there then clickupload
. - Paste the link by pressing
command
andV
together on your keyboard into the#📤logs-and-screenshots
chat.
Other Options
ResPack Folder Workaround
- Enter the
Resource Packs...
settings from Minecraft'sOptions...
menu. - Click
Open Pack Folder
at the bottom of that screen. - In the window that opens, navigate one layer up.
- 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
. - Battle logs (captured by doing
/battlelog
while in battle) can also be found inlogs
folder, in thebattlelog
folder. - Drag and drop the file into the
#📤logs-and-screenshots
chat.
This workaround will lead you to the correct log folder(s) regardless of the operating system or launcher you're using.
Notes
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.