MCPE-26659/gamerule will crash the game if the first argument contains uppercase letters
The bug
When the player tries to use the /gamerule command where the first argument contains any uppercase letters, the game will crash.
How to reproduce
- Start a new world with cheats/commands enabled
- Run the command /gamerule doDaylightCycle [true/false] (Note that this will work with any /gamerule command, as long as the first argument contains uppercase letters. It does not specifically need to be doDaylightCycle.)
Attachments1
![[Mod] bemoty](../../../data/avatars/users/50554.png){kind=small}
Created Issue:
Running /alwaysday followed by /gamerule doDaylightCycle false results in a crash
Steps to reproduce:
1. Start a new world with cheats/commands enabled
2. Run the command /alwaysday
3. Run the command /gamerule doDaylightCycle false
- Unresolved
- Open
- Unconfirmed
- Windows
- Windows 10 Pro
- 1.2.0.81
Steps to reproduce:
1. Start a new world with cheats/commands enabled
2. Run the command /alwaysday
3. Run the command /gamerule doDaylightCycle falseThe bug
When the player tries to enable "Always Day" and "Do Daylight Cycle" in the options menu, the one enabled before becomes disabled to prevent the game from crashing. However, those values can still be changed via commands, which apparently don't check if the other is enabled.
How to reproduce
- Start a new world with cheats/commands enabled
- Run the command /alwaysday
- Run the command /gamerule doDaylightCycle true
Running /alwaysday followed by /gamerule doDaylightCyclefalse results in a crashRunning /alwaysday followed by /gamerule doDaylightCycle true results in a crash
The bug
When the player tries to enable "Always Day" and "Do Daylight Cycle" in the options menu, the one enabled before becomes disabled to prevent the game from crashing. However, those values can still be changed via commands, which apparently don't check if the other is enabled.
How to reproduce
- Start a new world with cheats/commands enabled
- Run the command /alwaysday
- Run the command /gamerule doDaylightCycle true
The bug
When the player tries to enable "Always Day" and "Do Daylight Cycle" in the options menu, the one enabled before becomes disabled to prevent the game from crashing. However, those values can still be changed via commands, which apparently don't check if the other is enabled.
How to reproduce
- Start a new world with cheats/commands enabled
- Run the command /alwaysday
- Run the command /gamerule doDaylightCycle true
Helper EditIt's not yet 100% clear how this bug can always be reproduced. With the current guide, it sometimes works, sometimes it does not; sometimes worlds work, sometimes they do not. If anyone finds out a way to reproduce this bug every time, please add it to this report by writing a comment, thanks!
Both /gamerule doDaylightCycle true and /gamerule doDaylightCycle false are confirmed to be able to trigger this crash.
The bug
When the player tries to enable "Always Day" and "Do Daylight Cycle" in the options menu, the one enabled before becomes disabled to prevent the game from crashing. However, those values can still be changed via commands, which apparently don't check if the other is enabled.
How to reproduce
- Start a new world with cheats/commands enabled
- Run the command /alwaysday
- Run the command /gamerule doDaylightCycle true
Helper EditIt's not
yet100% clear how this bug can always be reproduced. With the current guide, it sometimes works, sometimes it does not; sometimes worlds work, sometimes they do not. If anyone finds out a way to reproduce this bug every time, please add it to this report by writing a comment, thanks!Both /gamerule doDaylightCycle true and /gamerule doDaylightCycle false are confirmed to be able to trigger this crash.
The bug
When the player tries to enable "Always Day" and "Do Daylight Cycle" in the options menu, the one enabled before becomes disabled to prevent the game from crashing. However, those values can still be changed via commands, which apparently don't check if the other is enabled.
How to reproduce
- Start a new world with cheats/commands enabled
- Run the command /alwaysday
- Run the command /gamerule doDaylightCycle true
Helper EditIt's not 100% clear how this bug can always be reproduced yet. With the current guide, it sometimes works, sometimes it does not; sometimes worlds work, sometimes they do not. If anyone finds out a way to reproduce this bug every time, please add it to this report by writing a comment, thanks!
Both /gamerule doDaylightCycle true and /gamerule doDaylightCycle false are confirmed to be able to trigger this crash.
The bug
When the player tries to enable "Always Day" and "Do Daylight Cycle" in the options menu, the one enabled before becomes disabled to prevent the game from crashing. However, those values can still be changed via commands, which apparently don't check if the other is enabled.
How to reproduce
- Start a new world with cheats/commands enabled
- Run the command /alwaysday
- Run the command /gamerule doDaylightCycle true
Running/alwaysdayfollowed by/gamerule doDaylightCycletrue results in a crashCommands /alwaysday and /gamerule doDaylightCycle don't seem to exclude each other
Helper EditIt's not 100% clear how this bug can always be reproduced yet. With the current guide, it sometimes works, sometimes it does not; sometimes worlds work, sometimes they do not. If anyone finds out a way to reproduce this bug every time, please add it to this report by
writing a comment, thanks!Both /gamerule doDaylightCycle true and /gamerule doDaylightCycle false are confirmed to be able to trigger this crash.
The bug
When the player tries to enable "Always Day" and "Do Daylight Cycle" in the options menu, the one enabled before becomes disabled to prevent the game from crashing. However, those values can still be changed via commands, which apparently don't check if the other is enabled.
How to reproduce
- Start a new world with cheats/commands enabled
- Run the command /alwaysday
- Run the command /gamerule doDaylightCycle true
Helper EditIt's not 100% clear how this bug can always be reproduced yet. With the current guide, it sometimes works, sometimes it does not; sometimes worlds work, sometimes they do not. If anyone finds out a way to reproduce this bug every time, please add it to this report by posting a comment, thanks!
Both /gamerule doDaylightCycle true and /gamerule doDaylightCycle false are confirmed to be able to trigger this crash.
The bug
When the player tries to enable "Always Day" and "Do Daylight Cycle" in the options menu, the one enabled before becomes disabled to prevent the game from crashing. However, those values can still be changed via commands, which apparently don't check if the other is enabled.
How to reproduce
- Start a new world with cheats/commands enabled
- Run the command /alwaysday
- Run the command /gamerule doDaylightCycle true
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
![[Bot] Arisa](../../../data/assets/gravatar/mustek2.png){kind=small}
Commands /alwaysday and /gamerule doDaylightCycle don't seem to exclude each other/gamerule will crash the game if the argument contains uppercase letters
Helper EditIt's not 100% clear how this bug can always be reproduced yet. With the current guide, it sometimes works, sometimes it does not; sometimes worlds work, sometimes they do not. If anyone finds out a way to reproduce this bug every time, please add it to this report by posting a comment, thanks!
Both /gamerule doDaylightCycle true and /gamerule doDaylightCycle false are confirmed to be able to trigger this crash.
The bug
When the player tries to
enable "Always Day" and "Do Daylight Cycle" in the options menu, the one enabled before becomes disabled to prevent the game from crashing. However, those values can still be changed via commands, which apparently don't check if the other is enabled.How to reproduce
- Start a new world with cheats/commands enabled
- Run the command /alwaysday
- Run the command /gamerule doDaylightCycle true
Helper EditIt's not 100% clear how this bug can always be reproduced yet. With the current guide, it sometimes works, sometimes it does not; sometimes worlds work, sometimes they do not. If anyone finds out a way to reproduce this bug every time, please add it to this report by posting a comment, thanks!
Both /gamerule doDaylightCycle true and /gamerule doDaylightCycle false are confirmed to be able to trigger this crash.
The bug
When the player tries to use the /gamerule command where the first argument contains any uppercase letters, the game will crash.
How to reproduce
- Start a new world with cheats/commands enabled
- Run the command /gamerule doDaylightCycle true (note that this will work with any /gamerule command, as long as the first argument contains uppercase letters
/gamerule will crash the game if the first argument contains uppercase letters
Helper EditIt's not 100% clear how this bug can always be reproduced yet. With the current guide, it sometimes works, sometimes it does not; sometimes worlds work, sometimes they do not. If anyone finds out a way to reproduce this bug every time, please add it to this report by posting a comment, thanks!
Both /gamerule doDaylightCycle true and /gamerule doDaylightCycle false are confirmed to be able to trigger this crash.
The bug
When the player tries to use the /gamerule command where the first argument contains any uppercase letters, the game will crash.
How to reproduce
- Start a new world with cheats/commands enabled
- Run the command /gamerule doDaylightCycle true (
note that this will work with any /gamerule command, as long as the first argument contains uppercase lettersThe bug
When the player tries to use the /gamerule command where the first argument contains any uppercase letters, the game will crash.
How to reproduce
- Start a new world with cheats/commands enabled
- Run the command /gamerule doDaylightCycle true (Note that this will work with any /gamerule command, as long as the first argument contains uppercase letters. It does not specifically need to be doDaylightCycle.)
The bug
When the player tries to use the /gamerule command where the first argument contains any uppercase letters, the game will crash.
How to reproduce
- Start a new world with cheats/commands enabled
- Run the command /gamerule doDaylightCycle true (Note that this will work with any /gamerule command, as long as the first argument contains uppercase letters. It does not specifically need to be doDaylightCycle.)
The bug
When the player tries to use the /gamerule command where the first argument contains any uppercase letters, the game will crash.
How to reproduce
- Start a new world with cheats/commands enabled
- Run the command /gamerule doDaylightCycle [true/false] (Note that this will work with any /gamerule command, as long as the first argument contains uppercase letters. It does not specifically need to be doDaylightCycle.)
Interesting bug. I play Minecraft (Bedrock Engine) on an Xbox One. I will try doing this to see if it crashes my game on an Xbox One.
I will try to reproduce it 100% of the time. I will contact you within this week or the next. I do find this bug as interesting as you do. Thanks!
So it turns out the bug as originally reported was worse than i thought. The crash actually occurs with ANY gamerule command where the gamerule contains uppercase characters. For example, /gamerule mobGriefing will result in a crash, while /gamerule mobgriefing will not. Should I open a new issue for this?
Thanks for the extra info about this.
I could not trigger a crash by using changing the daylight cycle settings at all - is that actually an issue still, or does the problem lie solely with using uppercase letters in the commands? (Which is easily reproducible)
It's most definitely the latter. As far as I can tell, only /gamerule is affected by the bug.
The issue has been updated with my new findings.