Skip to main content
Version: 2026.2

Support

What we can help with​

PCA is a compiler front end. We can help when PCA misbehaves: it does not find your Creation Kit, it will not start a compilation, a button does nothing, it crashes.

Papyrus scripting is out of scope

We do not provide support for papyrus scripting problems. Ask on the NexusMods forum instead.

unable to locate script x and is not a known user-defined type are scripting problems — they come from the compiler, about your code or your missing sources, not from PCA.

Try this first​

Most reports turn out to be one of these. Each takes a minute.

  1. Read the Creation Kit report in the settings. It names the problem and usually carries the button that fixes it.
  2. Check Common errors for the message you are seeing.
  3. Open the compilation logs and read the compiler output. The real reason a script failed is in there, not in the Failure badge.

Getting a debug log​

If you still need us, come with a log.

  1. Open the settings.
  2. Under Preferences, set log level to debug.
  3. Reproduce the bug.
  4. Open the log: click the PCA logo at the top left, then File — Logs....

The log covers the whole app, the interface included, and lives in %APPDATA%\PCA\logs — though the menu is the sure way to it.

PCA had to be restarted?

File — Previous Session... — Logs... opens the log of the run before this one, which is the one holding your crash. It is greyed out when there is no previous log.

Changed in 5.9.0

The -debug.exe.cmd launchers are gone, and so is the --debug command line flag. The log level is a setting now.

Reporting a bug​

Help — Report bug... opens a new issue on GitHub. You can also go to the issues page yourself.

Attach the log file, and tell us:

  • your game, and the folder it is installed in;
  • the PCA version, shown in the settings under About;
  • what the Creation Kit report says, if anything;
  • what you expected, and what happened instead.

For a script that will not compile, add the compiler output: the compilation logs have a copy button that puts the script, its path and the whole output on your clipboard in one click.