Fallout New Vegas NPC codes give players fast access to characters, companions, and quest markers using console commands. These shortcuts help you test scenes, move people, or fix broken encounters without grinding through the open world.
Below is a quick reference table that shows common code patterns, what they do, and when to use them so you can plan your experiments before typing anything into the console.
| Code Type | Example Code | Effect | Best Use Case |
|---|---|---|---|
| Move NPC To Player | moveto player | Forces targeted NPC to walk to you | Testing dialogue or combat triggers |
| Force Temporary Actor | player.placeatme [refID] | Summons a temporary copy of the NPC | Quick spawn for visual checks |
| Set Essential | setessential [refID] 1 | Makes NPC unkillable | Protecting key story characters |
| Enable NoAI | ai.enablescriptfriends 0 | Stops NPC from using combat or scripted AI | Freezing guards during testing |
| Add Companion Rejection | setrelationshiprank Player 2 | Forces NPC to act as a companion | Quest debugging and role tests |
Essential Console Commands for NPC Management
Moving and Spawning NPCs
Using moveto player and player.placeatme [refID] lets you pull NPCs into position instantly. Placeatme is great for visual checks, while moveto player is better when you want the character to walk to you and react to the world.
Protecting Story Characters
setessential 1 turns critical NPCs into unkillable allies, keeping story paths intact. This is useful when you accidentally aggro a key courier or when a companion keeps dying during quirky pathing.
Freezing AI for Testing
ai.enable scriptfriends 0 stops NPCs from using advanced combat or dialogue scripts. It helps you freeze guards during mission tweaks so your tests stay predictable and safe.
How to Find the Right NPC Reference ID
Using the GetReferenceID Method
Select an NPC, open the console, type getvalue game.getselectedrefid, and press Enter to see the exact reference ID you need for placeatme and other targeted commands.
Working with Base IDs and Editor IDs
Base IDs come from the editor and work for placeatme, while reference IDs point to the active in-world instance. Use base IDs for reliable spawns and reference IDs when you need the exact object already in the scene.
Managing Companions and Followers
Controlling Companion Behavior
Commands like setrelationshiprank Player 2 push NPCs into follower mode, making them stick close and obey combat orders. This is handy when companions wander off during timed events or stealth sections.
Resolving Companion Conflicts
If two followers fight each other, temporarily setessential 0 on one of them, move them apart using moveto player, then restore their essential status to keep both fighters in your party.
Advanced Debugging with NPC Codes
Diagnosing Broken Encounters
Turn on advanced logging, run ai.showcombatlog 1, and watch the console for NPC pathing failures or dialogue stalls. Use moveto player and ai.enable scriptfriends to isolate where the system gets stuck.
Testing Quest Stages with NPCs
Use setstage and getstage commands on the NPC reference to force a quest into a specific state. This reveals dialogue branches, hidden conditions, and missing triggers that are hard to see during normal play.
FAQ
Will using NPC codes break my save file or achievements?
Using console commands can sometimes disable achievements on PC and may cause minor save corruption if scripts are interrupted mid-action. Save before you experiment and avoid essential 0 on critical quest givers to reduce risk.
How do I make an NPC follow me reliably without combat AI errors?
Ensure ai.enable scriptfriends is set to 0, setessential 1 on the NPC, and use moveto player to guide them. Keep their reference ID stable and avoid fast travel while they are pathing to reduce desync.
Can I undo an NPC code change, like removing essential status?
Yes, run setessential [refID] 0 to restore normal death behavior. You can also use player.placeatme with a different refID to replace a temporary actor if you need a clean respawn.
What should I do if an NPC gets stuck after using moveto player?
Try ai.enable scriptfriends 1 to restore normal AI, or use stopmove [refID] to clear stuck pathing. If the NPC is still frozen, reload a prior save and approach the situation with a shorter movement route.
Best Practices for Reliable NPC Experiments
- Always create a manual save before running any setessential or ai.disable commands.
- Use player.placeatme [refID] for safe visual testing before committing to moveto player.
- Keep a list of reference IDs in a text file for the NPCs you test most often.
- Turn off advanced combat logging after debugging to keep the console clean.
- Avoid combining multiple experimental codes in the same session to isolate issues quickly.
