The most useful server gamerules to review are keep_inventory (or older Java keepInventory) for preserving items after death, mob_griefing (or older Java mobGriefing) for preventing mobs from changing blocks, and commandBlockOutput for reducing command-block messages. A fourth rule, doMobSpawning, is often suggested for spawn control, but its behavior was not confirmed in the available documentation, so treat it as a test-only option rather than a guaranteed fix.
Names differ by edition and Java version. Before changing anything, run /gamerule and press TAB to see the exact rule names your server accepts. Java arguments are case-sensitive.
As an Amazon Associate I earn from qualifying purchases.
If you want to run these gamerules on a hosted Minecraft world, Godlike.Host offers Minecraft Java, Bedrock and modded Minecraft servers with a Pterodactyl-based game panel. The service also provides SFTP/FTP access and up to three free backups a day with restore.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick recommendations
| Server goal | Rule to review | Newer Java spelling | Older Java spelling | Bedrock spelling or status |
|---|---|---|---|---|
| Keep a player’s inventory after death | Keep inventory | keep_inventory |
keepInventory |
keepinventory |
| Stop creepers, ghasts and similar mobs changing blocks | Mob griefing | mob_griefing |
mobGriefing |
Check the rule list on the running Bedrock world |
| Hide command-block output from the console | Command-block output | commandBlockOutput is the spelling shown in older command references; verify with TAB on current builds |
Not established in the available documentation | |
| Change natural mob spawning | Mob spawning | doMobSpawning is commonly listed |
doMobSpawning |
Behavior and spelling should be checked in-game |
“Best” is a use-case decision, not a measured ranking. A cooperative survival world commonly starts with keep inventory and mob-griefing protection. A technical or adventure server may also disable command-block output. Do not change a rule simply because another server does; each one changes the intended challenge or administration workflow.
#1 Best Overall
How gamerules work
A gamerule is a world-level setting changed with the gamerule command. The general syntax is gamerule <rule name> [<value>]. Supplying a value changes the setting; omitting the value reports its current setting.
Use the leading slash when entering a command in Minecraft chat:
/gameruleTo discover names supported by the exact server build, type /gamerule and press TAB. This is more reliable than copying a command from a guide written for a different release, especially because Java rule names have moved from camelCase to snake_case in recent versions.
Free tools Windows power users keep installed
One-click scans. No signup required.
Permissions and cheats
- In a single-player world or a Bedrock world, cheats must be enabled before gamerules can be changed.
- On a multiplayer server, the sender must have operator-level permission (or an equivalent permission supplied by the server software).
- If the command returns an unknown-rule or permission error, do not keep changing capitalization at random. Recheck the edition, use TAB completion, and confirm that the command is being run in the intended world.
1. Keep inventory after death
Keep inventory is the most common quality-of-life change for survival servers. When enabled, a player’s items are kept after death instead of requiring a recovery trip. It can remove the frustration of losing equipment, but it also reduces the risk associated with dangerous exploration, lava, and long-distance travel.
Commands by version
Recent Java versions use the snake_case form:
/gamerule keep_inventory trueOlder Java material uses camelCase:
/gamerule keepInventory trueBedrock is reported with a lowercase, unseparated name:
/gamerule keepinventory trueBecause the naming transition has been reported differently across Java releases, use the name offered by TAB on your server rather than assuming that one spelling works everywhere. The available documentation does not establish whether every older camelCase alias continues to resolve on newer Java builds.
Turning it off
Use the same spelling that succeeded when enabling it, replacing true with false:
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →/gamerule keep_inventory falseIf your server accepted keepInventory instead, run /gamerule keepInventory false. On Bedrock, use /gamerule keepinventory false.
When it fits
- Casual cooperative survival: useful when the group values building and exploration over punishment for a single mistake.
- Family or mixed-experience servers: prevents a new player from losing all progress before learning the game.
- Hardcore or competitive survival: usually a poor fit because death has less consequence.
- Event worlds: decide before the event starts; changing it after deaths can create an uneven result for players who already recovered items.
What it does not solve
Keep inventory concerns items carried at death. It does not by itself protect builds, prevent a death, or undo damage that occurred before the command was changed. If you are trying to protect a base from an explosion, use the mob-griefing rule instead.
2. Stop creepers and other mobs changing blocks
Mob griefing controls whether creepers, ghasts and similar mobs can alter blocks through their in-game behavior. Disabling it is a practical choice for public survival hubs, building-focused worlds, and servers where repairing explosion damage would otherwise consume administrator time.
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.
Commands by Java naming style
On newer Java versions, the reported spelling is:
/gamerule mob_griefing falseOlder Java references use:
/gamerule mobGriefing falseAs with keep inventory, confirm the accepted spelling with /gamerule plus TAB. The rule name is case-sensitive on Java.
Choosing the value
false: favors protected builds and less maintenance from mob-caused block changes.true: preserves the normal destructive behavior expected by a conventional survival challenge.
Changing this rule is a world-wide decision. It is not a per-player or per-region switch, so a server that wants protected spawn areas but normal mechanics elsewhere may need region or plugin controls in addition to the gamerule.
Common trade-off
Protection can alter farms, defenses, and contraptions that rely on a mob interacting with blocks. Explain the change to players before enabling it, especially on an established world where people may have built around normal mob behavior. If a redstone or farm design stops behaving as expected, first check whether the gamerule was changed before treating the build as broken.
3. Reduce command-block console noise
commandBlockOutput controls whether command-block output is sent to the console in the older references covered here. Suppressing output can make a busy technical server easier to administer when repeating command blocks would otherwise fill logs with routine messages.
Command
/gamerule commandBlockOutput falseTo restore output, run:
/gamerule commandBlockOutput trueThe supplied material does not establish a newer snake_case replacement or a Bedrock spelling for this rule. On a current server, use TAB completion and the no-value form to confirm the exact supported name before changing it:
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"!
/gameruleWhen to leave output enabled
- During initial command-block setup, output helps confirm that a command is firing.
- While diagnosing a failed teleport, scoreboard update, or redstone trigger, output can provide the first clue.
- On an unattended production server with high command volume, disabling routine output can make significant errors easier to spot.
A useful workflow is to leave output enabled while building and testing, then disable it only after the command chain is known to work. If an automated system later fails, temporarily re-enable output, reproduce the problem, and disable it again after diagnosis.
4. Treat doMobSpawning as a verification task
doMobSpawning is frequently listed as a candidate for controlling natural mob spawning. However, the available source material did not confirm its behavior, so this article does not present it as a guaranteed way to stop hostile mobs or all mob creation.
How to test without guessing
- Record the current setting with the no-value command form, using the exact name offered by TAB.
- Change the value in a test copy or a low-risk test world rather than experimenting first on a valuable production world.
- Observe the specific spawning behavior you want to change, including the location and time conditions.
- Restore the original value if the result is not what you intended.
This approach matters because “mob spawning” can be confused with other ways entities appear, such as commands, structures, farms, or special game events. Do not promise players that one unverified rule will eliminate every unwanted mob.
Recommended gamerule sets by server type
| Server style | Suggested starting point | Reasoning |
|---|---|---|
| Casual co-op survival | Enable keep inventory; leave mob griefing at the group’s preferred challenge level | Removes the harshest death penalty while allowing the group to decide whether explosions are part of the challenge. |
| Build-focused community | Enable keep inventory and set mob griefing to false |
Protects time invested in construction and makes exploration less costly. |
| Technical or automation server | Decide on keep inventory; test mob griefing against farms; disable command-block output after testing | Technical builds can depend on normal interactions, while quiet logs help administration once automation is stable. |
| Hard survival challenge | Keep inventory generally false; retain normal mob behavior unless the server’s rules say otherwise |
Preserves meaningful risk. Publish any exception before players begin. |
| Adventure or event map | Set rules before the event and avoid mid-event changes | Consistent settings prevent one team from receiving a different difficulty after the map has started. |
Safe change procedure for a live server
- Identify the edition and build. Java and Bedrock do not necessarily use the same spelling, and Java naming has changed across recent releases.
- Check the current value. Run
/gamerulewith no value, or use the completed rule name without a value when the interface accepts it. - Write down the old setting. This gives you a direct rollback command and prevents accidental permanent changes.
- Announce the impact. Tell players whether deaths, explosions, or command output will behave differently.
- Change one rule at a time. If several settings change together, it becomes harder to identify which one caused an unexpected result.
- Test the affected scenario. For example, use a disposable item for a death test, a protected test block for mob behavior, or a controlled command block for output.
- Record the accepted spelling and value. Keep the command in your server notes so a future administrator does not repeat the version-name search.
Troubleshooting gamerule commands
“Unknown or incomplete command”
Check that you are using the command in the correct edition and that the rule name matches TAB completion exactly. On Java, capitalization matters. Try the newer snake_case name first on a recent Java build, then check whether the older camelCase name is offered by the server.
“You do not have permission”
Enable cheats for the world or run the command as an operator on the server. A correctly spelled command still fails when the sender lacks permission.
The rule changed, but gameplay looks the same
Confirm the value with the no-value form and test the exact behavior affected by that rule. Keep inventory only matters when a player dies; command-block output matters when a command block runs; mob-griefing protection matters when a relevant mob attempts a block-changing action. A test that never triggers the relevant event cannot confirm the setting.
A copied command worked on one server but not another
Compare edition, release, and accepted rule spelling. The reported Java transition from camelCase to snake_case has conflicting version boundaries in community documentation, so the running server’s own rule list is the authoritative practical check for your installation.
You need different behavior in different areas
Gamerules are world-level settings. If only a spawn area, minigame arena, or protected build should behave differently, a gamerule alone is too broad; use the server’s area-management or gameplay tools in addition to the global rule, and document which layer controls each behavior.
Recommended Free Tools
Pre-change checklist
- Have you confirmed Java or Bedrock?
- Have you used TAB completion instead of relying on an old spelling?
- Have you recorded the current value and rollback command?
- Does the rule change affect every player and every area in the world?
- Have you warned players about the change to death penalties, explosions, or command diagnostics?
- Can you test the result safely before applying it to the live world?
The Bottom Line
Start with the rule that solves your actual administration problem: use the accepted keep-inventory spelling for death recovery, mob-griefing protection for build safety, and command-block output control for quieter logs. Because Java rule names and version boundaries are changing, always verify the exact name with /gamerule and TAB on the server you are running.
