REALMS-1122Upload stuck on "Preparing your world"
I downloaded a backup of my realm, added a datapack compatible with 1.13, and reuploaded the world. Upon reuploading the world, I'm shown a blank screen with text displaying "Preparing your world". The only option is to click "cancel" which cancels the world upload.
I did find a single duplicate bug report, but it has remained untouched since its original report date.
Environment
OS: Windows 10
Java Version: Bundled Java Runtime
Version 1.13 (i think 1.13.2, but it displays as 1.13)
Linked Issues
Attachments1
Created Issue:
Upload stuck on "Preparing your world"
I downloaded a backup of my realm, added a datapack compatible with 1.13, and reuploaded the world. Upon reuploading the world, I'm shown a blank screen with text displaying "Preparing your world". The only option is to click "cancel" which cancels the world upload.
Environment
OS: Windows 10
Java Version: Bundled Java Runtime
Version 1.13 (i think 1.13.2, but it displays as 1.13)
Attachments1
I downloaded a backup of my realm, added a datapack compatible with 1.13, and reuploaded the world. Upon reuploading the world, I'm shown a blank screen with text displaying "Preparing your world". The only option is to click "cancel" which cancels the world upload.
I downloaded a backup of my realm, added a datapack compatible with 1.13, and reuploaded the world. Upon reuploading the world, I'm shown a blank screen with text displaying "Preparing your world". The only option is to click "cancel" which cancels the world upload.
I did find a single duplicate bug report, but it has remained untouched since its original report date.
duplicates
Could you check the log, it might be a duplicate of
MC-134146if you have datapacks with long names?the datapack doesn't have a long name, but it does add around 800 advancements, but the whole file only totals 346 KB. Does it need to be a zip file for it to work?
Please attach .minecraft/logs/latest.log after having this issue.
Turns out that there were numerous .json files with names >100 bytes. Removing them fixed the issue. found them after looking in the logs. Is it intentional to limit .json name sizes?
We don't know. At the moment
REALMS-1128is still open.