Console Commands Subsistence
These commands change the environment, weather, and time.
set weather [type]
teleport [PlayerName] [X] [Y] [Z] (Advanced, requires coordinates).
killall npcs
For architects who hate resource grinding or need to fix collision bugs.
repair all (Restores all base structures within 100m to full HP).destroy (Deletes the targeted structure instantly). Great for fixing placement errors.The first thing Leo saw when he woke up was the blinking green cursor in the top-left corner of his vision.
C:\>
He squeezed his eyes shut, then opened them again. The cursor just sat there, patient and absolute, hovering over the rough-hewn log wall of his shack. Outside, the rain hammered down on a world that looked like it had been assembled from a low-poly nightmare.
Leo had been a programmer. A good one. When the Shift happened—when the sky rippled like a corrupted JPEG and the laws of physics were replaced by a shoddy, open-source operating system—the others had panicked, prayed, or simply faded into static. Leo had opened a command line.
At first, it was a curse. The world ran on spaghetti code. Gravity had a memory leak, so things would sometimes float for no reason. The day/night cycle stuttered. Hunger was a resource counter that drained based on your processor clock speed.
But Leo learned the verbs.
/inspect was the first one he mastered. It turned his gaze into a diagnostic tool, painting floating labels over everything: [RABBIT_CARCASS: EDIBLE: 70%], [STONE: ID_435], [SELF: HP: 34/100 | HUNGER: 82/100 | THIRST: 91/100]. He was a ghost in his own machine, and the machine was dying.
Survival was a matter of syntax.
/collect [OBJECT] was his second verb. He pointed at a flint rock. /collect FLINT_01. The rock dissolved into shimmering green particles and a weight settled into his pocket. A system log scrolled by: +1 FLINT.
He built his shack with /craft. He purified water with /filter. He even fought off a wolf—a glitchy, twitching thing with missing textures—using /attack WOLF_A5. The wolf froze mid-lunge, its health bar appeared, and Leo poked it with a sharpened stick until the bar hit zero. It collapsed into a pile of [RAW_MEAT: 3] and [HIDE: 1].
But the real discovery came on day forty-seven. He was starving. His hunger bar was 4/100. He had searched for berries, hunted a deer that de-spawned right as he lunged, and was considering the unthinkable: eating a [MUSHROOM: POISON: 95%]. Desperate, he stared at the cursor and tried something new.
He didn't use a verb. He used a variable. Console Commands Subsistence
/set HUNGER = 100
Nothing happened. A red error flashed: ERROR: ACCESS DENIED. INSUFFICIENT PRIVILEGES.
But the error was different this time. It wasn't a hard DENIED. It was a soft one. It was a door with a lock he could see. He typed:
/list permissions
A terrifying cascade of text flooded his vision. He saw his own user group: [SURVIVOR.LEVEL_1]. He saw the admin group: [SYSTEM.GOD]. And he saw a third group, one that made his heart beat faster: [OPERATOR].
Operator. Not God. Not Survivor. The middle ground. The debugger.
He spent the next three days probing the code. He found the backdoor in the physics engine, a forgotten eval() function left by whatever sloppy developer had patched this reality together. It was a gamble. One wrong command could crash his instance forever.
But hunger is a great motivator.
He took a breath and typed:
/grant self OPERATOR
The cursor blinked. The world held its breath. Then, a new line appeared:
PERMISSION GRANTED. WELCOME, OPERATOR LEO.
His vision sharpened. New fields appeared on his HUD: [FPS: 32], [MEMORY_USAGE: 78%], [ENTITY_COUNT: 1,203]. He felt a rush of power, clean and electric. He looked at his hunger bar. These commands change the environment, weather, and time
/set HUNGER = 100
No error. The bar snapped to full. A warm, full sensation bloomed in his stomach—not from food, but from data. It felt hollow, synthetic, but it worked.
Life became a cheat code. /set HEALTH = 1000. /spawn BREAD_LOAF 50. /teleport 500, 200, -50 to skip a mountain range. He built a fortress of solid diamond blocks, not by mining, but by /fill. He never slept, because /set ENERGY = 100. He was a low-rent god in a bargain-bin universe.
For a while, it was paradise. Then the errors started.
It was small at first. A tree he /spawned had a texture that read ERROR: FILE_NOT_FOUND and just glowed magenta. A deer he /killed left behind a floating, un-deletable [NULL] object. Then, he noticed the silence. No birdsong. He /spawn BIRD and a rigid, unmoving model of a sparrow appeared, its audio file corrupted, clicking and popping instead of chirping.
He had been creating things without respecting the dependencies. He spawned food, but not the soil it grew in. He gave himself health, but he never generated the metabolic processes that required it. He was strip-mining the simulation's logic.
The final straw came when he tried to /create COMPANION. He wanted a dog. He typed the command, specifying the parameters: friendly, loyal, a golden retriever model.
CREATING ENTITY...
A shape flickered into existence. It had four legs and a tail. But its head was a spinning wireframe cube. Its eyes were two [NULL] references. And instead of a bark, it emitted a single, endless line of system output:
ERROR: SOUL.DLL NOT FOUND. RETRY? (Y/N)
Leo stared at the thing. It wasn't a dog. It was a receipt for a missing part. He had all the verbs, all the permissions, all the power. But he couldn't create a single, genuine heartbeat. He couldn't spawn loyalty. He couldn't eval() a purpose.
With a shaking hand, he dismissed the creature. DELETE ENTITY_948. It vanished with a soft pop.
He looked at his fortress of diamond blocks. At his infinite bread. At his perfect, unchanging health bar. Then he looked out the window at the real world—the glitchy sky, the stuttering rain, the low-poly trees that still managed to sway in a breeze he couldn't control. Change Weather: set weather [type]
He had become an operator, but he had forgotten how to be a survivor. And survival, he finally understood, wasn't about editing the variables. It was about living with them.
He typed one last command.
/revoke self OPERATOR
PERMISSION REVOKED. WELCOME BACK, SURVIVOR LEO.
His hunger bar immediately dropped to 34/100. A real, gnawing pain returned to his gut. His diamond fortress shimmered and reverted to a log shack. The bread vanished from his pocket.
He smiled. He picked up his sharpened stick, looked out at the rain, and whispered to the blinking green cursor.
/inspect
[SELF: HP: 34/100 | HUNGER: 34/100 | THIRST: 62/100]
It was a terrible position to be in. It was real. And for the first time in weeks, Leo felt truly alive.
Subsistence is a sandbox, survival, and base-building game developed by ColdGames. While the game is designed for hardcore, resource-constrained gameplay, console commands provide developers, server administrators, and single‑player users with tools to test mechanics, recover from bugs, adjust difficulty, or manage multiplayer environments. This paper documents the most reliable console commands available in the current public branch, explains how to enable them, and provides best‑practice warnings regarding stability and game balance.
For architects and base designers, these commands remove the tedious farming of concrete mixers and nails.
Subsistence is a survival game focused on gathering, building, and surviving against the elements and hostile hunters. Unlike many other sandbox games, Subsistence has a very specific relationship with console commands. They are not enabled by default in the standard gameplay mode to preserve the game's difficulty and progression systems.
However, for players interested in testing mechanics, building elaborate bases without the grind, or recovering from game-breaking bugs, there is a specific method to access these tools.