Template talk:Navbox new content

Personally, I would prefer if this navbox was based more around "MineCon 2023" announced content, rather than 1.21. I'm not sure if armadillos were explicitly slated to be coming in 1.21, and I also think this is cleaner and more relevant to public interest than a 1.21 navbox that might end up including all of the other features in the update. –Sonicwave ^talk 22:39, 15 October 2023 (UTC)

I'm not opposed to that, whatever helps readers is what we should do. The reason I went with an update focused navbox was specifically so that it could include all the features in the upcoming update, since minecraft live doesn't cover everything in a single update anymore. Although you make a good point about the armadillo, and I did not include and of the spinoff game news or education edition news in this navbox, which probably would be added if it were focused on minecraft live. Overall I am not attached to the name or specific topic, I just want people to be able to navigate between pages easily and explore all the cool new content coming because its really exciting! Mudscape (talk) 22:51, 15 October 2023 (UTC)

I think it probably is more intuitive and makes more sense to keep it themed to the update. We could theoretically even expand this to also include past updates, like the update aquatic. I think that'd be very useful for returning players, or also to just explore the wiki. | violine1101 ^(talk) 05:56, 16 October 2023 (UTC)

Since we found out that armadillos won't be in 1.21, I unofficially changed this nav into an upcoming navbox. I now propose and therefore 👁 Image
 support "officially" implementing this change, by that I mean changing the nav's name and formally agreeing on the change in the process. - Harristic / Talk 👁 Image
14:17, 15 February 2024 (UTC)

Once 1.21 is released and we start getting features for 1.22, is the plan to remove this template from all existing pages? Or do we want to keep a "1.21 Update" template on all pages indefinitely? I suspect not, if so I 👁 Image
 Support moving the template. — Misode (talk) 14:23, 15 February 2024 (UTC)

I don't believe we ever agreed on having navs per major update, that would cause basically every page to have too many navs. So yeah we will remove this nav from all articles of content that releases fully. - Harristic / Talk 👁 Image
17:44, 15 February 2024 (UTC)

1.21 has released. Shouldn't the upcoming nav be removed already? We are 3 weeks since the release, so enough time has passed. For the armadillo update, the upcoming nav was removed after release, but this has yet to happen with the tricky trials update. Delvin4519 (talk) 17:35, 7 July 2024 (UTC)

👁 Image
 Support In my opinion, this template should be about the upcoming features. Also, the name is kinda misleading, since you can technically access these features as part of 1.20.x minor features (you need to enable a data pack, but it's already in the game) --TreeIsLife (talk) 14:30, 15 February 2024 (UTC)

I've added the move template to the template, requesting a move to "Navbox upcoming". Delvin4519 (talk) 04:12, 28 March 2024 (UTC)

👁 Image
 Strong support because the title is incorrect. This could also be misleading for the armadillo features if people just glance at it. 👁 Image
plighting_engineerd (talk) 13:28, 28 March 2024 (UTC)

👁 Image
 Support per @Plighting Engineerd and per @Harristic. -- Nerdyguy2000 (talk) 13:56, 8 July 2024 (UTC)

👁 Image
 Support 3A/ThreeEy - [T | C] 11:34, 16 August 2024 (UTC)

There is already a lot of confusion around which features are for 1.20.5 and which for 1.21. Grouping all these into one navbox isn't helping. That's why I propose making a major separation in the navbox between each version. It will also make it easier to remove a section when a version releases.

— Misode (talk) 22:02, 16 March 2024 (UTC)

👁 Image
 Support — 👁 Image
Delycache ^{(Talk | Contributions)} 22:04, 16 March 2024 (UTC)

👁 Image
 Implemented after getting no opposition. — Misode (talk) 00:55, 20 March 2024 (UTC)

Since the bundles of bravery drop was just released, we need to discuss when a section should be removed. One option is to do this immediately when the new content is released. Another option is to leave the released content for ~another month.

I am in favor of the second option, since this is a period where lots of people will want to find out about the new content and jump between pages. — Misode (talk) 19:03, 22 October 2024 (UTC)

@245e Pinging you here since you reverted my edit. I would like to hear your opinion on this. The template is called "new content", not "upcoming game drops". Also see the above reasoning for why readers will still find this useful after it's been released. — Misode (talk) 22:29, 23 October 2024 (UTC)

They should be kept, we kept the tricky trials stuff for a while. I'm unsure about an exact duration of keeping them though, a month for BoB content feels like too long considering it's such a small update. But a month for the pale garden drop makes sense to me. We could just go case by case, remove it when we feel like it. - Harristic / Talk 👁 Image
22:31, 23 October 2024 (UTC)

Personally I'd be in favor of having a separate navbox for each update, even past updates. I find the grouping of "features that have been updated in this update cycle" to be pretty useful for navigating personally and I could imagine other readers also thinking so. I suppose Bundles of Bravery and Winter Drop could be part of the Tricky Trials navbox, since they're both (presumably) part of 1.21. | violine1101 ^(talk) 23:46, 23 October 2024 (UTC)

The navbox already has collapsible sections and on each page only the relevant section is shown by default, so it wouldn't make a big difference. This navbox originally started partially because of the confusion between the armored paws content and the tricky trials. So keeping an overview of all the new content and which drop it belongs to sounds useful to me. — Misode (talk) 00:07, 24 October 2024 (UTC)

Proposal: This navbox should always contain content for the two newest known game drops/updates, including upcoming ones. I.e. at the moment it contains Bundles of Bravery and Winter drop, which will stay as is until the next drop is announced. We could write this down in the template docs so that there's a consistent rule. (Reasoning for this somewhat longer period of keeping new content in the navbox is that while wiki users are very up-to-date with the game, the same is not necessarily the case for readers who might come back to the game after a longer period of time.) | violine1101 ^(talk) 07:05, 2 November 2024 (UTC)

I think that we should remove the Bundles of Bravery section when the Winter Drop gets released. Bundles of Bravery has been out for awhile now and the message has been removed from the main page on November 7th. Java Edition has already started the pre-release phase of development for 1.21.4 and Bedrock Edition has already started development on 1.21.60. Bundles of Bravery was released on October 22. To me, I think it's getting close to time to remove it from Template:Navbox new content. 245e (talk) 14:56, 21 November 2024 (UTC)

What about all upcoming and the most recent released. For example now bundles of bravery and winter drop or before this year live they and 1.21 👁 Image
Miner(👁 Image
talk 👁 Image
contributions) 15:02, 21 November 2024 (UTC)

Fall Dorp 👁 Image
MinecraftFan1000 (talk) 22:13, 23 October 2024 (UTC)

What are you referring to? - Zamburger (talk) 22:58, 23 October 2024 (UTC)

well i can't find the file anymore i can comfurm that the names said FallDrop of The Images On MC.Net 👁 Image
MinecraftFan1000 (talk) 23:05, 23 October 2024 (UTC)

You might be confusing them with the Bundles of Bravery files (from that article), which are named "MCV_fall_drop_[...]". The Winter Drop files (from that article), on the other hand, are named "MCV_holiday_[...]". :) - Zamburger (talk) 23:12, 23 October 2024 (UTC)

Thx That Makes More Sence Now :) 👁 Image
MinecraftFan1000 (talk) 23:14, 23 October 2024 (UTC)

I'm wondering if the hardcore addition part should be changed from saying Hardcore‌^{[Bedrock Edition only]} to Hardcore^{[Bedrock Edition and Java Edition Realms only]}. NmbrblcksFan (talk) 02:34, 30 October 2024 (UTC)

You do have a good point. It wasn't technically released on only Bedrock Edition. -~- Nerdyguy2000   Talk   Edits  02:36, 30 October 2024 (UTC)

I'd say maybe have them be removed 4 months after their release, e.g. The Garden Awakens would be removed 03/04/2025, 3 months after its release on 03/12/2024. That seems like enough time, since as shown in that 3 year release timeline leak, they're going to release a new drop every ~3 months. Add 1 more month, and that's 4 months. — 3A |  T  C  08:53, 16 January 2025 (UTC)

Just found out there already was a discussion before, but looks like it never reached a consensus. I'll still keep this here. — 3A |  T  C  08:54, 16 January 2025 (UTC)

There are currently three discussions on this page that directly or indirectly concern the nature of this template and have not been resolved. This template is currently called "Navbox new content". What is "new"? Everyone seems to agree that upcoming content should be here. What about the latest release? Is the latest release always "new", or does it stop being new after a specified period of time? The topic #Change to upcoming nav discussed changing this navbox to cover only upcoming content, and seems to have some support, but was never implemented. The topics #When should sections be removed? and #About when newly released versions should be removed from the template are both about when to remove the newest release, but have gone unresolved. And there is currently an edit war about removing the latest release because some consider it to be no longer new. Should this template only cover upcoming content and not the newest release? If this template should ever contain the newest release, for how long? If you don't want to reply to this (fourth) topic about this, please reply to any of the three above discussions so we can begin resolving them. Rampage455 (talk) 11:50, 23 March 2025 (UTC)

I'd say that yes, upcoming content should be in a navbox, but what about having a navbox new content and a navbox upcoming content? Otherwise I think three months is as far as an update should go released and in this navbox, especially because of the new drop system. -~- Nerdyguy2000   Talk   Edits  18:54, 23 March 2025 (UTC)

Do note there was a previous discussion in favor of removing the latest update after the next update is actually released (i.e. removing The Garden Awakens when Spring to Life is released, which is about some time today). Outrowed (talk) 09:32, 25 March 2025 (UTC)

Thanks for the link. Yes, the consensus appears to be to leave the most recent version in the navbox until the next version is officially released. It was also mentioned in the discussion that the the template documentation should be updated, but it appears that it never was. The documentation is only two sentences, so easy to change. Any objections to changing the documentation to the following? "Use this navbox on pages for upcoming or recently released content. The contents of this navbox should include the most recent full release and officially announced upcoming content." Rampage455 (talk) 15:00, 25 March 2025 (UTC)

Yes that should be the criteria. - Harristic / Talk 👁 Image
15:02, 25 March 2025 (UTC)

Support, no objection from me. Outrowed (talk) 03:15, 26 March 2025 (UTC)

Yeah shore I guess. -~- Nerdyguy2000   Talk   Edits  03:37, 26 March 2025 (UTC)

👁 Image
 Done Rampage455 (talk) 03:40, 26 March 2025 (UTC)

The newest update added some content, but it's not a part of Chase the skies drop, so should be navbox changed to this: ?

Nesekf (talk) 07:27, 1 July 2025 (UTC)

👁 Image
 Oppose: Replacing the Chase the Skies section entirely with Java Edition 1.21.7, since Bedrock Edition doesn't have the feature yet. Plus, the Chase the Skies is still the promoted content for the player base right now, and likely what the player base expect to be the latest major content update.

👁 Image
 Weak support: We could add that after the Chase the Skies section in the table, but I think it's such a minor update that it could also be a part of the game drop section itself. Outrowed (talk) 07:31, 1 July 2025 (UTC) (Last edited on 07:45, 1 July 2025 (UTC))

I think it's better to have this as a 2nd section in the table, but I don't know how it should be noted that this is also upcoming BE content. For the painting, it could just have a BE only tag in the CTS section and a JE only tag in the 1.21.7 section, but the music disc? MinecraftBedrockPlayer7 (talk) (contribs) 👁 Image
11:17, 1 July 2025 (UTC)

I think it's better to have every 1.21.7 features merge to CTS, or have them seperate in their own section. Making one of them the odd one out is a little confusing. Apparently, the Dennis painting was added in the CTS update earlier for Bedrock Edition than Java Edition. Knowing this, I think it would be better to merge it to the CTS section with the BE/JE tag. Outrowed (talk) 12:41, 1 July 2025 (UTC)

My idea is to have a sort of "other" category for features that aren't part of any named release. I feel like that makes the most sense here considering the Lava Chicken disc is in a release version of Java Edition but not Bedrock Edition. Sightnado (talk) 18:17, 1 July 2025 (UTC)

That could also be used for additions in minor updates on Bedrock, like the flat world presets in 1.21.80. MinecraftBedrockPlayer7 (talk) (contribs) 👁 Image
19:56, 1 July 2025 (UTC)

I believe exclusive features should not be included as new content that is part of a drop, since features related to the drop are always released on both platforms. Exclusive features tend to be other technical changes that just so happen to be released alongside a drop. 👁 align=top
Sightnado ( talk / contribs ) 01:26, 16 September 2025 (UTC)

👁 Image
 Extremely strong support, I've also been thinking about this for a while. However, this means we also need to exclude version-exclusive technical changes from the drop article, which I'm also supporting. I think we should still keep a few exceptions that are announced to be part of the drop, such as Vibrant Visuals (Mojang has been calling the drop "Chase the Skies with Vibrant Visuals" for a while), and maybe also some parity features like End flashes and colored sheared sheep. But technical additions and changes like mannequins and debug screen customization should definetely not be in here, maybe in a separate "technical" section? I also think minor QoL features for one edition, like chat drafts, should be in the "Other" section. MinecraftBedrockPlayer7 (talk) (contribs) 👁 Image
08:36, 16 September 2025 (UTC)

👁 Image
 Soft support as Mojang sometimes formally announces those technical features as part of the drop, as they did with Vibrant Visuals and maybe End flashes if I remember correctly, but I agree that some other features don't really fit with the drop itself. --MinecraftExp123^{(talk|contribs)} 10:01, 16 September 2025 (UTC)

There's the "other" section where those could be moved. 👁 Image
Miner(👁 Image
talk 👁 Image
contributions) 13:36, 16 September 2025 (UTC)

Reply below.  Nixinova  T ⁄ C  22:29, 1 November 2025 (UTC)

👁 Image
 Support, only major changes should be included like zombie horse becoming no longer unused. the other changes are just an effect of the mob's parent class changing. putting too much in the changed section can be confusing.  Nixinova  T ⁄ C  22:29, 1 November 2025 (UTC)

👁 Image
 Support Removing piglins/zombies/zombified piglins/husks I can get behind as them wielding spears isn't a huge change. SeaOfPixels (talk) 22:33, 1 November 2025 (UTC)

👁 Image
 Oppose Removing horse/donkey/mule/camel/llama I don't support, as them being able to be ridden through water is a huge long-requested change that is not insignificant. The texture change to zombie horses is far less significant than the change to water riding, and yet we keep the former but not the latter? That doesn't make sense. SeaOfPixels (talk) 22:33, 1 November 2025 (UTC)

it's not a texture change, it's them basically being added to the game. don't misrepresent the changes.  Nixinova  T ⁄ C  22:37, 1 November 2025 (UTC)

I meant the zombie horse spawn egg. The jist is that texture changes are documented in these navboxes, so a much more significant change like being able to ride mounts through water should be too. SeaOfPixels (talk) 22:41, 1 November 2025 (UTC)

I'm 👁 Image
 Neutral on the new spear-weilding mobs. I think that the mobs that can now be ridden through water should be 👁 Image
 kept, as I think people are far more likely to use the navbox to get to those changes instead of the fact that zombified piglins can now hold spears. Plus, the riding changes are relevant to the update as a whole as the relevant mobs are mayhemic mounts. 👁 Image
GameCatastrophe (talk) 22:51, 1 November 2025 (UTC)

👁 Image
 Support removing all. This is a navbox, not a summary of changes. The links just lead to the mobs, leaving readers confused what changed/what this mob has to do with the update, which is pretty minor overall compared to the others.MinecraftBedrockPlayer7 (talk) (contribs) 👁 Image
22:59, 1 November 2025 (UTC)

Neither do the texture changes like the dye link in The Copper Age and the zombie spawn egg in Mounts of Mayhem. That argument doesn't make sense, as you could say that about literally anything that would be put in the "changed" section (the links don't link directly to a sentecne describing what was changed). SeaOfPixels (talk) 23:02, 1 November 2025 (UTC)

Zombie horse spawn egg texture is just as redundant as these mobs indeed. Dye textures on the other hand were pretty major, although it's also not very important. MinecraftBedrockPlayer7 (talk) (contribs) 👁 Image
23:04, 1 November 2025 (UTC)

How is one significant and not the other? That's totally arbitrary (they're both texture changes), not to mention subjective. SeaOfPixels (talk) 23:05, 1 November 2025 (UTC)

I think it's clearly visible the dye texture change is significantly more noticable than the spawn egg. Dye texture change was an actual (promoted) feature in the update while this texture change wasn't even in the changelog iirc. MinecraftBedrockPlayer7 (talk) (contribs) 👁 Image
23:08, 1 November 2025 (UTC)

Regardless, I already refuted your "The links just lead to the mobs, leaving readers confused what changed/what this mob has to do with the update" argument for not making sense, so it comes down to whether water riding on mounts is important or not and I and GameCatastrophe both think it absolutely is. If you're arguing that dye texture changes should stay because they were promoted, than the water riding should be kept too by that logic for the same reason. SeaOfPixels (talk) 23:11, 1 November 2025 (UTC)

Then make a link "Water riding mobs", to the section here. That's both not confusing and it's short. MinecraftBedrockPlayer7 (talk) (contribs) 👁 Image
23:15, 1 November 2025 (UTC)

I'm not against this, but I think it's a bit strange to have an entry link that isn't itself a mob/graphic/item/block/etc. SeaOfPixels (talk) 23:16, 1 November 2025 (UTC)

If it's not immediately obvious what changed, they shouldn't be in the navbox. As a sidenote, I feel like the "Added" subcategory should always just be the main category and _rarely_ we can add a "Changed" subcategory. | violine1101 ^(talk) 23:48, 1 November 2025 (UTC)

👁 Image
 Oppose With this logic all instances of "Changed" should be removed, as it's not immediately obvious what was changed with them. SeaOfPixels (talk) 23:52, 1 November 2025 (UTC)

That's exactly what I'm saying. E.g. instead of saying "Horse, Mule, Trader Llama, ..." it should at most be a link to something like "mobs can now traverse water when ridden", but since we don't have an article for that to link to, remove it.

Same as "Zombie, Husk, etc" - the change should be obvious in the navbox (e.g. a link to Jockey, or "spear-wielding mobs", or something similar, idk) or there shouldn't be a link.

This is a navbox, not a complete list of changes. | violine1101 ^(talk) 23:56, 1 November 2025 (UTC)

Implemented this approach, as MinecraftBedrockPlayer also suggested this. Kept the riding mounts through water via the link to the Mounts of Mayhem changed mobs section, also suggested by MinecraftBedrockPlayer. SeaOfPixels (talk) 00:05, 2 November 2025 (UTC)

👁 Image
 Support removing changed sections outright. This is a navbox, not a changelog, and if a change doesn't have its own article, it should be removed. The one obvious exception is the Zombie Horse, which gets to stay, since it's basically being added to the game. 👁 align=top
Sightnado ( talk / contribs ) 21:43, 4 November 2025 (UTC)

👁 Image
 Oppose Removing changed sections entirely, and for obvious reasons. Stating that the zombie horse was added to the game is false, and omitting major new changes is a bad idea. Yes, it's a navbox for new content, but "new major changes" are just as valid to include as "new additions", they are both new content. SeaOfPixels (talk) 21:53, 4 November 2025 (UTC)

Not a very valid response. "obvious reasons"? ….
Sightnado said basically being added to the game, which is correct.
Descriptions are not what navboxes are for, they are for navigating to relevant pages. "Mount changed" is not a page.  Nixinova  T ⁄ C  21:55, 4 November 2025 (UTC)

Sections for new changes, Violine1101 and BedrockPlayer both suggested that the changed section be a short description of the change so that it's clear what was changed:

- "Then make a link "Water riding mobs", to the section here. That's both not confusing and it's short. MinecraftBedrockPlayer7"

- "It should at most be a link to something like "mobs can now traverse water when ridden. violine1101"

Which is why I implemented this. Again, the zombie horse was not added to the game, it was changed. And to emphasize this descepency, there have been major *changes* in previous updates that would be completely omitted if there was no "New Changes" section in Navbox New Content, which would make the navbox terrible for knowing new additions/changes to content. For example, if we were using navbox new content back when 1.9 was new, this navbox would completely omit to state major changes to combat, such as the major changes to armor calculations or knockback. A section for changes should absolutely be in the Navbox for this reason, even if the links go back to just being the changed feature and not a short description of the change (ie: just "Dyes" instead of "Dyes retextured). SeaOfPixels (talk) 22:37, 4 November 2025 (UTC)

I don't have much problems with there just being a changed section, I'm very critical about which things should go in there. I'm referring to game drop as a correct summary, changed mentioned there are all changes worthy for this navbox, if it has a link to a page/section describing what changed, and it's clearly visible in the navbox how it changed. MinecraftBedrockPlayer7 (talk) (contribs) 👁 Image
22:42, 4 November 2025 (UTC)

You're taking those quotes completely out of context. They are not in support of your change, they are saying "even if we do include this, then ...". Please don't misrepresent the opinions of other editors. Also, you should not be making changes to the page while the discussion is still ongoing.  Nixinova  T ⁄ C  22:44, 4 November 2025 (UTC)

👁 Image
 Agreed, it is just not a summary of changes. MinecraftBedrockPlayer7 (talk) (contribs) 👁 Image
22:12, 4 November 2025 (UTC)

👁 Image
 Support - Obviously this should be the case I'm not even sure why the change was made to put them in since they are not new content Mudscape 👁 Image
talk 22:49, 4 November 2025 (UTC)

Why is it controversial to have the last two updates in this navbox? No matter what the doc says, this is how it has practically worked since the creation of the navbox. - Harri / Talk 👁 Image
13:47, 12 December 2025 (UTC)

Well, a release that isn't the latest one isn't really "new" anymore. When there are two updates, it's usually because there's the latest one and an upcoming one, and spring drop of 2026 isn't announced yet. ‑‑MinecraftExp123^{(talk|contribs)} 13:51, 12 December 2025 (UTC)

So, since the spring drop of 2026 is announced as the cutest drop with new models and animations for the baby variants, should we put them into the navbox? They don't have pages dedicated to the drop changes (except maybe for First Drop 2026), and I don't think it's an outright major change for these entities. But, I still consider them notable enough because the game have only released these features so far, plus there are only article and video dedicated to the drop (as of now) that highlights these new changes. Outrowed (talk) 06:13, 10 January 2026 (UTC)

All that is able to be put at the moment is "👁 EntitySprite rabbit.png: Sprite image for rabbit in Minecraft
Passive mob remodels", right?  Nixinova  T ⁄ C  07:17, 10 January 2026 (UTC)

And also craftable name tags, I guess. ‑‑MinecraftExp123^{(talk|contribs)} 07:20, 10 January 2026 (UTC)

Well... so far. Outrowed (talk) 09:50, 10 January 2026 (UTC)

It seems to be the main highlight of the game drop, Mojang even call it the cutest drop. Considering the past game drop content, I doubt there will be new major features a part from these changes. They typically are announced first, then revised/updated technically over time, with some minor additions, e.g., The Garden Awakens' pale gardens and creaking mob, and then later on snapshots they added resin (with the new armor trims), and eyeblossom. Outrowed (talk) 13:22, 11 January 2026 (UTC)

👁 Image
 Agree, I think there will just be more mob remodels, then maybe some other decorational stuff that are minor, maybe even no real additions, just changes. ‑‑MinecraftExp123^{(talk|contribs)} 13:32, 11 January 2026 (UTC)

We have to remember though this is a game drop, not a major update like in the past. Updates like these can vary from very small to big. Mojang likely intend to do this way because they want to be more flexible in adding more game content/updates.^[1] Outrowed (talk) 13:45, 11 January 2026 (UTC)