Opening the Console in Fallout New Vegas
The game has a built-in debug console that opens when you press the tilde key (`), usually located above the Tab key on standard keyboards. This gives you direct command-line access to the game's internal systems. It's an older engine, the Gamebryo version that Bethesda used back in the day, so the commands aren't as clean as you'd find in Skyrim but they get the job done. One thing that trips people up immediately is that the console won't open if you're in a cinematic sequence or some scripted moment. I spent twenty minutes swearing at my keyboard once because I tried to pull it up during the ending cutscene of Honest Hearts. Just wait for the game to settle into normal play first. Also, be aware that using the console voids your ability to earn achievements. If you care about that at all, make a fresh save before you type anything.
Ultimate Fallout New Vegas Cheat Command Guide Unlock Secrets Manipulate Gameplay And Master The Mojave
Here's the practical stuff. The most basic commands you'll use constantly are the player-related ones. Type player.additem [itemID] [amount] to add anything to your inventory. Weapons, caps, ammo, quest items, junk — it doesn't matter. The item IDs are long strings of numbers that you'll need to look up on a separate site. I use the Elder Scrolls Wiki or NVSE wiki when I need them. There are mods like CK Editor Plugins that let you search for items in-game without leaving, which saves a lot of back-and-forth. player.additem 0000000F 10000 will give you ten thousand caps, which is what you'll use most often. player.kill is the quick way to remove any enemy that's been giving you trouble. player.equipitem [itemID] forces the character to put something on immediately, which is useful when you want to test gear without walking to a wardrobe. For quest progression, qv [questID] [stage] advances a quest to a specific stage. This is where things get finicky. If you skip too far ahead without triggering prerequisite triggers, the quest can soft-lock and you'll be stuck until you reload. I've had this happen with several story quests. The workaround is to check the quest stage list online first to make sure you're not skipping past a critical trigger point.
Commands That Actually Matter
tcl toggles collision detection. You walk through walls and floors. Great for getting unstuck when you clip through geometry, which happens more often than you'd think in this game. tm toggles the minimap. Some people disable it to go full immersion mode. setlevel [value] changes your current level. But here's the catch — leveling up this way doesn't properly distribute perk points or attribute bonuses the normal progression system would. It's better to let the game handle leveling through normal play and use this only if you really need to be a specific level for a quest or encounter. I learned this the hard way when I set my level to 30 to skip the early game grind, then went back and realized my perks were a mess because I'd never actually earned them through play. Reloaded and played through the lower levels properly. Took about three hours extra but saved a lot of headache later. player.setav [actorValue] [value] modifies any of the game's actor values directly. This includes health, strength, perception, and every other SPECIAL attribute. player.setav health 500 makes you tankier. You can also use this on scripts and object references, which opens up more advanced possibilities if you're comfortable with the command syntax.
Get the Full Details
recalibrate recalibrates all weapons in your inventory. This fixes the condition percentage display if it's bugged, which is a common issue. resetactorstate returns an NPC to their default behavior, useful when someone gets stuck in a weird animation loop.
Advanced Navigation and Testing Commands
telemetry off disables data collection telemetry. Doesn't affect gameplay but removes a background process. showracemenu opens the character creation screen mid-game. You can reshuffle your SPECIAL attributes and appearance if you regret your choices. This one is genuinely useful and not something most guides mention prominently. showmenu opens the Pip-Boy menu overlay. Useful for checking stats without opening inventory. enable and disable toggle individual object references. Type prid [refID] first to select an object, then disable it. This is how you remove stray enemies or invisible objects that are blocking your path. The moveto command teleports you to an NPC or object by reference ID. player.moveto [refID]. Again, you need the correct ID from a external source. I keep a small text file with commonly used IDs for major characters and locations. Saves time compared to searching every time.
psb gives you every spell. Not particularly relevant for New Vegas since it's not Skyrim, but the command exists in the engine. Don't bother with it here.
Save Scumming and Undo
qsave quick saves. qload quick loads. These use slots Q1 through Q9 by default. The console override save [slotname] lets you name saves, which is better practice. undo reverts the last console command you executed. This is important because some commands are irreversible without a reload. If you accidentally kill an NPC you needed or remove a quest item, undo might fix it depending on what you did. There's no true infinite undo. Once you've closed the console or exited to main menu after certain commands, the changes stick. Always qsave before running a batch of commands. I learned this pattern early and it's saved me from multiple bad runs where I'd deleted a quest-critical item thinking it was just clutter.
Common Pitfalls
The biggest mistake people make is assuming console commands are safe for long-term use. They corrupt save files more often than you'd expect, especially when mixed with mods. The game engine wasn't designed with a debug console as a primary feature, so several commands have memory leaks or object reference bugs that accumulate over time. I've seen saves become unplayable after extended console use — items duplicating, NPCs phasing through terrain, quest triggers failing to fire. If you're going to use these commands extensively, maintain a separate save file without console modifications as your primary playthrough. Use the console versions only for testing or experimental runs. This is the same approach I take with my own games now. I keep one clean save per playthrough and a second one where I'm free to break things. Another issue: some console commands don't work on quest-critical objects. Bethesda locked certain items and NPCs to prevent players from accidentally soft-locking themselves. You'll get an error message when you try to affect them. There's no workaround for this other than using the qv command to progress past the blocked point manually.
Where to Find Item and Reference IDs
The Fallout New Vegas Wiki maintains a comprehensive database of every item ID in the game. The UAC Nexus page has the Creation Kit plugins that include search utilities. CK Editor Plugins is the mod most people install for this — it adds a content manager window where you can search for items and copy their IDs directly. It takes about five minutes to set up and eliminates the need to keep switching between browser tabs while gaming. For quest IDs and stage information, the same wiki has complete quest lists with all stage numbers. If you're trying to advance a quest and aren't sure what stage to target, this is where you look. Stage 0 is usually the starting state, and higher numbers progress toward completion. Not always linear though — some quests have branching stages depending on choices you've made.
Bottom Line
The console is a powerful tool but it's not elegant. It works well enough for casual cheating and troubleshooting, but it will cause problems if you rely on it heavily. Use it sparingly, save often under different names, and keep a clean backup of your saves. That's the routine that works. Everything else is just experimenting until something breaks.
