After testing a custom resource pack using the development_resource_packs folder, when you later deactivate it and delete it from that folder, an entry for it appears in the world's Resource Packs > Realms Plus Packs section, and its description says "This pack is missing!" This is an error because it is not a Realms Plus pack, and because getting rid of it in-game is difficult and unintuitive.
Steps to reproduce:
Create or obtain a trivial resource pack in source form. (You can download the attached "Map Helper - Yellow.mcpack" file I created as a workaround for MCPE-27720.)
Rename the file extension from ".mcpack" to ".zip" (if it isn't already in .zip format).
Extract All to the folder "%LocalAppData%\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang\development_resource_packs".
In Minecraft, create a simple test world. If the world loads, save and exit.
In the test world's settings for Resource Packs>My Packs you should see the resource pack you just installed for testing. Activate the pack.
Select the pack in Main Menu>Settings>Storage>Resource Packs, then delete it.
Look at the test world's settings for Resource Packs>Active. Note the error message "This pack is missing!". Select the entry and deactivate it.
Look at the test world's settings for Resource Packs>Realms Plus Packs.
Observed results:
You see an entry for the test pack with the error message "This pack is missing!" There is no corresponding entry (erroneous or otherwise) in the settings for Resource Packs>My Packs.
Expected results:
There is no entry for a missing pack in either My Packs or Realms Plus Packs because it was only installed temporarily in the development_resource_packs folder, which is meant for testing.
Screenshot showing the results:
[media]Attachments
Comments 4
Resolving temporarily as Awaiting Response. Is this still an issue in the latest version of the game?
This ticket will reopen automatically when you reply.
This is still happening in 1.20.12. However, I noticed that I forgot to include a step to deactivate the pack in the repro steps. I have now corrected this.
As additional information, I thought perhaps installing the same pack (with the same UUID and version) the normal way, from a .mcpack file, might overwrite the saved pack information, after which I could use the Storage settings to delete it and it might then be gone for good. This didn't work, though: it still appears in the world's Resource Pack settings, either the Active list or the Realms Plus list, still with the error message.
Speculating, this seems to be an edge case in the logic for updating the world_resource_pack_history.json file. I would think that when the game loads a pack from the development_resource_packs folder, which I assume is meant for testing, perhaps it shouldn't be recorded in the history file at all? Of course, leaving it out might break something else, so I might be wrong.
Additional information:
This appears to be the same issue as was reported in MCPE-149046, which was closed as Incomplete.
This issue does not occur if you install the pack by opening the .mcpack or .mcaddon file.
This issue does not occur if you activate the pack in Global Resources; only in a world's Resource Packs.
It's quite possible that the same problem could happen with behavior packs. The devs should check for similar logic.
I have attached an exported world Test.mcpack that has this error.
Once the error occurs, the only way I know of to fix the problem is to find the world's folder under com.mojang\minecraftWorlds and delete its world_resource_pack_history.json file.
Impact
It seems likely that people having this problem are unaware of it or are just leaving the erroneous entry in Realms Plus Packs since it causes no obvious immediate harm. However, having a missing pack, even a bogus one, might be causing other problems we've had trouble reproducing, such as not letting other players join the world (because the host has marked the world as requiring them to download the packs) or not being able to upload the affected world to Realms Plus and load it successfully.