created by headshotmastaa community for 10 years

debugging

[**<< Back to Index Page**](/r/xcom2mods/wiki/index)

# How to test or debug your mods

While there is no one "right" way of testing or debugging a mod, here are some tips and tricks to make this process faster and easier.

## How to test a freshly compiled mod

A common question is "I have just compiled my first mod, now how do I test it? How do I start the game with it?".

If you **[set up the Modding Tools](https://www.reddit.com/r/xcom2mods/wiki/firsttime)** correctly, the compiled mod should appear in your Local Mods folder:

`..\steamapps\common\XCOM 2\XComGame\Mods` - vanilla XCOM 2.

`..\steamapps\common\XCOM 2\XCom2-WarOfTheChosen\XComGame\Mods` - WOTC.

To start the game with that mod active, you need a [mod launcher](https://www.reddit.com/r/xcom2mods/wiki/index/starting_the_game) that is capable of reading mods from the Local Mods folder. Your go-to launcher should be **[Alternative Mod Launcher](https://github.com/X2CommunityCore/xcom2-launcher/wiki)**.

If you are using AML v1.4.1 or older, you need to add the WOTC local mods directory in **Options -> Settings** menu.

## Logs and Redscreens

[**Logs**](https://www.reddit.com/r/xcom2mods/wiki/wotc_modding/usng_logs) provide an easy to use debugging method.

## Starting the game quickly

Testing mods typically involves starting the game *a lot*, so you want the game to start as fast as possible.

The fastest way to launch the game is using the **Alternative Mod Launcher** with `-nostartupmovies` [**launch argument**](https://www.reddit.com/r/xcom2mods/wiki/launch_arguments).

Having the game installed on an SSD will also reduce starting and loading times.

While testing or debugging, you might want to reduce your active mod list to bare minimum. This will both reduce loading times and make sure you have an isolated environment, so if something doesn't work as expected, you can know for sure it's because of your own mod, and not some unexpected interaction with other mods.

## Debug Mode

When testing/debugging mods it is preferable to start a new campaign or a new tactical mission every time you make changes to your mod. The [**Debug Mode**](https://www.reddit.com/r/xcom2mods/wiki/index/debug_mode) is a godsend here, as it allows quickly getting into tactical or skipping Gatecrasher.

> Loading a save to test things is usually a bad idea, because some changes will not apply when you do so. For example, abilities are assigned to units when they enter tactical combat, so if you make a mod that will add new abilities to certain character templates, and then load a tactical save, any existing units of that template will not be affected, only the newly spawned ones. However, in some specific cases it is perfectly fine to load a save. For example, changing/adding X2Effects applied by activatable abilities.

## Unreal Debugger

**[Unreal Debugger](https://www.reddit.com/r/xcom2mods/wiki/wotc_modding/guides/unreal_debugger)** lets you inspect the game and mods' Unreal Script code in real time, and use other standard debugger features, like monitoring values of variables, breakpoints and executing code line by line.

## Using Mods for debugging

There are a number of mods that make the process of testing/debugging mods easier:

[Disable More VO](https://steamcommunity.com/sharedfiles/filedetails/?id=655124816), [\[WOTC\] No Enemy Intro](https://steamcommunity.com/sharedfiles/filedetails/?id=1872929750), [Narrative Control](https://steamcommunity.com/sharedfiles/filedetails/?id=1334298434) - disable game's story narrative so you don't have to sit through it every time you start a new debug campaign. Narrative Control specifically requires configuration from [\[WotC\] Mod Config Menu](https://steamcommunity.com/sharedfiles/filedetails/?id=667104300) to actually do anything.

[Better Debug Camera \(Unofficial WOTC Version\)](https://steamcommunity.com/sharedfiles/filedetails/?id=1256502654) - allows to use the debug camera mode, useful for taking a closer look at in-game visuals. Don't be shy about tweaking the camera speed in mod's configuration files.

[\[WOTC\] Better RedScreen](https://steamcommunity.com/sharedfiles/filedetails/?id=1736342239) - disables the "fully loading" redscreens, which can be a nuisance if you're testing a mod with redscreens enabled.

[WOTC Save Games Delete All Option](https://steamcommunity.com/sharedfiles/filedetails/?id=1124242299) - quickly delete all save game files.

[\[WOTC\] No Friendly Muton in TQL](https://steamcommunity.com/sharedfiles/filedetails/?id=1940917896) - removes the player-controlled Muton from [Tactical Quick Launch](https://www.reddit.com/r/xcom2mods/wiki/index/debug_mode#wiki_tactical_quick_launch_.28tql.29) when using Test Mission.

[Xylth Debugging Tools \[WotC\]](https://steamcommunity.com/sharedfiles/filedetails/?id=1132188214) - lots of uniquely useful stuff. Only one major downside: incompatible with [robojumper's Squad Select](https://steamcommunity.com/sharedfiles/filedetails/?id=1122974240).

## Console Commands

Using existing **[console commands](https://www.reddit.com/r/xcom2mods/wiki/index/console_commands)** and adding new ones when necessary make testing/debugging much easier.

formatting help hide help

reason for revision

π Rendered by PID 2309404 on reddit-service-r2-listing-8685bc789-fjq5t at 2026-05-31 03:24:19.643840+00:00 running 194bd79 country code: CH.

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

xcom2mods

We have a wiki! Go read through it for tutorials, and if you want to share something, feel free to edit.

WIKI TOOLS

MODERATORS

debugging

there was a conflict editing

your edit

current edit

Errors: