MC-2911Gamerule commands allow parameters other than true/false
When issuing a gamerule command, for example:
/gamerule doFireTick on, the game will accept that "on" parameter without throwing any errors.
This can result into major confusion, since the game will parse anything other than "true" as false.
Expected
- Throw an error for an incorrect paramter
What happens
- The game accepts the faulty parameter, yet considers it as false
To reproduce
1. Change a gamerule to anything other than "true/false"
2. Check the gamerule, it will say the exact parameter that was entered
3. Notice that it will be considered as false
Environment
N/A
Created Issue:
Gamerule commands allow parameters other than true/false
When issuing a gamerule command, for example:
/gamerule doFireTick on, the game will accept that "on" parameter without throwing any errors.This can result into major confusion, since the game will parse anything other than "true" as false.
Expected
- Throw an error for an incorrect paramter
What happens
- The game accepts the faulty parameter, yet considers it as false
To reproduce
1. Change a gamerule to anything other than "true/false"
2. Check the gamerule, it will say the exact parameter that was entered
3. Notice that it will be considered as falseEnvironment
N/A
discovered while testing
is duplicated by
is duplicated by
is duplicated by
/gamerule randomTickSpeed voluntarily accepts values, so I think that's intended
![[Mod] CubeTheThird](../../../data/assets/gravatar/cubethethird.jpeg){kind=small}
![[Mojang] Searge (Michael Stoyke)](../../../data/assets/gravatar/searge.png){kind=small}
[Mojang] Searge (Michael Stoyke)A comment with security level 'global-moderators' was removed.
is duplicated by
um there is a bug in both 14w30a-b and 14w31a
there seems to be an issue with the render distance!
It seems like if you don't have you vbos on theres glitch or bug with in over 10 render distance where you can't see nothing but randomly spining chunks!
its one of the most wildest bugs I've seen so far but it doesn't seem to crash MC!
Hope you figure whats up with that by the next snapshot!
I don't know if its a problem for everyone but it sure is for me!
@{~tomorrows world]: What has your comment to do with this ticket "Gamerule commands allow parameters other than true/false" ?
Duplicate of MC-2911 - If you have not, please use the search function in the future, to see if your bug has already been submitted. If you could not find the original report, please comment with the keywords you searched for.
I've not checked in a while, I think it was 14w30c, but may've been 14w29b or whatever it was called but you can type things like /gamerule lol <true|false> and you could type /gamerule TAB and it would be in the list. The command also didn't fail. Just so no one gets confused, this is not the same as MC-2911, it says the last part is custom. (/gamerule <gamerule> anything) I am saying /gamerule <anything> <true|false> This is new, and MC-2911 has been in the game.
See issue
MC-2887for an example of confusion that this issue causes.also affects pre 1.5 it only accepts the word "TRUE" lower or uppercase mix up doesn't matter, but the only way to turn it on
the word 'on' is wrongis the word "true" any other value it will be accepted and be turned falseoffbut will show the value introduced, works on single and multi player.tried on a flat world, changing to any difficulty, and died on purpose several times wither fall damage or killed by zombies.
way to reproduce and easy to be misleaded into
-->this part i thought i could write 'on' due to the game telling me it was 'off'
-->didn't knew the value is still off, seems 'on' and 'off' are just display info not a real value
worked on win7, lastest java and preMc release at the time of the post, i found out in multiplayer while deep underground killed by cavespiders x.x R.I.P. our loot
The gamerules are parsed with parseBoolean, the only recognized keyword is "true" (in any case):
Is this still a concern in the current Minecraft version 1.6.4 / Launcher version 1.2.5 ? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
Also note that /gamerule doTileDrops 0 works (0 = false) while /gamerule doTileDrops 1 doesn't do anything.
Anything except true is false, thus /gamerule doTileDrops IDoNotWantMyTilesToDrop will work too...
NOT intended. This is about parameters, not value.
Confirmed for 14w18b.
Confirmed for 14w28b
Nice, but when creating a gamerule/scoreboard objective I always put the first word lowercase and the rest capital for example /gamerule spongesAreAmazing true. BTW related to
MC-65113.Hey, I liked that "feature" and it's now fixed...
/gamerule mobGriefing nope