Join our discord
In partnership with NodeCraft Logo NodeCraft


You are not logged in! Create an account or login to contribute! Log in here!

Difference between revisions of "Finding your logs"

From Pixelmon Wiki
(Added missing Launchers and paths for other Operating Systems)
 
(2 intermediate revisions by 2 users not shown)
Line 10: Line 10:
 
# If you were experiencing a crash, open <code>crash-reports</code>. For other issues, open <code>logs</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>.
 
# 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.
 
# Drag and drop the file into the <code>#📤logs-and-screenshots</code> chat.
  
 
===MacOS===
 
===MacOS===
# Open <code>Finder</code> on your Mac.
+
# Click on your desktop and go to menu bar ( by default at top of your screen), click on <code>Go</code>.
# Navigate to your user's '''home directory'''.
+
# Hold <code>option</code> key on your keyboard and click on <code>Library</code>.
# Click on <code>Library</code>.
 
 
# Click on <code>Application Support</code>.
 
# Click on <code>Application Support</code>.
 
# Click on <code>minecraft</code>.
 
# Click on <code>minecraft</code>.
 
# If you were experiencing a crash, open <code>crash-reports</code>. For other issues, open <code>logs</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>.
 
# 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.
 
# Drag and drop the file into the <code>#📤logs-and-screenshots</code> chat.
  
Line 27: Line 28:
 
# If you were experiencing a crash, open <code>crash-reports</code>. For other issues, open <code>logs</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>.
 
# 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.
 
# Drag and drop the file into the <code>#📤logs-and-screenshots</code> chat.
  
Line 34: Line 36:
 
# If you were experiencing a crash, open <code>crash-reports</code>. For other issues, open <code>logs</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>.
 
# 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.
 
# Drag and drop the file into the <code>#📤logs-and-screenshots</code> chat.
  
Line 41: Line 44:
 
# If you were experiencing a crash, open <code>crash-reports</code>. For other issues, open <code>logs</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>.
 
# 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.
 
# Drag and drop the file into the <code>#📤logs-and-screenshots</code> chat.
  
Line 48: Line 52:
 
# If you were experiencing a crash, open <code>crash-reports</code>. For other issues, open <code>logs</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>.
 
# 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.
 
# 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:

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. Click on your desktop and go to menu bar ( by default at top of your screen), click on Go.
  2. Hold option key on your keyboard and click on Library.
  3. Click on Application Support.
  4. Click on minecraft.
  5. If you were experiencing a crash, open crash-reports. For other issues, open logs.
  6. Find either the newest crash report file, or the file named latest.log. The latter file may also show up as just latest.
  7. Battle logs (captured by doing /battlelog while in battle) can also be found in logs folder, in the battlelog folder.
  8. 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.

Prism Launcher

  1. Choose The Pixelmon Modpack instance and click Edit on the side menu bar.
  2. In the Console Window which you just opened, go to Minecraft Log tab, click upload. 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 Other logs tab, and select the log there then click upload.
  3. Paste the link by pressing command and V together on your keyboard into the #📤logs-and-screenshots chat.

Other Options

ResPack Folder Workaround

  1. Enter the Resource Packs... settings from Minecraft's Options... menu.
  2. Click Open Pack Folder at the bottom of that screen.
  3. In the window that opens, navigate one layer up.
  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.

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.

© 2012 - 2025 Pixelmon Mod