MCPE-32949/time query gametime does not appear to return correct gametime value
While reviewing original documentation and testing /time query gametime command, it appeared that the command was not returning the result of the world age. Instead, it appeared to return a result indicating the world was only a few days old maximum.
Please confirm if this is a bug on bedrock android version. My world was originally created on Nov 29, 2017. The values being returned by the commands are as follows:
Day is 1.
Daytime is 15029.
Gametime is 39590.
Based on the information from this page ( https://minecraft.gamepedia.com/Day-night_cycle#Minecraft_time_to_real_time ), it would appear that this gametime should be much higher than a mere 39590. This is a SMP game world that is played on for at several hours daily. The day-night cycle is active in this world.
The only thing to note is that this world was originally created on a different android device and then copied to a new device in December and continued playing on the new device since that date. Should that affect the gametime stamp returned by the command?
Edited by [MCPE Mod] Auldrick: Questions to be resolved by mods
In a single-player world, /time query gametime returns the number of ticks since the world was opened.
- Is this also true for multiplayer and Realms worlds?
- Does Java return the same measurement?
- Is this the intended behavior?
(I need the answer to the first two questions so I can update the wiki.)
Created Issue:
/time query gametime does not appear to return correct gametime value
While reviewing original documentation and testing /time query gametime command, it appeared that the command was not returning the result of the world age. Instead, it appeared to return a result indicating the world was only a few days old maximum.
Please confirm if this is a bug on bedrock android version. My world was originally created on Nov 29, 2017. The values being returned by the commands are as follows:
Day is 1.
Daytime is 15029.
Gametime is 39590.Based on the information from this page ( https://minecraft.gamepedia.com/Day-night_cycle#Minecraft_time_to_real_time ), it would appear that this gametime should be much higher than a mere 39590. This is a SMP game world that is played on for at several hours daily. The day-night cycle is active in this world.
The only thing to note is that this world was originally created on a different android device and then copied to a new device in December and continued playing on the new device since that date. Should that affect the gametime stamp returned by the command?
- Unresolved
- Open
- Unconfirmed
- Phone - Android - LG Other (Specify in description)
- Android - Nougat (LG Q6)
- 1.2.13.60
![[MCPE Mod] Auldrick](../../../data/avatars/users/10122.svg){kind=small}
While reviewing original documentation and testing /time query gametime command, it appeared that the command was not returning the result of the world age. Instead, it appeared to return a result indicating the world was only a few days old maximum.
Please confirm if this is a bug on bedrock android version. My world was originally created on Nov 29, 2017. The values being returned by the commands are as follows:
Day is 1.
Daytime is 15029.
Gametime is 39590.Based on the information from this page ( https://minecraft.gamepedia.com/Day-night_cycle#Minecraft_time_to_real_time ), it would appear that this gametime should be much higher than a mere 39590. This is a SMP game world that is played on for at several hours daily. The day-night cycle is active in this world.
The only thing to note is that this world was originally created on a different android device and then copied to a new device in December and continued playing on the new device since that date. Should that affect the gametime stamp returned by the command?
Edited by [MCPE Mod] Auldrick: Questions to be resolved by mods
In a single-player world, /time query gametime returns the number of ticks since the world was opened.
- Is this also true for multiplayer and Realms worlds?
- Does Java return the same measurement?
- Is this the intended behavior?
(I need the answer to the first two questions so I can update the wiki.)
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
I experimented with the /time command. Immediately after opening my world, both daytime and gametime returned 1000 with the daylight cycle turned off. When I turned the daylight cycle on, both values incremented at the same rate. So from this I conclude that gametime returns the number of ticks since the world was opened, not since it was created. In other words, daytime resets to 0 at 6:00 AM, but gametime continues incrementing.
This could be at odds with what the wiki says — that gametime returns "the age of the world" — but it depends on how that age is intended to be measured. The wiki should be more explicit about this (and I will look into correcting it), but first we have to determine how Java Edition measures the world age, and we also need to get a developer to confirm that Bedrock should measure the same way. It's quite possible, for example, that what you were expecting is how it works on a dedicated server such as Realms, but on a singleplayer or multiplayer hosted world it has to start over every time the world is opened.
Thanks Auldrick. I agree my expectation was to return time lapsed since the world was created. If developers intended that it is "server" lapsed game time, then I agree, it would reset each time the game is restarted and that they should update the official wiki.
Would be nice to have a command "/time query gameday" to show us non-realm players exactly how many game days have lapsed since world creation.
Cleaning up old tickets: This ticket has not been updated recently (~1 year+) so is being closed as Cannot Reproduce. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
On my server time query gametime gives 811 million which is about right for how long the server has been going.
However time query day keeps resetting to 1. I have a data pack that advances the time when half the server sleep. I also restart the server every 2 hours because of the persistent memory leak.
According to the wiki this should be gametime /24000 so something of the order of 33,000.