![]() |
VOOZH | about |
/time| Permission level required |
|
|---|---|
| Restrictions | Cheat only[BE only] |
{
"title": "<code>/time</code>",
"rows": [
{
"field": "\n* 2 <sup class=\" nowrap Inline-Template \" title=\"\">[<i><span title=\"This statement only applies to Java Edition\">(link to Java Edition article, displayed as JE) only</span></i>]</sup>\n* 1 <sup class=\" nowrap Inline-Template \" title=\"\">[<i><span title=\"This statement only applies to Bedrock Edition\">(link to Bedrock Edition article, displayed as BE) only</span></i>]</sup>",
"label": "(link to Permission level article, displayed as Permission level<br>required)"
},
{
"field": "(link to Cheat article, displayed as Cheat) only<sup class=\" nowrap Inline-Template \" title=\"\">[<i><span title=\"This statement only applies to Bedrock Edition\">(link to Bedrock Edition article, displayed as BE) only</span></i>]</sup>",
"label": "(link to Commands#Restrictions article, displayed as Restrictions)"
}
],
"invimages": [],
"images": []
}
Changes or queries the world's game time or the time of a world clock.
There are four types of time involved in this command:
advance_time is false.In Java Edition, if the world is frozen by the /tick command, the four times above do not elapse.
/time set ... command in Java Edition always directly sets the daylight cycle time to the specified number. But in Bedrock Edition, when time: TimeSpec is specified, it increases the daylight cycle time to meet the specified time: TimeSpec.
For example:
/time set day or /time set 1000, the daylight cycle time is set to 1000, so the "day" value returns to 0./time set 1000, the daylight cycle time is also set to 1000. But, for /time set day, if now the daylight cycle time is 25001 (1 day + 1001 ticks), after executing /time set day, it won't become 1000 or 25000, since it only increases the daylight cycle time when using time: TimeSpec. In fact, it turns into 49000 (2 days + 1000 ticks), and the "day" value becomes 2. If now the daylight cycle time is 25000 (1 day + 1000 ticks), after executing /time set day, it remains unchanged.time add <time>time of <clock> add <time>
<time> to the specified world clock's daylight cycle time.time pausetime of <clock> pause
time query gametime
time query timetime of <clock> query time
<clock>.time query <timeline> repetitiontime of <clock> query <timeline> repetition
<clock>'s timeline <timeline>.time query <timeline>time of <clock> query <timeline>
<clock>'s timeline <timeline>.time resumetime of <clock> resume
time set (<time>|<timemarker>)time of <clock> set (<time>|<timemarker>)
(day|night|noon|midnight).time add <amount: int>
<time> to the daylight cycle time.time query <daytime|gametime|day>
time set <amount: int>time set <time: TimeSpec>
JE: <time>: time
BE: amount: int: int
d: an in-game day, 24000 gameticks;s: a second, 20 gameticks;t (default and omitable): a single gametick; the default unit..5d is same as 12000 gameticks.daytime|gametime|day
daytime, gametime or day.JE: day|night|noon|midnight
BE: time: TimeSpec: enum
sunrise = 23,000[Bedrock Edition only]day = 1,000noon = 6,000sunset = 12,000[Bedrock Edition only]night = 13,000midnight = 18,000/time instead of /time of <clock>), defaults to the default world clock of the dimension of execution. Currently, only the Overworld and the End have default world clocks, which are minecraft:overworld and minecraft:the_end respectively.minecraft:world_clock registry.minecraft:timeline registry.| Command | Trigger | Java Edition | Bedrock Edition |
|---|---|---|---|
| Any | The command is incomplete, or any argument is not specified correctly. | Unparseable | Unparseable |
| Otherwise | Successful | ||
| Command | Edition | Situation | Success Count | /execute store success ... | /execute store result ... |
|---|---|---|---|---|---|
/time add ... | Java Edition | On success | 1 | 1 | the daytime (the daylight cycle time modulo 24000) after execution |
/time query ... | On success | 1 | 1 | the obtained value | |
| Any | Bedrock Edition | On fail | 0 | N/A | N/A |
| On success | 1 | N/A | N/A |
time set 1000time add 24000time set <desired day number*24000+time of day in ticks>; to change day count to day 472 at noon (6000): time set 11334000| Java Edition Beta | |||||||
|---|---|---|---|---|---|---|---|
| 1.3 | Added /time. Both add and set can be used. | ||||||
| Java Edition | |||||||
| 1.3.1 | 12w16a | /time is now usable in singleplayer.
| |||||
/time set now accepts day (equivalent to 0) and night (equivalent to 12500). | |||||||
| 1.7.2 | 13w36a | /time set day now is equivalent to 1000, and /time set night now is equivalent to 13000. | |||||
| 1.8 | 14w29a | Added /time query, accepting daytime and gametime. | |||||
| 1.9 | 15w49b | /time query now accepts day as a value. | |||||
| 1.13 | 18w01a | Added the options noon and midnight to /time set. | |||||
| 26.1 | snap3 | The / command is now based on world clocks. | |||||
The return value (e.g. from /execute store) from the set and add subcommands is now the total elapsed ticks of the clock instead of the current time of day. | |||||||
| pre1 | Added / [of <clock>] rate <rate>. | ||||||
| Pocket Edition Alpha | |||||||
|---|---|---|---|---|---|---|---|
| v0.16.0 | build 1 | Added /time. | |||||
| Bedrock Edition | |||||||
| 1.17.30 | beta 1.17.30.20 | Now /time set <amount: int> directly sets the daylight cycle time to the specified number, instead of incrementing the daylight cycle time to satisfy the specified daytime. | |||||
/time Command" – Microsoft Learn, October 11, 2023.