Controls & Saves
Export a Save and Prepare a Useful Bug Report
In the save selection screen, choose Export to obtain the save file string the developer asks for. For a freeze investigation, also collect your system specifications and the full swarmslam.log from the same place as the save files. These are the developer’s actual November 7 requests; sending a short excerpt or describing a subtle button alone may leave out the information needed to investigate.
On this page
Export the save that exhibits the issue
- Identify the save and the situation in which the problem occurs.
- Go to the save selection screen.
- Use Export to obtain its save file string.
- Keep that string with the description of the affected save and reproduction steps.
joffarex supplies that route after a player asks how to send the save. The read answer does not establish an Import screen, a conversion utility or what happens when overwriting another slot. Exporting support evidence and migrating into the full game are different tasks.
Collect the full log and the relevant environment
- Locate the game’s actual save-file location.
- Look there for swarmslam.log, as requested by the developer.
- Keep the complete file rather than only selected lines from its end.
- Record the system specifications and whether this is the Demo or full game.
- Describe what happened, what you were doing and whether you can reproduce it with that save.
The October 2 Demo notes document an Open Folder button in the save picker. If that option is present in your current build, it provides a dated route to the location. The saved sources do not establish universal Windows or Linux paths, so this guide does not invent one.
In the freeze discussion, the developer specifically asks for the full log after the player posts a partial excerpt. The visible save’s version field belongs to that particular report; it is not an independently checked version number for every current client.
Use a real support route and keep the outcome separate
The release announcement names the in-game feedback form in Settings and the developer’s official Discord. In the autoplay thread, joffarex also offers the original discussion as a place to provide the exported save string. Follow the actual support request and the destination’s rules.
The older Demo notes describe a separate Crash Reports preference shown in the intro and adjustable later in Settings. Choosing that preference is not the same as preparing the manual save, full log and environment details requested for a particular issue.
The freeze thread ends with the player providing the requested material, not a published solution. Do not call a support submission a confirmed fix, and do not run code copied from somebody else’s posted save as a troubleshooting step.
The support package is ready when it contains the correct exported save string, the complete log and enough environment and symptom information to identify the case. The issue is resolved only if a later result establishes that; this page supplies the documented reporting route.
Sources & version
joffarex’s November 7 Export reply supplies save selection → Export → save file string. Game freezes every few minutes for ~10 seconds, complete Demo opening post and four replies, supplies the specifications, same-location swarmslam.log and full-file requests. The November 5 release announcement names the feedback form and Discord; the October 2/7 Demo notes supply the dated Open Folder and Crash Reports context. No files were submitted or fix tested for this guide.