MCPE-50518Behavior when installing .mcpack via double-click
When installing a resource pack .mcpack file, there seems to be no way to "upgrade" an existing installation.
Shouldn't double-click on a .mcpack file that uses the same UUID as one that is already installed, upgrade the resource pack, vs just creating a new install?
If the .mcpack author wants the ability for users to choose from different versions, then they use a new UUID, but if they use the same UUID then shouldn't it do an "in-place" upgrade? Otherwise, what is the point of the UUIDs to begin with?
When a resource pack is installed via double-click on a .mcpack file its contents are copied into:
{{ %app_data%\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang\resource_packs}}{{
{first 10 of resource_packname}}}{{}}
...and an entry is added to both:
%app_data%\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang\minecraftpe\global_resource_packs.json
%app_data%\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang\minecraftpevalid_known_packs.json
...at that point, it becomes available as a "global resource pack" which can be "added" via the "global_resources" menu from the main interface (vs. the Play/World interface) , which is expected behavior.
But, if I were to double-click that same .mcpack file again, then a duplicate resource_pack is installed as:
{{%app_data%\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang\resource_packs
(#)}}
This results in two completely duplicate entries in the global resources menu, with no easy way to tell them apart; nor is there a way to delete a package from "Available Packs". The only way to delete a package is to add the package to "Active Packs" then using the Validate button, you can then delete the resource pack. Shouldn't it be the other way around? Shouldn't you have to move a resource pack from Active Packs to Available Packs before you can delete it?
I'm not even gonna touch the way individual world save directories handle resource packs via duplicating all the content, etc., because I'm sure that's tied up into Realms, etc.
BUT an "upgrade/update" should all still be based around the UUID, otherwise, why use both UUID and the version number in the various manifest files?
- Unresolved
Zac Morris- 1
- 0
- Confirmed
- 1012950
- Windows
- Windows 10 version 1809
- 1.12.0
Created Issue:
Behavior when installing .mcpack via double-click
When installing a resource pack .mcpack file, there seems to be no way to "upgrade" an existing installation.
Shouldn't double-click on a .mcpack file that uses the same UUID as one that is already installed, upgrade the resource pack, vs just creating a new install?
If the .mcpack author wants the ability for users to choose from different versions, then they use a new UUID, but if they use the same UUID then shouldn't it do an "in-place" upgrade? Otherwise, what is the point of the UUIDs to begin with?
When a resource pack is installed via double-click on a .mcpack file its contents are copied into:
{{ %app_data%\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang\resource_packs}}{{
{first 10 of resource_packname}}}{{}}
...and an entry is added to both:
%app_data%\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang\minecraftpe\global_resource_packs.json
%app_data%\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang\minecraftpevalid_known_packs.json
...at that point, it becomes available as a "global resource pack" which can be "added" via the "global_resources" menu from the main interface (vs. the Play/World interface) , which is expected behavior.
But, if I were to double-click that same .mcpack file again, then a duplicate resource_pack is installed as:
{{%app_data%\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang\resource_packs
{first 10 of resource_packname minus characters to add the standard windows number at the end}(#)}}
This results in two completely duplicate entries in the global resources menu, with no easy way to tell them apart; nor is there a way to delete a package from "Available Packs". The only way to delete a package is to add the package to "Active Packs" then using the Validate button, you can then delete the resource pack. Shouldn't it be the other way around? Shouldn't you have to move a resource pack from Active Packs to Available Packs before you can delete it?
I'm not even gonna touch the way individual world save directories handle resource packs via duplicating all the content, etc., because I'm sure that's tied up into Realms, etc.
BUT an "upgrade/update" should all still be based around the UUID, otherwise, why use both UUID and the version number in the various manifest files?
- Unresolved
- Open
- Unconfirmed
- Windows
- Windows 10 version 1809
- 1.12.0
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
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
This is still an issue, that no one ever addressed. At this point double-clicking an .mcpack file will install multiple copies of the same addon. The "version" information in the json file is not being used for anything.
We were able to repro this problem at Mojang, taking a look