This idea adds some gamerules that could be used to make better maps, or even adding the option to change your survival experience.
maxStack:this would probably need some major code changes and probably not worth adding, but this would be used to change the max stack size from 64 to any other value. Usage: /gamerule maxStack <value>; Default:64
maxStackProjectiles: similar to the previous one, but this one changes the max stack number of projectiles like snowballs, ender pearls etc. because they have different value of 16. Usage: /gamerule maxStackProjectiles <value>; Default:16
maxStackItem: this one has the priority over the previous two, because it targets one item type, not all of them. Usage: /gamerule maxStackItem <item> <value> (Credits to flaminghawk83)
furnaceTime: Furnace cooking time, in seconds. Usage: /gamerule furnaceTime <value>; Default:10
useHunger: This determines whether the hunger is active or not. Usage: /gamerule useHunger true/false; Default:true
dayDuration: This one is a bit more complicated. It determines the duration of the day (the whole day, not only the bright period) in ticks. Usage: /gamerule dayDuration <value>; Default:24000
dayNightRatio: This one determines the day (the bright part)/night ratio. Usage: /gamerule dayNightRatio <value>; Default:≈1.352
breedAnimals: This one determines whether animal breeding is possible or not. Usage: /gamerule breedAnimals true/false; Default:true
playerHealth: This gamerule would probably need some code changes in order to work properly, but it can set default player health. Usage: /gamerule playerHealth <value>; Default:20
enableHardcore: Hardcore mode would not be a world-fixed thing anymore. It would be a gamerule. This would be good for mapmakers who want, for example, to enable Hardcore after the player triggers something or achieves some goal. Usage: /gamerule enableHardcore true/false; Default: 0 if the world hasn't been chosen to be Hardcore, 1 if it was.
placementRange: This gamerule determines the player placement/mining range in blocks. Usage: /gamerule placementRange <value>; Default: not sure, probably about 4-5...
commandBlockSurvival: Determines whether the players in Survival are able to edit command blocks' commands. Usage: /gamerule commandBlockSurvival true/false; Default:false
inventorySize: Probably requires major code rewrites but here it is. It can determine the player inventory size. VERY useful for maps. Usage: /gamerule inventorySize <value>,<value>. The first value is width, the second one is height. Default:9,3
hotbarSize: Basically the same, but it determines the Hotbar size. Minimal value is 1, maximal is 10 (the 10th slot would be "bound" to 0 (zero) key.) Usage: /gamerule hotbarSize <value>; Default:9
enableSleeping: Determines whether you are able to sleep or not. Usage: /gamerule enableSleeping true/false; Default:true
enableCrafting: If false, you are not able to use the crafting table. Usage: /gamerule enableCrafting true/false; Default:true
enableInventoryCrafting: If false, the 2*2 inventory crafting is not shown. Usage: /gamerule enableInventoryCrafting true/false; Default:true
zombieCuring: Determines whether you are able to cure Zombie villagers. Usage: /gamerule zombieCuring true/false; Default:true
showBossBar: If false, the boss bars don't show when fighting Ender Dragon/Wither. Usage: /gamerule showBossBar true/false; Default:true
enableDrowning: Determines whether the player loses air when under the water. Usage: /gamerule enableDrowning true/false; Default:true
fallDamage: Fall damage multiplier. Usage: /gamerule fallDamage <value>; Default:1
This idea adds some gamerules that could be used to make better maps, or even adding the option to change your survival experience.
I'd recommend staying to default font. This may set you apart, but it can get a little annoying to read, and a lot of people don't like it.
maxStack:this would probably need some major code changes and probably not worth adding, but this would be used to change the max stack size from 64 to any other value. Usage: /gamerule maxStack <value>; Default:64
Read below comment.
maxStackProjectiles: similar to the previous one, but this one changes the max stack number of projectiles like snowballs, ender pearls etc. because they have different value of 16. Usage: /gamerule maxStackProjectiles <value>; Default:16
In stead of having two different commands, why not have
/gamerule maxStack <item> <value>
That way, you can make every item different. Then if you just leave the item tag blank, it would apply to everything.
furnaceTime: Furnace cooking time, in seconds. Usage: /gamerule furnaceTime <value>; Default:10
Again, put an item tag in there so you can make it different for different things, and leave it blank for everything.
useHunger: This determines whether the hunger is active or not. Usage: /gamerule useHunger true/false; Default:true
I have a feeling this is available, though I could just be thinking of peaceful. If it isn't already in, I support.
dayDuration: This one is a bit more complicated. It determines the duration of the day (the whole day, not only the bright period) in ticks. Usage: /gamerule dayDuration <value>; Default:24000
I can see this being very helpful for adventure maps.
dayNightRatio: This one determines the day (the bright part)/night ratio. Usage: /gamerule dayNightRatio <value>; Default:≈1.21
You might want to explain this a little more. Not entirely sure how this works.
breedAnimals: This one determines whether animal breeding is possible or not. Usage: /gamerule breedAnimals true/false; Default:true
This is cool, but I'd just leave it as
/gamerule mobBreeding true/false
So it fits better with the other mob commands.
playerHealth: This gamerule would probably need some code changes in order to work properly, but it can set default player health. Usage: /gamerule playerHealth <value>; Default:20
Using some confusing commands that I don't know how they work, this is possible. I think this would be a cool command, but it would probably be hard to code.
enableHardcore: Hardcore mode would not be a world-fixed thing anymore. It would be a gamerule. This would be good for mapmakers who want, for example, to enable Hardcore after the player triggers something or achieves some goal. Usage: /gamerule enableHardcore true/false; Default: 0 if the world hasn't been chosen to be Hardcore, 1 if it was.
I kind of like it, but I think hardcore would be better as a game mode. Maybe this would make it like hardcore, but commands can still be used, and stuff like that. I don't think it should replace the game mode.
placementRange: This gamerule determines the player placement/mining range in blocks. Usage: /gamerule placementRange <value>; Default: not sure, probably about 4-5...
There's a mod that allows you to do this. I like it.
commandBlockSurvival: Determines whether the players in Survival are able to edit command blocks' commands. Usage: /gamerule commandBlockSurvival true/false; Default:false
I guess. I don't really see a point, though.
inventorySize: Probably requires major code rewrites but here it is. It can determine the player inventory size. VERY useful for maps. Usage: /gamerule inventorySize <value>,<value>. The first value is width, the second one is height. Default:9,3
Very cool, but like you said, would most likely take some major coding. It would be cool to have, but may not be worth it.
hotbarSize: Basically the same, but it determines the Hotbar size. Minimal value is 1, maximal is 10 (the 10th slot would be "bound" to 0 (zero) key.) Usage: /gamerule hotbarSize <value>; Default:9
This would be cool, but again, probably would be hard to code.
I have had some other ideas, but I forgot them so I will add more gamerules when I remember.
Comments in bold.
Basically, most of them would be cool and very helpful for map makers, but would require a lot of coding and recoding, and I'm not sure it would be worth it. Also, just FYI, I'd change the font.
Basically, most of them would be cool and very helpful for map makers, but would require a lot of coding and recoding, and I'm not sure it would be worth it. Also, just FYI, I'd change the font.
If it's possible, support.
Thanks for the support. You wanted to explain the day/night ratio. Dawn+The brightest period count as the day. Dusk+The darkest period count as night.
The values for the default day/night cycle that already exist in Minecraft are:
Dawn=1.5 minutes
Brightest period=10 minutes
Dusk=1.5 minutes
Darkest period=7 minutes
meaning:
Day:11.5 minutes
Night:8.5 minutes
11.5/8.5=1.352 (I was wrong with my calculation in OP, I will correct that). 1.352 is the default Day/Night ratio. What I wanted is to make it possible to change that ratio to any value. If, for example, the ratio was set to 2, the day would last 13.33333 minutes, and the night would be 6.6666 minutes. I hope that is clear.
Almost forgot. About your idea for maxstack, to make it individual for each item: I would keep both of them. Because, if the mapmaker wants every item to be stackable up to, say, 100, he would use my original gamerule. But, if he wants stone to be stackable up to 1000, he will use your command. Your and my command could be stackable because yours would have priority, if specified.
I know they are capped, but as I said, it would probably require coding. That is exactly what I meant when I said that.
Ah, sorry. I thought that you meant the "major code changes" would be for allowing dynamic stack sizes, not overcoming the hard-coded stack size limit.
Very useful for mapmakers. Some would be awesome if it's going to be in Herobrine 3 (upcoming map by Hypixel; IDK if he discontinued it).
Rollback Post to RevisionRollBack
If I helped you in any way or agree in my ideas or posts, make sure you click that green arrow pointing up below my post or simply huggle me! I use 1.7.10 (Modded), so when I comment that I like a 1.8 mod, I will comment to downgrade to 1.7.10. I support no pics, no clicks. Suggestions that I think that are the best deserves a banner!
It is almost time to say goodbye to 1.7.10 because of the recent surge of big 1.9 mods.
Why MCreator sucks: jcm2606's file (doesn't open a new tab) He allows/welcomes anyone to link the file, so I put it here in my signature for people to know how MCreator functions. I thank jcm2606 (he's awesome) for creating the document/file and I'm just here to spread the word.
I've got a good one for multiplayer maps and servers. enablePVP can disable or enable PVP when false or true, correspondingly. This would help in multiplayer maps because if you and your friend are going to be in close quarters you don't want to accidentally hit each other. This gamerule will keep you and them from taking damage from eachother.
This idea adds some gamerules that could be used to make better maps, or even adding the option to change your survival experience.
maxStack:this would probably need some major code changes and probably not worth adding, but this would be used to change the max stack size from 64 to any other value. Usage: /gamerule maxStack <value>; Default:64
maxStackProjectiles: similar to the previous one, but this one changes the max stack number of projectiles like snowballs, ender pearls etc. because they have different value of 16. Usage: /gamerule maxStackProjectiles <value>; Default:16
maxStackItem: this one has the priority over the previous two, because it targets one item type, not all of them. Usage: /gamerule maxStackItem <item> <value> (Credits to flaminghawk83)
furnaceTime: Furnace cooking time, in seconds. Usage: /gamerule furnaceTime <value>; Default:10
useHunger: This determines whether the hunger is active or not. Usage: /gamerule useHunger true/false; Default:true
dayDuration: This one is a bit more complicated. It determines the duration of the day (the whole day, not only the bright period) in ticks. Usage: /gamerule dayDuration <value>; Default:24000
dayNightRatio: This one determines the day (the bright part)/night ratio. Usage: /gamerule dayNightRatio <value>; Default:≈1.352
breedAnimals: This one determines whether animal breeding is possible or not. Usage: /gamerule breedAnimals true/false; Default:true
playerHealth: This gamerule would probably need some code changes in order to work properly, but it can set default player health. Usage: /gamerule playerHealth <value>; Default:20
enableHardcore: Hardcore mode would not be a world-fixed thing anymore. It would be a gamerule. This would be good for mapmakers who want, for example, to enable Hardcore after the player triggers something or achieves some goal. Usage: /gamerule enableHardcore true/false; Default: 0 if the world hasn't been chosen to be Hardcore, 1 if it was.
placementRange: This gamerule determines the player placement/mining range in blocks. Usage: /gamerule placementRange <value>; Default: not sure, probably about 4-5...
commandBlockSurvival: Determines whether the players in Survival are able to edit command blocks' commands. Usage: /gamerule commandBlockSurvival true/false; Default:false
inventorySize: Probably requires major code rewrites but here it is. It can determine the player inventory size. VERY useful for maps. Usage: /gamerule inventorySize <value>,<value>. The first value is width, the second one is height. Default:9,3
hotbarSize: Basically the same, but it determines the Hotbar size. Minimal value is 1, maximal is 10 (the 10th slot would be "bound" to 0 (zero) key.) Usage: /gamerule hotbarSize <value>; Default:9
enableSleeping: Determines whether you are able to sleep or not. Usage: /gamerule enableSleeping true/false; Default:true
enableCrafting: If false, you are not able to use the crafting table. Usage: /gamerule enableCrafting true/false; Default:true
enableInventoryCrafting: If false, the 2*2 inventory crafting is not shown. Usage: /gamerule enableInventoryCrafting true/false; Default:true
zombieCuring: Determines whether you are able to cure Zombie villagers. Usage: /gamerule zombieCuring true/false; Default:true
showBossBar: If false, the boss bars don't show when fighting Ender Dragon/Wither. Usage: /gamerule showBossBar true/false; Default:true
enableDrowning: Determines whether the player loses air when under the water. Usage: /gamerule enableDrowning true/false; Default:true
fallDamage: Fall damage multiplier. Usage: /gamerule fallDamage <value>; Default:1
enableDualWielding: Enable/disable 1.9 dual wielding. Usage: /gamerule enableDualWielding true/false; Default:true
enableMobDespawn: Determines whether the mobs despawn. Usage: /gamerule enableMobDespawn true/false; Default:true
tntGriefing: self-explaining. Usage: /gamerule tntGriefing true/false; Default:true
doPhysics: if false, sand and gravel won't fall, fluids won't spread etc. Usage: /gamerule doPhysics true/false; Default:true
I have had some other ideas, but I forgot them so I will add more gamerules when I remember.
Comments in bold.
Basically, most of them would be cool and very helpful for map makers, but would require a lot of coding and recoding, and I'm not sure it would be worth it. Also, just FYI, I'd change the font.
If it's possible, support.
Please read these two threads:
http://www.minecraftforum.net/forums/minecraft-discussion/suggestions/2572194-please-read-this-before-making-a-suggestion-v2-0
http://www.minecraftforum.net/forums/minecraft-discussion/suggestions/44180-for-the-critics-ftc
Thanks for the support. You wanted to explain the day/night ratio. Dawn+The brightest period count as the day. Dusk+The darkest period count as night.
The values for the default day/night cycle that already exist in Minecraft are:
Dawn=1.5 minutes
Brightest period=10 minutes
Dusk=1.5 minutes
Darkest period=7 minutes
meaning:
Day:11.5 minutes
Night:8.5 minutes
11.5/8.5=1.352 (I was wrong with my calculation in OP, I will correct that). 1.352 is the default Day/Night ratio. What I wanted is to make it possible to change that ratio to any value. If, for example, the ratio was set to 2, the day would last 13.33333 minutes, and the night would be 6.6666 minutes. I hope that is clear.
Almost forgot. About your idea for maxstack, to make it individual for each item: I would keep both of them. Because, if the mapmaker wants every item to be stackable up to, say, 100, he would use my original gamerule. But, if he wants stone to be stackable up to 1000, he will use your command. Your and my command could be stackable because yours would have priority, if specified.
I can see how this would be useful for map makers.
Support
Thanks for the support!
As far as I know, stack sizes are hard-capped at 255, so stack sizes above that would be impossible.
Inb4 Mastercaver demolishes my post with 30 million facts about why I'm wrong and should feel bad for spreading lies.
I know they are capped, but as I said, it would probably require coding. That is exactly what I meant when I said that.
Seems useful, and I can see some of these being used to make survival challenges.
SUPPORT
Ah, sorry. I thought that you meant the "major code changes" would be for allowing dynamic stack sizes, not overcoming the hard-coded stack size limit.
Please don't hurt me.
I have added a gamerule
Added 8 new gamerules that I have just remembered.
From the looks of it this would be pretty hard to code.
But these gamerules are basically christmas presents to map makers.
Support!
Thanks for the support.
Fish fruit like.
support
My signature is broken. I am currently fixing it
You can support my suggestions at:
Kiwi birds: -The link broke-
Every biome gets at least 1 mob: -The link broke-
Pirates: -The link broke-
Chorus apes: -The link broke
Thanks for the support!
Very useful for mapmakers. Some would be awesome if it's going to be in Herobrine 3 (upcoming map by Hypixel; IDK if he discontinued it).
If I helped you in any way or agree in my ideas or posts, make sure you click that green arrow pointing up below my post or simply huggle me! I use 1.7.10 (Modded), so when I comment that I like a 1.8 mod, I will comment to downgrade to 1.7.10. I support no pics, no clicks. Suggestions that I think that are the best deserves a banner!
It is almost time to say goodbye to 1.7.10 because of the recent surge of big 1.9 mods.
Why MCreator sucks: jcm2606's file (doesn't open a new tab) He allows/welcomes anyone to link the file, so I put it here in my signature for people to know how MCreator functions. I thank jcm2606 (he's awesome) for creating the document/file and I'm just here to spread the word.
500+ huggles? U wot, m8?
Support
Support
This looks good! I'd want these!!
hunter x hunter = yas
I've got a good one for multiplayer maps and servers. enablePVP can disable or enable PVP when false or true, correspondingly. This would help in multiplayer maps because if you and your friend are going to be in close quarters you don't want to accidentally hit each other. This gamerule will keep you and them from taking damage from eachother.
Oh, and Support