This is the forbidden undo. The engine constantly stores the last 10 seconds of destruction data in a circular buffer. This cheat lets you "rewind" time for individual voxels or entire regions. That bridge you blew up? Hold [ and left-click the rubble. The voxels will uncrumble, flying backwards in perfect reverse-trajectory, reassembling into a pristine bridge. But here’s the exploit: the "mass" value doesn't reset correctly. If you destroy, then rewind, then destroy again, you duplicate the mass. Do this ten times on a single boulder, and you’ve created a super-dense "black hole voxel" with the mass of a small moon. Drop it on a fortress. The physics engine won't know what hit it.
But after hundreds of hours of testing our new physics engine, we’ve realized something. The "vanilla" destruction is just the tutorial. Hidden beneath the surface (sometimes literally, inside the voxel matrices) are cheat codes that turn this engine into something closer to a god simulator. cheat codes in voxel destruction physics
The Vanilla Rule: You can only destroy voxels you have line-of-sight or explosion-radius to. The Cheat: noclip_destruction 1 (combine with render_voxel_ghosts 1 ) This is the forbidden undo