Guides / Commands & Data

The gamerules worth changing — and the defaults people get wrong

There are over 40 gamerules and most guides list them without saying which matter. Here are the ones that change how a world plays, with their real default values.

/gamerule has grown past forty entries. Most are debug switches nobody touches. A handful genuinely change how a world feels, and a few have defaults that surprise people.

The ones that change a world

GameruleDefaultWhy you would change it
keepInventoryfalseThe single most-changed rule on private servers
doDaylightCycletrueFreeze at noon for building
doWeatherCycletrueStop rain ruining a build session
mobGriefingtrueCreepers stop cratering your base; also stops villagers farming
doFireTicktrueFire stops spreading — set false before a nether build
randomTickSpeed3Crop growth speed. 0 freezes growth entirely
playersSleepingPercentage100Set to 1 so one player can skip the night
spawnRadius10Tighten the world-spawn scatter

Defaults people assume wrong

  • randomTickSpeed is 3, not 1. Cranking it to 1000 to speed up crops also

accelerates leaf decay, fire spread and ice melting, and will tank server TPS.

  • mobGriefing covers more than creepers. Turning it off also stops villagers

picking up and planting seeds, enderman block placement, and sheep eating grass. Iron farms and villager farms quietly break.

  • doInsomnia is on by default — that is what spawns phantoms. Turn it off rather

than fighting them.

  • doImmediateRespawn exists and is false; setting it true skips the death

screen entirely.

  • commandBlockOutput is true, which is why a redstone contraption spams admin

chat. Almost every server sets it false.

Integer versus boolean

Gamerules are typed, and the command silently rejects a wrong type rather than explaining. randomTickSpeed, spawnRadius, maxEntityCramming, playersSleepingPercentage and maxCommandChainLength take numbers; everything else is true/false.

/gamerule <rule> with no value reads the current setting instead of changing it — useful for checking what a downloaded map has already altered.

They are per-world, not per-server

Gamerules live in level.dat, so they travel with the world folder and do not apply to other worlds on the same server. A multiverse setup needs them set per world.

Pick any rule and get the command with the right type already applied in the Player Command Builder, which also covers teleport, gamemode, xp, time and weather from the same form.

Open the Player Command Builder →

More guides

Browse all →

Looking for more Minecraft tools?

A suite of client-side generators, viewers and converters — all free, all in your browser.