SWORN keeps crashing
The useful official instruction is about the log, not a magic toggle. A pinned Steam post from 11 February 2025, written by Matt B at Windwalk, tells PC players where that file sits.
The log the developer asked for
On Steam: right-click SWORN, Manage, Browse local files, open the log folder, and take the session file from the run that just died. The post describes that file as the one to attach. Players are pointed at the Discord bug forum or the Team17 support form. The form wants a description, steps that repeat the crash, workarounds already tried, and a screenshot.
I am not calling file verification an official fix. Steam’s “verify integrity” control, a GPU driver update, and turning overlays off show up in Reddit threads and in a YouTube fix clip. They are ordinary PC steps. The Unity crash dialog itself does not have a single error code collected in one public table, so I do not print a code.
Xbox and “it just closes”
Console posts describe the same symptom without a local log folder. Those players have the support form and the capture, not the Steam log path. If the crash is actually a co-op drop back to the menu, that behavior is documented as a host disconnect on the multiplayer page, which is a different problem from a Unity fault.
Nothing in Update 2’s public notes says “this build ends the crash.” I will not tie stability to v1.2.
FAQ
Where are SWORN crash logs?
Steam local files, then the log folder, then the file for that session. That path is from the developer’s February 2025 Steam post.
Does verifying files fix it?
It is a step players try. It is not listed as a confirmed fix in the developer post.
Related
Sources
- Steam discussion: reporting crashes — checked 2026-11-10
- Team17 support — checked 2026-11-10
Page updated 2026-11-10. Site check date 2026-11-10.