Guide contents
This is a Windows dedicated-server procedure. Confirm the Mod is server-ready, use PackageName from Info.json, configure the documented server settings, and restart before verifying.
This page keeps platform, version, dependency, and source boundaries visible so a safe test has a clear result.
Follow the smallest useful path.
Prepare the Workshop project
From the folder containing PalServer.exe, place each project at Mods/Workshop/<any folder name>/Info.json and read PackageName from that Info.json file.
Info.json is directly below the project folder and the recorded PackageName is not copied from the Workshop ID or folder name.
Configure the server
After the server has launched once, edit <PalServerRoot>\Mods\PalModSettings.ini. Set bGlobalEnableMod=true and add one ActiveModList=<PackageName> line per Mod.
The file has one [PalModSettings] section, the global flag is true, and every ActiveModList value comes from Info.json.
Restart and verify
Restart after enabling or updating the Mod, then inspect Mods/ManagedMods/<PackageName>/InstallManifest.json and the expected server behavior.
The manifest exists for the intended PackageName and the server log does not report a missing dependency or unsupported server InstallRule.
Use the exact server-root paths and settings.
PalModSettings.ini is generated after the Windows dedicated server launches once. PackageName comes from Info.json; it is not the Workshop ID or the project folder name.
Server-root config path
Resolve PalServerRoot as the directory containing PalServer.exe.
<PalServerRoot>\Mods\PalModSettings.iniValid example
Use repeated ActiveModList lines when enabling more than one PackageName.
[PalModSettings]
bGlobalEnableMod=true
ActiveModList=GamingCattiva
ActiveModList=FarmingQuivernIncorrect example
This disables Mods globally and mistakes a Workshop ID or folder name for PackageName.
[PalModSettings]
bGlobalEnableMod=false
ActiveModList=1234567890Post-restart verification path
A successful deployment creates this manifest for the selected PackageName.
<PalServerRoot>\Mods\ManagedMods\<PackageName>\InstallManifest.jsonUse the symptom to choose the next check.
| Symptom | Check | Recovery |
|---|---|---|
| The server ignores the project. | Compare Info.json placement and PackageName with the official guide. | Remove the new entry, restore the prior server config, and reapply the documented layout. EvidenceSSource checked |
| Clients connect but do not see the expected behavior. | Check whether the Mod is server-ready and whether its own page requires client-side installation. | Treat the Mod's author instructions as the boundary; do not generalize one Mod's behavior. |
Questions this source set can answer.
Is the folder name the PackageName?
Not necessarily. The official server flow uses PackageName from Info.json.
Does every Workshop Mod work on a server?
No. Server support is Mod-specific and the official loader/server notes do not make client behavior universal.
If the current source disagrees with an older tutorial, pause the change and re-check the release, platform, and original Mod page before continuing.