Questions, answered plainly.

A Windows mod manager being built around a library, load order, profiles, external tools and an integrated assistant called Smith. It is intended for multiple games, with game-specific features supplied by integrations.

Not yet. The application is in development and no public release date has been announced. Screens on this site are development previews. Check the release status for availability.

Yes. Mod management, Nexus integration and local checks will remain free. The paid part is Smith’s optional cloud AI service. No subscriptions are on sale now.

That is the aim, but it is not ready to replace your current manager yet. Modsmith uses real files or hardlinks in the game folder. See the workflow comparison, and keep a backup before moving a setup.

The free manager will not require a Modsmith account. Smith’s cloud features will require one. A Nexus account is separate and is needed for Nexus downloads. Registration is not open yet.

Modsmith is an independent project developed by Arane. It is not affiliated with the game publishers, stores or mod sites mentioned here.

Modsmith is designed for multiple games. Skyrim Special Edition and Anniversary Edition are the first integration being developed and tested. Adding a custom game folder provides basic file deployment; it does not automatically add plugin sorting, save support or crash analysis for that game.

Each integration describes what its game can do: installation detection, mod deployment, profiles, plugin order and any supported save or crash-log formats. A feature shown in a screenshot is not a promise that it works for every game. Release notes will identify the supported combinations.

These are outside the initial support scope. Store packaging, game versions and modding requirements differ, so we are not claiming compatibility with them.

Steam, GOG and Epic installation records. You can also choose a folder manually. Finding a game on disk does not mean every modding feature supports it.

It links or copies enabled mod files into the game folder, backs up originals it replaces and records the changes. Rollback uses those records to undo the deployment. Unexpected changes made outside Modsmith need review.

The journal lets recovery identify unfinished work and attempt a rollback on the next start. If files are missing, changed or inaccessible, recovery may need your attention. Do not delete the journal or backups while resolving it.

Rollback aims to restore the state before that deployment. If the game already contained manual mods, it restores that state, not a clean installation. It cannot undo every change made by a running game or an external tool. Keep separate save backups.

The supported save checks read plugin references to flag missing dependencies. They do not repair or rewrite save contents, and a clean check does not guarantee that a save is compatible with your build.

The FOMOD wizard reads declarative installer options and conditions. Scripted installers are not executed. External tools you explicitly launch are real programs and can change files; they are not sandboxed by Modsmith.

No. Quarantine holds back unrecognised native files, such as DLLs and executables, for review. It is not an antivirus verdict. Verify the source before restoring a file; recognition alone is not a guarantee.

Modsmith is designed to install and run as your Windows user. Your game and library folders must be writable. An external tool may have different requirements; check its documentation.

The development build uses your personal Nexus API key. It is stored locally using Windows DPAPI and sent to Nexus, not to a Modsmith server. The public build will include connection instructions.

Nexus controls access to downloads. Modsmith respects those rules and does not automate the website clicks required of free accounts. Mod Manager Download links hand the chosen file to the app for confirmation.

No. Nexus membership is separate. Download permissions, limits and Premium features are set by Nexus. A Smith subscription will not bypass or replace them.

The intended flow asks before assigning Mod Manager Download links to Modsmith. Use one handler at a time and follow the chosen manager’s instructions when switching.

The development importer reads an instance and profile, registers existing mod folders by reference, and imports order and separators. It does not make an independent copy of those mod files. Keep the source folders and a backup, and avoid editing shared files from two managers at once.

Neither workflow is currently supported. Modsmith’s collections list mod references for downloading through your own Nexus account; they do not contain or redistribute the mods.

Avoid active deployments from two managers at once. Undo the current deployment, check the game folder and keep backups before switching. Tools may otherwise treat deployed files as part of the original installation.

The development build has local checks for overlaps, dependencies, deployment drift and recognised crash patterns. There is no public app release yet. Cloud diagnosis, patching, translation and build planning are still being prepared; the Smith page describes the plan.

The design separates model output from execution. A model proposes; Modsmith validates a supported action and asks you to apply it. The model does not receive direct file-system access. Review proposals and keep backups, because validation cannot guarantee that every suggestion is useful or correct.

The intended catalog includes models from Anthropic, Google and OpenAI, selected by name or by a role such as Auto or Spark. Model choice will not be restricted by paid tier. Heavier models use allowance faster; the final catalog and usage rules will be published at launch.

It depends on the task. A crash diagnosis uses parsed log fields and plugin names; translation needs the text to translate; build planning needs the relevant setup and your description. The request preview and privacy policy will describe the actual data before the service launches. Never include secrets in a prompt.

Local checks do. Cloud AI needs internet access for every request. A subscription or a licence-validation grace period cannot make a remote model work offline.

No. It is a scripted illustration using fictional mod names. Apply, Skip and Replay only change the demonstration on the page.

No. Accounts, trials and paid subscriptions are not open. There is no preorder or paid early access. The pricing page shows planned prices and allowances.

Lite and Pro are intended to launch first. Max follows when Build with Smith is available. The free manager has its own release and does not require a paid plan.

The plan is to pause the affected cloud feature until the next period or a plan change, without automatic overage charges. Heavier models consume allowance faster. The rules shown before purchase will explain how usage is counted.

A 14-day window for the first Smith payment. A lawful usage deduction may apply only if disclosed before purchase. The refund policy covers the conditions, renewals and statutory rights. No payments are being taken now.

Cancellation will stop the next renewal and leave access until the paid period ends. Instructions will be provided with checkout and the receipt. Account deletion and billing must both be addressed; deleting a local installation is not cancellation.

The planned limit is three signed-in devices sharing one allowance. The free manager does not use this subscription limit.

Xsolla is the intended payment partner, subject to confirmation. The actual seller, payment terms and taxes will be identified at checkout. No payment integration is live on this site.

A subscription explicitly sold at a founder price is intended to keep that price while it remains continuously active. Other price changes apply to future periods with advance notice and an option to cancel. No founder offer is on sale yet.

We have not added analytics, advertising trackers or account forms. Cloudflare still processes ordinary request data to deliver and protect the site and may use necessary security cookies. See the privacy policy.

Nexus downloads, masterlist downloads and update checks contact their respective services. Future sign-in, billing and cloud AI will also need network access. Using local mod management does not require sending your library to us.

The development app writes logs locally. Redaction removes recognised personal paths, but names and text can still contain private information. Review anything you choose to send for support.

First undo deployments you no longer want, check the result and keep important saves and backups. Uninstalling the app does not necessarily remove libraries stored elsewhere. Review data locations before deleting them: removing the journal or backups can prevent rollback. Account-data controls will be documented when accounts launch.

No public build is currently listed here. Use the official release page to confirm availability and the download source. Do not treat a file as official just because it uses the name or logo.

Check that the file came from the official release and verify the publisher information. Do not disable Windows protection or bypass a warning based solely on a website instruction. If the source or identity is unclear, do not run it.

Read the reason shown by the app. Close the game and tools, confirm folder access and preserve logs and backups. If recovery reports an incomplete deployment, resolve that before trying another deployment.

Check the game version, selected profile, expected mod folder and integration support. A successful file copy is not proof that the game supports or loads those files. After library changes, copied deployments need to be updated.

Include the app version, game version, steps to reproduce and the message shown. Review logs for private information before sharing them. Contact support@modsmith.app; never send account tokens or payment details.