Forum:Named update pages

Named update pages currently consist of a merged changelog of the release versions, without bugfixes and some minor changes. Furthermore, they include promotions in the gallery and some other sections, some information about development and the announcement, and a list of further revisions.

Recently, there has been a discussion on Discord about whether to include edition-exclusive and technical changes/additions in the named update section of the navbox new content. That discussion extended to what changes should be included on the named update page, since it's generally the same. It has also been proposed to outright remove named update pages and turn them into a disambiguation.

The problem currently is that there are no clear guidelines about what should be included in the "changelog" of the named update page and what not, and there have been some disagreements on Mounts of Mayhem about that recently. Another problem is that the update page essentially just duplicates information from the version changelog, while hiding most information.

I also want to bring up that update guides are duplicating all this information again, but in a different format. I don't see them being very useful, and it's very weird that they're split for editions, while almost all of these features are multi-edition.

My proposal is to make all named update pages primarily focus on the "event". A named update is nothing more than a Mojang Studios promotion for new features, so it should be about the promotion and new features Mojang Studios promoted.

It should not be a changelog; that's what the version changelogs are for. However, it should still include an overview of new features, more than just a bullet list. The format of the "guide" pages is closer to what I'm talking about, although it shouldn't be a table, rather sections about each addition with a short summary.

What to include must be anything that has been announced to be part of the named update; refer to mc.net articles (not changelogs!). Basically anything needs to be multi-edition (so not End flash), although an exception can be made when something has been promoted as part of the update (like Vibrant Visuals, they even called the update "Chase the Skies with Vibrant Visuals" in the trailer). Changes like retextured dyes can also be included, if it has been announced. Technical changes like new commands shouldn't be included, except when it has been promoted for the named update of course.

The rest of the named update page can still be the same, although I'd like to see a section listing all versions related to the update, possibly above "Further revisions".

I don't have an example yet, but I could make a draft in the future.

I propose to delete all update guides, all information should be summarized in the named update page instead.

Reply here for opinions and suggestions! MinecraftBedrockPlayer7 (talk) (contribs) 👁 Image
14:59, 15 November 2025 (UTC)

👁 Image
 Support​ in parts This proposal. I agree that the named updates pages should be changed, but I am against the removal of the guides. As you said, these pages should include information about the update event, and in my opinion, we should only include a list of the main features added, without more details. This information should be on the guide pages, which should be merged between editions, in a title model "Guides/Update" (which would also facilitate a future dedicated namespace). Specific additions or changes to an edition can be simply marked with {{only}}, and updates to only one edition can have "(Edition)" at the end of the title.
  — Herobrine222376 ^{( Talk | Contributions | pt-br )} 21:55, 23 November 2025 (UTC)

👁 Image
 Support. I do have an example, although it's probably too barebones: Special:Permalink/2700915 (an early version of the "The Garden Awakens" article). I think a simple list like this should be enough for the notable features. Optimally, the named update pages would be a combination of this and the current guide pages, so maybe have a guide-style table for the most notable features instead? | violine1101 ^(talk) 22:10, 23 November 2025 (UTC)

I'll draft an idea soon. MinecraftBedrockPlayer7 (talk) (contribs) 👁 Image
22:11, 23 November 2025 (UTC)

I have made a draft here for Chase the Skies. MinecraftBedrockPlayer7 (talk) (contribs) 👁 Image
21:12, 16 December 2025 (UTC)

👁 Image
 Support I really like that! | violine1101 ^(talk) 22:13, 16 December 2025 (UTC)

Ooh yes I like me a nice bit of prose. 👁 Image
 Nixinova  T ⁄ C  23:54, 16 December 2025 (UTC)

👁 Image
 Support, it looks good! –LauraFi - talk 01:00, 17 December 2025 (UTC)

I kinda have mixed feelings about this... Jaime-Spec MC (talk) 09:49, 17 December 2025 (UTC)

That looks nice, and it really sets them apart from the version pages.👁 Image
WillyBlue (talk) 00:46, 17 December 2025 (UTC)

The named update pages should also be condensed changelogs, not going into detail, and just listing the main features related to the update's theme conceptually. Just like bullets for spawning, variants, behavior, and usage for each feature, and that's it.  Nixinova  T ⁄ C  22:12, 23 November 2025 (UTC)

I also have a (possibly controversial) view that a named update is a discrete collection of changes. E.g., version 1.14 is made up of "Village & Pillage" + "Texture Update" + misc changes – 1.14 doesn't exactly 'equal' V&P, it contains it. The named update pages shouldn't include the other changes in the version (Lava Chicken shouldn't be part of Chase the Skies, for instance). This would keep the named update pages concise and all features relevant to one another.^{[note 1]}  Nixinova  T ⁄ C  22:15, 23 November 2025 (UTC)