Gamebryo console commands

The Console is a debugging tool left by the developers in the PC version of the game.

It is useful for developing and quality assurance, but it can also be used to cheat.

To access the console, use the tilde key (~). You will get a prompt (|) in the lower left corner of the screen.
 * The left side of the console might not be visible if you are not using a widescreen display.
 * The key is the top left key under escape, on non-english keyboards. (Example: § on Swedish keyboards.)

For nice screenshots

 * - toggle free camera; lets you move around the camera at will. To take pictures of your character, make sure you go into third person mode first.
 * - toggle menus; removes the HUD for even nicer pictures.
 * , fast,, slow moving camera in tfc.
 * , narrow,, wide angle lens. , default lens.

Inventory manipulation

 * - add item to your inventory,
 * for instance: - add Vengeance to your inventory.


 * - remove item from your inventory; useful to get rid of useless quest items

NPC manipulation

 * - set an id target. Same as clicking, but will work even if the target isn't visible.
 * - move player to NPC
 * followed by - move NPC to player
 * - kills NPC
 * - resurrect NPC (Will also reset the inventory!)
 * , - disable and enable the NPC in the game (total vanish, reappearing)


 * - set NPC as unkillable.
 * - create/clone an NPC and place it at the player.

(Note the difference: marks the "character sheet" and  marks an instance of the character with location.)

Example (commands in order)

 * - target Sydney
 * - move Sydney to the player
 * followed by - add Vengeance and ammunition to Sydney
 * - make Sydney unkillable
 * - place a new Super Mutant Master at Sydney. Can be repeated for more.

NPC reset example (in order)

 * - target Sydney
 * followed by - disable and enable, make sure the NPC is active
 * followed by - kill and resurrect, reset the NPC
 * - move NPC to player (or to move the player to Sydney.)

Stats and character manipulation

 * - set player scale; is default;  is small,  is big,  is huge (not recommended to use indoors)
 * - read out a character value, for instance karma, intelligence or smallguns.
 * - modify a value; it will peak normally (100 for skills, etc). Negative values lowers the variable.
 * - set a value
 * - add a perk
 * - remove a perk
 * - toggle male/female
 * - open the menu to change the name of the player
 * - open the menu to change the race and face of the player
 * - advance one level
 * - set level
 * , - give player karma or xp

Example

 * - add Power Armor Training
 * - set Small Guns 100, to the maximum of 100
 * - lower Intelligence by 5 (minimum 1)

Warnings
If you max all your skills to 100 and then level, you will freeze your game, as you cannot advance through the level up screens if you can't assign all of your skillpoints. A similar issue happens if you aquire all perks. It is highly recommended that you choose a skill that you rarely use and keep it at a very low level to leave some room for the level up screen, as well as pick one or two perks that you don't need and leave those for when you level. You can then use removeperk to untrain the perk again for the next level, and force your skill back to the lower level again, etc.

Also, be extremely careful when using setscale to large numbers like 10. You may seem big and powerful, but a very small dropoff (in comparison to your size) will be fatal. Cliffs look very tiny from 50 feet up, but still kill you as if you were normal size.

Items & world manipulation
This is easiest if you first click on something in the world with the console open, to target it.
 * - unlock door or safe; you can of course also.
 * - activate an item, say a door, that is normally operated by a switch
 * - make the item yours (for instance a cabinet or a bed)
 * - place an item next to the player; for many items only a of  is valid

Quests

 * - move player to current quest target
 * - show the quest log, everything the player has encountered and done
 * - complete quest
 * - reset quest
 * - list current quest targets

(raw quest base id list here)

Game

 * - save current game with description
 * - load a game from a previous named save

Debugging and mapping

 * - turn on all Pip-Boy map markers.
 * - toggle fog-of-war in the Pip-Boy local map.
 * - toggle god mode; gives you invincibility to damage and radiation, unlimited AP and ammo
 * - toggle clipping, you can move through anything (aka "noclip")
 * - kill all NPCs in the area
 * - teleport to cell
 * - write console output to the specified file

Advanced use
All commands applying to the player, npcs or items can be used on any of those, with varying result.


 * has already been used like this in the examples above.

Example

 * - target Sydney
 * - show Sydney's inventory
 * - check her Small Guns skill
 * - make her very small

Position
Some users can't see the left-most columns of text in the console; they can only see the end of statements, and can't see what they're typing, unless it's very long. This is known to impact some (all?) users without widescreens (a 4:3 screen like 1600x1200, 800x600, etc. - not 25:16 widescreen). Fortunately, Fallout 3 has an easy fix for this.

The position of console text can be set in the Fallout.ini file. In Windows XP at:


 * C:\Documents and Settings\\My Documents\My Games\Fallout3\FALLOUT.INI

Open the file in a text editor like Notepad. Search for "iConsoleText".
 * Set iConsoleTextXPos to 200 or so. Higher figures move console text to the right. This is the main problem.
 * IConsoleTextYPos should be approx. 100 or 200 less than your Y resolution. Lower figure moves it up (0 is the top of the screen).

An example for a 1280x1024 (XxY) 4:3 display: Setting           Default  New Setting  Notes iConsoleTextYPos    940        900      Y (up/down) pos is 100-200 less than your Y res (here, 1024) iConsoleTextXPos     30        200      X (left/right) position is higher (which moves it to the right)

You can use a command like to see if the console works. Even though you can't see the editing line or the cursor, it will flood the console with text.

Other bugs
It has been reported that the console will not work with some Vista 32 and 64 bit systems with NO fix. Those people can only hope for a mod that solves this (example - the ring of console in Oblivion).

[Temp Fix] Control Panel > System > Hardware > Device Manager > Human Interface Devices > uninstall Infrared driver (don't ask me why but this driver interferes).

[New Possible Fix]

open regedit

Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters

There should be an entry named OverrideKeyboardSubtype with a type of REG_DWORD and a value of 2. Set the value to 0 and reboot.

now, uninstalling the IR drivers in the device manager (if you have them) will work to enable the console to come up.

if you don't have any IR drivers, then just doing the reg change should fix it for you.

Full Fix: At launcher screen, select options, set screen quality to high.

[Full fix with Microsoft eHome remote/receiver]

If you use the Microsoft eHome remote/receiver (official media centre remote and USB receiver) you'll notice under your device manager you have a new device named Microsoft eHome MCIR 109 Keyboard; this is the cause of the tilde key not working. It also affects your plus, minus, parenthesis, hash, @, and slash keys remapping them to different functions. (some are even weird Kanji characters)

Solution is as follows and will not affect the functionality of your Media Centre remote:

1. Go into Device Manager -> Keyboards.

2. Right-click "Microsoft eHome MCIR 109 Keyboard", choose "Update Driver" ("Update Driver Software" on Vista).

3. Choose "Browse my computer for software" (XP users tell it not to install automatically and say you'll specify the location, then when it asks you where you would like it to search for drivers choose the option to choose from a list) then "Let me pick from a list of device drivers on my computer".

4. Make sure "show compatible hardware" is checked, then select "HID-compliant device" and click next. Click any remaining "OK" or "Finish" buttons after Windows has installed the driver.