TheSkyType

After a deeper investigation into this issue, I have theorized another potential cause; I believe the Xbox cloud may not have a functioning pack cache folder inside of the encrypted Minecraft GDK folder (Windows and other platforms all do in their Minecraft folders). For Mojang to fix this, they would have to go to the LocalCache folder visible in the Minecraft GDK folder, and create folders in the LocalCache folder following this file-path: LocalCache -> minecraftpe -> packcache -> resource

This would finally allow the game to save downloaded server packs/cached data and ONLY require them to be redownloaded after a game reinstallation. 

Players CANNOT create this filepath or the folders themselves on Xbox as the folder for the Minecraft GDK build is completely encrypted, whereas the folder for the old UWP build was not. 

@gumdropolotl would you additionally mind letting me know where I can find the xbl profile cache files on windows? 

Can confirm. Issue is present on Windows and IOS but not Xbox consoles. 

This issue is due to/caused by conflicts between the Xbox cloud syncing system and local saves, similar to the issue that caused corrupted worlds after the October 5th, 2022 Minecraft Xbox performance update (MCPE-162920). The game is prioritizing cloud data over locally cached files, causing it to redownload cached data/server & realm resource packs every time it’s restarted.

It may also be mistakenly flagging downloaded packs as temporary and not correctly syncing them to the Xbox cloud.

THANK YOU MOJANG!

As of yesterday, I am no longer able to reproduce this issue, or at least as consistently as I used to be. While there are still some occasional frame drops as skinpacks load in while loading this section of the dressing room after a game restart, they are nowhere near as extreme, long lasting, or consistent as they were when I first reported this issue. It seems like a fix was rolled out from the server side, thank you Mojang. 

I took a look at my clip I attached to this report on April 4th, 2024, and was able to notice that at the start of the clip, my crosshair did indeed seem to briefly cross contact with the head of an enderman in the very far distance (at least 20 blocks away). This would make GoldenHelmet’s theory about enderman instantly becoming aggravated by a player’s crosshair briefly pointing at their head correct. The way to fix this would indeed be to increase the amount of ticks a player has to look at an enderman for in order for the endermen to become aggravated, as it seems like it can sometimes be instantaneous, and they can become aggravated almost instantly after the player’s crosshair comes in contact with their head. 

I would additionally like to add on to this report that the more owned skinpacks you have, the longer/worse the freezes occur when loading classic skins after a game restart

Not sure why you’re quoting Hive community manager when there’s a literal screenshot under my ticket with the label “Hive community manager” right underneath the username Splodg3r, and a comment directly from that user stating that their developers have determined the bug to be within the Minecraft client, on a public forum of theirs that you can literally view yourself, but each to their own I guess? And why would he report the issue directly to Mojang? He is the community manager, he doesn’t manage server development and I’m almost positive a sound related bug that isn’t in anyway game-breaking isn’t something their developers are necessarily gonna be leaping in priority to report to Mojang when they have a variety of other server related bugs they have to work through that can be a bit more problematic on the player experience on their server. The entire goal of my report was to bring the issue to Mojang’s attention as it’s already been confirmed CLIENT SIDED, not server sided, started directly after a game update, and has been confirmed out of the server developers’ controls. I will see if I can somehow reproduce the issue in a multiplayer realm and comment back here with reproduction steps if successful. Thanks 

This report is valid. The Hive’s community manager has confirmed that their developers determined the bug to be within the Minecraft client itself, and as I’ve stated, the bug started after 1.20.0. I’ve also gotten varying reports of the issue being present across multiplayer realms where a large amount of players are present with custom entities/models and would appreciate if this report could be re-opened. Thank you

This bug is highly likely related to memory, as the Hive’s community manager has stated, and is possibly related to custom entities/modes, more-specifically, when a large amount of custom entities/models collide with a large amount of players at once. The game’s engine/memory may become overloaded and not know to respond, so as a result, custom sounds begin to cut-out in a chain-reaction esque effect.

Another issue noted by Frankie pang that I’ve noticed appears to be resolved in 1.21.50;

• In Classic Skins, viewing all the skins from Marketplace sometimes lead to nothing (can pinpoint which skin packs were affected more reliably if performed in 1.21.60.21 Preview), for example Dungeons Hero Skin Pack, which cannot be purchased for new owner recently.

^ I would however like to add that you may briefly open affected marketplace skinpacks and see nothing for a few brief seconds, but after those brief seconds, the skins should all load in/become visible inside of the skinpack.

A few of these issues were fixed with 1.21.50 this morning, including the custom skinpacks not opening issue.

So I just played Minecraft on PS5 yesterday and one of the first things I noticed was the controller deadzone seems to be slightly smaller than it is on Xbox, with less acceleration curve too providing for much more precise progressive movement/track aiming. Where-as the controller deadzone on Xbox is so large that it makes aiming feel much more clunky, especially track aiming (this contradicts what I’ve previously said in comments under this thread about the Xbox controller deadzone being too small, but there was a time where it was indeed too small and the acceleration curve was too rapid, which is no longer the case, now both the deadzone and acceleration curve are slightly too large). 

Whatever the deadzone and acceleration curve are on PS5, it’s perfect and allows for extremely smooth aim and turns, please make the Xbox deadzone and acceleration curve similar to what they are on PS5. Thank you Mojang

Can confirm custom skinpacks are openable again in 1.21.60.21 Preview. But some of the smaller issues with the character creator/dressing room are still present. Additionally, custom personas added to the game folder on Windows appear to still not show in the classic skins section of the dressing room in-game. Regardless, thank you for fixing the custom skinpacks issue Mojang.

I’ve additionally gone ahead and attached the manifest to the marketplace skinpack called “1st Birthday Skinpack” by Mojang Studios, for those that would like to attempt the steps mentioned in my previous comment. 

@Zgajak Hi there. The current issue being experienced is that any custom skinpacks containing a custom manifest / manifest that doesn’t belong to a marketplace skinpack cannot be opened in the dressing room, meaning, pressing the plus button in an attempt to open the custom skinpack does not work. All custom skinpacks are unopenable, while marketplace skinpacks are openable. The game seems to detect whether a skinpack contains a custom manifest to it now, and if the skinpack does contain a custom manifest, the game refuses to let you open it. Here’s a video showcasing: https://youtu.be/ocsrMyW3P60?si=OHwN0vFvFMkSiIon

The only solid way around the issue right now for those on non-console devices is to replace your custom skinpack’s manifest with a manifest to a marketplace skinpack, and then throw your skinpack into premium_cache -> skin_packs where marketplace skinpacks are stored this way the game fully reads your skinpack as a marketplace skinpack and allows it to become openable again. Make sure you obviously download whatever marketplace skinpack the marketplace skinpack manifest belongs to as well. 

Actually a duplicate of MCPE-181194

Duplicate of MCPE-187719 and MCPE-181194

Duplicate of MCPE-187719 and MCPE-181194