The update in brief
SAND’s first major content update introduces Spaceport, a new island that serves as the final extraction point in Storm Dive. It also adds the Obsidian Crater biome, the Dropship Crash Site event, expanded islands, new environmental hazards, lore notes, and a range of fixes.
Aurogen Crystals are exclusive to Obsidian Crater. The biome includes damaging lava cracks and the new Heat system: once enough temperature builds up, the character takes damage. Crash Sites appear on the map, and approaching one spawns Ironclads.
Those changes create new routes, hotspots, and reasons for squads to contest the same locations. For cheat users, though, the immediate issue is the updated game client rather than the loot route itself.
What this means for cheat users
The published notes contain no statement about an anti-cheat update, a detection campaign, or a ban wave. That is not a safety signal: no cheat can offer guaranteed safety.
The patch changes world generation, map content, events, items, transport-related behavior, UI elements, and multiple game systems. Compatibility with the current SAND build needs to be confirmed by the cheat developer after an update of this scale. A build that worked before the patch should not be assumed to work now.
Check the current provider status for the product you use, whether that is Shack for SAND or Phoenix for SAND. If there is no confirmation for the live game build, wait for the provider’s update rather than using your main account to find out.
What to do before launching
Confirm that the game has fully updated, then check the product’s current status. Do not treat the patch size, the absence of anti-cheat notes, or a successful launch before the update as evidence of compatibility.
When a provider has marked a build as updated, keep your setup clean: avoid unverified loaders, do not combine old files with a newer release, and shut down unnecessary overlays or debugging tools. The safe launch checklist covers the basic preparation steps.
Do not try to modify the game client to force an outdated build to run. Post-patch incompatibility can show up as crashes, freezes, bad visuals, or missing game data. None of those symptoms can establish that a setup is low-risk.
Changes you will notice in raids
Spaceport becomes a predictable end-of-run destination, while the map-marked Crash Site can pull players into the same area. Obsidian Crater adds a separate environmental threat: players need to account for Heat buildup and lava cracks as well as other raiders.
World generation has also been adjusted to make terrain less mountainous and to keep islands farther from map edges, reducing the number covered by the first circle. The developers fixed an item-duplication exploit that included Orbital Strike and changed item dropping so objects cannot be dropped through obstacles.
The developers warn that shader compilation may cause stutters or FPS drops during roughly the first 20 minutes of a match. That is listed as a game issue, so do not use one unstable match to judge cheat compatibility.
Play now or wait?
If your provider has not explicitly confirmed support for the current SAND client, wait. That is the practical call after this update.
A confirmed product status indicates provider-stated compatibility, not immunity from detection or penalties. The update also adds a Report Player button to the death screen, and player reports and in-game behavior remain part of the overall risk picture. Read why cheats get detected for a breakdown of detection waves, reports, and other factors.
Original source developer announcement