Minecraft Gamerules Guide - All Game Rules Explained

Customize your Minecraft world without installing any mods, thanks to gamerules. These settings, integrated into the game since version 1.4.2, allow you to radically transform your experience. Freeze the sun at noon, prevent creepers from destroying your builds, or keep your gear after dying: everything becomes achievable with a few commands. Here is the reference guide to master each of these rules.

---

How Gamerules Work

Each Minecraft world stores its own game rules. Modifying a gamerule in one world does not affect others. These adjustments open the door to tailored experiences: hardcore servers, adventure maps, or simply relaxing games with friends.

Accessing Gamerules

On Java Edition, you have two options. First, the world creation screen offers a dedicated menu for game rules, organized by categories with simple toggles. Second, once in-game, the command /gamerule remains available for any adjustments.

On Bedrock Edition, only a few options appear in the world settings. Most rules require the use of the in-game command.

Using the Command

/gamerule <rule> <value>

Accepted values are either true/false for binary options or an integer for numerical parameters. Typing only /gamerule <rule> displays the currently active value.

Some concrete examples:

Desired Action	Command to Type
Freeze time at noon	/gamerule doDaylightCycle false
Protect terrain from mobs	/gamerule mobGriefing false
No longer lose items	/gamerule keepInventory true

---

Environmental Rules

These settings shape the world around you: weather, passage of time, behavior of fire and natural elements.

---

randomTickSpeed

Characteristic	Information
Compatibility	Java and Bedrock
Initial Setting	3 on Java, 1 on Bedrock
Introduced in	1.8

This value orchestrates the speed of many natural processes in each chunk. Crops grow, grass spreads, leaves decay, ice melts: all of this depends on this parameter.

Setting	Result Obtained
0	Total freeze of nature (nothing grows)
3	Standard rate on Java
10	Accelerated growth
1000+	Near-instant evolution (risk of lag)

/gamerule randomTickSpeed 10

---

doDaylightCycle

Characteristic	Information
Compatibility	Java and Bedrock
Initial Setting	true
Introduced in	1.6.1

The sun and moon cease their course when this rule is disabled. The time remains frozen at the exact moment of the change. Perfect for capturing a sunset or ensuring permanent darkness.

/gamerule doDaylightCycle false

---

doWeatherCycle

Characteristic	Information
Compatibility	Java and Bedrock
Initial Setting	true
Introduced in	1.6.1

Blocks the natural evolution of the weather. Rain or sunshine, the current atmosphere persists indefinitely. The command /weather remains functional to force a manual change if necessary.

/gamerule doWeatherCycle false

---

doFireTick

Characteristic	Information
Compatibility	Java and Bedrock
Initial Setting	true
Introduced in	1.4.2

Controls the spread of flames and their spontaneous extinction. Once disabled, each fire remains confined to its original location without ever spreading to neighboring blocks, and burns indefinitely as long as its support exists. Ideal for preventing forest fires caused by lightning.

/gamerule doFireTick false

---

doVinesSpread

Characteristic	Information
Compatibility	Java only
Initial Setting	true
Introduced in	1.19.4

Prevents jungle vines from colonizing adjacent surfaces when disabled. Nether variants (twisted, dripping vines) and cave vines retain their usual behavior.

/gamerule doVinesSpread false

---

Snow Accumulation and Liquid Sources

These three rules, exclusive to Java and added in 1.19.3, modify fundamental mechanics:

Rule	Initial Setting	Function
snowAccumulationHeight	1	Maximum number of stackable snow layers
waterSourceConversion	true	Ability to create infinite water sources
lavaSourceConversion	false	Ability to create infinite lava sources

With waterSourceConversion set to false, it is impossible to generate an infinite well with two buckets. Lava becomes a truly finite resource.

/gamerule snowAccumulationHeight 4
/gamerule waterSourceConversion false

---

globalSoundEvents

Characteristic	Information
Compatibility	Java only
Initial Setting	true
Introduced in	1.19.3

Some sounds resonate normally for all players on the server, regardless of their position: the fall of the Ender Dragon or the activation of a Nether portal, for example. By disabling this rule, only nearby players will perceive these sound events.

/gamerule globalSoundEvents false

---

Bedrock Exclusive Settings

Rule	Initial Setting	Role
respawnBlocksExplode	true	Beds explode in the Nether/End
tntExplodes	true	TNT can explode

On Bedrock, disabling respawnBlocksExplode makes beds and respawn anchors harmless in inappropriate dimensions. With tntExplodes set to false, lit TNT disappears without causing any damage.

/gamerule respawnBlocksExplode false
/gamerule tntExplodes false

---

spawnChunkRadius

Characteristic	Information
Compatibility	Java only
Initial Setting	2
Introduced in	1.14

Determines the size of the perpetually active area around the global spawn point. With the default value, a 5×5 chunk square remains constantly loaded. Increasing this radius allows automatic mechanisms to run at spawn even without a player present, at the cost of additional server resources.

/gamerule spawnChunkRadius 4

---

spectatorsGenerateChunks

Characteristic	Information
Compatibility	Java only
Initial Setting	true
Introduced in	1.9

Observers in Spectator mode can normally reveal unexplored territories by going there. This rule, once disabled, prevents spectators from creating new chunks. Particularly useful in UHC to prevent a referee from accidentally revealing the map.

/gamerule spectatorsGenerateChunks false

---

projectilesCanBreakBlocks

Characteristic	Information
Compatibility	Java only
Initial Setting	true
Introduced in	1.19

Allows certain projectiles to break specific blocks. A thrown trident can, for example, detach a stalactite of calcite. Disabling this mechanic protects the scenery from collateral damage.

/gamerule projectilesCanBreakBlocks false

---

Creature Rules

These settings govern the spawning of mobs and their interactions with the environment.

---

mobGriefing

Characteristic	Information
Compatibility	Java and Bedrock
Initial Setting	true
Introduced in	1.4.2

Prevents creatures from modifying terrain or manipulating objects when disabled. This single rule neutralizes many behaviors:

Creature	Blocked Behavior
Creeper	Explosion craters
Enderman	Block theft and movement
Zombie	Trampling turtle eggs
Villager	Harvesting and planting
Wither	Surrounding destruction
Allay	Item pickup

/gamerule mobGriefing false

---

doMobSpawning

Characteristic	Information
Compatibility	Java and Bedrock
Initial Setting	true
Introduced in	1.4.2

Completely stops the spontaneous spawning of creatures in the world. Spawners and structure mobs (bastions, mansions) continue to function normally.

/gamerule doMobSpawning false

---

doInsomnia

Characteristic	Information
Compatibility	Java and Bedrock
Initial Setting	true
Introduced in	1.15

Phantoms, those winged creatures that harass players deprived of sleep, cease to appear when this rule is disabled. No need to monitor your sleepless night counter.

/gamerule doInsomnia false

---

Specific Spawns (Java)

Three distinct rules control specific spawns on Java Edition:

Rule	Initial Setting	Added in	Target
doPatrolSpawning	true	1.15.2	Pillager patrols
doTraderSpawning	true	1.15.2	Wandering trader
doWardenSpawning	true	1.19	Warden

/gamerule doPatrolSpawning false
/gamerule doTraderSpawning false
/gamerule doWardenSpawning false

---

disableRaids

Characteristic	Information
Compatibility	Java only
Initial Setting	false
Introduced in	1.14.3

Completely removes raids from pillagers on villages once activated. Entering a village with the Bad Omen effect no longer triggers any wave of assault. A nice bonus: this effect is no longer consumed, you keep it indefinitely.

/gamerule disableRaids true

---

Neutral Mob Anger (Java)

Two interconnected rules modify the resentment of neutral creatures:

Rule	Initial Setting	Effect
universalAnger	false	Anger extended to all nearby players
forgiveDeadPlayers	true	Automatic forgiveness after the guilty player's death

Enabling universalAnger turns every provocation into a collective threat: hitting a wolf endangers all nearby players. Disabling forgiveDeadPlayers makes this resentment permanent, even after your death.

/gamerule universalAnger true
/gamerule forgiveDeadPlayers false

---

Player Survival Rules

These settings directly influence the life, death, and respawn of players.

---

keepInventory

Characteristic	Information
Compatibility	Java and Bedrock
Initial Setting	false
Introduced in	1.4.2

Probably the most famous gamerule. Once activated, dying no longer means losing your precious gear or accumulated experience points. Only health, hunger, and active effects are reset normally.

/gamerule keepInventory true

---

naturalRegeneration

Characteristic	Information
Compatibility	Java and Bedrock
Initial Setting	true
Introduced in	1.6.1

The passive recovery of health points through a filled hunger bar. When disabled, only potions, golden apples, beacons, or totems allow regaining hearts. Essential for UHC challenges.

/gamerule naturalRegeneration false

---

Individual Damage Types

Four rules allow neutralizing specific sources of damage:

Rule	Compatibility	Source of Damage
fallDamage	Java and Bedrock	Falls
fireDamage	Java and Bedrock	Fire, lava, magma
drowningDamage	Java and Bedrock	Drowning
freezeDamage	Java and Bedrock	Frost (powdered snow)

All are enabled by default (true) and were introduced in version 1.15 (except freezeDamage in 1.17).

/gamerule fallDamage false
/gamerule fireDamage false
/gamerule drowningDamage false
/gamerule freezeDamage false

---

doImmediateRespawn

Characteristic	Information
Compatibility	Java and Bedrock
Initial Setting	false
Introduced in	1.15

Removes the death screen and instantly teleports the player to their spawn point. On Bedrock, this rule is named immediateRespawn.

/gamerule doImmediateRespawn true

---

showDeathMessages

Characteristic	Information
Compatibility	Java and Bedrock
Initial Setting	true
Introduced in	1.4.2

Death announcements in chat disappear when disabled. This also includes notifications sent to owners of deceased pets.

/gamerule showDeathMessages false

---

spawnRadius

Characteristic	Information
Compatibility	Java and Bedrock
Initial Setting	10 (Java) / 5 (Bedrock)
Introduced in	1.9

Defines the area around the global spawn where players can appear upon their first connection or after a death without a personal spawn point. A value of 10 creates a square of 21×21 blocks.

/gamerule spawnRadius 0

---

pvp (Bedrock)

Feature	Information
Compatibility	Bedrock only
Initial setting	true

Player confrontations become impossible once disabled: hits no longer inflict any damage. On Java, this option is configured via the server.properties file.

/gamerule pvp false

---

Portal Delays (Java)

Two parameters adjust the waiting time in Nether portals:

Rule	Initial setting	Affected
playersNetherPortalCreativeDelay	1	Creative players (almost instantaneous)
playersNetherPortalDefaultDelay	80	Survival/adventure players (4 seconds)

/gamerule playersNetherPortalDefaultDelay 40

---

playersSleepingPercentage

Feature	Information
Compatibility	Java and Bedrock
Initial setting	100
Introduced in	1.17 (Java) / 1.20.30 (Bedrock)

Proportion of connected players that must sleep simultaneously to speed up the night transition.

Value	Behavior
100	Unanimity required
50	Simple majority
1	One sleeper is enough
101+	Night transition blocked

/gamerule playersSleepingPercentage 25

---

Rules for Rewards and Loot

These parameters determine what blocks, entities, and creatures drop.

---

doMobLoot

Feature	Information
Compatibility	Java and Bedrock
Initial setting	true
Introduced in	1.4.2

Living creatures stop dropping items and experience upon death when disabled. Independent drops from death remain functional: chicken eggs, sheared wool, or roses generated by the Wither.

/gamerule doMobLoot false

---

doTileDrops

Feature	Information
Compatibility	Java and Bedrock
Initial setting	true
Introduced in	1.4.2

Minable blocks disappear without dropping their usual resource. Special attention to shulker boxes: when disabled, this rule results in the permanent loss of both the container AND its contents. Standard chests release their inventory but not the chest itself.

/gamerule doTileDrops false

---

doEntityDrops

Feature	Information
Compatibility	Java and Bedrock
Initial setting	true
Introduced in	1.8.1

Concerns non-living entities: boats, minecarts, frames, armor stands. When destroyed, they no longer return their corresponding item.

/gamerule doEntityDrops false

---

Explosion Drop Decay (Java)

Three distinct rules, added in 1.19.3, control the recovery of blocks destroyed by different explosions:

Rule	Initial setting	Type of explosion
tntExplosionDropDecay	false	TNT
mobExplosionDropDecay	true	Creatures (Creeper, Wither)
blockExplosionDropDecay	true	Others (beds, crystals)

When enabled, the probability of recovering a block decreases with its distance from the center of the explosion. TNT retains a full recovery rate by default.

/gamerule mobExplosionDropDecay false
/gamerule blockExplosionDropDecay false

---

Chat and Interface Rules

These parameters modify the display of information and the behavior of command feedback.

---

sendCommandFeedback

Feature	Information
Compatibility	Java and Bedrock
Initial setting	true
Introduced in	1.8

Each executed command generates a confirmation message in the chat. Disabling this rule significantly cleans up the conversation, particularly useful on servers using many automated commands.

/gamerule sendCommandFeedback false

---

commandBlockOutput

Feature	Information
Compatibility	Java and Bedrock
Initial setting	true
Introduced in	1.4.2

Command blocks normally transmit their execution results to connected operators. When disabled, these machines remain silent in the chat while retaining their functionality.

/gamerule commandBlockOutput false

---

announceAdvancements

Feature	Information
Compatibility	Java only
Initial setting	true
Introduced in	1.12

Progress made by players is publicly displayed in the chat. When disabled, these achievements remain private. Replaces the old rule announceAchievements removed during the system overhaul.

/gamerule announceAdvancements false

---

logAdminCommands

Feature	Information
Compatibility	Java only
Initial setting	true
Introduced in	1.8

Records each admin command in the server log files. Disabling this rule lightens the logs but removes all traceability of admin actions.

/gamerule logAdminCommands false

---

reducedDebugInfo

Feature	Information
Compatibility	Java only
Initial setting	false
Introduced in	1.8

The debug screen (F3) is significantly lightened when enabled:

Item	Status
Exact XYZ position	Hidden
Direction of view	Hidden
Chunk information	Hidden
Shortcut F3+B (hitboxes)	Inactive
Shortcut F3+G (grid)	Inactive

Perfect for competitions where coordinates must remain secret.

/gamerule reducedDebugInfo true

---

Bedrock Display Options

Rule	Initial setting	Version	Function
showCoordinates	true	1.12.0	Visible XYZ position on screen
showTags	true	1.14.0	"Can place/destroy" indicators on items
showBorderEffect	true	1.17.30	Particles from border blocks

/gamerule showCoordinates false
/gamerule showTags false
/gamerule showBorderEffect false

---

Crafting Rules

These parameters adjust the recipe system and crafting progression.

---

doLimitedCrafting

Feature	Information
Compatibility	Java and Bedrock
Initial setting	false
Introduced in	1.12 (Java) / 1.20.x (Bedrock)

Restricts crafting to only the recipes previously discovered by the player. By default, any item can be created even without having "unlocked" its recipe in the book. Ideal for encouraging exploration and gradual learning.

/gamerule doLimitedCrafting true

---

recipesUnlock

Feature	Information
Compatibility	Bedrock only
Initial setting	true
Introduced in	1.20.30

Normally, picking up an ingredient automatically reveals the associated recipes. When disabled, the entire recipe book becomes immediately accessible without any prior discovery.

/gamerule recipesUnlock false

---

Administrator Rules

These technical parameters mainly concern server management and system limits.

---

maxEntityCramming

Feature	Information
Compatibility	Java only
Initial setting	24
Introduced in	1.11

Beyond this limit of entities occupying the same space, creatures suffer progressive suffocation damage. Setting to 0 completely disables this mechanism, allowing unlimited stacking without consequence.

/gamerule maxEntityCramming 0

---

Command Limits

Rule	Edition	Initial setting	Role
maxCommandChainLength	Java and Bedrock	65536	Chained commands per tick
maxCommandForkCount	Java	65536	Command branches per tick
commandModificationBlockLimit	Java	32768	Blocks modifiable by /fill or /clone
functionCommandLimit	Bedrock	10000	Instructions per function file

These values prevent infinite loops and abuse. Increasing them allows for larger operations at the risk of impacting performance.

/gamerule commandModificationBlockLimit 100000

---

commandBlocksEnabled

Feature	Information
Compatibility	Bedrock only
Initial setting	true
Introduced in	1.7.0

When disabled, command blocks become completely inert. Impossible to place, modify, or execute.

/gamerule commandBlocksEnabled false

---

minecartMaxSpeed

Feature	Information
Compatibility	Java only
Initial setting	8.0
Introduced in	1.8

Velocity ceiling for minecarts on rails. Increasing this value speeds up rail transport, but excessive speeds can disrupt the functioning of powered rails.

/gamerule minecartMaxSpeed 16.0

---

Anti-cheat Checks (Java)

Rule	Initial setting	Version	Target
disableElytraMovementCheck	false	1.9	Elytra movements
disablePlayerMovementCheck	false	1.21	All movements

The server normally monitors abnormal speeds to detect cheaters. Disabling these checks eliminates the "rubberbands" caused by latency, but also opens the door to flying and speed hacks.

/gamerule disableElytraMovementCheck true

---

Summary of Essential Gamerules

Rule	Java	Bedrock	Standard	Main utility
keepInventory	✅	✅	false	Keep items on death
mobGriefing	✅	✅	true	Terrain protection
doDaylightCycle	✅	✅	true	Time control
doWeatherCycle	✅	✅	true	Weather control
naturalRegeneration	✅	✅	true	Passive health regeneration
doMobSpawning	✅	✅	true	Creature spawning
doFireTick	✅	✅	true	Fire spread
randomTickSpeed	✅	✅	3/1	Nature speed
playersSleepingPercentage	✅	✅	100	Night transition
doInsomnia	✅	✅	true	Spawn of phantoms

---

Recommended Configurations by Server Type

Default Minecraft gamerules are suitable for a solo game, but a multiplayer server has different needs depending on its orientation. Here are the configurations we recommend for each type of server, tested on hundreds of servers hosted by OuiHeberg.

Survival Server

The goal of a survival server is to provide a balanced experience where progression matters, while protecting players' builds.

GameRule	Value	Why
keepInventory	false	Death should have consequences. It's the heart of survival mode.
mobGriefing	false	Prevents creepers from destroying builds and endermen from moving blocks. Essential on a community server.
doFireTick	false	Prevents fire from spreading and burning wooden structures. Also reduces lag related to block updates.
playersSleepingPercentage	30	Allows the night to pass as soon as 30% of players sleep, instead of waiting for everyone.
spawnRadius	10	Reasonable spawn area to prevent players from respawning all at the same block.
maxEntityCramming	24	Default limit. Reducing it to 8 improves performance without notable impact on gameplay.

Quick command to apply this configuration:

/gamerule mobGriefing false
/gamerule doFireTick false
/gamerule playersSleepingPercentage 30

Creative Server

In creative mode, the goal is to allow players to build freely without constraints.

GameRule	Value	Why
doDaylightCycle	false	Freezes time so builders can work uninterrupted at night. Set the time to noon with /time set 6000 before disabling.
doWeatherCycle	false	Removes rain and thunderstorms that obstruct visibility during construction.
doMobSpawning	false	No mobs spawn. Zero distractions, zero unwanted combat.
commandBlockOutput	false	Disables command block messages in chat. Useful if your map contains redstone/command block mechanics.
keepInventory	true	No item loss when falling into the void or accidental death.
doFireTick	false	Prevents fire from destroying ongoing constructions.

PvP Server

A PvP server must offer fast-paced combat with minimal environmental disruptions.

GameRule	Value	Why
keepInventory	true	Avoids the frustration of losing gear upon death. Players fight more often if the penalty is low.
naturalRegeneration	false	Disables passive regeneration. Players must use potions or golden food to heal, making combat more tactical.
doMobSpawning	false	No mobs interfering with combat.
announceAdvancements	false	Disables advancement messages in chat to keep it clean.
showDeathMessages	true	Keep death messages for the PvP feed.
pvp	true	This is not a gamerule but a setting in server.properties. Make sure it is enabled.

Mini-games Server

Mini-games require strict control of the environment for mechanics to function properly.

GameRule	Value	Why
doDaylightCycle	false	Time control set by command blocks according to the current mini-game.
doWeatherCycle	false	Weather controlled by the game system, not by chance.
doMobSpawning	false	Only mobs summoned by command appear.
mobGriefing	false	Prevents any unwanted destruction of arenas and structures.
commandBlockOutput	false	Essential to prevent command block messages from spamming the chat.
sendCommandFeedback	false	Masks command feedback to players for a cleaner experience.
randomTickSpeed	0	Freezes crop growth, grass spread, and all natural processes. The environment remains exactly as you designed it.

---

GameRules FAQ

How to enable keepInventory?

The gamerule keepInventory prevents players from losing their items upon death. To enable it, type /gamerule keepInventory true in chat (as an operator) or in the server console. Players will retain their inventory and XP levels after each death. To disable it, use /gamerule keepInventory false. This change is immediate and does not require a restart.

How to disable the day/night cycle?

To freeze time, use /gamerule doDaylightCycle false. Time will remain locked at the current hour. If you want to set the time first, type /time set day (6,000 ticks, noon) or /time set 18000 (midnight) before disabling the cycle. To reactivate the cycle: /gamerule doDaylightCycle true.

How to reset a gamerule?

Minecraft does not offer a "reset" command for gamerules. To revert to the default value, simply set it manually. For example, the default value of randomTickSpeed is 3: type /gamerule randomTickSpeed 3. For boolean gamerules, most are set to true by default (check the main table of this article). If in doubt, /gamerule ruleName (without a value) displays the currently active value.

Are gamerules saved per world?

Yes. Each Minecraft world stores its own gamerules in the level.dat file. If you have multiple worlds on your server (via Multiverse for example), each world has its own independent settings. Changing a gamerule in the main world does not affect the others.

---

To create your Minecraft server and apply these configurations, check our server creation guide or discover our Minecraft hosting offers.

Conclusion

Gamerules are a powerful tool to shape your Minecraft experience according to your desires. Peaceful mode without destructive creepers, hardcore challenge without regeneration, or event server with unique rules: the possibilities are vast.

Test these settings in a dedicated experimental world before deploying them on your main server. Each modification remains reversible at any time via the /gamerule command.

Happy customizing!