I host a realm on Minecraft Bedrock 1.16.200 (although I have noticed this issue on earlier versions). Cheats are OFF in this world, always have been. Of course, I can still change the difficulty of the world from easy to normal to hard etc, but the issue is I can't do it in the slash commands because it says it's a cheat command.
I'm not sure if this makes it a bug. But I just wonder why I can't change a setting via slash commands when I can in the main Game Settings.
This has become more of an issue now I have a second Operator on the world. He can't change the game difficulty when he technically should be able to because he can't use the slash commands, and the Game Settings don't appear for him. (For reference, he's using the game on iOS)
The image attached shows the error message in game chat when /difficulty easy is typed
Linked issues
is duplicated by 10
MCPE-112039
/Difficulty command can't be used with Cheats Off despite it being adjustable in the Game Menu
Resolved
MCPE-115090
/difficulty needs cheat activated to be used
Resolved
MCPE-173306
/difficulty command is seen as a cheat
Resolved
REALMS-6613
Operator realm members can't change difficulty setting.
Resolved
REALMS-10336
Operator on realm cant change difficulty using /difficulty command on realm
Resolved
Attachments
Comments 6
Still an issue in 1.20.40. I would really like to see this changed. It is a pain to have only one person able to change the difficulty.
I 100% agree that this is a bug. What is the point of having operators in a realm if they can't change the difficulty setting when the owner isn't online? Please fix this. Either give operators the ability to change in the settings or allow the chat command to work with cheats off.
Thank you for your report!
After consideration, the issue is being closed as Won't Fix.
Please note that this is not the same as Working as Intended, as this bug report correctly describes behavior in the game that might not be the intended or desirable behaviour, but it will not be fixed right now. Sometimes, this is because the issue reported is minor and/or impossible to change without large architectural changes to the code base.
If you'd like to post a suggestion or give further feedback, please visit the Minecraft Feedback Site or choose a link below.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
It's because /difficulty isn't a gamerule command even tho it should be. Just checked and it's the only one that acts like this (not sure about respawn radius as I've forgotten the command for it). I'd class it as a bug because it contradicts the settings. I'm not sure if it acts the same way in java but from memory I think it's the same there.
Still affects 1.18.31