-
Bug
-
Resolution: Fixed
-
1.17.20.21 Beta, 1.16.100.54 Beta, 1.16.0.51 Beta, 1.15.0.56 Beta, 1.14.25.1 Beta, 1.14.0.6 Beta, 1.13.1, 0.15.90.0, 0.15.90.7, 0.15.90.8, 0.16.1, 1.2.8.0, 1.2.10.2, 1.4.2.0, 1.9.0, 1.11.0.1 Beta, 1.11.0.3 Beta, 1.13.0, 1.16.21, 1.16.40 Hotfix, 1.17.2 Hotfix
-
None
-
Confirmed
-
Multiple
-
103076, 392840
The bug
When using /time set, the time does not actually get set to the value you tell it to. Instead, the command gets transformed into a /time add command with a value between 0 and 24000, making various things impossible.
How to reproduce
1. Create a new world
2. /time set 0
→ It set the time to 24000 instead of 0
3. /time set 100000
→ It set the time to 28000 instead of 100000
Consequences
This makes /time set just /time add, but worse. Two things that very obviously should be possible with /time set are not:
- Going back to a previous day (even though /time add can do it just fine)
- Skipping ahead more than one day (even though /time add can do it just fine)
For example, a very common use of /time set is going to a specific moon phase. /time set 14000 should give you a full moon. Instead, it gives you the "next" moon phase, which is not at all what you specified. If you wanted to go to the next moon, you would have used /time add.
- is duplicated by
-
MCPE-16885 Setting time to 24000 causes incorrect feedback messages
- Resolved
-
MCPE-43320 /time set doesn't set the time, it adds instead
- Resolved
-
MCPE-65836 The time set buttons in the chat are showing the wrong number
- Resolved