SANDUSTRY

Sandustry Cheats: Debug Tools, Commands, and Save Safety

Sandustry has no confirmed public cheat-code list. Review the hidden debug-menu report, its unsupported status, and save-safety steps before testing it.

Sandustry Wiki · Updated

On this pageWhat is actually confirmedThe reported debug featureWhy command lists are unreliableSafer testing procedureSources and status

There is no confirmed, supported list of Sandustry cheats or native text commands in the collected sources. A removed Steam Community guide describes an undisplayed debug menu, but it was marked incompatible with Sandustry and is not an official support path. Treat debug access as an experiment on a disposable save, not as a guaranteed cheat system.

What is actually confirmed

QuestionEvidence-based answer
Built-in cheat-code listNone found in the collected sources
Public console commandsNo reliable command list was found
Third-party trainersWeMod’s collected page says it does not yet have Sandustry cheats; another trainer page is promotional rather than official documentation
Debug menuA removed Steam guide reports an internal menu and browser-storage flags, but the guide was marked incompatible and unsupported

Search results that promise an “infinite resources” trainer are not enough to establish a safe or working method. The collected trainer article also conflicts with the WeMod listing and provides no developer confirmation, so it is not used as an instruction here.

The reported debug feature

The removed community guide claims that the build contains tools such as a cell inspector, lighting and chunk overlays, authorization-zone views, and a debug brush. It says the interface toggle is unreachable and that the setting is read from browser storage at startup. Because the guide was removed and marked incompatible, the wiki cannot promise that these tools work in the current build or that the storage keys remain unchanged.

The same report says saves carry a cheatsUsed flag alongside a modsUsed flag. It does not map exactly which actions set that flag. That uncertainty is enough reason to keep a backup and avoid a main progression save.

Why command lists are unreliable

No collected source verifies commands such as item-spawn or god-mode text entered into a developer console. Sandustry’s materials are physical pixels and the game is in Early Access, so an old guide, a memory address, or an undocumented key can stop working after an update. Do not present a third-party trainer’s feature list as an in-game command reference.

Safer testing procedure

  1. Copy or back up the save you want to protect.
  2. Test only in a separate world made for debugging.
  3. Record the game version and any mod or guide used.
  4. Verify that the save still loads and that progression behaves normally.
  5. Remove the experiment before returning to a legitimate playthrough.

If the goal is simply to build faster, use the normal research, logistics, blueprint, and resource guides in this wiki. They are supported by the collected game information and do not depend on hidden flags.

Sources and status