While trying to update a pack on my Realm, I incremented the version number and left the UUID the same. The game read it as a new update, and overwrote the other pack in my single player world. On the Realm, in the resources, it showed that it was the 1.3 pack, but when I left the settings page nothing uploaded. I looked on the Realm, and it was still the 1.2 pack. I then went back into the settings page and deactivated the pack and backed out so it would save. It saved the settings this time, and when I went back in there was no pack, so I reattached the 1.3 pack and backed out. This time it uploaded with no problems. Checked on the Realm and it was the 1.3 pack. so I did get it to update without pulling the world down, but in order to do it, I had to remove the pack first.
If possible, this is the behavior I would expect:
I have pack 1.0.0 on my realm
I install pack 1.1.0 to my machine with updates to the version, but the same UUID
I open the Realm settings, and verify that the Realm settings show 1.1.0 as the current pack
I leave Realm setting or click play world At this point the new pack is uploaded, therefor closing the Realm, and if version number is increased, it overwrites the old version
The realm reopens, and as users join, they are prompted to redownload the pack to overwrite the pack they have on their local machines cache Realm pack is updated
Linked issues
Comments 8
I also had a realm add-ons issue where I uploaded my add-on and all the versions of it where I was working on it and updating it incrementally and tinkering with a single setting at a time back and forth all uploaded onto the realm at once instead of just the one selected version of the pack. Then when I tried to remove all the different versions of the same pack and keep the one version I wanted to keep on the realm I got an error when I tried to log on that read "Some of the selected content could no be applied"
To resolve this issue I had to go to the storage setting off of the main menu settings button and delete all but the one version of the pack I wanted installed.
(and to clarify when I upload a different version of the same pack I am getting different and separate entries under the packs to install onto a map or realm for each individual version of the pack like each version is its own pack. I suspect I am doing something wrong to end up with this behavior but wanted to explain this to clarify how my experiences can be slightly different from how Savage's experience was)
Are you still having the same issue with 1.16.220? What exact message(s), if any, are you seeing when adding/uploading the add-ons to the realm?
This ticket has been temporarily closed as Awaiting Response. It will automatically reopen when you add information. Tickets that do not contain enough information may be closed as Incomplete.
Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Hi
Does this issue still occur after updating to 1.20.31?
This ticket will automatically reopen when you reply.
Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
This appears distinct from 2108, which is about experimental gameplay features not working on Realms (hopefully fixed in the Nether Update!). This bug is about behavior pack version updates not being picked up without removing and reapplying the behavior pack.