-
-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
No. KPatcher focuses on TSLPatcher-style installs. It is not trying to replace every other KOTOR modding workflow.
Usually, yes. KPatcher can load either the mod root or the tslpatchdata folder itself, but the mod still needs the expected config files inside.
A namespace is usually one install option from a mod package. Think of it as "which version of this mod do you want KPatcher to apply?"
There can be a normal start confirmation and also a mod-specific confirmation message from the mod's own config.
It can try. KPatcher checks common install paths and fills the list when it finds them, but you can still browse manually if needed.
Sometimes. KPatcher can uninstall from backup if the needed backup data exists. If no backup directory is present, uninstall cannot restore what was never saved.
In installlog.txt inside the mod folder.
KPatcher tries to render RTF instructions. If that is not possible, it can fall back to plain text.
Yes. KPatcher has a command-line mode for install, uninstall, validation, namespace listing, dry-run summary, and parity reporting.
No. The configuration summary is a read-only report. It does not start the patching process.