Choose a supported Palworld dedicated-server mod installation

A Palworld mod working in a player's game does not establish that it can run on your dedicated server. Start by identifying the server operating system, game build and mod distribution method. Keep your live world unchanged while you establish a supported combination.

Check the platform before uploading anything

Pocketpair's dedicated-server mod guide currently limits its server-side mod workflow to the Windows dedicated server. A native Linux service should not be treated as compatible simply because its files are accessible. Ask CloudExa to confirm the actual runtime if your template does not identify it.

UE4SS is a separate loader with its own requirements. Its upstream documentation describes Windows DLL loading and warns that compatibility is not automatic. A Windows DLL is not a Linux server extension. A Lua script or a file ending in .pak also does not establish dedicated-server support; inspect the author's requirements, dependencies and supported builds.

Prepare a recoverable trial

Record the running game version, platform, existing loader and every installed mod. Save the mod authors' release links and version numbers.
Make a separate, downloadable backup of saves and configuration. Keep an unmodified checkpoint outside the directory used for the trial.
Read each author's server instructions. Identify whether players also need the mod and whether their platform can install it. Stop if those requirements are unclear.
Arrange a separate test installation and disposable world. Do not discover compatibility by opening your established world with missing content mods.

Use the managed Windows workflow when applicable

For a supported Windows installation, Pocketpair documents Workshop packages under Mods/Workshop beside PalServer.exe. Each package folder must expose its Info.json directly. The enable list in Mods/PalModSettings.ini uses the manifest's PackageName, not the folder name. Check for server installation rules and required dependencies before enabling one package.

Have CloudExa confirm file access and the supported installation method before modifying executable or loader files. There is no universal panel button that makes every Palworld mod compatible. Keep an existing manual loader separate from a proposed managed installation until its migration requirements are understood.

Validate one change at a time

Stop the test server cleanly, apply the selected package through its documented method, then start it and retain the complete startup log. A successful process start is only the first checkpoint: connect with a prepared client, exercise the mod's advertised feature, save the disposable world and confirm it survives a clean stop and start.

If startup fails before a client joins, investigate the server package, loader and dependencies. If the server is healthy but only one client fails, compare that client's build and required mods. Neither symptom justifies deleting a save.

Keep rollback usable

Retain the previous compatible package set and configuration alongside the pre-change checkpoint. If a trial writes modded content into a save, return to the corresponding checkpoint rather than assuming disabling the mod reverses its changes. Schedule production changes only after the trial passes.