-
-
Notifications
You must be signed in to change notification settings - Fork 0
How KPatcher Works
KPatcher is designed to behave like a modern, cross-platform version of an older TSLPatcher-style installer workflow.
You do not need to understand the code to use it, but it helps to know what the app is looking for.
Most supported mods ship with a folder named tslpatchdata. That folder contains the instructions telling the installer what to patch.
KPatcher accepts:
- a mod folder that contains
tslpatchdata - or the
tslpatchdatafolder itself
If neither one is present, KPatcher cannot load the mod.
Some mods contain several possible install choices. KPatcher shows those as namespaces.
Examples in plain language:
- one install choice for KOTOR 1 and another for KOTOR 2
- one install choice for a full version and another for a compatibility version
- one install choice for a specific texture or gameplay option
If a mod only has one install choice, KPatcher may show a default namespace automatically.
When you choose a namespace, KPatcher tries to load the mod's instructions file.
That means the large panel is usually there to help you read the mod author's instructions before you patch anything.
If you switch to the configuration summary, KPatcher shows a plain-text report instead. This is useful when you want to inspect what the installer is about to use without starting the install.
KPatcher checks common KOTOR install locations and fills the game-path list when it can.
If it guesses wrong, you can browse to the correct folder yourself.
During install work, KPatcher writes status messages to the visible log area and also saves a log file in the mod folder.
Backups are part of the normal TSLPatcher-style workflow. If the mod and install process created usable backups, those backups are what the uninstall flow depends on later.
KPatcher can also run in command-line mode for advanced tasks like validation, dry runs, and uninstall. Most players do not need this, but the option exists.