Send your logs to the developers
When something goes wrong, you can send your logs to the developers straight from the launcher.
- Select Send Logs to Developers at the bottom of the sidebar, above ACTIVE PROFILE.
- Enter your Discord username. The developers use it to reply to you.
- Optionally, describe what went wrong under What went wrong? (up to 1000 characters).
- Select Send.
The dialog shows the progress, then Sent — thanks!. If the logs could not be sent, it shows the reason, such as no connection to Discord or the HTTP status Discord returned, and Try again. The launcher remembers your username for next time.
Send the zip yourself
The launcher keeps a copy of the zip in $DATA/logs/, the newest 10. To send it to someone else, such as the author of a track or a mod:
- Send your logs as above. The zip is kept whether or not they were sent.
- Under the result, select Click here to open them in File Explorer (on Linux, in your file manager). The folder opens with the zip selected.
- Drag the zip into Discord or a message.
On Linux, the launcher asks your file manager to select the zip over D-Bus (org.freedesktop.FileManager1). Without one that answers, it opens the logs folder.
What gets sent
The logs go to the developers' Discord as one zip file, swofty-logs-<username>-<time>.zip. A large zip goes in several parts.
| In the zip | Contents |
|---|---|
summary. | Your username and message, the launcher version, your operating system, CPU and memory, the game's version and folder, a summary of the latest crash report, the summary of the latest performance report, and the active profile's addons by name: those on in load order, then the rest, each with its version, id, where it came from (built in, DB Editor, imported from which mod file, or installed) and the settings changed from their defaults |
crash/crash-<time>., crash/crash-<time>. | The newest crash report the game wrote and its minidump, when there is one. The minidump is left out, noted in the summary, when it is too big for the zip |
game/loader., game/perf. | The loader log and the performance report of the game that's running |
state/*. | The launcher's own logs, such as launcher-run. and wrapper-run. |
sessions/<time>/ | The logs and small files of your three latest game sessions, such as loader., perf., env. and exit_code |
addons/<id>/helper. | Each addon helper's log |
addons. | The id, name, version, source, category, types and origin of every installed addon, and each profile's addons with their names and settings |
conflicts. | From the active profile's last build: each pair of addons that change the same thing, which one wins, and the records, resources, files and text they both change |
config. | The launcher's settings |
game/career-editor/snapshot. | The Career Mode Editor's snapshot, when the game folder has one |
The logs can include folder paths with your computer's user name, your hardware, and your installed mods and profiles. Passwords, tokens and keys in config.json, in addon settings and in each session's env.txt are replaced with [redacted]. Each file is cut to its last 5 MB, and the whole zip holds at most 40 MB before compression.
A bot in the developers' Discord reads each report with Anthropic's Claude API to suggest a cause, so the zip's contents are also sent to Anthropic.
From the command line
swofty logs send --name <your Discord username> --message "What went wrong"The command keeps the zip in $DATA/logs/ too and prints its path. To write the zip and list what it holds without sending it, add --dry-run. See swofty logs send.
Builds from source don't include the developers' Discord address. There, the button reads Save Logs: it saves the zip to $DATA/logs/ without sending it, then offers the same link to the zip. swofty logs send only works with --dry-run.