Understanding the Console in Fallout New Vegas
The console in Fallout New Vegas is essentially a developer debugging tool that got left exposed in the final game. It's accessed by pressing the tilde key (the one above Tab) and gives you direct control over almost every variable in the game state. Once you know how it works, you can fix broken quests, spawn items, adjust difficulty, teleport, and bypass most of the things that make the base game frustrating. This is the comprehensive reference I actually use when something goes wrong. Rather than scrolling through scattered forums, I keep it bookmarked and search for the specific command I need. The guide covers the standard commands plus the edge cases that nobody bothers documenting. Here's how to actually use these things without bricking your save. Open the console by hitting the tilde key. You'll see a text prompt appear at the top of the screen. Everything you type goes into that prompt. The game doesn't respond to anything until you hit Enter. That's it. There's no visual confirmation other than the command executing.
The most immediately useful command is tcl. Toggle Clip Mode turns off collision for your character. You've probably wandered into a cave, gotten stuck on a geometry seam, and had no way out. tcl lets you walk right through walls and floors. Type it again to turn it back on. Simple. One thing people miss is that tcl doesn't always work properly on certain objects like train tracks or elevator platforms. If you clip through and get stuck again, just close the console and reopen it, then try moving in the opposite direction you entered from. For quest issues, the command you need most often is showquestgoals. It lists every stage of every quest in your journal, including ones you haven't started yet. When a quest objective says "kill X" and you've already killed them but the quest won't advance, you can find the quest ID and jump it forward with the setstage command. You type the quest ID, then the stage number you want to set. Stage numbers go from 0 to whatever the final number is for that quest. Check the guide for the specific quest you're stuck on rather than guessing, because the stage numbers aren't always sequential in any logical way. I ran into a specific problem with the quest "The House Always Wins" where the terminal in the Ultra-Luxe basement refused to interact regardless of what I did. The console showed the object was active and available, but the game simply wouldn't trigger the dialogue. I pulled up the quest goals, found the relevant stage, and used setstage to push it forward two stages. The quest continued normally after that. I still don't know what caused the glitch in the first place, but jumping the stage fixed it permanently.
Item spawning works through the player.additem command. You need the item's base ID, not the ref ID. The base ID stays the same no matter where the item appears in your world, while ref IDs are generated per-object-instance. A legendary item like the Legendary Hellstrom might have a different ref ID depending on which version of the game loaded it, but its base ID is always the same. I keep a separate reference sheet for the weapons and armor I use most, with their IDs written down, so I don't waste time looking them up every time I want to spawn something. There's a common misconception that using console commands disables achievements. In Fallout New Vegas, the Steam version tracks achievements separately, and console commands don't block them in most cases. The exception is commands that alter skill levels permanently, like setskilllevel for perks you can't normally obtain. If you give yourself a perk through the console, it may prevent achievement tracking for that session. I don't use it myself, but it's worth knowing if you care about that sort of thing. Difficulty adjustments are straightforward with setdifficulty. The value goes from 0 to 5, where 0 is no kill rewards and 5 is the hardest setting. Some players think this only changes combat difficulty, but it also affects health regeneration rates and some AI detection parameters. If you're playing on 0 difficulty and it feels too easy, bumping it to 1 or 2 usually makes the biggest difference without becoming punishing.
Get the Full Details
One thing beginners routinely mess up is the resurrect command. It requires a target. You click on the dead NPC or creature first to select them, then type resurrect. If you type it without selecting anything, the console either does nothing or resurrects the last thing you clicked on, which is usually yourself if you were aiming at something else. This has cost me multiple saves where I accidentally revived a corpse instead of the character I meant to bring back. Always double-check the selected object before hitting Enter. The fasttravel command doesn't exist as a single command. What actually works is using prid to select a location, then moveto player to teleport yourself there. I use this when I need to get back to a specific settlement after getting lost in the desert. The catch is that fast travel via console doesn't trigger the loading screen, so you don't get the option to hire a guide or get ambushed during travel. Some players find this annoying because it removes a layer of immersion, but it's faster than walking and doesn't skip random encounters on purpose. If you're dealing with a crash or freeze, the qs command saves your current state to a quicksave slot. I do this before running any commands I'm unsure about. If something breaks, I can reload from that quicksave and try a different approach. I've lost two saves this way where I used the wrong command on an important NPC and couldn't undo it properly.
The console also has a search function. You can type partial commands and use the up arrow to cycle through your command history. If you just typed a long setstage command three games ago, you can press up repeatedly until it comes back. This saves a lot of time compared to retyping long strings of IDs. There's one limitation that's important to understand: console commands don't fix corrupted save files. If your save is already broken and the game won't load it, no amount of command-line work will repair it. The commands manipulate the game state in memory and on disk, but they can't reconstruct data that's been overwritten or truncated. Always keep backups of your important saves in separate folders. I use a naming convention with dates instead of relying on the auto-save system, because auto-saves get overwritten continuously and you can't tell when they happened. For the commands that modify relationship ranks or faction reputation, use modrec for relationship points and modifyav for actor values. These are less commonly needed but come in handy when a companion has turned hostile due to a bug and you want to reset their attitude without restarting the entire questline.
The guide I mentioned earlier organizes all of this by category, which is more practical than the default console help system. The built-in help command shows you the syntax but not the actual IDs you need to use it. The guide fills that gap by listing the most common item IDs, quest IDs, and location IDs with examples of how they're used in context. If you're planning to use console commands extensively, I'd recommend starting a fresh playthrough first rather than trying to fix an existing one. It's easier to understand how the commands interact with a clean game state than to reverse-engineer what went wrong in a heavily modded save. I learned that the hard way after spending three hours trying to fix a quest in a save file that had been altered by six different mods.
