mojira.dev
MCPE-186515

First edited profile can overwrite second edited profile in Dressing Room

From the beginning of 1.21.30, the dressing room UI causes a bug, while you editing your preferred skins, and then edit another skins, it displays your previous skins, and it look very terrible.

There are 2 methods to reproduce this issue:

Method 1: from the video provided by the reporter:

  1. With Minecraft open, go to Dressing Room

  2. Have 2 classic skins prepared, the skins have to be different so the result would be more obvious

  3. Try editing the first skin, this unequipped the cape if there's one, so a re-equip of a cape is required, otherwise it stays unequipped. (what the reporter faced in this step was MCPE-179630)

  4. Return to Dressing Room

  5. Try editing the second skin

Expected result: The second skin loads without any problem.
Actual result: The second skin loads, but gets replaced with the first one after some time.

Method 2: simplified to the main point only:

  1. With Minecraft open, go to Dressing Room

  2. Create / edit the first character / skin

  3. Return to Dressing Room

  4. Create the second character / skin if there is a free slot, if not, try editing another slot that's not the the first one

Expected result: the second character / skin loads as their own.
Actual result: the first character / skin loads when you try to edit the second character / skin, and can overwrite the second character / skin / capes with the first one.

Workaround to both methods: Restart Minecraft if you want to edit the second character / equip another skin for the second one.

Linked issues

Attachments

Comments

migrated
[media][media][media][media][media][media]
frankiedauser

Can confirm. Also this issue affects Custom Characters. But I needed more context,

There are 2 methods to reproduce this issue:

Method 1: from the video "video_20240911_185105_edit.mp4" provided by the reporter:

  1. With Minecraft open, go to Dressing Room

  2. Have 2 classic skins prepared, the skins have to be different so the result would be more obvious

  3. Try editing the first skin, this unequipped the cape if there's one, so a re-equip of a cape is required, otherwise it stays unequipped. (what the reporter faced in this step was MCPE-179630)

  4. Return to Dressing Room

  5. Try editing the second skin

Expected result: The second skin loads without any problem.
Actual result: The second skin loads, but gets replaced with the first one after some time.

Method 2: simplified to the main point only:

  1. With Minecraft open, go to Dressing Room

  2. Create / edit the first character / skin

  3. Return to Dressing Room

  4. Create the second character / skin if there is a free slot, if not, try editing another slot that's not the the first one

Expected result: the second character / skin loads as their own.
Actual result: the first character / skin loads when you try to edit the second character / skin / Emotes / cape, and can overwrite the second character, skin, Emotes and cape with the first one. However, based of "Screenrecording_20241005_143406..." provided by the reporter, re-equipping the exact cape that was removed due to MCPE-179630 on second profile (skin / character) does not result in skin / character being overwritten with the first one.

Workaround to both methods: Restart Minecraft if you want to edit the second character / equip another skin for the second one.

Edit: Affects cape and Emotes
Edit 1: Added more clips, besides those from the reporter, "character-overwritten.mov" shows how a Custom Character can be overwritten with the first edited one, "character-showing-wrong.mov" shows that the Character Creator showed the wrong (first) character and "emotes-overwritten.mov" shows how emotes were overwritten with the first edited character, downsized mine to 480p for size saving.

GonzoStudioz

can confirm this bug. Been suffering it for SOOO long! About a month and half now! I’ll be getting a Minecraft Experience  cape soon, so I would like if this issue is resolved soon.

GonzoStudioz

Its fixed for me now.

frankiedauser

Still an issue in 1.21.50.29 Preview. Check "Minecraft Preview 2024-11-14 11-19-27.mov" for proof.

JYN2018X

(Unassigned)

1339975

Community Consensus

Multiple

1.21.50.26 Preview, 1.21.50.25 Preview, 1.21.40.25 Preview, 1.21.40.22 Preview, 1.21.40.21 Preview, ..., 1.21.41 Hotfix, 1.21.43 Hotfix, 1.21.44 Hotfix, 1.21.50, 1.21.51 Hotfix

1.21.72 Hotfix

Retrieved