Owned classic skins that are unavailable to new players, no longer show in Classic Skins as an owner, Although the skin from affected skin-pack loads, you cannot choose that skin again unless via a workaround.
Since every players have different library, reproducing the issue as a player might be impossible, as it requires owning a skin-pack before it was made unavailable to be purchased to others who did not bought that in the first place.
Most notable skin-pack for me were Minecraft Legacy Skin-pack, Dungeons Hero Skinpack, Minecraft X Puma: Sprint Dash and Minecraft x Burberry: Freedom to Go, which are currently unavailable to be purchased in recent days (based by searching on my owned content in Marketplace Catalog).
Workarounds: in the game menu, go to Marketplace (Minecraft Store on PlayStation), and then go to My Library, and filtering the library by Skins or Mash-up. There you can apply skins from owned skin-packs that would not be available if not purchased, this currently does not apply to skins from Super Mario Mash-up Pack on Nintendo Switch as it is not listed on Marketplace Library.
If created as custom character, Switch to Classic Skins by pressing it's icon, then return to Dressing Room, and press "Change Skin" after that as pressing Classic Skin again goes to broken UI.
Attachments
Comments 6
I'm still able to access these packs both in the skin picker and the marketplace inventory. Are there any particular reproduction steps needed to see this issue?
It is reproduced by pressing "Classic Skins" instead of "Change Classic Skins" on the Dressing Room (with the broken UI / backend). Workarounds still works as of today This issue seemed to be fixed thanks to changes to the backend on Dressing Room
It seemed to be fixed (no longer be reproduced) on my devices thanks to the backend change to Dressing Room.
No idea if this is related, but whenever I equip ANY skin, including the classic skins that are considered trusted skins under any server, it automatically becomes a default skin, like the red one in these images. I have been using this skin since 1.19 and have had no issues whatsoever until the 1.20.80 update for MCPE. Even the skin packs I don’t use that are no longer available to newer players don’t even work for me.
@unknown That's kind of off-topic and I can't reproduce the issue you're having, for the issue you're having in multiplayer, I can change to trusted skin that's downloaded from Marketplace and mine won't be reset to default skins. For images you've uploaded, all the classic skins I've downloaded from Minecraft Marketplace (and all imported skin-packs) load for me, and I've surfed the supposed affected Marketplace skinpacks, "My Snowy Journey Skin Pack" seemed to be removed from Marketplace Catalog (hence why I can't search for one), other than that, I don't see any problem on my devices. Maybe you want to clear the cache by accessing "My iPad\Minecraft\internal\premium_cache\skinpacks" (depends what OS you use) and move the skinpacks to a safe location that can't be accessed by the game, just so the game redownloads the skinpacks you own (including skinpacks that are no longer available in recent days).
If the problem (especially Marketplace skins not loading on multiplayer) still persists, you can contact Minecraft Support via Minecraft Help for their assistance.
This also affects skins from Super Mario Mash-up Pack (MCPE-152609), that is currently exclusive on Nintendo Switch (but may not include LittleBigPlanet Mash-up Pack on PlayStation as I can search for it in Minecraft Marketplace Catalog, I don't have a PlayStation console so I only know there's an optional mash-up pack that could be purchased for) because it seemed to not be available in Minecraft Marketplace catalog. I just found a workaround to the issue.
However for PC and mobile, imported skin-packs do appear. So despite them not being available in Minecraft Marketplace, no workaround is required and can be applied as-is.You know what I would do if this happened with a bad plan...?
I don't know if it was to fight gate-keeping or a phase-out, Developers, reply to me, I want to know what happened.