Smith
Smith sits inside Modsmith and sees what you see: the library, the order, the conflicts, the crash logs. Ask it what broke and it answers with a fix you can apply in one click and undo in another.
The crash is inside Cloth Physics Extended. That DLL was built for game runtime 1.5.97, and you are running 1.6.1170. The mod page lists a build for your version.
Update Cloth Physics Extended to 2.3, built for 1.6.1170
Opens the file on Nexus for you to download; it installs as a new version when it lands. The current version stays in the library.
Smith proposes, Modsmith executes.
What Smith does
Every Smith feature follows the same shape: you ask, Smith works it out and proposes, Modsmith shows the plan, you apply it. Allowances count proposals, not tokens.
Pick a crash log. Local signatures handle the usual suspects offline: display drivers, upscalers, overlays, a plugin over the limit. For the rest, Smith reads the parsed log, names the module and the mod behind it, explains why, and proposes the fix: update, disable, reorder, or install a missing dependency.
one diagnosis per log
Two mods edit the same record and the last one wins, losing the other's change. Smith works out what each mod wanted and proposes a patch that keeps both. Modsmith builds the patch plugin, adds it to the load order after its masters, and keeps a backup like for any other change.
one patch per proposal
Pick a mod and a language. Smith translates plugin strings, interface text and descriptions while leaving record ids, tags and formatting codes untouched. The translation installs as a separate patch so the original stays intact and updates cleanly.
measured in words
Describe what you want: quieter cities, a harder early game, a particular look. Smith picks mods that fit, checks them against what you already have and against each other, and explains each choice. You decide what gets downloaded, through your own Nexus account.
one pick per request
Start from a description or from a build you have and work through it together: what to add, what to drop, what needs a patch, where the order should change. Smith keeps track of the build state, Modsmith applies each step as an ordinary, reversible operation.
Pro limited · Max full
Local checks
Before a model is ever involved, Smith already reports the state of the build: which mods overlap and who wins, what the game will load, what cannot load, and whether the deployed build still matches the one selected. The same panel answers the usual crash with a local signature.
Models
Choose a role and let Smith route each task, or name a model from Anthropic, Google or OpenAI outright. No plan locks a model away. A heavier model simply uses your monthly allowance faster.
Picked per task. A crash diagnosis and a translated description do not want the same model.
Fastest to answer, and the gentlest on your monthly allowance.
One steady middle. Not the quickest, not the deepest, the same every time.
Deepest, for long load orders and stubborn crashes. Slowest, and it uses your allowance fastest.
A role names what you want from the answer, never a model: the mapping from role to model lives on our service and can improve without an app update. A named model is exactly the model you asked for.
Where Smith stops
These are properties of how the program is built, not settings you could get wrong.
What is sent
For a crash diagnosis the request carries the parsed structure of the log: the logger, the game version, the exception, the faulting module, the call stack, the loaded modules, the plugin names and their load-order indices. It does not carry file paths, your Windows account name, the raw log text, your saves, your Nexus key or the contents of any mod.
The first time, the exact request body is shown and nothing goes until you allow it. Afterwards, Show what is sent is always one click away. The consent can be withdrawn in Settings. Details are in the privacy policy.
Plans are measured in operations you can count, with a fair-use ceiling stated as a number.