Add Unturned Workshop content or maintained server plugins safely

Unturned Workshop content and server plugins take different installation routes. A Workshop map or asset pack is not a plugin DLL, and copying a plugin into a Workshop directory will not load it. Choose the route your feature requires, then keep the server instance and its saves intact.

Plan the package set

Record the current instance. Note the Unturned build, startup instance ID, selected map, enabled modules and current packages. Resolve the active Servers/<instance-ID>/ directory from the service's actual startup. Hosted templates can relocate the installation root.
Read the author's requirements. Check supported game/framework releases, dependencies and any migration or client requirements. A Workshop item title is not its numeric file ID, and a plugin advertised for another framework is not automatically compatible with yours.
Save, stop and back up. Keep the instance configuration, world/player data, permission files, modules, plugins and plugin databases. Preserve the existing instance ID; starting under a new name can make a server appear empty while its original saves remain elsewhere.

Install Workshop content

The developer's server-hosting instructions use the instance's WorkshopDownloadConfig.json. Add numeric Workshop item IDs to its File_IDs array, retaining valid JSON and existing settings. The item ID comes from its Workshop URL. On startup, the server obtains the configured content and dependencies; connecting players download required Workshop content.

Do this first on an isolated instance copy with separate allocations and storage. For a map, use the author's documented map name in Server/Commands.dat; the numeric download ID is not the map name. Confirm the map content finishes downloading before interpreting a load failure. Adding content to the list does not guarantee an existing world can safely change maps or remove old assets.

Install a supported plugin framework

For the Rocket-compatible route, use the developer-maintained Legally Distinct Missile (LDM) fork. SDG supplies its current module with the dedicated server, copied from Extras/Rocket.Unturned into Modules. The original Rocket projects include abandoned archives; their familiar names do not make arbitrary old downloads suitable.

Start the test framework and follow the chosen plugin author's instructions for its generated directories, dependencies and configuration. Install only the supported plugin release, then stop and start normally. Do not mix frameworks or replace bundled game assemblies to satisfy an unexplained error. DLL plugins execute server code: use identifiable upstream releases and keep database credentials private.

Validate and keep the previous set

Read startup output for the expected map, module and package, then test the intended feature with an ordinary player account. For administrative plugins, confirm permissions restrict privileged commands. Inspect existing progress, save, restart and join again. A visible server listing alone does not prove content loaded correctly.

If the test fails, preserve its first error and return the isolated instance to the recorded combination. Keep pre-change data and packages together. Do not remove content from the only live save and save over it as a diagnostic shortcut. Promote the tested files during a planned restart and retain the rollback copy.