mojira.dev
MCPE-53933

Minecon 2016 capes not showing in the capes section

The cape skin packs were supposed to allow you to equip the capes included to your skin, that is not the case for the minecon 2016 skinpack for some reason.

(This effects all platforms)

 

MCPE-54234 is NOT a duplicate, but a seperate issue. Please unresolve it.

Linked issues

MCPE-54180 The Minecon 2016 Skins Bundle Capes are not in the Character Creator Resolved MCPE-57640 MINECON 2016 Skin Pack Capes Resolved MCPE-63365 Minecon 2016 Skin Pack Capes don't show up in the Character Creator Cape Menu. Resolved MCPE-71943 2016 minecon capes are not in the cape section Resolved MCPE-75254 Capes don't show up in the new "capes" menu. Resolved

Attachments

Comments 17

In 1.14.0.3 this bug is even worse because the capes are simply overwritten with the "Founder-Edition"-Cape, so you don't have these capes anymore.

No they didnt , nobody said that , u wont be able to put minecon capes on your own skins , unless u get a code if you were on minecon

@Stjepan that is for java edition, not bedrock. 🤦‍♀️

There are no minecon codes for bedrock, except for the 2016 capes pack.

@Stjepan What are you talking about? This cloak, which is available now, did not oblige to attend in person. So in 2016 they were given out without a personal presence. And if you follow the logic, then they must be provided to those who activated in 2016.

I apologize in advance, because I use a translator.

@HungryBoy02 yea but im talking that maybe in future all people who been on minecon 2011-2016 will maybe get code to activate cape on mc bedrock

7 more comments

Thank you for including those images. I was writing a reply to you when you uploaded them, and I was very very confused, partly because of our language difference but mostly because you and I were seeing different things.

You see, on my computer those two skin packs do show the capes. I'm currently on the 1.13.0 release version, so Mojang must have done something in 1.14 that broke the capes. That's a new bug, not related to what you were originally reporting. A quick search found that this new bug has already been reported, see MCPE-54181.

So all the same, the system understands that in the 2016 package there are the same capes? Once she removes their display as in the "Founders cape".

Sorry for the translator. I translate several times from my own language to yours, and then again to my own, in order to verify the correctness of thought. It can be seen that it still does not work perfectly.

I'm not quite sure what you mean in the first paragraph. The capes are still in the Minecraft 2016 Skin Pack, something is just causing them not to be rendered in the current Beta release. The fact that it's affecting both kinds of capes (old ones built into the skin and new ones created from the component) probably indicates that the bug is late in the processing, where the composed skin gets translated into data for the renderer. It might indicate that they're trying to turn the Minecon capes into Capes section components after all, despite what I was told. (I can't promise you that, though.)

Don't worry about your translation, it's really not bad. Like I said, the problem was mostly because I wasn't seeing the same thing, so I thought I was misunderstanding you. The only other problem was "cape Creator". The word order is reversed from English, and you used the synonym Creator instead of the English word Founder. That made me think you were talking about the Character Creator. Once I thought about how many languages use the opposite word order, it all fell into place and I understood you.

Yes, I used the wrong word. Sorry.(
I am very glad that we understood each other.
Thank you again for explaining everything to us!

HungryBoy02

(Unassigned)

Unconfirmed

Multiple

Android 10

1.14.0.2 Beta

Retrieved