Advanced CLI and Validation

Advanced CLI and Validation

Most players do not need this page. The desktop app is the normal path.

Use the command line when you want to inspect, validate, or automate something more carefully.

Basic Rule

If you start KPatcher with no arguments, it launches the desktop app.

If you pass CLI options, KPatcher runs in command-line mode instead.

Common Advanced Commands

Show Help

KPatcher --help

List The Available Namespaces In A Mod

KPatcher --tslpatchdata /path/to/mod --list-namespaces

Use this when a mod contains multiple install choices and you want to inspect them before installing.

Show A Dry-Run Style Configuration Summary

KPatcher --tslpatchdata /path/to/mod --dry-run

This prints a read-only summary of the selected config without starting installation.

Validate A Mod Configuration

KPatcher --game-dir /path/to/kotor --tslpatchdata /path/to/mod --validate

This checks configuration validity without patching the game.

Install Through The CLI

KPatcher --game-dir /path/to/kotor --tslpatchdata /path/to/mod --install

Uninstall Through The CLI

KPatcher --game-dir /path/to/kotor --tslpatchdata /path/to/mod --uninstall

Print The Current Parity Confidence Ledger

KPatcher --parity-report

This prints the app's current curated parity-confidence summary.

Notes About Namespace Indexes

When a mod has multiple namespaces, the CLI can also take a numeric namespace index.

Example:

KPatcher /path/to/kotor /path/to/mod 0

That final number selects the first namespace.

When The CLI Is The Better Choice

Use it when you:

• are running remotely without a GUI
• want a dry run or validation result in plain text
• want to script repeated installs or checks
• need namespace listing without opening the desktop app

When The Desktop App Is The Better Choice

Use the desktop app when you:

• want the easiest path
• need to read the mod's instructions comfortably
• want visible confirmation prompts and progress
• are not already comfortable with terminal commands