Support log and crash reports¶
A support log is one text file with everything needed to look at a problem. It is redacted on your computer before it is written, and Xol never sends it anywhere. You decide who gets it.
Export a support log¶
- Open Settings ▸ Support.
- Press Export support log….
- Choose where to save it. The suggested name is
xol-support-<date>-<time>.txt. - Read it, then attach it to your email to contact@xol.dev.
After a crash, the "Minecraft crashed" panel has the same Export support log button, and Copy for support, which puts a short summary with the last lines of the crash on the clipboard, private details removed.
If it cannot be saved, the launcher says "The support log was not saved" with the reason.
What it contains¶
Xol support log
generated: 2026-09-18T10:40:31.407Z
launcher: 0.3.1 (Electron 44.4.2)
os: darwin 23.6.0 / arm64
cpu: Apple M2 x8
ram: 16384 MiB
profile: xol-1.8.9 (Xol 1.8.9, experimental)
instance: xol-1.8.9
preset: balanced
memory: 4096 MiB
custom java: no
java runtime setting: auto
instance last ran on: native-arm64
extra jvm args: (none)
manifest: revision 11 (bundled)
last exit: (no game run in this session)
Tokens, session strings, e-mail addresses, IP addresses and your home folder path are redacted below.
===== automatic java arguments =====
…
===== crash report: crash-2026-09-18_12.01.07-client.txt =====
…
===== multiplayer: connections and disconnect reasons =====
…
===== game log: game-2026-09-18T10-01-02-113Z.log =====
…
The values above are an example.
| Part | Detail |
|---|---|
| Custom Java | Only "yes" or "no". The path is not included. |
| Java runtime setting | On an Apple Silicon Mac, the choice in Settings ▸ Java ▸ Java runtime for 1.7 / 1.8: auto, native or rosetta. On every other machine it reads "(n/a)". See Apple Silicon. |
| Instance last ran on | What the selected instance last started with, from its runtime.json: native-arm64, rosetta-x64, mojang (Mojang's runtime without translation) or custom. If the Apple Silicon runtime was tried and gave up, the line adds "(the Apple Silicon runtime was tried and fell back: …)" with the reason, for example "no game window after 90s". An instance with no record reads "(no record)". |
| Automatic Java arguments | Every argument Xol added for the last launch, with the rule and the reason. See Automatic Java arguments. |
| Crash report | The last crash report of this session, if there was one: its last 4,000 lines, at most 400,000 characters |
| Multiplayer | Each server the game connected to and each disconnect reason, taken from the game log. "(no server was joined in this log)" if there was none. |
| Game log | The end of the game log of the last run in this session, or else the newest game-*.log: at most 4,000 lines and 1,500,000 characters. If the beginning was cut, the first line reads "(earlier lines omitted)". With no log: "(no game log found)". |
What is removed¶
Tokens, session strings, access keys, email addresses, IP addresses and your home folder path, plus any other user's profile folder name. The exact list is on Privacy and data. This is the second net: the launcher already scrubs the live access token out of the game's output before it reaches the log file.
Read it before you send it
Redaction looks for patterns. A game log also contains what the game prints: chat, the names of servers you joined, other players' names. None of that is removed. If you would rather not share something, delete those lines from the file. It is plain text.
Where logs and crash reports are¶
| What | Where |
|---|---|
| The game log the launcher keeps for each run | logs/game-<date and time>.log in the data folder. Settings ▸ Instance ▸ Open folder ▸ Game output logs opens it. (Logs in the same row of buttons is the logs folder inside the instance, which the game writes itself.) |
| Crash reports written by the game | crash-reports/ inside the instance folder. Open crash report on the crash panel opens the latest. |
"There is no crash report from the last run." means the game ended abnormally without writing one. The game log then has the details.
Sending a crash report to Xol¶
This is separate from the support log, and it is the only thing of this kind Xol ever sends.
- Switch on Settings ▸ Support ▸ Diagnostics ▸ Allow sending reports to Xol. It is off by default.
- After a crash, press Send this crash report… on the crash panel.
- The dialog shows exactly what would be sent, already redacted, with its size. Nothing has left your computer at this point.
- Press Send, or Cancel.
| Message | Meaning |
|---|---|
| Sending is off. Turn the switch on to send this report. | Diagnostics are off. The switch is in the dialog too. |
| There is no crash from this session to report. | Reports can only be made from a crash in the current session. |
| The service is not taking more reports from this connection right now | The service limits how many reports it takes. Try again in an hour, or use Copy for support. |
| The service would not take the report without an access key | The service has not been updated yet. Try again later, or use Copy for support and send it yourself. |
| The report was not sent: … | The service was unreachable or refused it. The report stays in the dialog, so you can press Send again. |
| Report sent. Thank you. It contains no account data and cannot be used to sign in as you. |
What the report contains, how it is limited and how long it is kept (30 days) is on Privacy and data.