Minecraft Forums

Hey everybody,
as you all know, the last snapshot gave us the /gamerule-command. I thought about some more gamerules that could be changed with this command, so let's just start, right?

TOOLS

=> /showgamerule <gamerule> <values(like IDs, without the <true/false>)>
- shows you whether a gamerule is set to true or false.
= original idea by Pulse_Daemon, edited by me =

BLOCKS/ITEMS

=> /gamerule breakable <ID> <data> <true/false>
- toggle whether a certain block can be broken or not. By default set to "false" for all IDs. Does only apply to adventure mode, you can still break all blocks in survival and creative. Replace <ID> with "all" to set it for all IDs.

=> /gamerule placeable <ID> <data> <true/false>
- toggle whether a certain block can be placed or not. By default set to "false" for all IDs. Does only apply to adventure mode, you can still place all blocks in survival and creative. Replace <ID> with "all" to set it for all IDs.

=> /gamerule placeable <ID> <data> <true/false> on <ID1> <data1> - <ID2> <data2> - ... - <IDx> <datax>
- toggle whether a certain block can be placed on certain blocks only. By default set to "false" for all IDs. Does only apply to adventure mode, you can still place all blocks in survival and creative. Replace <ID> with "all" to set it for all IDs.
- when set to "true" several times in a row for the same ID, only the values for <ID1> <ID2> etc from the last command will be saved.
- when set to "false", the values for <ID1> <ID2> etc will be deleted.
= original idea by Samshotz, edited by me =

=> /gamerule craftable <ID> <data> <true/false>
- toggle whether a certain block/item can be crafted or not. By default set to "false" for all IDs. Does only apply to adventure mode, you can still craft everything in survival and creative. Replace <ID> with "all" to set it for all IDs.

PLAYERS/MOBS

=> /gamerule mobdamage <true/false>
- toggle whether mobs deal damage or not. By default set to "true".

=> /gamerule playerdamage <entity-ID> <true/false>
- toggle whether the player can deal damage to a certain entity (including other players, mobs, minecarts, boats, etc.) or not. By default set to "true" for all entity-IDs.
= original idea by Pulse_Daemon, edited by me =

OTHERS

=> /gamerule autodownfall <true/false>
- toggle whether the weather changes automatically or only when using the /toggledownfall-command. By default set to "true".

=> /gamerule timechange <true/false>
- toggle whether the time changes or not. By default set to "true".
= original idea by Pulse_Daemon, edited by me =

=> /gamerule randomspawn <true/false>
- set whether the randomspawn-function is on or off (the randomspawn-function makes you not spawn exactly at the spawnpoint, but in a certain area around it. Has been designed for multiplayer-servers to prevent ppl from spawning at the same spot, but it's a problem for many custom maps). By default set to "true".

That's all I have for now, I'll add more when i have ideas. Feel free to post your ideas in the comments and i may add them to the OP (with your name).

Peace,
5ting

I myself felt like making a tutorial world. I've been thinking about it a lot. Allowing (certain) blocks to be destroyed but not placed. However, I don't think game rules should be limited to adventure mode. If players were disallowed to break string or other redstone components, it could help to protect select regions. It would be nice if the rule could be set according to each player or to the whole world. Another nice but unlikely feature would be the possibility to apply the game rule to a select region. The player should be able to view what game rules are applied to him and to the entire server.

Edit
After further reflexion, I think that game rules on a player basis would not be practical and hard to manage. The ability to allow certain game rules in a specific area would be great! Another useful game rule would be a toggle allowing/disallowing the player to hurt mobs. Perhaps it's a race for survival or perhaps you don't want people killing villagers with custom trades.

Another useful game rule would be the ability to choose whether or not time progresses, effectively freezing time. I'm not sure if this suits the game rule idea or if it should be added to the existing time command in the following fashion: /time change <true/false>.

Hope you liked my feedback.

hey I just made a post about this, lol. Can I add those to my post? I'd give you the credit

@Kuppsy I just want to say that

5tingr4y thread has more gamerules than your thread and is slightly older. I don't mind your sunblock idea for mobs. Your block idea is also nice. How do you like my idea of applying gamerules to a certain zone and/or players?

Awesome this is very good, I would like this a lot, there should be an option for place on, so where things can be placed on.
=> /gamerule placeon <ID> <true/false> <data>
Don't you think?

Oh, I see! So let's say the player can place torches only on glass blocks. It wouldn't be bad but their should be a log that tracks all these gamerules. I'm not sure where though... Perhaps a command to list them all wouldn't hurt or maybe they would be visible when clicking F3 (not Shift+F3) or use another F# key.

Thanks for the feedback everyone

Quote from Samshotz

Awesome this is very good, I would like this a lot, there should be an option for place on, so where things can be placed on.
=> /gamerule placeon <ID> <true/false> <data>
Don't you think?

The idea is cool, but there is the problem that then blocks can only be placed on this type of block. What if you want certain blocks being able to be placed anywhere? That's something that should be considered, right?

What about something like

/gamerule placeable <ID> <data> <true/false> on <ID1> <data1> - <ID2> <data2> - ... - <IDx> <datax>

as an addition to the original placeable-gamerule?
When you do that command, the block with the ID <ID> can only be placed on blocks with the IDs <ID1> <ID2> etc.
When you set the gamerule back to false for the block <ID>, the blocks it can only be placed on (<ID1> <ID2> etc) will be deleted.
That'd work, I'll add that to the OP

Peace,
5ting

Quote from Pulse_Daemon

I myself felt like making a tutorial world. I've been thinking about it a lot. Allowing (certain) blocks to be destroyed but not placed. However, I don't think game rules should be limited to adventure mode. If players were disallowed to break string or other redstone components, it could help to protect select regions. It would be nice if the rule could be set according to each player or to the whole world. Another nice but unlikely feature would be the possibility to apply the game rule to a select region. The player should be able to view what game rules are applied to him and to the entire server.

Edit
After further reflexion, I think that game rules on a player basis would not be practical and hard to manage. The ability to allow certain game rules in a specific area would be great! Another useful game rule would be a toggle allowing/disallowing the player to hurt mobs. Perhaps it's a race for survival or perhaps you don't want people killing villagers with custom trades.

Another useful game rule would be the ability to choose whether or not time progresses, effectively freezing time. I'm not sure if this suits the game rule idea or if it should be added to the existing time command in the following fashion: /time change <true/false>.

Hope you liked my feedback.

Made a quote about what gamemodes the gamerules should apply to.
I think the thing with the area would be cool for a mod or plugin, but not for vanilla Minecraft as it would require a tool like WorldEdit to select the areas. Good idea anyway.
I also added the gamerules that you suggested, good work
thx for the feedback ^^

Peace,
5ting

Perhaps certain gamerules should have the ability to be applied across a server and/or per player. Mob spawning and time freezing wouldn't work but the others could be used in conjunction with the command block. I might elaborate later.

Game rules should be the main feature of adventure mode.

These new gamerules are awesome and very powerful, but I'd like to see a couple more to help with more detailed adventure maps.

/gamerule spawnmob [mobname] [chance]

Would control the chances for a particular mob to spawn, mobname being the entity, and chance being 0-100. This could be used to saturate certain maps with a particular mob type, or to stop certain mobs from spawning. This could be used for a Zombie Apocalypse style map, for instance.

/gamerule durability [true|false]

This would control whether or not items degrade in durability in the game. This could be used in 'RPG' style maps, where you might acquire an item at a certain place in the game, and it would be intended that you have it permanently.

This would be so useful for people creating adventure maps. +1

Quote from admacey

These new gamerules are awesome and very powerful, but I'd like to see a couple more to help with more detailed adventure maps.

/gamerule spawnmob [mobname] [chance]

Would control the chances for a particular mob to spawn, mobname being the entity, and chance being 0-100. This could be used to saturate certain maps with a particular mob type, or to stop certain mobs from spawning. This could be used for a Zombie Apocalypse style map, for instance.

/gamerule durability [true|false]

This would control whether or not items degrade in durability in the game. This could be used in 'RPG' style maps, where you might acquire an item at a certain place in the game, and it would be intended that you have it permanently.

Perhaps the mob spawning one could be integrated in the existing gamerule?

Quote from 5tingr4y

=> /gamerule placeable <ID> <data> <true/false> on <ID1> <data1> - <ID2> <data2> - ... - <IDx> <datax>
- toggle whether a certain block can be placed on certain blocks only. By default set to "false" for all IDs. Does only apply to adventure mode, you can still place all blocks in survival and creative. Replace <ID> with "all" to set it for all IDs.
- when set to "true" several times in a row for the same ID, only the values for <ID1> <ID2> etc from the last command will be saved.
- when set to "false", the values for <ID1> <ID2> etc will be deleted.

I do not feel that this gamerule is one that should be added. It seems kind of pointless (except for maybe adventure maps). I love all the others, though

Quote from Pulse_Daemon

I myself felt like making a tutorial world. I've been thinking about it a lot. Allowing (certain) blocks to be destroyed but not placed. However, I don't think game rules should be limited to adventure mode. If players were disallowed to break string or other redstone components, it could help to protect select regions. It would be nice if the rule could be set according to each player or to the whole world. Another nice but unlikely feature would be the possibility to apply the game rule to a select region. The player should be able to view what game rules are applied to him and to the entire server.

Edit
After further reflexion, I think that game rules on a player basis would not be practical and hard to manage. The ability to allow certain game rules in a specific area would be great! Another useful game rule would be a toggle allowing/disallowing the player to hurt mobs. Perhaps it's a race for survival or perhaps you don't want people killing villagers with custom trades.

Another useful game rule would be the ability to choose whether or not time progresses, effectively freezing time. I'm not sure if this suits the game rule idea or if it should be added to the existing time command in the following fashion: /time change <true/false>.

Hope you liked my feedback.

I like this I would really want there to be an "area" of land that you could brake, but not another "area"! Nice

Quote from 16cadrian

This would be so useful for people creating adventure maps. +1

Same thought

what are the current gamerules i need them for my sleepover so they die and keep their stuff

I think /gamerule doWeatherEffects would be nice. It would by default be on true, which would be the average weather, but if set to false, the weather would stay as it was when you set the gamerule to false. So, lets say, if you were an adventure map maker, you might want it to rain all the time. So you wouldn't need to keep a clock running to keep the weather how you want it.