-
Bug
-
Resolution: Fixed
-
Minecraft 1.4.2
-
None
-
Windows 7, Java 1.7.0_09
-
Unconfirmed
I'm not 100% sure whether this is a bug or a feature.
Expectation:
Typing /difficulty <0|1|2|3> into the command line with the allowCommands NBT tag set to 1 or having spawned a world with cheats enabled to change the default difficulty for the save, not just the runtime difficulty
Occurrence:
With the NBT tag allowCommands set to 1, or after spawning a world with cheats enabled, typing /difficulty <0|1|2|3> into the chatbox (command line) does not change the difficulty set by the setting in the ESC menu. The environment correctly reflects the change (mobs despawning when set to 0), but after changing the difficulty and reloading the world the difficulty set by the ESC menu takes precedence over that previously set.
- is duplicated by
-
MC-5378 Difficulty command in SP doesn't affect difficulty in options menu.
- Resolved
-
MC-9629 /difficulty resets after reloading the map!
- Resolved
-
MC-10875 When changing difficulty with command /difficulty, difficulty in options does not change.
- Resolved
-
MC-29418 Difficulty Auto Updates on Viewing Options Screen
- Resolved
-
MC-31942 /difficulty doesn't persist in singleplayer
- Resolved
-
MC-33203 Difficulty doesn't update properly.
- Resolved
-
MC-44335 /difficulty 0 doesn't affect mobs.
- Resolved
-
MC-44805 /difficulty doesn't update on singleplayer
- Resolved
-
MC-45055 /difficulty does not change difficulty when used in singleplayer
- Resolved
-
MC-45249 /difficulty command no longer working
- Resolved
-
MC-54436 Difficulty changes when chaning resource pack
- Resolved
-
MC-2435 Command Block Difficulty Changes Do Not Update The Player Options GUI
- Resolved
-
MC-3320 Command Block Difficulty Change
- Resolved
- relates to
-
MC-44368 Difficulty Locking
- Resolved
-
MC-78276 Difficulty command doesn't update the escape menu in multiplayer
- Resolved