The Witcher 3: Wild Hunt debug console is a powerful developer tool that, when enabled, gives you access to a broad set of commands for manipulating the game state. This verified reference covers enabling the console, essential commands for testing and exploration, and practical examples you can apply immediately. Used responsibly, these commands are invaluable for QA, mod support, performance checks, and world interaction without altering narrative progress.
Enable the Debug Console
Before you can use Witcher 3 debug console commands, you must enable the developer console in the game configuration. Open the root folder of your Witcher 3 installation and locate the user.settings file. Add the line ConsoleEnabled=true to this file and save. If the file does not exist, create a plain text file named user.settings with that single entry. Launch the game; pressing the tilde key (~) will now open the console in supported configurations.
Essential Console Commands
Once enabled, the Witcher 3 debug console supports a variety of commands focused on testing, performance, and exploration. Below are core commands grouped by primary use case. Many commands accept parameters such as object IDs or numeric values, which makes them flexible for specific tests.
Testing and Inventory
Inventory and item-related commands let you add or remove items, adjust quantities, and inspect object properties. These are helpful for balancing and verifying item behavior.
additem <ID> <quantity>: Adds an item to your inventory by its unique ID.removeitem <ID> <quantity>: Removes a specified quantity of an item.giveall: Grants a broad set of items and abilities, useful for testing content without manual progression.
Player and Stats
Commands that directly affect your character’s attributes, level, and abilities are useful for stress-testing builds or reproducing progression states.
setlevel <level>: Sets your player level to the specified number.addxp <amount>: Adds experience points, useful for reaching specific thresholds quickly.stats: Opens a menu to modify core stats such as health, stamina, and vitality.
World and Interaction
These commands control time, weather, fast travel, and object spawning, allowing you to manipulate the living world of the game without standard constraints.
time set <hour>: Sets in-game hour (24-hour format).weather <name>: Changes current weather to a named preset, such as clear, rain, or snow.warp <location>: Warps you to a known location or waypoint.
Debug and Diagnostics
For technical verification and performance assessment, debug commands provide scene information, budget tracking, and engine-level details.
- \n
debugfps: Toggles an on-screen frame rate counter.showinfo: Toggles detailed on-screen information such as draw calls, budgets, and memory stats.stat averages: Shows rolling averages for performance metrics.
Command Syntax and Conventions
Witcher 3 debug console commands follow straightforward conventions. Entity and item IDs are typically numeric or short string identifiers. When entering commands, use the exact case and spelling the engine expects, and supply numeric arguments without angle brackets. Many commands return textual feedback in the console, which can help confirm success or reveal usage errors.
Practical Examples
Execute these sequences to test common scenarios quickly. Each example demonstrates a safe, reversible operation that avoids permanent save corruption when used thoughtfully.
| Test Goal | Command Sequence | Expected Outcome |
|---|---|---|
| Verify item addition | additem 505 10 | Ten units of item 505 appear in inventory. |
| Test level scaling | setlevel 40 | Player level changes to 40, stats rescale accordingly. |
| Check performance under stress | debugfps; showinfo | On-screen counters display FPS and engine budgets. |
| Explore weather presets | weather storm | Immediate transition to storm weather state. |
Limitations and Safeguards
The Witcher 3 debug console operates within the running process and does not persist across launches unless explicitly saved by a supported mod. Certain commands may have context restrictions or fail if prerequisites are missing. The developer console is intended for testing, mod development, and technical investigation, and its use in online or ranked contexts may conflict with terms of service. Always back up important saves before running unfamiliar or bulk commands.
Conclusion
Used with care, Witcher 3 debug console commands are a stable, repeatable way to inspect and test game systems. This reference aims to provide clear, accurate command descriptions and practical examples that remain useful for technical exploration, mod support, and performance review. For long-term utility, treat the console as a diagnostic instrument and document any changes you make during testing sessions.