You try to join a Palworld server and get told that mods are not allowed on this server, please disable all mods and try again. The confusing part is that this often happens to people who are certain they have no mods installed, or who deleted their mods folder and are still being refused. The message is nearly always about your own game rather than the server, and the reason a deletion does not fix it is that Palworld mods live in more than one place. This guide explains what the message actually means, where every kind of mod hides, and how to get back in.
What the Message Actually Means
This is a client-side check. When you connect, your game compares its mod state against what the server expects. If your client is running mods that the server does not have enabled, the connection is refused and you see this message.
That means two things worth being clear about:
- It is usually your mods causing it, not something misconfigured on the server.
- The fix is normally on your machine, not in the server settings.
The confusion comes from the wording, which reads like the server is rejecting a policy rather than reporting a mismatch.
Note: The message is triggered by a mismatch between your client and the server, and the client is usually the side to fix
Tip: If a friend can join the same server and you cannot, the difference is on your PC
Why Deleting a Mods Folder Did Not Work
Palworld mods install in more than one location depending on how they were made, and most guides only mention one. If you removed one folder and are still blocked, there is another still present.
| Location | What lives there |
|---|---|
Pal\Content\Paks\~mods | Pak-based mods, which are the most common kind |
Pal\Binaries\Win64\Mods | Script mods loaded by a mod loader |
Pal\Binaries\Win64\ue4ss | The mod loader itself, plus its own files |
Pal\Content\Paks\LogicMods | Blueprint mods, which need the loader present |
These sit inside your Palworld install folder. To find it, right click Palworld in Steam, choose Manage, then Browse local files.
Delete the mod content from every one of those locations, not just the first. Leaving the loader behind is the single most common reason the message keeps appearing after a cleanup.
Warning: Removing mods but leaving the loader in
Pal\Binaries\Win64can still trip the check. Remove the loader tooTip: Some installers also drop files loose in
Pal\Binaries\Win64, so check that folder itself rather than only its subfolders
The Reliable Way to Get Back In
If you want to be certain rather than hunting individual files, let Steam do it.
- Close Palworld completely
- Delete the mod folders listed above
- Right click Palworld in Steam, choose Properties, then Installed Files
- Choose Verify integrity of game files
- Wait for it to finish and try joining again
Verification replaces anything modified and reports missing files, which catches mods that patched a game file rather than adding a new one. It does not touch your saves.
Tip: Verifying integrity is the fastest complete fix, and it does not delete your save data
Note: Verification only repairs game files, so you still need to delete the mod folders first or it may leave them alone
Mods on the Server Side
The other half of the question is whether you can just enable the mod on the server instead. On a hosted Palworld server the honest answer is usually no, and it is worth understanding why rather than fighting it.
Palworld ships separate Windows and Linux dedicated server builds. Loafhosts, like most performance-focused hosts, runs the Linux build, because it is what performs well in a managed environment. The mod loaders that make server-side Palworld mods work are Windows-only, so they have nowhere to load on a Linux server.
On top of that, the majority of Palworld mods are client-only by design. They change your interface, your camera, or your local visuals, and they do nothing on a server even where one could load them.
Note: Most Palworld mods are client-only and have no server-side effect at all
Note: Server-side mod loading is a Windows-only path, so it does not apply to a Linux dedicated server
What You Can Change Instead
Plenty of what people install mods for is available as an actual server setting, which is both supported and safe. Palworld exposes a large set of options covering rates, difficulty, combat, guilds and more.
On Loafhosts these are in the Palworld Config Editor in your server’s sidebar, which presents PalWorldSettings.ini as a grouped form rather than the single dense line it is on disk. It covers the full Palworld 1.0 option set, including capture and drop rates, EXP, damage multipliers, death penalty, PvP, guild and base camp limits, and voice chat, with one-click presets. This feature is currently in BETA.
Two useful details. First, you can save while the server is running or stopped, and the change applies the next time it restarts. Second, it can set an option that is missing from an older config file entirely, so a server created before 1.0 can still reach the newer settings.
Server name, description and player slots are editable there too and apply on restart. Ports, passwords and RCON stay read-only, because those are managed for you.
Note: The Palworld Config Editor is in BETA
Tip: Check the settings list before hunting for a mod, a lot of what mods are used for is already an option
If You Are the Server Owner
If your players are hitting this message, the first thing to establish is whether it is one player or everyone.
| Situation | What it points to |
|---|---|
| One player affected | That player’s client mods. Send them the cleanup steps above |
| Everyone affected after a game update | Clients on mismatched versions, wait for mods to update or ask players to run clean |
| Everyone affected after a server change | Check that the server actually started cleanly and is on the expected version |
Also worth knowing: a Palworld update can make a previously fine mod start tripping this check, because the mod is now built against the wrong version. That is why this tends to appear in waves right after a patch rather than randomly.
Tip: After any Palworld update, expect a wave of these reports. It is usually outdated client mods rather than anything you changed
Warning: Remove mods before updating a server rather than after, an update on top of a modded install is much messier to clean up
Frequently Asked Questions
What does “mods are not allowed on this server” mean in Palworld?
It means your client is running mods that the server does not have enabled, so the connection is refused. Despite the wording it is normally about your own installation rather than a server policy, and the fix is to remove your client mods and reconnect.
I deleted my mods and it still says mods are not allowed
Palworld mods install in several places. Check Pal\Content\Paks\~mods, Pal\Content\Paks\LogicMods, Pal\Binaries\Win64\Mods, and the mod loader folder in Pal\Binaries\Win64. Leaving the loader behind is the usual cause. Then verify your game files through Steam.
How do I completely remove Palworld mods?
Close the game, delete the mod folders listed above, then use Steam’s Verify integrity of game files under Properties and Installed Files. Verification restores anything a mod modified and does not affect your saves.
Can I install mods on a Palworld dedicated server?
In practice, no. The mod loaders required for server-side Palworld mods are Windows-only, and hosted servers run the Linux build. Most Palworld mods are client-only anyway and would have no server-side effect.
Will removing mods delete my Palworld save?
No. Mods and saves are stored separately, and verifying game files through Steam only repairs game files. Back up anyway if the save matters to you.
Why did this start happening after an update?
A Palworld update can leave a mod built against the previous version, which then trips the mod check on connect. This is why the problem tends to appear in waves right after a patch. Remove or update the mod.
What can I change on the server instead of using mods?
A great deal. Rates, difficulty, damage, death penalty, PvP, guild limits and voice chat are all server settings. On Loafhosts they are in the Palworld Config Editor, which is in BETA and presents them as a grouped form with presets rather than one long line in a file.