The Unknown capes notes should be edited to something like, "A Unknown cape that looks like a Sniffer has been found on Mojang's staging texture server and on Mojang's production texture server. It was added to staging on October 10th and added to production 7 days later on October 17th. The cape was first seen on 2 accounts on Mojang's staging database." - faav (im part of the group who found it)
Latest comment: 15 April 20242 comments2 people in discussion
Under the valentine capes section, i've noticed the grammar seems kind of poor. Can't edit it because i'm not autoconfirmed, so can someone maybe fix it up? Salad (talk) 03:18, 15 April 2024 (UTC)
Latest comment: 22 April 20242 comments2 people in discussion
First of all, "Unused capes of Bedrock Edition" are also unused on Legacy Console.
Second of all, looking at LCE skin pack files shows that capes and skins have ID numbers attached to their .pngs.
This allows for wiki to document what skins were meant to have capes.
95.220.122.10407:31, 21 April 2024 (UTC)
I'm not sure if i understand. If you have any information that would make things accurate than please go and change it to the way it should be. I do not have any information about what was or wasn't on Legacy Consloe edition so if you know, go ahead and change it to be correct. Richard01CZE (talk) 20:33, 22 April 2024 (UTC)
Latest comment: 15 May 20242 comments2 people in discussion
Suggesting small corrections here as the page is locked:
The word "Anniversary" is mispelled in the 15 Year Cape notes
The Mojang Studios Cape "was given to employees..." - shouldn't this be "is given" as the cape is presumably still awarded to employees?
The "Note: This cape is not released yet" text preceding notes for Follower's Cape, Purple Heart Cape, and 15 Year Cape should be on separate lines for readability
Latest comment: 25 May 20244 comments2 people in discussion
Hello, today I redesigned the capes selector to look like the Minecraft site with figma, the capes are sorted alphanumerically with the addition of the birthday cape. Multilingual versions are also available. What do you think?
Latest comment: 5 August 20244 comments3 people in discussion
It's been a while, and I just realized the cherry cape is sorted incorrectly in this article. While we still don't have 100% confirmation of the requirements for getting the cape on java, we know for sure that they weren't the same as bedrock. LateLag (talk) 00:28, 23 June 2024 (UTC)
Although you did fix it earlier today, so as not to leave this message unanswered; I asked Mwam, and according we do know the requirements. They are as follows:
One get the cape on Java if they voted
One get the cape on Bedrock if they joined the event server
Though I do wonder if "cross-platform" should means that the actual design is cross-platform, or if the means of obtaining it are (I honestly do not have any opinion about this anyway). - Zamburger (talk) 18:07, 10 July 2024 (UTC)
Yeah I double checked before doing the edit. No official message from Mojang afaik, but seems pretty clear cut. I removed it from the cross platform section because of the precedent set by the Mojang Studios cape, which makes sense in my opinion. If by design someone can get a cape on one edition and not the other, it's not really cross platform. LateLag (talk) 20:44, 10 July 2024 (UTC)
Technically, all the cross platform capes could be obtained exclusively on Bedrock if a player only owned bedrock edition when they obtained the cape. Just because the Cherry cape is only one possible the other way (only on java) as well doesn't justify unique treatment in my eyes. Either they should all be split or none of them should be. Plus, the cross platform capes section only reads "Capes listed here are available for both Java Edition and Bedrock Edition," it doesn't say anything about being obtained in an identical manner. Walnut Simulacrum (talk) 23:45, 5 August 2024 (UTC)
Initially not my idea, but since I like it and it will be lost if it stays on the MCW Discord, I am writing that on-wiki proposal: just like how official renders are made, as well as Character Creator#Animations, I propose we switch from using Steve as the default model on this page to a blank skin (preferably the same one used by Mojang and used in the previously cited page; though I guess that there is nothing stopping us from making our own blank skin if someone finds flaws with this one).
By using a blank skin, the mannequin is less distracting and cape design far more visible. Also, although it makes sense that Steve is currently used, this removes the weird bias of using them rather than one of the other 9 default skins. - Zamburger (talk) 14:03, 2 July 2024 (UTC)
I think it shouldnβt have shorts because the intention is to focus the cape and the cape doesnβt apply shorts to the character. The shorts are already causing some confusion in this instance. How important is it to use that version of the skin when others are also available?
π Image Actually I think that you're right, the shorts isn't needed. Though, instead of using the second version ("dummy"), I'd sugget making our own custom skin by removing the shorts from the current one ("dummy earth"). - Zamburger (talk) 15:33, 2 July 2024 (UTC)
I support the use of the "custom" one, because it isn't even truly custom. There are a bunch of character creator thumbnails that don't have the tanktop, and a couple of leg pieces that show the other leg without the shorts. That means it's actually a replica of an official Mojang texture! LateLag (talk) 20:55, 10 July 2024 (UTC)
π Image I disagree - I like the idea but it could be a little confusing as you lose the context that it's on the back of the player model. If it was any other game model sure, have it one colored (like the Xbox 360 cape renders), but it's Minecraft which is just cubes with no depth unlike other game models where you have nose, eyes, ears, boobs which give the model some depth and context of what is displayed and in what orientation. On the Animations page, this context is preserved with the movement the animations have. So i'm not sure about the change --Richard01CZE (talk) 14:17, 21 July 2024 (UTC)
That was a concern to me as well initially, but it seems like something easy enough to solve by #1 having one leg of the model stepping forward or another option could be #2 showing two models wearing the cape facing opposite directions. We can also be sure there is text in the article that states that all capes are worn on the back of the player model to alleviate any further potential confusion. -BrianGLHF (talk) 20:25, 21 July 2024 (UTC)
There is the Cape model render project at Isometric renders page. It just shows the cape from front and back, with a little more refinement it could be made so that it shows the cape better and with a frame or something, same could be done for the open and closed elytra desings. Richard01CZE (talk) 14:41, 23 July 2024 (UTC)
As long as the user knows the feature they are looking at is called "Cape" they will assume it's worn on the back, because capes are a real thing. It is hard to be on any part of the cape page without the word "Cape" being present. You would need to present someone one of these renders off-wiki and not tell them it is a cape in order for there to be a chance for confusion to arise, and so I think this is not going to be an issue. But if other people think this is an issue, we could just add some grayscale hair to the model. - Harristic / Talkπ Image 17:59, 3 August 2024 (UTC)
I don't think adding hair is necessary. There is plenty of context provided that capes are worn on the back of the player including the opening line of Cape which states that "Capes are commemorative items that are worn on the back of the player." As I mentioned on Discord but should have added here... When there's a cape that's worn on the front I think then we should deal with sorting that concern. -BrianGLHF (talk) 18:16, 3 August 2024 (UTC)
Latest comment: 23 July 20241 comment1 person in discussion
Why is there a quantity counter, it fluctuates very often and it's impossible to keep it updated. And it relies on a single website. I think it is extremely unnecessary. Richard01CZE (talk) 14:44, 23 July 2024 (UTC)
Latest comment: 13 August 20244 comments3 people in discussion
Why exactly do the Java Edition capes get listed with community given names? I know the API names are still in the page, but they're overshadowed by the unofficial ones.
The Java cape names are based on API Names, what Mojang has called them and Logic. As an example... Only cheapsh0t has the japanese flag translator cape, the texture is exactly the same as normal Translator cape and the only difference being the flag, so should it really have the API name? That would make the cape be named after an account of an individual (not that the API name isn't, but that's a Mojang's thing). And the names are there for consistency and it was like this for years.
Another example... Everybody knows what Minecon 2011 cape is and looks like so why remove the name? It would only make new people interested in Minecraft confused why the Minecon 2011 isn't on the wiki. I think this isn't the greatest idea. Richard01CZE (talk) 08:29, 24 July 2024 (UTC)
But the API name is already "Minecon2011", which essentially says the same thing. Most of these community given names are just repeating the actual names, so I don't see the point. LateLag (talk) 20:47, 13 August 2024 (UTC)
Latest comment: 28 July 20243 comments3 people in discussion
Why isn't the cherry cape considered a cross platform cape? It's available on both java and bedrock, it doesn't get more cross platform than that.
I understand that you could get it from the launcher and from the website but that doesn't make it not cross platform as you got it for both editions either way from what i know
On each edition you had to get it separately. Participating in the vote only gave you the cape on Java, while joining that Bedrock server only gave you the cape on Bedrock. You couldn't get the cape on Bedrock by voting or vice versa. BabylonAS11:14, 24 July 2024 (UTC)
On the java section of the wiki, it says that it can be obtained by joining the event server on bedrock, the confusion probably comes from there. SyhixTV (talk) 17:56, 28 July 2024 (UTC)
Latest comment: 6 August 20242 comments2 people in discussion
In the No-Circle caep row, there is a link to a section that does not exist. What would go in its place? The thing it is referring to in the said section does not seem to exist on the page at all. Salad (talk) 06:48, 6 August 2024 (UTC)
So, a person on the feedback page claims that support said that the Minecraft Experience Villager Rescue cape would be coming to java. I havent seen the actual email, so it could be a hoax, but it would be a weird thing to lie about so I believe its true. Is there a screenshot of that email, or any actual proof that Mojang will be adding this cape to Java edition? If there is proof, should that be added as a citation? I imagine someone will come along and move the cape back to Bedrock Only because 'nothing offical has been announced.' https://feedback.minecraft.net/hc/en-us/community/posts/30435641601933-Minecraft-Experience-Cape-for-Java-Edition β Unsigned comment added by Tchadensis (talk β’ contribs) at 16:38, 27 September 2024 (UTC). Please sign comments with ~~~~
It should be in Bedrock only unless an official and publicly verifiable statement is made by Mojang or whoever organizes the Experience event and added to the page.--Capopanzo (talk | contribs) 16:48, 27 September 2024 (UTC)
Since it's disputed whether the cape will be available on both editions, and the provided references aren't verifiable (for both Bedrock-only, and crossplatform), I've created a new section "Future capes" where the cape can be until we have official confirmation that can be verified. | violine1101(talk)19:27, 27 September 2024 (UTC)
This is hardly the most pressing matter on the site, but with how long the page is getting and will continue to be I think it could be wise to split it. The page as it is could still be around as a list, like skin pack or Mojang cinematics, but the nitty gritty of the individual capes would go on their own pages. The creeper cape at least I feel has enough to justify its own page, since it appeared in Tricky Trials Update Official Trailer, got some marketing towards it, and now has its own merch. Realshow19 (talk) 04:33, 30 November 2024 (UTC)
π Image Comment My opinion is that this page should only contain Capes that are in the respective Cape selection sections of game. Skin capes (like Marvel as well as Minecon Skin Packs) should live on respective skin pack pages, and 360 Avatar Capes could live on an 360 Avatar Items page with all of the 360 Avatar stuff that's Minecraft related. There is also a lot of redundant images that could be removed and the formatting of some of the boxes adjusted because there are some very long descriptions that are in very narrow fields that force the page to be longer than it needs to be with a ton of white space. At the moment I don't feel that each game Cape should have its own page, but I do feel that this page needs some sprucing up. -BrianGLHF (talk) 05:24, 30 November 2024 (UTC)
π Image Agree I do think that the xbox 360 avatar capes and skinpack capes (possibly more stuff) should move to a different page as it's essentially a different type of capes. But i would leave a link behind so people can find them from the Cape page. Richard01CZE (talk) 09:36, 30 November 2024 (UTC)
As mentioned earlier on Discord, I'm changing my comment to π Image Support. My concerns still stand, though the status quo is far worse (and pretty much objectively bad, unlike a split). - Zamburger (talk) 14:33, 4 December 2024 (UTC)
π Image Strong support splitting. The table format is not useful for containing all the information cramped in this article. This page could still serve as an overview of capes (and cape skin packs), but this article has become way too crowded for it to be really useful. | violine1101(talk)13:38, 4 December 2024 (UTC)
Got some time to waste, here's what I came up with since the original proposal is not very developed (which I feel would have lead to maintaining the status quo): User:Zamburger/draft/Cape.
My draft suggests that these capes should not have individual pages, but share pages instead:
Under the name of Mojang capes:
Mojang cape (classic), Mojang cape and Mojang Studios cape
Under the name of Translator capes:
Translator cape and Chinese translator cape (nb: not Cheapsh0t's cape).
I've used tables akin to the mob pages, which sucks, I'm aware. Though it was made with Talk:Mob#Dropping tables in favor of a custom class in mind. (Therefore, the draft might be unbearable on mobile, just as mob pages!)
This could be replaced by tables in a more traditional way (although I reckon that tables for anything else than numbers, sprites or compact text do not work - and it is one of the main reasons why the current page doesn't work).
It was made using a lot of copy/paste/tweaking; so don't pay attention to any mistake or formatting error.
Any input is obviously greatly welcomed (including by those who have no interest in that page and its content). That draft is obviously far from being perfect and is only supposed to be a seed.
I noticed your draft does not include information like the capes' API names. Will the individual cape pages have an infobox with that sort of information? bigfoot (talk) 23:57, 5 December 2024 (UTC)
Yup, naturally! It'd have its internal name, way(s) of obtaining, texture, elytra render, complete history, etc. There'd no reason to lose information. - Zamburger (talk) 00:04, 6 December 2024 (UTC)
This looks really good! I think we can still discuss the categorization later, but formatting wise I really like this. (Agree about using flexbox instead of tables too.) | violine1101(talk)00:11, 6 December 2024 (UTC)
π Image Comment I'd like to document the non-ingame Xbox 360 content (avatar items, gamerpics, themes), possibly in the Xbox 360 Edition page - I have some table drafts I haven't worked on for months in a sandbox page. The avatar capes are no different than the other avatar items, so I agree with removing them from Cape and simply document them with the other avatar stuff. Capopanzo (talk | contribs) 01:03, 6 December 2024 (UTC)
π Image Support - Mojang is just going to keep adding capes. The page should be split because it is only ever going to get longer and longer until it can no longer load.Drour1234 (talk) 20:14, 19 March 2025 (UTC)
The above discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.
There is a clear consensus that this page should be split (cf. above discussion). Before going futher, as Violine mentioned, I think we can now discuss the exact categorization (not all capes should have a specific page, e.g. the April Fool's capes or the API capes could both arguably share a single page respectively).
I honestly am perfectly happy with the proposed merged pages listed on your draft, with all other "main" capes getting individual pages. I would prefer to not use subpages in the example case, but, I don't think we even have any guidelines on when to use subpages... - Harristic / Talkπ Image 00:06, 20 March 2025 (UTC)
I think it's generally better to avoid subpages since they're more easily searchable (and also the article title just looks nicer). Apart from that your proposal looks good! I think it's better to get started on this as soon possible, since Mojang appears to now release new capes quite often and we can probably expect even more capes being added in the future. | violine1101(talk)00:25, 20 March 2025 (UTC)
Latest comment: 13 December 20242 comments2 people in discussion
I don't think Vanilla Cape is a pure cross-platform because in JE is called Vanilla Cape, but in BE, it is One Vanilla Cape, like Cherry Blossom/Cherry Cape. Porpiang (talk) 08:16, 13 December 2024 (UTC)
The cherry cape is not considered cross-edition due to its different requirement for obtaining in both editions (joining the server for Bedrock and voting for Java), not because of its different names. Personally, I don't think that a different name is a good reason not to consider the vanilla cape cross-edition anymore, it still has the same requirement on both editions. - Zamburger (talk) 12:02, 13 December 2024 (UTC)
The minecraft.net cape section of the User Page has changed
Latest comment: 12 March 20251 comment1 person in discussion
As I've saw today (12/03/25), the cape selection menu of the Minecraft.net User Page has changed their visuals, being now dark mode and more consistent with the website's general pixel look, this Topic is created because the "Minecraft.net cape selection menu" still have the old look, so it must change to adapt to the new look ElMinehuy (talk) 19:33, 12 March 2025 (UTC)
Latest comment: 20 March 20251 comment1 person in discussion
besides of another player gave them a code. there is also another way of getting minecraft cape for Players that lived in regions where TikTok is banned,please add this into the cape section on cross platform Fireyneedshelp301 (talk) 08:49, 20 March 2025 (UTC)
Menace Cape & Home Cape's texture on JE are not same as BE
Sorry, I didn't notice when I found this out that it was a caching issue that caused Bedrock Edition to show the unfixed cape, please ignore it McSteve7644 (talk) 09:07, 22 March 2025 (UTC)
Exact Change Dates for the Menace Cape & Home Cape Textures
Latest comment: 3 April 20251 comment1 person in discussion
In the Minecraft Launcher with the April Fools' Day 2025 update, at the bottom of the "Launcher Leveling System" menu, there's a "Launcher Cape" option for level 9001. Is this cape real? Could more information be added? Santoi5810 (talk) 16:04, 3 April 2025 (UTC)
Remove leaked date from Common Cape, Minecraft Wiki doesn't allow leaks that are not from Mojang or found on official Minecraft game
Latest comment: 18 April 20254 comments4 people in discussion
Remove leaked date from Common Cape in Unreleased Capes section, Mojang themselves haven't confirmed it yet + Minecraft Wiki doesn't allow leaks that are not from Mojang or found on official Minecraft game Kiyanaaaaaa (talk) 07:53, 10 April 2025 (UTC)
Latest comment: 12 May 20252 comments2 people in discussion
Resolved
I dont like how this article is organized, I liked it better on how it was formatted yesterday (so the 11/05/25) I feel like it was more organized with clear sections dividing what was what.
I much prefer the new one. Previously you had to scroll through an immense amount of capes that are completely unobtainable just to get to all the capes that are actually in the game. Separating by edition doesnβt work when 90% of the publicly obtainable capes are multi-edition anyway. - Harristic / Talkπ Image 18:31, 12 May 2025 (UTC)
Latest comment: 21 May 20252 comments2 people in discussion
The size-m and Oxeye capes are now in namemc, the Oxeye cape is seen on the account "iSxckk" and the other one is in "KemiAmu"'s and "etanaratsastaja"'s accounts. I think they should be added to the main capes section and to the image that has all capes idk
--Qwe rfv (talk) 08:20, 20 May 2025 (UTC)
We do not know if any account still has the size-m cape. NameMC still lists it because it shows all capes an account has ever been seen with it. It most likely does not exist anymore. ManosSef (talk) 08:59, 21 May 2025 (UTC)
Latest comment: 13 October 20252 comments2 people in discussion
Unresolved
It would be neat to have here a list featuring in order of release of all the capes mojang has gave over time, from the oldest to the newest, because by now is a bit difficult to see which cape were the most recent released by mojang for example
Latest comment: 15 October 20252 comments2 people in discussion
Resolved
Copper Cape, which was released on Monday, October 13th, 2025, at 6 p.m. GMT+2, as detailed in the article available at "https://www.minecraft.net/en-us/article/the-copper-cape-quest-is-almost-over." The cape can/could be acquired by either placing and posing a copper golem statue in either survival or creative mode (Bedrock only), watching a Twitch streamer for five minutes, or watching a TikTok streamer for three minutes.
The history section only covers general changes to capes. A dedicated table for cape addition dates would be useful and something we should add to this page. --Capopanzo (talk | contribs) 21:58, 10 June 2026 (UTC)
