Console commands

*Remains* has a simple command line interface, which allows executing debug commands. Some commands can help in case of game bugs, others can be used to cheat.

**Caution**: some console commands can break save files (see Save file corruption). Use at your own risk and **always make a backup of your save file**.

## Command line interaction

* Command line can be opened/closed with the [end] key. Command input field appears in top-left corner of the screen.
* Confirm command by pressing [enter] or pressing the confirmation button on the right side of command input field.
* Commands can be executed at any time - during gameplay, when PipBuck, S.A.T.S., or other menu is open, and even in main menu (although most commands won't have any effect when no save file is loaded).
* Player character can't be controlled while console is open (with the exception of pointing the gun). Interaction with PipBuck and weapons rack is possible.
* Sometimes the console doesn't close automatically after executing a command. [esc], [end], or the close button at the right side of command input field must be pressed to close the console.
* Text in the command input field remains there if console is closed and reopened.
* Previously executed commands are saved, you can go back to previous commands by pressing [up]/[down] keys while console is open.
* Values displayed in PipBuck will not update if command is executed while PipBuck interface is open. To see the result (e.g. new items), close and open PipBuck again, or change page.
* Opening the console doesn't pause the game (unless PipBuck/S.A.T.S. is already open).
* Most commands don't have any output (no message will appear after successful/unsuccessful command). Exceptions are `?`, `trigger` and `triggers` commands.
* In some cases you will need to use the command `mqt` in order to activate the other commands.
* You can paste text into the command line with [shift]+[insert].

## Commands

Many commands accept additional parameters, separated by space - e.g. `command param1 param2`.

**Important**: most commands (except `die` and `hardinv`) are disabled by default - typing them in won't have any effect. To enable access to all commands, execute the `mqt` command once (execute it again to disable access).

## Save file corruption

Known ways to break save files with console commands (**this will break your save file**):

* Adding a non-existent perk with the `perk` command (e.g. `perk asdf`). Saving the game and trying to load the save file will result in *Error #1009.*
* Adding a grenade normally unobtainable by the player (used by enemies) with the `weapon` command (e.g. `weapon drongr`). This will cause *Error #1010* when opening Weapons page in PipBuck, and the PipBuck will start glitching. Saving the game and trying to load the save file will result in the same error again.

In some cases it is possible to fix a save file after it was corrupted. See Fixing a corrupted save file.

## IDs

### Finding missing IDs

Not all IDs are listed on this wiki. You can find some of the missing IDs by using the `?` command - three scrollable lists will appear (when command line is shown). You can also search in game files - it's easiest to search the translations file (e.g. *text\_en.xml*).