Sunless Skies: How to Report a Bug
Hello! If you’re reading this, you’ve probably found a bug and want to report it to us. Before you do, please take a moment to scan our Known Issues page so you don’t waste time reporting an already known bug. If you can’t see your bug listed there, please see below for how to report your issue to email@example.com.
When submitting a bug, the more information we have, the better! Every email will be looked at, but we’re a small team and are likely to be inundated with reports during Early Access. Please be patient with us, and forgive us if you don’t receive a personalised response.
Current build: 220.127.116.11.e8412a5
One bug per report please!
- Clearly summarise the bug in one or two sentences. Explain where you were in game and what you were doing when you experienced the issue. Please give reproduction steps if possible.
- The build you are using (visible on the title screen)
- Platform and tech specs:
- OS (Windows, MacOS, Linux)
- Version (XP, 10, Ubuntu, Mint, El Capitan, Sierra, etc.)
- OS (Windows, MacOS, Linux)
- Troubleshooting steps you’ve already undertaken
There is an example bug report below.
Please include a screenshot where possible. Videos can also be helpful but our ticketing system has a 7MB file size limit, so please compress video files or zip them up.
If you find typos or grammatical errors, please include a screenshot as this often helps us locate the issue in our CMS.
No need to check the Known Issues list for typos as we do not list them. In a break from our one bug per report policy, it can help if you group typos by the areas they are encountered in where you can. So rather than one typo per email or even a list of 50 typos across the entire game, the best thing to do is send all typos found at Magdalene’s, for example, in one email. This makes it much easier for our writing team to deal with.
Often, to track down a bug, we need to take a look at your output log. Here’s how to find it on your operating system. Please note: the log file is replaced each time you run the game, so it’s important to submit the file immediately after the session in which you experience the bug.
N.B. As part of the Reach Redesign build we upgraded our Unity version and this has resulted in the output log being generated in a different location on PC. This is not something we can revert just at the moment without significant work, so we have updated the location below. Ensure you are sending the correct output log based on the version of the game you are running.
Windows – after Reach build (v18.104.22.168.aa85c96 – 10th Oct 2018)
STEAM/GOG: C:\Users\[USERNAME]\AppData\LocalLow\Failbetter Games\Sunless Skies\output_log.txt
Windows – prior to Reach build
STEAM: C:\Program Files (x86)\Steam\steamapps\common\Sunless Skies\Sunless Skies_Data\output_log.txt
GOG GALAXY: C:\Program Files (x86)\GOG Galaxy\Games\Sunless Skies\Sunless Skies_Data\output_log.txt
~/.config/unity3d/Failbetter Games/Sunless Skies/Player.log
If you experience a crash then crash files are auto-generated and should appear in the install directory (the name of the folder will be the date on which the crash occurred). This is usually found in the following location:
C:\Program Files (x86)\Steam\SteamApps\common\Sunless Skies (if you’re using Steam)
C:\Program Files (x86)\Sunless Skies (if you are not)
C:\Program Files (x86)\GOG Galaxy\Games\Sunless Skies (if you’re using GOG Galaxy)
~Library/Application Support/Steam/steamapps/common/Sunless Skies (if you’re using Steam)
~/.local/share/Steam/steamapps/common/Sunless Skies (if you’re using Steam)
Intermittent errors that occur regularly in a particular save game can be difficult for us to identify, so occasionally we may ask you to provide us with your save files. These files, listed below, can be found in one of the Lineage folders in the characterrepository directory.
The characterrepository directory can be found in the following locations depending on your operating system:
C:\Users\[USERNAME]\AppData\LocalLow\Failbetter Games\Sunless Skies\storage\characterrepository
~Library/Application Support/unity.Failbetter Games.Sunless Skies/storage/characterrepository
~/.config/unity3d/Failbetter Games/Sunless Skies/storage/characterrepository
Example Bug Report
Below is an example report for an existing issue in Sunless Skies.
Bug: The Hold interface does not update automatically after jettisoning cargo
- Open the Hold UI
- Click on the jettison icon and jettison an item – the jettison interface will update automatically with the correct number of items but the Hold interface does not
Specs: Windows 10, 64bit, 16.0GB RAM, i7-4770 CPU @ 3.40Ghz, AMD Radeon R9 200 series
Troubleshooting: Closing and reopening the Hold interface resolves the issue