Unlock The Game’s Hidden Power: The Outer Worlds 2 Console Commands Step-by-Step

If you like Obsidian games because you can tinker under the hood, The Outer Worlds 2 keeps that tradition alive — it just makes you do a tiny bit of homework first. The game does not ship with a built-in console, but it works perfectly fine once you bolt on a small mod. Here is the clean, no-fuss way to get it running, what the commands actually expect, and which ones currently play nice.

First: yes, you need a mod

The Outer Worlds 2 requires a console enabler and a mod loader. It is simple, but a couple of the file names are a little inconsistent and the install path has a funny name — more on that in a second.

1. Go to the Console Enabler and BP Mod Loader page on Nexus Mods.
2. Download two zips: SML.zip (the mod loader) and ConsoleEnabler.zip.
3. Find your game install directory, then open this path: Arkansas/Content/Paks. Yes, it is actually called 'Arkansas' in the files.
4. Create a new folder inside Paks named '~mods' (include the tilde).
5. Extract everything from SML.zip and ConsoleEnabler.zip into that '~mods' folder.
6. Launch the game and press the '~' key to pop open the console. If nothing shows up, switch your keyboard layout to English (US) or check the mod README to rebind the console to another key.

How the console reads your commands (and why typos break everything)

Commands use a simple pattern: the command name, then its arguments, all separated by spaces. If your spacing, casing, or values are off, the game shrugs and does nothing.

Example the mod author gives: 'LootTableDebug MyTable 1 2'. In this case 'LootTableDebug' is the command, 'MyTable' is a string, and '1' and '2' are integers. That is the vibe across the board.

Data types in plain English: booleans are 'True' or 'False' (flip a feature on/off), integers are whole numbers (the source shows a weird '321-9999' range, but treat ints as... whole numbers), and floats are decimals like '0.1' through '2.0' that usually scale something.

What works right now (and what does not)

The famous 'God' invincibility toggle is not working in the current build. Trait-related commands can be hit-or-miss depending on context. That said, a few useful ones are behaving:

'AddCurrency' adds Bits to your wallet. Example: 'AddCurrency 9000 1'.

'GiveSkills' sets every skill category to 20, which is the cap.

'LootTableDebug' spawns items from a specified loot table. Example: 'LootTableDebug MyTable 1 2'.

'TraitAddDebug' or 'AddTraitDebug' will attach a trait to your character. Example: 'AddTraitDebug Trait_Innovative'.

Heads up: some commands only work in certain areas or during specific combat segments, so you might be doing everything right and still get nothing if the game state does not allow it.

When it refuses to cooperate

If you press '~' and the console does not appear, switch to the English (US) keyboard layout or rebind the key in the mod's README. If commands do not fire, double-check that you actually put all the files from SML.zip and the console enabler zip (you might see it referred to as ConsoleEnabler.zip or ConsoleLoader.zip) inside the '~mods' folder in Paks — that exact location matters. Then check your syntax, spacing, and values.

That is the whole setup. Once the console is live, you can nudge the rules however much you like — from bumping your Bits to cranking skills to 20 — with a few caveats while the usual god-mode stuff sits on the bench. If you try a command cocktail that works especially well (or hilariously breaks something), I want to hear about it.