Using Mods and Plugins on a Palworld Dedicated Server
Install server-side mods with the official v0.7 mod loader on Windows dedicated servers.
Mods can add fresh gameplay, quality-of-life features, and custom rules. Server owners can install server-side mods that apply to everyone who joins, but the official mod loader has specific requirements. This guide covers installation, activation, and troubleshooting.
Platform support
The official Palworld mod loader was introduced in version 0.7. It currently works only on the Windows Steam client and the Windows dedicated server. Linux dedicated servers and console clients cannot load mods through this official loader.
If your community plays on multiple platforms, remember that mods may only affect players on Windows. Console and Game Pass players often cannot see modded content.
Installing server mods
Server mods are placed in the Mods/Workshop folder. Each mod package contains an Info.json file with metadata such as the package name, version, and install rules. The file Mods/PalModSettings.ini controls which mods are active.
A minimal PalModSettings.ini looks like this:
bGlobalEnableMod=true
ActiveModList=MyServerMod
Replace MyServerMod with the actual package name from the mod's Info.json. If you want multiple mods, list them according to the loader's expected format, usually separated by commas.
Server-only rules
Only mods whose InstallRule includes IsServer=true will run on a dedicated server. Client-only mods must be installed by each player individually. Installing a client-only mod on the server has no effect.
Always check the mod description for whether it is server-side, client-side, or both. Server-side mods can change world behavior, stats, and drops. Client-side mods change visuals or UI for that player only.
Finding compatible mods
Download mods from reputable sources such as the official Palworld mod community, Nexus Mods, or the mod author's website. Check the Info.json for the supported game version. A mod built for an older patch may crash the server or silently fail.
The Mods/Workshop folder can contain multiple packages. Each package should have a unique folder name and an Info.json at the top level. Do not nest mod folders inside each other. If the loader cannot find Info.json, the mod will not load. For a large mod list, enable mods one at a time and test each restart to identify the mod that causes a crash.
Enabling and restarting
After placing mods and editing PalModSettings.ini, restart the server. Mods are loaded during startup, so watch the console for load order and error messages. If the server fails to start, remove the mod from ActiveModList and restart. With patience and good backups, mods can turn a standard Palworld server into a unique experience for your community.
Tips
Keep a backup of your save folder before adding mods. Some mods can alter world data in ways that are not easy to revert. Check the mod's documentation for updates and compatibility with the current game version. If a mod stops working after a patch, wait for the author to update it before re-enabling.
Sources and further reading
This guide is an original synthesis. Check these references for official details and changes after publication.
- Palworld Modding Documentation — Pocketpair
- Palworld Community Mods — Nexus Mods
Ready to grow your Palworld community?
List your server so players can discover its live status, features, and community.
Keep learning
Related guides
Managing Your Palworld Server with the REST API
Enable the REST API, authenticate with Basic Auth, and use endpoints to manage players and broadcasts.
Backing Up, Updating, and Restoring Your Palworld Server
Protect your world by backing up saves, updating through steamcmd, and restoring when needed.
Palworld Server Ports and Firewall Guide
Open the right UDP and TCP ports and protect management interfaces like REST API and RCON.