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

Red blocks in my world will not break. How do I remove them?

The workaround has a hard numeric ceiling, and the developer says the real fix is written but deliberately unshipped.

Quick answer

Delete them in a small selection. Update #1, published 16 August 2026 for v0.5.4, made red blocks removable, and the developer states the demolisher only scans for orphans when you delete 256 tiles or less, because that scan adds overhead. A large sweep is the one case where it does not run. Red blocks sitting on puzzle doors are handled separately: the developer states that closing and opening the door should restore it, and asks to be told if it does not. None of this is the fix. The same post states that a fix for the underlying causes exists, touches a lot of core paths, and is being held back until it is risk-free.

Steps

  1. Update to v0.5.4 or later first. Before that build the developer's own heading for the problem is the indestructible red block, and no removal existed.
  2. Use the demolisher on a small area rather than one large sweep. The developer's stated condition is a deletion of 256 tiles or less.
  3. If the red block sits on a puzzle door, close the door and open it again instead. The developer states this should restore it.
  4. If that does not work, the developer explicitly asks to hear about it, which is worth knowing before you rebuild the puzzle around the block.
  5. Do not delete a puzzle's reset button to clear the state. Since v0.5.4 it cannot be deleted, and the developer states it is restored on reload if an older save lost it.

Requirements / limits

  • The 256-tile condition is the developer's own number and comes with the developer's own reason: the orphan scan costs the demolisher performance, so it only runs on small deletions.
  • No source states what creates red blocks. The developer refers to root causes in the plural and names none of them.
  • The door restore is published together with a request for failure reports, which is the developer treating it as unconfirmed rather than settled.
  • Update #2, three days later, does not revisit red blocks. This page was checked against it.
  • This site has not played the game. Every statement here is the developer's, restated.

Common mistakes

  • Sweeping a huge area to clear them. That is the one case the developer states the removal does not run in.
  • Reading the change as the bug being fixed. The developer separates the workaround from the fix and says the fix is deliberately unshipped.
  • Assuming a save that lost its puzzle reset button is ruined. The developer states the button is restored on reload.
  • Waiting for a patch note that says red blocks are fixed. The removal shipped in v0.5.4 under workaround wording.

Still unverified

  • What causes red blocks to appear?Not verifiedThe developer refers to root causes without naming them, and no other published source describes a trigger.
  • Has the risk-free fix shipped since?Developer statementAs of Update #2 on 19 August 2026 it had not. Not ready to ship it yet is the latest published position.
  • Does closing and opening the door reliably restore it?Developer statementPublished with a request for failure reports attached, so the developer does not treat it as confirmed either.