Sandustry Answers
Sandustry Early Access 0.5.5Sources checked 22 August 2026Unofficial player-run reference
Home / Answers / COMMUNITYEarly Access 0.5.5Checked 23 August 2026Developer statement

Where do I report a Sandustry bug or suggest a feature?

One channel is current and explicit. The other is nineteen months old, and this page says so rather than smoothing it over.

Quick answer

Feature requests have a current destination: the developer's suggestion board at sandustry.nolt.io, named again in Update #1 on 16 August 2026, with the reason stated — ideas kept there can be upvoted, and that is how the developer decides what to work on next. Bug reports have no equally current instruction. The only explicit one, that the easiest way to report something is through Discord, was published on 27 January 2025 during the Steam playtest and has not been repeated since. Crashes are the exception the developer does address in the present tense: Update #2 states that crash dumps may contain sensitive information, so the developer will reach out to affected players individually and explain how to enable the diagnostics.

Steps

  1. For a feature or a suggestion, post it on the board the developer names, sandustry.nolt.io. The stated reason for keeping them there is that upvotes help the developer prioritise.
  2. For a bug, the developer's only explicit instruction points at the Discord server. Read its date before relying on it: 27 January 2025, during the playtest, before Early Access existed.
  3. For a crash specifically, send nothing unprompted. The developer states he will contact people experiencing crashes and explain how to turn the extra diagnostics on.
  4. Know where your log file is either way. The per-platform paths are published, and are covered on the crash logs page.
  5. Do not go looking for a public bug tracker. None is published.

Requirements / limits

  • The suggestion board did not load from this site's checking environment on 23 August 2026: the request was stopped by a Cloudflare bot check. The URL is cited as the destination the developer published, not as a page verified here, and nothing on this page describes the board's contents.
  • The Discord instruction is quoted with its date attached deliberately. It predates Early Access, and no announcement since has repeated or withdrawn it.
  • The Discord invite links the developer has published inside announcements are also from the playtest and demo period. Current announcements link Discord without exposing an invite in their text.
  • This site has not joined the Discord server, created an account, or posted anywhere.
  • No source states a response time, a triage policy, or who reads which channel.

Common mistakes

  • Filing a bug on the suggestion board. The developer's stated purpose for it is feature requests and suggestions, ranked by upvote.
  • Sending a crash dump because a forum reply asked for one. The developer's published position is that he initiates that exchange, and gives a privacy reason for it.
  • Treating the 2025 Discord line as current policy without noticing its date.

Still unverified

  • Is Discord still the intended bug channel?Not verifiedThe only explicit statement is from 27 January 2025 and has neither been repeated nor withdrawn in any Early Access announcement.
  • Does the developer read Steam discussions for bug reports?Not verifiedUpdate #1 credits a player by name for a clean bug report without saying where it arrived.
  • Is the suggestion board still in use?Not verifiedNamed in an announcement seven days before this check. The board itself was not loaded from here.