Pretty sure this is a bug so I'm posting here.
If you start a BDS server and somehow check the in-game time without logging in to the server (NBT Editor etc) take a note of the time. Check after some time it will be the same (Expected)
Login to the server, then logout. check time. Check again after some time again and time has continued to pass even with no players online. This is commonly noticed when you logout in the day and it's night when you go back on.
Expected: time should stop progressing when the last member logs off
Related issues
is duplicated by
relates to
Comments
GoldenHelmet
Rayth
currentTick does indeed increase as well
migrated
Thank you for your report!
However, this issue is Invalid.
You have posted a feature request or a suggestion. This site is for bug reports only.
For suggestions, please visit Minecraft Suggestions on Reddit or visit the Feedback website.
Quick Links:
📓 Bug Tracker Guidelines – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 BDS Wiki – 📖 FAQs
Rayth
how is this a feature request or suggestion? Surely this is a valid bug since time and tick should not continue with no players online
GoldenHelmet
The issue reported here has negative impacts on the game:
Incrementing
Timemeans that a player could log off safe in the daytime and log back on unsafe at night when they know that no one else has been playing in the world. In many multiplayer scenarios players cannot expect to be at the same time of day when they log off and back on because players come and go at different times. However, in a scenario where players know who is on and when, they might naturally expect to be safe logging off under the Minecraft sun. For example, consider a small family server where everyone always plays together--the members might reasonably expect it would work the same as a local multiplayer game.
Incrementing
currentTickcould potentially impact villages, because the village manager makes comparisons withcurrentTickto determine if enough villagers have worked to spawn iron golems, and to determine if villagers should be dropped from the village dweller's list. This could be the cause of MCPE-131043 on realms and servers; alternatively, the fix for MCPE-43071 in 1.16.200 may already prevent the potential problem and MCPE-131043 could be due to user errors (e.g. destroying the village by sleeping in the only bed). I am not able to test this as I do not have a BDS, but here is a set of steps to follow:
Create a new, flat world on BDS with simulation distance set to 4.
Place a bed at 4, 0, place a fletching table next to it, and spawn a villager.
Along a N-S line at X = -20 make 10 small rooms with no door (2 x 2 is fine). Place a fletching table in the wall of a room and spawn a villager, then repeat room-by-room for all 10 rooms. The result should be that each villager links to the fletching in its wall so it can restock there. (If this does not result, kill all villagers and start over at step 2.)
(Optional: kill the villager at 0, 0. Best to test this both ways.)
Stand at 65, 0.
Log off.
Wait 25 minutes.
Log on, wait a minute, then walk back to the village.
Trade with each villager until it locks a trade.
Wait until the next Minecraft morning.
Expected result
The villagers all remain linked to the workstation in their room, and they refresh trades at the next sunrise.
Hypothetical bugged result
The villagers all lose their links and do not refresh their trades.
Do both time and currentTick continue with no players, or just time?