When something breaks — a crash, a black screen, a launch that never opens — the client writes a log of what it was doing. Attach those files to your Discord bug report so staff can see the same error you hit, instead of guessing from a screenshot.
Most players
1. Windows
.spawnpvp\logs
HD client logs live here, under your user folder.
client.log
The latest log. Send this first.
-
Open the folder
Press Win+R, paste this, and press Enter:
%USERPROFILE%\.spawnpvp\logs -
Grab the latest log
Copy
client.log. If you also see dated files such asclient_2026-10-30.1.log, those are older rolls of the same log — include today’s if the crash was earlier in the day. -
Extra crash files, if they exist
If the same folder has a file starting with
jvm_crash_, attach that too. The Windows launcher does not write its own log file — the HD client log is the one that matters.
Game-side error dumps, when present, sit in %USERPROFILE%\SpawnPvP-Cache as error_full.txt and error_temp.txt. Attach those two files if they are there. Do not zip the whole cache folder.
Finder
2. macOS
~/.spawnpvp/logs
HD client logs. Same files as Windows: client.log and dated rolls.
~/Library/Logs/SpawnPvP
Mac launcher logs: launcher.log and another client.log.
-
Open the HD client logs
In Finder, choose Go → Go to Folder… (or press Shift+Command+G), paste
~/.spawnpvp/logs, and press Return. -
Open the launcher logs
If you used the Mac launcher, also open
~/Library/Logs/SpawnPvPthe same way. Sendlauncher.logandclient.logfrom that folder as well. -
Extra crash files, if they exist
Attach any
jvm_crash_file in the HD logs folder. Game-side dumps, when present, areerror_full.txtanderror_temp.txtin~/SpawnPvP-Cache.
HD client jar
3. Linux
Linux uses the HD client the same way. Logs are in ~/.spawnpvp/logs. Copy client.log, plus today’s dated client_*.log rolls if they are there, and any jvm_crash_ file in that folder. Game-side dumps, when present, are error_full.txt and error_temp.txt in ~/SpawnPvP-Cache.
There is no Linux launcher log. If you started the HD client yourself, the .spawnpvp/logs folder is still the one to send.
Buttons that already exist
4. Open it from the client
- If the client fails to start, the error window has a button labelled Open logs folder. That opens the same
.spawnpvp/logsfolder. - If the client is already open, right-click the screenshot (camera) button in the sidebar and choose Open screenshot folder.... Screenshots live next to logs — go up one folder, then open
logs.
The Windows launcher has Troubleshoot for Java and cache checks. That is a text report, not the log folder. The Mac launcher does not have an open-logs button; use Finder as above.
Keep it small
5. Which files, and zip if needed
Always send the latest client.log from .spawnpvp/logs.
Send a crash dump or error_full.txt / error_temp.txt if those files are there.
On Mac, also send launcher.log from ~/Library/Logs/SpawnPvP.
Do not zip the whole cache or your settings folder. Those are large and are not the logs.
If you have several files, zip just the logs folder (and the Mac launcher log folder if you used it). One zip is easier to attach than a pile of loose files.
Discord
6. Attach them to your bug report
-
Open Discord
Join SpawnPvP if you have not already: discord.com/invite/BcWaCJXWXY. You can also use spawnpvp.com/discord.
-
Open a bug report ticket
Create a ticket and describe what happened: what you clicked, what you saw, and when. Then attach the log zip or the files from above.
Logs are safe to send
The client log records startup details, Java arguments, and errors. It does not write your password. Saved login details live in a separate settings folder — send only the log files, never your settings. Never share your password.