iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Prefer not to run the server on your own PC? Godlike.Host offers hosted Minecraft Java servers with free DDoS protection and up to three free backups a day.
Use /gamerule pvp false on current Java Edition servers (1.21.9 and newer) and on Bedrock Dedicated Server. On older Java or Spigot-era servers, stop the server, change pvp=true to pvp=false in server.properties, then restart. The correct method depends on your edition and version; the old Java property was removed in 1.21.9.
Choose the method that matches your server
Minecraft has two different PvP configuration systems. Java Edition 1.21.9 introduced a pvp game rule and removed the historical pvp server property. Older Java servers still read the property from server.properties. Bedrock Dedicated Server documentation does not list a pvp property, so its reliable control is the game rule.
| Server | Use this setting | Does it need a restart? | Required access |
|---|---|---|---|
| Java Edition 1.21.9 or newer | /gamerule pvp false |
No | Console or operator permission |
| Older Java, including many Spigot-era servers | pvp=false in server.properties |
Yes | File access and permission to stop/start the server |
| Bedrock Dedicated Server | /gamerule pvp false |
No | Console or operator permission |
The rule prevents players from dealing damage to other players. It does not turn off hostile-mob attacks, fall damage, fire, drowning, explosions, or other environmental damage.
Disable PvP on Java Edition 1.21.9 and newer
Mojang’s Java Edition 1.21.9 release notes added the pvp game rule and removed the pvp server property in favor of it. If your server reports a 1.21.9-or-later version, use the command method rather than editing server.properties.
#1 Best Overall
From the server console
- Open the control panel’s live console, or the terminal running the server.
- Enter
gamerule pvp falsewithout a leading slash. Console command parsers generally expect the command text without/. - Submit the command and wait for the confirmation message. The rule is applied to the world currently loaded by that server process.
- Have two ordinary players attempt a direct attack against each other. A player should no longer damage the other player, while mob and environmental damage should still work.
From inside the game
- Join the target world with an account that has operator permission.
- Open chat and run
/gamerule pvp false. - Confirm that the command is accepted. A message indicating the rule is now
falsemeans PvP has been disabled for that world. - Test with two non-operator accounts. Operators can have extra permissions or protection plugins that make a test misleading.
If the command is rejected, check that you are an operator, that cheats or commands are enabled for the world, and that you are connected to the intended backend server rather than a proxy or lobby.
Turn PvP back on
Run /gamerule pvp true from an authorized in-game account, or enter gamerule pvp true in the console. The change is immediate and does not require a restart.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteDisable PvP on an older Java or Spigot-era server
On versions that still use the historical server property, the setting is stored in the server’s server.properties file. Spigot documentation describes pvp as a Boolean that controls whether players can damage one another, with true as the default.
Change the property safely
- Make a backup of the relevant world and configuration files. At minimum, preserve
server.propertiesand the world directory before editing. - Stop the server cleanly. Use the panel’s Stop button or the console’s normal stop command and wait until the process exits.
- Open the server’s root directory and edit
server.propertieswith a plain-text editor. - Find the line
pvp=true. Change only the value topvp=false. Do not add quotation marks or spaces around the equals sign. - Save the file while the server is stopped.
- Start the server again. The property is read during startup; changing it while the process is running does not reliably update the active setting.
- Test player-versus-player damage with two non-operator accounts.
If the file does not contain a pvp line, add pvp=false on its own line while the server is stopped, then restart. If the server creates a new value or reverts the change, check whether a control panel, startup script, or plugin is regenerating the file.
Why editing while the server runs can fail
A running server keeps configuration in memory and may write its in-memory values back to disk when it shuts down. If you edit the file first and then stop the server, your edit can be overwritten. Stop the process before changing a file-based property, and verify the saved file after the next startup.
Re-enable PvP on an older server
Stop the server, change pvp=false back to pvp=true, save the file, and restart. The property’s documented default is true, but the explicit value is preferable because it records your intended configuration.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallDisable PvP on Bedrock Dedicated Server
Microsoft’s current Bedrock Dedicated Server properties reference documents server.properties as an INI-style file but does not list a pvp key. Do not assume that adding the Java-style property will control Bedrock PvP.
Use the Bedrock game rule
- Open the Bedrock Dedicated Server console, or join the world with an account that has operator permission.
- Run
gamerule pvp falsein the console, or/gamerule pvp falsein chat. - Check for the command confirmation and test with two non-operator players.
- To restore combat, run
gamerule pvp truein the console or/gamerule pvp truein chat.
Do not rely on disable-player-interaction
Bedrock’s properties reference labels disable-player-interaction as “not server authoritative.” That qualification means it is not a dependable server-side PvP switch. Use the pvp game rule through the console or an authorized operator instead.
Rank #3
- The classic UNO card game builds fun on game night with a Minecraft theme.
- UNO Minecraft features a deck and storage tin decorated with graphics from the popular video game.
- Players match colors and numbers to the card on top of the discard pile as in the classic game.
- The Creeper card unique to this deck forces other players to draw 3 cards.
- Makes a great gift for kid, teen, adult and family game nights with 2 to 10 players ages 7 years and older, especially Minecraft and video game fans.
What the PvP rule changes—and what it leaves enabled
The rule targets damage dealt by one player to another. It is not a general invulnerability setting.
- Blocked: direct player attacks and other player-caused damage covered by the PvP rule.
- Still enabled: hostile mobs, neutral mobs that become hostile, fall damage, fire and lava, drowning, suffocation, starvation, terrain hazards, and other environmental damage.
- Potentially separate: plugins, add-ons, command blocks, custom abilities, or server software that applies damage independently of vanilla PvP.
If players can still lose health after the rule is false, identify the damage source rather than assuming the PvP setting failed. A zombie attack, a fall, or a plugin-generated projectile is not evidence that player-versus-player damage is enabled.
World scope, multi-world servers, and proxies
The game rule belongs to a world. On a simple single-world server, one command covers the active world. A multi-world setup can load several worlds with separate gamerule states, and a proxy network can send players to different backend servers.
When only one world should be peaceful
Run /gamerule pvp false while you are in the specific world that should block PvP. Leave the rule set to true in worlds intended for combat. Confirm each world independently with two test accounts.
Rank #4
- Now Minecraft lovers can play a special version of UNO!
- Same as Basic UNO but features Minecraft characters and includes special Creeper rule card. Draw this card and the other players have to draw three more cards from the pile!
- The goal is to get rid of all the cards in your hand.
- First player or team to 500 wins.
- When you're down to one card, don't forget to yell "UNO"!
Vanilla server settings do not provide region-level PvP zones. If you need a protected spawn, duel arenas, faction boundaries, or mode-specific rules, use server software or a plugin that explicitly supports those scopes. Apply and document the setting on every affected world or backend; changing the lobby server does not automatically change a survival backend.
Proxy and managed-panel checks
On a proxy network, the console you see may belong to the proxy rather than the Minecraft server that owns the world. Execute the command on the backend server hosting that world. In a managed panel, identify whether the panel offers a console, an operator-management screen, or a file manager. Your available method depends on those permissions.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshooting when pvp=false does not work
The server says the property is unknown
This usually indicates Java Edition 1.21.9 or newer, where Mojang removed the server property. Stop trying to edit server.properties and run /gamerule pvp false with operator or console access.
The gamerule command is unknown
Confirm the edition and version. An older Java server may require the property method. Also check that the command is being sent to the game server, not a proxy console, and that the account has operator permission. A misspelled command or an unsupported server implementation can produce the same symptom.
The setting resets after a restart
For a file-based configuration, verify that the server was stopped before editing and that the file was saved in the actual server root. For a game rule, verify that you changed the intended world and that a plugin or world-management system is not loading a saved rule afterward. Capture the startup log and inspect which world the process loads.
Free tools Windows power users keep installed
One-click scans. No signup required.
Players still damage one another
- Check the rule’s current value in the target world with
/gamerule pvp, where supported. - Make sure both players are testing in that same world and backend.
- Test with ordinary players rather than operators.
- Temporarily review plugins, add-ons, command blocks, and custom combat systems that may apply damage outside vanilla PvP.
- Confirm that the observed damage is actually from another player and not a mob, fall, fire, or another environmental source.
The file keeps reverting to pvp=true
Stop the server, edit the file, save it, and inspect its timestamp and contents before restarting. A hosting panel template, deployment script, container image, or plugin may be writing defaults on startup. Remove or update that automation, or use the server’s documented configuration interface instead of making a one-time manual edit.
Verification checklist
Use this checklist after changing either method:
- Edition and version identified.
- Correct control selected: game rule for Java 1.21.9+, game rule for Bedrock Dedicated Server, or property for older Java.
- Command run in the world and backend that host the players.
- Operator or console authorization confirmed.
- Two non-operator players used for the test.
- Direct attacks fail while a separate mob or environmental damage test behaves normally.
- Backup retained before any file edit.
- Rollback command or property value recorded.
Backups, rollback, and administrative practice
Back up the relevant world and configuration before changing a production server. For a command-based change, record the original gamerule value so you can restore it quickly. For an older property-based server, preserve the original server.properties file and change only the pvp value.
Do not paste untrusted commands into a console merely because they claim to disable PvP. A normal change requires only the single gamerule command or the one Boolean property. Keep operator access limited to trusted administrators, and communicate the change to players so they know that PvP is disabled but ordinary Minecraft hazards remain.
When you lack console or file access
The task requires at least one of these capabilities: access to the server console, operator permission in the target world, or file-manager access plus the ability to stop and restart an older Java server. If your account has none of them, ask the server owner or administrator to apply the command. A managed Minecraft host can perform the same operation only if its panel grants the required console, operator, or configuration controls.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Final decision
For Java Edition 1.21.9 and later, use /gamerule pvp false; the former pvp entry in server.properties is no longer the supported switch. For older Java and Spigot-era servers, stop the server, set pvp=false, and restart. For Bedrock Dedicated Server, use the game rule rather than adding a Java property or relying on the non-authoritative disable-player-interaction setting.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
