On this page
Palworld PvP won’t turn on until three separate values inside PalWorldSettings.ini are all set to True at the same time, on a dedicated server. This is the single most common reason players open the config, flip one line, restart, and still can’t damage another player. This guide names the three keys, shows exactly where the file sits on both a dedicated server and a local install, and explains why the “PvP” toggle you see when creating a world in the base game is not the same system as the one in that ini file at all.
TL;DR
- Three ini keys must all read True: bIsPvP, bEnablePlayerToPlayerDamage, and bEnableDefenseOtherGuildPlayer
- The file lives under Pal/Saved/Config/WindowsServer/ or LinuxServer/, and only exists after the server has been started once
- Editing while the server is running gets silently overwritten on shutdown — stop it first
- A world’s own WorldOption.sav can override your ini edits entirely if the world already existed
- The in-game “PvP” checkbox on a local or co-op world is a different system from the dedicated server ini
Where the PvP Settings Live on a Dedicated Server
On a rented or self-hosted dedicated server, everything routes through one config file. Palworld server configuration happens entirely through a single file: PalWorldSettings.ini, and it controls difficulty, the Pal spawn rate, PvP, max players, automatic backups and whether mods are allowed. On Windows that’s steamapps\common\PalServer\Pal\Saved\Config\WindowsServer\PalWorldSettings.ini, and on Linux it’s the equivalent path under Config/LinuxServer/. If you don’t see the folder yet, that’s expected — running the PalServer executable at least once is essential, since without that the PalWorldSettings.ini file will not be created. There’s also a template file sitting nearby called DefaultPalWorldSettings.ini. Don’t touch it: PalWorldSettings.ini is the active configuration your server reads, while DefaultPalWorldSettings.ini is just a reference template and editing it has no effect. If base defenses feel off after you enable PvP, it’s worth cross-checking your base pal work suitability setup too, since combat-capable Pals stationed at a base behave differently once other guilds can actually be attacked.
Step-by-Step: How to Turn On PvP on a Dedicated Palworld Server
Warning
Editing the ini on a live server does nothing lasting. Stop the server first, since Palworld rewrites the live config on shutdown and editing a running server loses your work.
Follow this sequence to get it done fast.
-
1
Stop the server completely
do not edit the file while the server is running, or your changes get discarded on the next save.
-
2
Open the live PalWorldSettings.ini, not the Default one
navigate to the WindowsServer or LinuxServer config folder and confirm the filename before editing.
-
3
Find the OptionSettings=(...) line
every setting sits on one long comma-separated line under the PalGameWorldSettings header, so scroll carefully rather than searching for line breaks.
-
4
Set the three PvP keys to True
bIsPvP=True, bEnablePlayerToPlayerDamage=True, and bEnableDefenseOtherGuildPlayer=True, keeping the surrounding parentheses intact.
-
5
Save and restart the server
the new rules only take effect once the server process reloads the file on startup.
-
6
Have players reconnect
anyone already logged in when you restart may need to disconnect and rejoin before the new PvP state applies to their session.
Dedicated Server vs Local Co-op: Which Setup Actually Lets You Fight
Not every Palworld PvP question is about a rented box. Plenty of players just want to duel a friend in a self-hosted or single-host world, and that path doesn’t touch PalWorldSettings.ini at all — it runs through the world creation screen inside the base game instead. Here’s how the common setups compare.
| Method | Speed to Apply | Effort | Best For |
|---|---|---|---|
| Rented dedicated server (control panel) | Fast — edit and restart from the panel | Low | Groups who want a persistent PvP world others can join |
| Self-hosted SteamCMD dedicated server | Moderate — manual file edit, manual restart | Medium | Players comfortable with FTP/SSH who want full control |
| Local or Steam-hosted co-op world | Depends on the in-game menu, not the ini | Low | Small friend groups who just want to fight without server admin |
| Community rental with a settings generator | Fast — presets output a ready line | Low | Anyone unsure of the exact syntax who wants a PvP preset pasted in |
What Actually Changes After a Server Restart, and What Doesn't
This is where most “I set it and it’s still broken” reports come from. Palworld reads the configuration at startup, so you have to save your changes and restart the server for them to take effect. That part is straightforward. What trips people up is everything around it. Almost every case of settings not applying comes down to either editing DefaultPalWorldSettings.ini instead of the live copy, or the world already existing and reading WorldOption.sav instead — so confirm you’re editing the right file and, if it’s an existing world, replace or delete WorldOption.sav. On top of that, players may need to disconnect and reconnect to the server to experience the updated settings, because the server may not automatically apply the changes to players who are already connected.
A related wrinkle: guild-owned base defenses and Pals stationed at a base don’t automatically start fighting outsiders just because bIsPvP is True. If your Pals stopped reacting to intruders once you flipped these settings, it’s worth checking a general troubleshooting pass on why base Pals stop working before assuming the PvP config itself is the culprit.
Common Misconceptions About Palworld PvP Settings
Myth: bIsPvP=True Is All You Need
This is the most repeated mistake in every discussion thread about broken PvP. Turning on bIsPvP alone does nothing — you must also enable bEnablePlayerToPlayerDamage and bEnableDefenseOtherGuildPlayer. Without the second key specifically, bEnablePlayerToPlayerDamage allows players to directly damage other players, and without it “PvP” is mostly cosmetic — the mode flag is on, but nobody can actually land a hit.
Myth: Friendly Fire Is Part of the Same Toggle
Friendly fire is a separate, optional dial, not one of the three required keys. There is also an optional setting called bEnableFriendlyFire=True, which allows players to damage members of their own guild — only enable it if you specifically want teammates to be able to hurt each other. Leave it False if your PvP is meant to be guild-versus-guild rather than free-for-all.
Myth: The Local World PvP Checkbox Is the Same System
The PvP toggle you see when creating or hosting a world from inside the base game is a separate mechanism from the dedicated server ini. A dedicated PalServer reads PalWorldSettings.ini on every startup, but an existing world — including one hosted through the game client — carries its own saved state that can override the ini entirely, which is exactly why replacing or deleting WorldOption.sav is a standard fix when settings refuse to apply to a world that already exists.
Tip
If your Trust or friendship stats seem to swing combat behavior between guildmates once PvP is live, it’s worth reading through how Trust actually affects Pal stats — it’s easy to blame the PvP config for something that’s really a separate mechanic.
Our Take: Is Turning On Palworld PvP Worth the Hassle
Our Take
The three-toggle requirement is annoying but not complicated once you know it exists.
The real friction isn’t the ini syntax, it’s that Palworld’s PvP is scattered across two unrelated systems that happen to share a name, and the game gives you almost no in-game feedback when one of the three required keys is missing — it just quietly does nothing. That design choice is the actual source of most “PvP not working” reports, more than any single misconfigured value.
PvP is also still a Pocketpair-flagged trial feature, so expect rough edges rather than a fully polished mode. That’s worth setting expectations around before you build a whole server community on top of it. If you’re running a PvP server, pairing this setup with a sensible death penalty and drop rule matters too — killing a player can drop bonus loot, since the bAdditionalDropItemWhenPlayerKillingInPvPMode setting, when enabled, drops a bonus item on a player kill in PvP, which changes how punishing losing a fight actually feels. Worth checking your gold farming routes too if PvP losses are going to cost your group gear regularly.