Dishonored Console Commands Better -

Then the command line would vanish. The save files would corrupt. And the next morning, the player would find their desktop background changed to a screenshot of their character standing in their own bedroom, taken from an angle that shouldn’t exist.

I remember the first one I found. It was in a late-90s shooter, a game already old when I bought it from a bargain bin. The disc was scratched, the label worn to a silver mirror. Inside the config.cfg file, nestled between cl_updaterate and fov , was a line I had never seen:

But some commands… some commands were dishonored . dishonored console commands

Worse, he said, the other NPCs would notice. Not in a programmed way—their AI had no reaction script for unmake . They would just… stop. Turn their heads toward the empty spot. And go silent. No patrol routes. No idle chatter. Just a collective, mechanical mourning.

They’re dishonored for a reason.

Their character—a hero they had spent 200 hours building—would look up. Look through the screen. And whisper in a voice not written in any dialogue file:

The second dishonored command I learned from a friend of a friend, a former QA tester who spoke in whispers. He told me about unmake . Not delete , not destroy . unmake . He said if you targeted an NPC and typed it, the NPC wouldn’t die. It would simply cease . No ragdoll. No blood. No entry in the death log. The game’s memory would stutter, trying to recall what used to occupy that space, and find nothing. Then the command line would vanish

The most dishonored command of all, though, has no name. Or rather, it has too many. In the source code of a cult classic RPG, buried under 17 layers of obfuscation, is a function called Reclaim.exe .