Template talk:Navbox Legacy Console Edition versions

Currently we have seperate templates for Xbox 360, Xbox One, PS3, PS4, PS Vita, Wii U, and Switch Edition Version History, even though they are already used in this template, so should we just deprecate those templates and simply just be their respective section from this template? LeftQuadrilateral (talk) 21:31, 20 July 2025 (UTC)

👁 Image
 Support - Just easier to maintain fewer pages, I'd do the same for {{world features}}. I just don't have the motivation to merge them all myself anymore. I tried to use the sandbox to see if I could add a nodisplay flag to the navbox, but couldn't get it to fully work. Delvin4519 (talk) 04:24, 25 July 2025 (UTC)

done LeftQuadrilateral (talk) 10:51, 25 July 2025 (UTC)

Technically, if you want to do so @LeftQuadrilateral, you can make a request in MCW:Bot requests for a bot to do the following tasks across the mainspace name space to clear out the deprecated template redirects completely. I noticed the old template redirects are still being used across the entire wiki. The following list is what a bot will need to do:

{{Navbox Xbox 360 Edition versions}} to {{Navbox Legacy Console Edition versions|xbox360}}

{{Navbox Xbox One Edition versions}} to {{Navbox Legacy Console Edition versions|xbone}}

{{Navbox PlayStation 3 Edition versions}} to {{Navbox Legacy Console Edition versions|ps3}}

{{Navbox PlayStation 4 Edition versions}} to {{Navbox Legacy Console Edition versions|ps4}}

{{Navbox PlayStation Vita Edition versions}} to {{Navbox Legacy Console Edition versions|psvita}}

{{Navbox Wii U Edition versions}} to {{Navbox Legacy Console Edition versions|wiiu}}

{{Navbox Nintendo Switch Edition versions}} to {{Navbox Legacy Console Edition versions|switch}}

{{Navbox carvers}} to {{Navbox world features|carvers}}

{{Navbox generated features}} to {{Navbox world features|features}}

{{Navbox generated structures}} to {{Navbox world features|structures}}

{{Navbox terrain features}} to {{Navbox world features|terrain features}}

I noticed the LCE version history templates were already merged. Because of so, I also went through and prepared {{world features}} to allow the 4 template redirects for that navbox to be merged as well (mostly just getting the categories set up and prepared for the merge), so there is only 1 single large round of navbox condensing to do. Both navboxes would undergo the same bot run to change the template redirects to point to the parent navbox directly.

Since it would be a massive change, I'm not planning to make the bot request myself, unless there is a desire from multiple editors to do so. Delvin4519 (talk) 04:08, 26 July 2025 (UTC)

Can you better explain what's going on with {{Navbox world features}}, all of the other navboxes redirect to world features, so what's going on with them? LeftQuadrilateral (talk) 11:07, 26 July 2025 (UTC)

It is the same exact issue as with the LCE version templates. Because all the template redirects for world features are just redirects to world features, the template redirects can just be replaced with the parent navbox outright with no change in functionalilty. The template redirects only create confusion and hence they can be deprecated and removed from active use; in the same manner as with LCE version template redirects. So that is why we can strike two out in one go, as one round, with just one stone. Delvin4519 (talk) 15:00, 26 July 2025 (UTC)

I forgot to tag my lest message, @LeftQuadrilateral. Anyhow, I have attached merge templates on all the navboxes that redirect to {{world features}}, since they could easily be merged as with LCE version navbox templates; and both can be done with a bot run request if you think it would be worth it to do so. Delvin4519 (talk) 20:52, 29 July 2025 (UTC)

At the moment this navigation box just categorizes versions by their version number (TU1x, 1.2x, etc)

Like the other editions of the game some console updates do have names: TU5 is 1.8 update, TU43 is October Update, TU46 is Holiday Update and last versions of LCE mirror other editions (Update Aquatic and Village & Pillage).

Even if these names are not common knowledge I think that their addition would improve UX 93.113.25.41 05:39, 2 January 2026 (UTC)

👁 Image
 Support if there is a clear way to understand what versions are or aren't part of the update, and if it doesn't become too messy D62 10:35, 2 January 2026 (UTC)

👁 Image
 Done, I removed the arbitrary groupings and replaced them with groupings by major update. Delvin4519 (talk) 22:19, 2 January 2026 (UTC)

Some major Console Edition updates used Java version numbers,. Specifically,

• TU3 is listed as "1.7.3 Title Update" on 4J's changelog
• TU5 was advertised as "1.8.2" [1][2][3][4][5]
• TU19 had "1.6.4" in its trailer
• TU31 was advertised as "1.8.8" [6][7]

I feel like these updates should be named after their "official" names, but I'm pretty sure they might confuse some people who are used to other editions (especially the 1.8.2 and 1.8.8 TUs). What should be done about them?

93.113.25.41 09:29, 4 January 2026 (UTC)

These should just be treated as update names like how 1.21 is Tricky Trials. So, mentioned on the relevant pages' leads, but not in the template. I have done so for these pages (except TU19, that didn't seem explicit as the name).  Nixinova  T ⁄ C  06:04, 28 February 2026 (UTC)

Versions that introduced mini-games have small item icons to indicate their addition, but they don't seem to be correctly assigned for all editions of the game.

1.33 of Vita Edition for example has sword icon, despite introducing Tumble. ~2026-BedrockTerracottaGrove15083 (talk) 16:57, 1 June 2026 (UTC)

Yeah, some error seem to had gone through, I'm not sure how, it should be fixed for the PS versions. If there are still errors feel free to fix them. Delvin4519 (talk) 02:26, 2 June 2026 (UTC)