-
-
Notifications
You must be signed in to change notification settings - Fork 0
What KPatcher Can and Cannot Do
This page is here to set expectations early.
- Install TSLPatcher-style KOTOR mods through a desktop app.
- Read a mod from its root folder or from the
tslpatchdatafolder directly. - Show multiple install options when a mod provides them.
- Try to detect common KOTOR install folders for you.
- Show the mod's instructions and a configuration summary.
- Validate mod configuration without installing it.
- List namespaces and run dry-run style inspection from the command line.
- Uninstall from backup when the needed backup data exists.
- It does not promise support for every possible KOTOR mod package.
- It is not a general-purpose mod manager.
- It is not a mod creation tool.
- It does not replace the need to read mod-specific instructions.
- It does not guarantee that every older mod will patch cleanly on every setup.
- It does not invent missing backups during uninstall.
- It does not turn a headless Linux session into a desktop session by itself.
KPatcher's goal is compatibility first: help older TSLPatcher-style mod installs keep working in a modern .NET application.
That is different from promising a brand-new workflow or a one-click solution for every modding problem.
Some versions may be labeled as alpha. If so, the app itself shows a warning banner. Treat those builds more cautiously than a stable release.
When a mod ships RTF instructions, KPatcher tries to render them properly. If that is not possible in your environment, it can fall back to plain text.
The uninstall flow is not magic. If the needed backup directory does not exist, KPatcher cannot restore what was never backed up.
The command-line interface is real and useful, but it is an advanced surface. Most users should stay in the desktop app unless they already know why they need the CLI.