Minecraft gamerules guide - all game rules explained
Customizing your Minecraft world without installing any mods is possible thanks to gamerules. These built-in parameters in the game since version 1.4.2 allow you to radically transform your experience. Freezing the sun at noon, preventing creepers from destroying your constructions, or keeping your equipment after death: everything becomes achievable with just 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 on one world does not impact others. These adjustments open the door to custom experiences: hardcore servers, adventure maps, or simply relaxing games with friends.
Accessing gamerules
In Java Edition, you have two options. Firstly, the world creation screen offers a menu dedicated to game rules, organized by categories with simple switches. Secondly, once in the game, the /gamerule command remains available for any adjustments.
In 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 the terrain from mobs | /gamerule mobGriefing false |
| No longer lose items | /gamerule keepInventory true |
Environment rules
These parameters shape the world around you: weather, time passage, fire behavior, and natural elements.
randomTickSpeed
| Feature | 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 decompose, ice melts: all of this depends on this parameter.
| Setting | Result Obtained |
|---|---|
0 | Total nature freeze (nothing grows) |
3 | Standard pace on Java |
10 | Accelerated growth |
1000+ | Almost instantaneous evolution (risk of slowdown) |
/gamerule randomTickSpeed 10
doDaylightCycle
| Feature | Information |
|---|---|
| Compatibility | Java and Bedrock |
| Initial Setting | true |
| Introduced in | 1.6.1 |
The sun and moon stop their course when this rule is disabled. The time remains fixed at the precise moment of the modification. Perfect for immortalizing a sunset or ensuring permanent darkness.
/gamerule doDaylightCycle false
doWeatherCycle
| Feature | 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 /weather command remains functional to force a manual change if necessary.
/gamerule doWeatherCycle false
doFireTick
| Feature | 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 eternally as long as its support exists. Ideal for avoiding forest fires caused by lightning.
/gamerule doFireTick false
doVinesSpread
| Feature | Information |
|---|---|
| Compatibility | Java only |
| Initial Setting | true |
| Introduced in | 1.19.4 |
Prevents jungle vines from colonizing adjacent surfaces when disabled. Nether variants (twisted, weeping 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 | Possibility to create infinite water sources |
lavaSourceConversion | false | Possibility to create finite 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
| Feature | Information |
|---|---|
| Compatibility | Java only |
| Initial Setting | true |
| Introduced in | 1.19.3 |
Some sounds normally resonate for all players on the server, regardless of their position: the Ender Dragon's fall or the Nether portal activation, for example. By deactivating this rule, only players nearby will perceive these sound events.
/gamerule globalSoundEvents false
Exclusive Bedrock Settings
| Rule | Initial Setting | Role |
|---|---|---|
respawnBlocksExplode | true | Beds explode in the Nether/End |
tntExplodes | true | TNT can explode |
In Bedrock, disabling respawnBlocksExplode makes respawn beds and anchors safe in inappropriate dimensions. With tntExplodes set to false, ignited TNT disappears without causing any damage.
/gamerule respawnBlocksExplode false
/gamerule tntExplodes false
spawnChunkRadius
| Feature | 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 operate at spawn even without a player present, at the cost of additional server resources.
/gamerule spawnChunkRadius 4
spectatorsGenerateChunks
| Feature | Information |
|---|---|
| Compatibility | Java only |
| Initial Setting | true |
| Introduced in | 1.9 |
Spectators in Spectator mode can normally reveal unexplored territories by visiting them. Disabling this rule prevents spectators from generating new chunks. Particularly useful in UHC to prevent a referee from accidentally revealing the map.
/gamerule spectatorsGenerateChunks false
projectilesCanBreakBlocks
| Feature | Information |
|---|---|
| Compatibility | Java only |
| Initial Setting | true |
| Introduced in | 1.19 |
Allows certain projectiles to break specific blocks. For example, a thrown trident can dislodge a calcite stalactite. Disabling this mechanic protects the environment from collateral damage.
/gamerule projectilesCanBreakBlocks false
Creature Rules
These settings govern mob spawning and their interactions with the environment.
mobGriefing
| Feature | Information |
|---|---|
| Compatibility | Java and Bedrock |
| Initial Setting | true |
| Introduced in | 1.4.2 |
Prohibits creatures from modifying the terrain or manipulating items when disabled. This single rule neutralizes many behaviors:
| Creature | Blocked Behavior |
|---|---|
| Creeper | Explosion craters |
| Enderman | Teleportation and block movement |
| Zombie | Trampling turtle eggs |
| Villager | Harvesting and planting |
| Wither | Environmental destruction |
| Allay | Item pickup |
/gamerule mobGriefing false
doMobSpawning
| Feature | Information |
|---|---|
| Compatibility | Java and Bedrock |
| Initial Setting | true |
| Introduced in | 1.4.2 |
Completely stops spontaneous creature spawning in the world. Spawners and structure mobs (bastions, mansions) continue to function normally.
/gamerule doMobSpawning false
doInsomnia
| Feature | Information |
|---|---|
| Compatibility | Java and Bedrock |
| Initial Setting | true |
| Introduced in | 1.15 |
Phantoms, the winged creatures that harass sleep-deprived players, stop appearing when this rule is disabled. No need to monitor your sleepless nights counter anymore.
/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 | Deep dark warden |
/gamerule doPatrolSpawning false
/gamerule doTraderSpawning false
/gamerule doWardenSpawning false
disableRaids
| Feature | Information |
|---|---|
| Compatibility | Java only |
| Initial Setting | false |
| Introduced in | 1.14.3 |
Completely removes pillager raids from villages once activated. Entering a village with the Bad Omen effect no longer triggers any assault waves. Appreciable bonus: this effect is not consumed anymore, you keep it indefinitely.
/gamerule disableRaids true
Neutral Mobs' Anger (Java)
Two interconnected rules modify the grudge of neutral creatures:
| Rule | Initial Setting | Effect |
|---|---|---|
universalAnger | false | Anger extended to all nearby players |
forgiveDeadPlayers | true | Automatic forgiveness after the culprit's death |
Enabling universalAnger turns every provocation into a collective threat: hitting a wolf endangers all nearby players. Disabling forgiveDeadPlayers makes this grudge permanent, even after your death.
/gamerule universalAnger true
/gamerule forgiveDeadPlayers false
Player Survival Rules
These settings directly influence the life, death, and reappearance of players.
keepInventory
| Feature | 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 precious equipment or accumulated experience points. Only health, hunger, and active effects are reset normally.
/gamerule keepInventory true
naturalRegeneration
| Feature | Information |
|---|---|
| Compatibility | Java and Bedrock |
| Initial Setting | true |
| Introduced in | 1.6.1 |
Passive health regeneration 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 neutralize specific sources of damage:
| Rule | Compatibility | Damage Source |
|---|---|---|
fallDamage | Java and Bedrock | Falls |
fireDamage | Java and Bedrock | Fire, lava, magma |
drowningDamage | Java and Bedrock | Drowning |
freezeDamage | Java and Bedrock | Freezing (powdery snow) |
All are enabled by default (true) and introduced in version 1.15 (except freezeDamage in 1.17).
/gamerule fallDamage false
/gamerule fireDamage false
/gamerule drowningDamage false
/gamerule freezeDamage false
doImmediateRespawn
| Feature | Information |
|---|---|
| Compatibility | Java and Bedrock |
| Initial Setting | false |
| Introduced in | 1.15 |
Removes the death screen and instantly teleports the player to their respawn point. In Bedrock, this rule is named immediateRespawn.
/gamerule doImmediateRespawn true
showDeathMessages
| Feature | Information |
|---|---|
| Compatibility | Java and Bedrock |
| Initial Setting | true |
| Introduced in | 1.4.2 |
Death announcements in the chat disappear when disabled. This also includes notifications sent for deceased tamed animals.
/gamerule showDeathMessages false
spawnRadius
| Feature | Information |
|---|---|
| Compatibility | Java and Bedrock |
| Initial Setting | 10 (Java) / 5 (Bedrock) |
| Introduced in | 1.9 |
Sets the area around the world spawn where players can appear on their first connection or after a death without a personal respawn point. A value of 10 creates a 21×21 block square.
/gamerule spawnRadius 0
pvp (Bedrock)
| Feature | Information |
|---|---|
| Compatibility | Bedrock only |
| Initial Setting | true |
Player versus player combat becomes impossible when disabled: attacks no longer deal damage. In 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 instant) |
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 required to 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
Rewards and Loot Rules
These settings 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 productions 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 |
Mined blocks disappear without leaving 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 drop 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 | Explosion Type |
|---|---|---|
tntExplosionDropDecay | false | TNT |
mobExplosionDropDecay | true | Entities (Creeper, Wither) |
blockExplosionDropDecay | true | Others (beds, crystals) |
When enabled, the probability of recovering a block decreases with its distance from the explosion center. TNT retains a full recovery rate by default.
/gamerule mobExplosionDropDecay false
/gamerule blockExplosionDropDecay false
Chat and Interface Rules
These settings modify information display and command feedback behavior.
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 relay their execution results to connected operators. When disabled, these machines remain silent in the chat while still functioning.
/gamerule commandBlockOutput false
announceAdvancements
| Feature | Information |
|---|---|
| Compatibility | Java only |
| Initial Setting | true |
| Introduced in | 1.12 |
Player-unlocked advancements are publicly displayed in the chat. When disabled, these achievements remain private. Replaces the old announceAchievements rule removed during the system overhaul.
/gamerule announceAdvancements false
logAdminCommands
| Feature | Information |
|---|---|
| Compatibility | Java only |
| Initial Setting | true |
| Introduced in | 1.8 |
Logs every administrator command in the server files. Disabling this rule reduces log size but eliminates all traceability of administrative actions.
/gamerule logAdminCommands false
reducedDebugInfo
| Feature | Information |
|---|---|
| Compatibility | Java only |
| Initial Setting | false |
| Introduced in | 1.8 |
The debug screen (F3) is significantly streamlined when activated:
| Element | Status |
|---|---|
| Exact XYZ position | Hidden |
| Looking direction | Hidden |
| Chunk information | Hidden |
| F3+B shortcut (hitboxes) | Inactive |
| F3+G shortcut (grid) | Inactive |
Perfect for competitions where coordinates must remain confidential.
/gamerule reducedDebugInfo true
Bedrock Display Options
| Rule | Initial Setting | Version | Function |
|---|---|---|---|
showCoordinates | true | 1.12.0 | Display XYZ position on screen |
showTags | true | 1.14.0 | "Can place/break" indications on items |
showBorderEffect | true | 1.17.30 | Boundary block particles |
/gamerule showCoordinates false
/gamerule showTags false
/gamerule showBorderEffect false
Crafting Rules
These settings 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 recipes previously discovered by the player. By default, any item can be created even without "unlocking" its recipe in the recipe 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 associated recipes. When disabled, the entire recipe book becomes immediately accessible without any prior discovery.
/gamerule recipesUnlock false
Administrator Rules
These technical settings mainly concern server management and system limits.
maxEntityCramming
| Feature | Information |
|---|---|
| Compatibility | Java only |
| Initial Setting | 24 |
| Appeared 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 consequences.
/gamerule maxEntityCramming 0
Command Ceilings
| 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 more massive operations at the risk of impacting performance.
/gamerule commandModificationBlockLimit 100000
commandBlocksEnabled
| Feature | Information |
|---|---|
| Compatibility | Bedrock only |
| Initial Setting | true |
| Appeared in | 1.7.0 |
When disabled, command blocks become completely inert. It is impossible to place, modify, or execute them.
/gamerule commandBlocksEnabled false
minecartMaxSpeed
| Feature | Information |
|---|---|
| Compatibility | Java only |
| Initial Setting | 8.0 |
| Appeared in | 1.8 |
Maximum speed limit for minecarts on rails. Increasing this value speeds up rail transportation, but excessive speeds can disrupt powered rail operations.
/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 "rubberbands" caused by latency, but also opens the door to flight and speed hacks.
/gamerule disableElytraMovementCheck true
Summary of Essential Gamerules
| Rule | Java | Bedrock | Standard | Main Use |
|---|---|---|---|---|
keepInventory | ✅ | ✅ | false | Keep items on death |
mobGriefing | ✅ | ✅ | true | Terrain protection |
doDaylightCycle | ✅ | ✅ | true | Time control |
doWeatherCycle | ✅ | ✅ | true | Weather control |
naturalRegeneration | ✅ | ✅ | true | Passive life regeneration |
doMobSpawning | ✅ | ✅ | true | Creature spawning |
doFireTick | ✅ | ✅ | true | Fire spread |
randomTickSpeed | ✅ | ✅ | 3/1 | Nature speed |
playersSleepingPercentage | ✅ | ✅ | 100 | Night passage |
doInsomnia | ✅ | ✅ | true | Phantom spawning |
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 experimentation world before deploying them on your main server. Each modification remains reversible at any time via the /gamerule command.
Happy customizing!