For players arriving from another server

Moving from another server

A Vortex profile helps separate mods, but some files and the active load order still touch the same Skyrim installation. Give Nineholds a clean path before asking the launcher to join.

Keep what is yours

Move carefully

  1. Finish your other server’s session

    Close Skyrim, that community’s launcher, and Vortex deployment work. Keep a record of the profile and installation you already use. Do not delete another server’s mods, saves, or files to make Nineholds work.

  2. Make a separate Vortex profile

    In Vortex, open Profiles and create a Nineholds profile for Production, or a Nineholds Development profile for testing. Keep your other profiles as they are. With the Nineholds profile active, install and deploy the matching collection: Production revision 14 or the current Development collection. Do not import a previous community’s plugin list or copy its Data/Platform/Plugins folder into Nineholds.

  3. Run the Nineholds check

    Open the Nineholds launcher, choose the right server on the dashboard above Play, and let it check your setup. When offered, select Prepare server files to start setup; the launcher checks again afterwards. It checks the game runtime, frameworks, native plugins, client scripts, and load order, and it audits every collection file in one pass: you get the whole list, grouped by the Vortex mod that owns each file, with the steps to fix it, instead of one file at a time. If most of the collection is missing it will tell you that Vortex is probably on a different profile. Use that list to decide the next action.

  4. Fix the owner, then check again

    Use the named owning mod to choose the next step. Missing or incorrect required files need the matching mod reinstalled and deployed through Vortex. For recognized conflicting files, you can disable the owning mod through Vortex or choose Review conflicts with the launcher in the launcher, inspect the list and confirm it. Close Skyrim and Vortex before automatic repair. Numbered backups and Restore disabled files preserve your way back; another Vortex deployment may restore a conflict, so select Recheck setup afterward. Never force a mismatch just to reach Play.

When a separate game copy is wiser

Some community setups place native files straight in the Skyrim folder or redeploy them whenever Vortex runs. If the same collision returns after you fix the Nineholds profile, use a separate, compatible Skyrim installation for Nineholds or ask support to inspect the named file before moving anything manually.

The three common collisions

Another client starts
Skyrim Platform can load more than one client script. Keep the other community’s client out of Nineholds’ active plugin folders.
Native plugin conflict
A DLL from a different setup can load before the game opens. Disable the mod that owns it in the Nineholds profile and redeploy.
Wrong load order
Skyrim uses an active Plugins.txt across profiles. Activate and deploy Nineholds, then let the launcher verify the actual order.