How to Enable or Disable PvP on a Minecraft Server

Direct answer

The pvp property in server.properties controls ordinary player-versus-player damage on a Java server. Other plugins, region flags and team rules can still change combat behavior.

Recommended procedure

1. Stop the Minecraft server and back up server.properties.
2. Set pvp=true to enable ordinary PvP or pvp=false to disable it in that server’s properties.
3. Restart the server; do not expect a client-side setting to override backend combat rules.
4. Test with two non-operator accounts in an unprotected area outside spawn protection.
5. If PvP still behaves unexpectedly, inspect region/claims plugins, minigame plugins and scoreboard team friendly-fire rules.

Why this matters

A proxy does not usually enforce PvP for every backend; each game server has its own relevant game rules and plugins. OP testing can bypass restrictions and hide permissions or region issues.

Practical example: Example: if pvp=true but combat fails only inside a town, inspect the land-protection plugin rather than changing server.properties again. If it fails everywhere, test two non-OP players in a clean wilderness area. Separating global settings from local region flags avoids disabling valuable protection rules.

How to verify the result

• Try a controlled attack between two consenting test players.
• Test both a normal area and a plugin-protected region to identify whether a plugin is overriding vanilla behavior.
• Keep combat plugins enabled one at a time during troubleshooting on a copy of the server.

Version and compatibility notes

• Some minigames intentionally replace default PvP rules with custom mechanics.
• Do not delete protection data to test this setting.

Official references

These sources were checked for the current MSH revision. Version-sensitive details should always be confirmed against the project documentation for the release you run.

• Paper server.properties reference
• Paper configuration

Related guides