Gamerules appear to be stored in the level.dat file for the world, so they are persistent. Once set, they stay until manually changed. They don't need to be set every time you load the world.
All you can do is turn them on and off, like /gamerule doFireTick false turns fire spread off. They are case-sensitive. doMobLoot disable makes nothing drop items, the monsters and animals just drop xp. doMobSpawning turns off mob spawning, i don't know what doTileDrops do. keepInventory decides if you keep your inventory when you die. mobGriefing turns off creeper block damage and endermen block pickup.
Very interesting indeed. So I could make a map out of wool and TNT, add a pool of lava, and stop fire from spreading until someone solves the final puzzle?
I could....
doFireTick = Turn fire spread on and off.
doMobLoot = Keep mobs from dropping loot and potentially making my adventure map easier.
doMobSpawning = Keep new mobs from spawning except where I want them to.
doTileDrops = No more looting chests by breaking them!
keepInventory = ...I have no idea. o_O
mobGriefing = No creeper craters or enderman blocks! I'll bet it stops zombies from breaking doors, too.
the "keepInventory" lets you keep your inventory apon death, instead of dropping it. I like to use that one on adventure maps.
I was going to get a server to use "Anticreeper" plugin which is basically like the MobGriefing command, except for the enderman part. Now that I know there is an option for no creeper damage In single player can save my money for something else.
doTileDrops = false
This prevents blocks from dropping anything. For example, you can dig all the dirt you want to make a trench, or pickaxe your way through rock to make mine shafts without it dirt or cobblestone piling up in your inventory causing you to have hundreds of useless blocks of dirt or cobblestone. When you want to start getting stuff for your effort (like when you want to start getting iron, cobblestone, etc from your mining operations) then you use set doTileDrops = true. Setting it to false is also great if you want to experiment with commands that make megaton size explosions like:
/summon Fireball ~ ~ ~ {ExplosionPower:1000,direction:[0.0,0.0,0.0]}
The above summon command creates a Ghast Fireball with enough explosive power to destroy a block of obsidian many times over! (note that Blast Resistance is not the same value as ExplosionPower, and that the 6000 Blast Resistance of obsidian is rougly equivalent to ExplosionPower of 278)To unleash the fireball you've spawned just step back from where you were when it spawned (or else it will blow up on you when launched) and then punch it to launch it.
When it hits a block, KAAAAAAAABOOOOOOOOOMMMM! This explosion normally will nearly crash the game as hundreds (if not thousands) of blocks convert to items. All of a sudden your computer's RAM is flooded with data about dropped items. Unless you have a custom gaming computer with maxed-out specs, and depending on the complexity of the terain where the explosion happened, your RAM will likely quickly be used up, and as MC tries to load into RAM still more data into non-existant RAM, the game will solidly freeze, requiring you to kill the execution of your Java JRE's exe file (javaw.exe) from the Windows Task Manager under the Processes tab.doMobLoot is the same as doTileDrops, except that instead of stopping drops from destroyed blocks, it stops drops from killed mobs.
doFireTick from my understanding will cause a fire to burn indefinitely if it is disabled. There is an internal clock associated with each "fire" block. When that clock is disabled, it does not tick down to zero as the fire burns, so the flame lasts indefinitely. It may also disable the fire spread counter. As a flame ignites a flamable substance, the newly spawned flame has a lower fire spread counter value than the flame that caused the ignition of the flamable substance. As a result fire can spread only by a certain ammount before the fire becomes incapable of igniting flamable substances, so that wildfires in MC (unlike in real life) will be limited in how far they can spread. I'm not sure but disabling doFireTick may also disable the fire spread counter, so that you can wipe out an entire forrest biome by igniting one tree with a Flint and Steel.
If any of my above statements are wrong, please provide me with a correction. I'm just going by what it seems these gamerule switches do when I've used them.
Has anyone run into an issue with /gamerule doFireTick where if it's false, chickens don't lay eggs? i have this going on in my game. It's just weird. If I set it back to true my chickens immediately start popping out eggs normally. It also seems to interfere with the Chickenshed mod so when false chicken won't shed extra feathers. I have no idea why this command would affect chickens.
Personally I always have MobGriefing = False and KeepInventory = True because I hate my terrain being destroyed by creepers and Minecraft can lag spike pretty hard and I can be snuck up on by Creepers so screw that.
Defaults to 3 (Only game rule that isn't true and false) And when increased, all crops and other things that grow at random speed, will start growing faster for every level. When decrease, they will grow slower, and when 0, they won't grow at all. Very useful sometimes.
Rollback Post to RevisionRollBack
So.. How do I sign my device?
Havent played this game in 1 year... so much new stuff...
For crying out loud, look at the wiki:
http://www.minecraft...i/Command_block
commandBlockOutput- Enables/disables text output of command block commands to console (chat).
by c0yote
I tried it with terrible results. I gave my wife my glasses for a second, a creeper showed up and now my wife is pregnant.
Stupid 3D..
the "keepInventory" lets you keep your inventory apon death, instead of dropping it. I like to use that one on adventure maps.
/gamerule doMobSpawning false --> Will stop spawning squids?
This prevents blocks from dropping anything. For example, you can dig all the dirt you want to make a trench, or pickaxe your way through rock to make mine shafts without it dirt or cobblestone piling up in your inventory causing you to have hundreds of useless blocks of dirt or cobblestone. When you want to start getting stuff for your effort (like when you want to start getting iron, cobblestone, etc from your mining operations) then you use set doTileDrops = true. Setting it to false is also great if you want to experiment with commands that make megaton size explosions like:
/summon Fireball ~ ~ ~ {ExplosionPower:1000,direction:[0.0,0.0,0.0]}
The above summon command creates a Ghast Fireball with enough explosive power to destroy a block of obsidian many times over! (note that Blast Resistance is not the same value as ExplosionPower, and that the 6000 Blast Resistance of obsidian is rougly equivalent to ExplosionPower of 278)To unleash the fireball you've spawned just step back from where you were when it spawned (or else it will blow up on you when launched) and then punch it to launch it.
When it hits a block, KAAAAAAAABOOOOOOOOOMMMM! This explosion normally will nearly crash the game as hundreds (if not thousands) of blocks convert to items. All of a sudden your computer's RAM is flooded with data about dropped items. Unless you have a custom gaming computer with maxed-out specs, and depending on the complexity of the terain where the explosion happened, your RAM will likely quickly be used up, and as MC tries to load into RAM still more data into non-existant RAM, the game will solidly freeze, requiring you to kill the execution of your Java JRE's exe file (javaw.exe) from the Windows Task Manager under the Processes tab.doMobLoot is the same as doTileDrops, except that instead of stopping drops from destroyed blocks, it stops drops from killed mobs.
doFireTick from my understanding will cause a fire to burn indefinitely if it is disabled. There is an internal clock associated with each "fire" block. When that clock is disabled, it does not tick down to zero as the fire burns, so the flame lasts indefinitely. It may also disable the fire spread counter. As a flame ignites a flamable substance, the newly spawned flame has a lower fire spread counter value than the flame that caused the ignition of the flamable substance. As a result fire can spread only by a certain ammount before the fire becomes incapable of igniting flamable substances, so that wildfires in MC (unlike in real life) will be limited in how far they can spread. I'm not sure but disabling doFireTick may also disable the fire spread counter, so that you can wipe out an entire forrest biome by igniting one tree with a Flint and Steel.
If any of my above statements are wrong, please provide me with a correction. I'm just going by what it seems these gamerule switches do when I've used them.
Formerly known as ORabbit around these parts.
keep inventory makes your inventory stay when you die
So what about random tick speed?
Defaults to 3 (Only game rule that isn't true and false) And when increased, all crops and other things that grow at random speed, will start growing faster for every level. When decrease, they will grow slower, and when 0, they won't grow at all. Very useful sometimes.
So.. How do I sign my device?
Havent played this game in 1 year... so much new stuff...
Note: in 1.10, doFireTick doesn't seem to work. I set it to false which is supposed to stop it from spreading....and it'll still spread.