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 skies@failbettergames.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.

Core information

Current build: 1.0.1.5.91c3278

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.)
      • 64/32bit
    • RAM
    • CPU
    • GPU
  • Troubleshooting steps you’ve already undertaken

There is an example bug report below.

Graphical Issues

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.

Text Issues

If you find typos or grammatical errors, please include a screenshot as this often helps us locate the issue in our CMS.

Output Logs

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.

Windows

C:\Program Files (x86)\Steam\steamapps\common\Sunless Skies\Sunless Skies_Data\output_log.txt

OS X

~/Library/Logs/Unity/Player.log

Linux

~/.config/unity3d/Failbetter Games/Sunless Skies/Player.log

Crash Logs

If you experience a crash then crash files are auto-generated and should appear in the install directory. This is usually found in the following location:

Windows

C:\Program Files (x86)\Steam\SteamApps\common\Sunless Skies (if you’re using Steam)

C:\Program Files (x86)\Sunless Skies (if you are not)

OS X

~Library/Application Support/Steam/steamapps/common/Sunless Skies (if you’re using Steam)

Linux

~/.local/share/Steam/steamapps/common/Sunless Skies (if you’re using Steam)

Save Files

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.

  • autosave_m.json
  • autosave_s.json
  • saveSnippet.json

The characterrepository directory can be found in the following locations depending on your operating system:

Windows

C:\Users\[USERNAME]\AppData\LocalLow\Failbetter Games\Sunless Skies\storage\characterrepository

OS X

~Library/Application Support/unity.Failbetter Games.Sunless Skies/storage/characterrepository

Linux

~/.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

  1. Open the Hold UI
  2. 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

Build: 1.0.1.5.91c3278

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