Coming in from MCPE-86843 here.
This bug affects local worlds as well as realms. Although we started keeping a persistent world in preparation for the better together update, I've owned MCPE on android since 2011 and could potentially have nearly 9 year old maps. As I reported in the other bug, we ran the world as a server with a 24/7 dummy account for over a year and even without single player sleep command blocks we'd be hitting 3.5 years already.
Does this affect BDS as well? or does time stop progressing on BDS when no one is connected?
This does appear to be the cause of linked "MCPE-86843 Villagers either don't sleep or don't wake up".
And to comfirm, loaded the backup world in MCC Toolchest and time was negative as you expected. Changed it to positive and the villagers sleep cycle returned to normal
Adding to the time integer limitations:
Before moving this world to a realm, we were hosting it on an android device and later a win10 system. We had setup an extra account and left the world running 24/7 for at least a year.
This was before bedrock server was out.
It is not unreasonable for worlds to hit 3+ years of gametime. Thank you for continuing to look into this and make the game better for us all.
I downloaded the realm backup from July and it looks like that is far enough back that the problem still exists. I've attached the level.dat to this email, and will try to upload it to the issue if that doesn't work.
(if you have access to the realms environment you can also see all the world files)
It does sound related to MCPE-98361, this is a long time world that has been through all gamemodes, and we were running 1 player sleep systems that would mess with time
From memory, the 1 player sleep was a basic 2 command block system that set time to a specific hour early morning and cleared weather. It used the execute that used to trigger if you were even standing on the pillow of the bed. More recently we switched to FoxyNoTails 1 player sleep resource pack. If it's important I can pull out the commands from the old system or try to see if i can find when we switched to the resource pack.
hth
Replying via email did not reopen. I will post the messages and files directly
I also have the problem with uploading or replacing the realm, getting the error on initialising. In my case, I found that the level.dat had gotten corrupt on the realm and was able to fix it on win10.
I wasn't able to upload on win10, so i transfered to android and tried uploading there. the upload error persisted for a few days. i tried resetting the world which worked but did not allow an upload.
I managed to find a workaround that worked for me:
looking through the realm backups, I noticed that there was a backup entry for pretty much every failed upload. I was able to upload the world and, after receiving the error, reload the failed upload from the backup.
Not sure if my error is the same tracked on this ticket, and not sure if my workaround will work for anyone else.
--FG
I managed to resolve the issue by downloading the world & replacing the level.dat with a copy from a newly created world with the same seed.
I haven't tracked down the exact dates, but it looks like the actual bug is that Realms corrupted our level.dat, and that the corrupted level.dat affected the sleep cycle of the villagers.
Can this bug be moved to realms or should it be closed and a new one opened?
This is still happening in 1.18.12