Guide To Minecraft Gamerules: All Rules Explained

Accessing Gamerules

• 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.
• Bedrock Edition: Only a few options appear in the world settings. Most rules require the use of the in-game command.

Using the Command

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

randomTickSpeed

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. (Initial Setting: 3 on Java, 1 on Bedrock).

• 0: Total freeze of nature
• 3: Standard rate on Java
• 10: Accelerated growth
• 1000+: Near-instant evolution (risk of lag)

/gamerule randomTickSpeed 10

doDaylightCycle

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. (Initial Setting: true).

/gamerule doDaylightCycle false

doWeatherCycle

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. (Initial Setting: true).

/gamerule doWeatherCycle false

doFireTick

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. (Initial Setting: true).

/gamerule doFireTick false

doVinesSpread (Java Only)

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

/gamerule doVinesSpread false

Snow Accumulation and Liquid Sources (Java Only)

These three rules modify fundamental mechanics:

• snowAccumulationHeight: Maximum number of stackable snow layers (Initial: 1).
• waterSourceConversion: Ability to create infinite water sources (Initial: true).
• lavaSourceConversion: Ability to create infinite lava sources (Initial: false).

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 (Java Only)

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. (Initial Setting: true).

/gamerule globalSoundEvents false

Bedrock Exclusive Settings

• respawnBlocksExplode: Beds explode in the Nether/End (Initial: true).
• tntExplodes: TNT can explode (Initial: true).

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 (Java Only)

Determines the size of the perpetually active area around the global spawn point. With the default value, a 5x5 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. (Initial Setting: 2).

/gamerule spawnChunkRadius 4

spectatorsGenerateChunks (Java Only)

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. (Initial Setting: true).

/gamerule spectatorsGenerateChunks false

projectilesCanBreakBlocks (Java Only)

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. (Initial Setting: true).

/gamerule projectilesCanBreakBlocks false

mobGriefing

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

• 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

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

/gamerule doMobSpawning false

doInsomnia

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. (Initial Setting: true).

/gamerule doInsomnia false

Specific Spawns (Java Only)

Three distinct rules control specific spawns on Java Edition:

• doPatrolSpawning: Pillager patrols (Initial: true).
• doTraderSpawning: Wandering trader (Initial: true).
• doWardenSpawning: Warden (Initial: true).

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

disableRaids (Java Only)

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. (Initial Setting: false).

/gamerule disableRaids true

Neutral Mob Anger (Java Only)

Two interconnected rules modify the resentment of neutral creatures:

• universalAnger: Anger extended to all nearby players (Initial: false). Enabling this turns every provocation into a collective threat: hitting a wolf endangers all nearby players.
• forgiveDeadPlayers: Automatic forgiveness after the guilty player's death (Initial: true). Disabling this makes resentment permanent, even after your death.

/gamerule universalAnger true
/gamerule forgiveDeadPlayers false

keepInventory

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. (Initial Setting: false).

/gamerule keepInventory true

naturalRegeneration

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. (Initial Setting: true).

/gamerule naturalRegeneration false

Individual Damage Types

Four rules allow neutralizing specific sources of damage (all enabled by default):

• fallDamage: Falls
• fireDamage: Fire, lava, magma
• drowningDamage: Drowning
• freezeDamage: Frost (powdered snow)

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

doImmediateRespawn

Removes the death screen and instantly teleports the player to their spawn point. On Bedrock, this rule is named immediateRespawn. (Initial Setting: false).

/gamerule doImmediateRespawn true

showDeathMessages

Death announcements in chat disappear when disabled. This also includes notifications sent to owners of deceased pets. (Initial Setting: true).

/gamerule showDeathMessages false

spawnRadius

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 21x21 blocks. (Initial Setting: 10 on Java / 5 on Bedrock).

/gamerule spawnRadius 0

pvp (Bedrock Only)

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

/gamerule pvp false

Portal Delays (Java Only)

Two parameters adjust the waiting time in Nether portals:

• playersNetherPortalCreativeDelay: Creative players (Initial: 1 - almost instantaneous).
• playersNetherPortalDefaultDelay: Survival/adventure players (Initial: 80 - 4 seconds).

/gamerule playersNetherPortalDefaultDelay 40

playersSleepingPercentage

Proportion of connected players that must sleep simultaneously to speed up the night transition. (Initial Setting: 100).

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

/gamerule playersSleepingPercentage 25

doMobLoot

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. (Initial Setting: true).

/gamerule doMobLoot false

doTileDrops

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. (Initial Setting: true).

/gamerule doTileDrops false

doEntityDrops

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

/gamerule doEntityDrops false

Explosion Drop Decay (Java Only)

Three distinct rules control the recovery of blocks destroyed by different explosions:

• tntExplosionDropDecay: TNT (Initial: false).
• mobExplosionDropDecay: Creatures like Creepers or Withers (Initial: true).
• blockExplosionDropDecay: Others like beds or crystals (Initial: true).

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

sendCommandFeedback

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. (Initial Setting: true).

/gamerule sendCommandFeedback false

commandBlockOutput

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

/gamerule commandBlockOutput false

announceAdvancements (Java Only)

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. (Initial Setting: true).

/gamerule announceAdvancements false

logAdminCommands (Java Only)

Records each admin command in the server log files. Disabling this rule lightens the logs but removes all traceability of admin actions. (Initial Setting: true).

/gamerule logAdminCommands false

reducedDebugInfo (Java Only)

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

• 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. (Initial Setting: false).

/gamerule reducedDebugInfo true

Bedrock Display Options

• showCoordinates: Visible XYZ position on screen (Initial: true).
• showTags: "Can place/destroy" indicators on items (Initial: true).
• showBorderEffect: Particles from border blocks (Initial: true).

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

doLimitedCrafting

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. (Initial Setting: false).

/gamerule doLimitedCrafting true

recipesUnlock (Bedrock Only)

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

/gamerule recipesUnlock false

maxEntityCramming (Java Only)

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. (Initial Setting: 24).

/gamerule maxEntityCramming 0

Command Limits

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

• maxCommandChainLength: Chained commands per tick (Initial: 65536).
• maxCommandForkCount: Command branches per tick (Java Initial: 65536).
• commandModificationBlockLimit: Blocks modifiable by /fill or /clone (Java Initial: 32768).
• functionCommandLimit: Instructions per function file (Bedrock Initial: 10000).

/gamerule commandModificationBlockLimit 100000

commandBlocksEnabled (Bedrock Only)

When disabled, command blocks become completely inert. Impossible to place, modify, or execute. (Initial Setting: true).

/gamerule commandBlocksEnabled false

minecartMaxSpeed (Java Only)

Velocity ceiling for minecarts on rails. Increasing this value speeds up rail transport, but excessive speeds can disrupt the functioning of powered rails. (Initial Setting: 8.0).

/gamerule minecartMaxSpeed 16.0

Anti-cheat Checks (Java Only)

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.

• disableElytraMovementCheck: Elytra movements (Initial: false).
• disablePlayerMovementCheck: All movements (Initial: false).

/gamerule disableElytraMovementCheck true

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.