Global resource restart, resources could not be loaded
Whenever they start Minecraft, an error appears saying "reset global resources", this affects most Xbox players, since those of PS4, PS5 or Windows 10 are not affected with custom texture resources or from the marketplace. I suggest they fix this bug. This error also happened in the update of the capture that I sent them.I'm sorry but the screenshot is in Spanish since I didn't find another one in English
Linked Issues
- Duplicate
Heron Santiago Mendoza Muñoz
- 0
- 1
- Unconfirmed
- Xbox
- Xbox series S, Xbox series X, Xbox one, Xbox one X, Xbox one s
- 1.16.201 Hotfix
Created Issue:
Global resource restart, resources could not be loaded
Whenever they start Minecraft, an error appears saying "reset global resources", this affects most Xbox players, since those of PS4, PS5 or Windows 10 are not affected with custom texture resources or from the marketplace. I suggest they fix this bug. This error also happened in the update of the capture that I sent them.I'm sorry but the screenshot is in Spanish since I didn't find another one in English
- Unresolved
- Open
- Unconfirmed
- Xbox
- Xbox series S, Xbox series X, Xbox one, Xbox one X, Xbox one s
- 1.16.201 Hotfix
duplicates

The screenshot shows that you are using an old unsupported version 1.14.60! Please update to the latest version 1.16.201 and report if your bug appears in the new version.
Thank you for your report!
We're tracking this issue in
MCPE-39045, so this ticket is being resolved and linked as a duplicate.If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Hello, it has not been resolved why I said that I would send a capture and from that version of the game there is that error and they have not given me a solution. what I need is to know how to fix that error in 1.16.201