Talk:Legacy Console Edition version history

As the Pocket Edition, Pi Edition, and the regular editions all have their updates split into separate pages, should the Console Edition follow this too? Or is it simply too difficult because of the variations of platform/version labeling on each platform? --MarioProtIV (talk) 21:27, 14 July 2015 (UTC)

That has already been discussed here. It isn't too complex, but how would you name an article? The console edition versions don't have equal or similar version numbers, so it would be way more confusing than it is now. | violine1101^(Talk) 21:32, 14 July 2015 (UTC)

The pages could be named Console Edition TU<number>/CU<number>/PS <version>. If one update is only for one or two platforms, just make the title Console Edition CU<number>/PS <version> or Console Edition PS <version>. An example title would be Console Edition TU25/CU14/PS 1.17. --MarioProtIV (talk) 21:40, 14 July 2015 (UTC)

Who would find such a page? Noone searches for "Console Edition CU1/PS4 1.00/PS Vita 1.00" or "Console Edition CU3/PS4 1.02" (or even "Console Edition TU42/CU8/PS3 1.28/PS4 1.23/PS Vita 1.22" - this version doesn't exist but such a title is theoretically possible according your system). I think it isn't worth the effort. Also, a table is way more clear to read. | violine1101^(Talk) 21:52, 14 July 2015 (UTC)

To make it easer to search for the page you could have the title of the page still be Console Edition TU<number>/CU<number>/PS <version> but have a redirect for each version number. TU <number>, CU <number>, and PS version. Wolffillms (talk) 23:59, 28 July 2015 (UTC)

That's a good idea, but the only issue would be it would take a LONG time creating redirects for every single Console versions (there's like 60 versions), plus there is the concern of broken redirects. --MarioProtIV (talk) 00:06, 29 July 2015 (UTC)

I agree with Violine1101 on the titles, absolutely no combined all versions into one title. That would not only making linking them harder, but would look terrible.

I would personally love to split the article for consistancy, but until that and the other difficulties are resolved, it is perfectly fine as one article. –KnightMiner ^t/_c 22:00, 14 July 2015 (UTC)

Is Wolffilms' suggestion of creating redirects really as daunting as MarioProtIV suggests? Creating 60 redirects doesn't seem like that big of a job. – Sealbudsman ^talk/_contr 20:48, 23 September 2015 (UTC)

I suggest to create pages gradually. GRAND RADION (talk) 10:09, 16 November 2015 (UTC)

Reviving this discussion in 2019. I would strongly support a split of this page into as many smaller pages as possible (i.e. every update for every console). Since certain newer PlayStation 4 Edition versions are getting individual pages, it only feels fair for at the very least all other PlayStation 4 Edition updates to have dedicated pages, especially when taking the relatively recent splitting of Java Edition Classic, Indev and Infdev pages into consideration. Indeed, there would be a lot of duplicated information due to near-identical updates in different consoles, but it's a price I'd be more than willing to pay (and there won't be any more of them, since said editions are discontinued). - User-12316399 (talk) 19:27, 20 February 2019 (UTC)

👁 Image
 Strong oppose. Would lead to too many redirects and too many links to fix. -BDJP ^(t|c) 22:05, 21 February 2019 (UTC)

Are you saying that we should have "Xbox 360 Edition TU1" etc? That would not be good as there's be a ton of duplicated content. – Nixinova 👁 Image
👁 Image
05:52, 27 February 2019 (UTC)

There would likely be a lot of duplicate information, but not all of the information would be duplicated (there's quite a few console-dependent bugfixes mentioned, and also note that not all console editions were launched simultaneously). If duplicate information really is that much of an issue, we could always redirect all Console Edition versions to their respective PS4 edition equivalents, and note what's different about other console releases. Still, I'd prefer a complete split, since that decreases the need to include information about completely different consoles and still keeps it out of a massive, user-unfriendly table. - User-12316399 (talk) 13:41, 7 March 2019 (UTC) - edit 17:13, 7 March 2019 (UTC)

Still 👁 Image
 Oppose per my comment above, and I also disagree with making pages just to redirect to such versions prior to 1.85. -BDJP ^(t|c) 20:50, 7 March 2019 (UTC)

👁 Image
 Oppose this idea, While PS4 and Xbox 360 both combined hold the complete lifespan of Minecraft Console Editions, this would create inconsistencies where earlier updates have a X360 update but no PS4 equivalanet, and later updates have a PS4 version, but no X360 equivalent. And also there are several console updates where say, only Switch users got but there is no PS4 or X360 equivalent. Delvin4519 (talk) 15:53, 17 April 2019 (UTC)

👁 Image
 idea: Have subpages titled something like "TU74/1.83/Patch 43" with the content and transclude it on 'Xbox One Edition TU74', 'PlayStation 3 Edition 1.83', 'Wii U Edition Patch 43', etc. – Nixinova 👁 Image
👁 Image
03:07, 30 March 2019 (UTC)

👁 Image
 Support, 👁 Image
 idea title pages based on the (most common) date they were released, i.e. "Minecraft Console Update June 23, 2019" or whatever date format seems relevant. Redirects as you need them/see bets fit for all. Delvin4519 (talk) 15:43, 17 April 2019 (UTC)

👁 Image
Mockup of my previous idea: User:Nixinova/Xbox 360 Edition TU13 which transcludes User:Nixinova/TU13/1.00. "TU13/1.00" would be a subpage of Console Edition version history or something. – Nixinova 👁 Image
👁 Image
07:01, 21 April 2019 (UTC)

👁 Image
 Oppose per BDJP. 174.252.195.18 09:41, 21 April 2019 (UTC)

👁 Image
 Strong oppose as having up to seven pages with duplicate information is wholly unacceptable. 68.112.167.7 19:01, 21 April 2019 (UTC)

Note that this is this user's first and only edit. Nixinova  T C 04:49, 1 January 2020 (UTC)

👁 Image
 Oppose per above. 64.134.162.32 17:40, 22 April 2019 (UTC)

Note that this is this user's first and only edit. Nixinova  T C 04:49, 1 January 2020 (UTC)

👁 Image
 Support Every version of the game from PC and Bedrock have their own articles, there is no point not to have them for legacy console. Sure, it will be a lot of effort, but when done it will be rewarding and easier to read, because this long table sure isn’t Rexma423 (talk) 03:43, 1 January 2020 (UTC)

👁 Image
 idea I think that instead of having 1 page per update instead having 1 page per console containing its changelog. Wappeynappey444 (talk) 21:41, 2 April 2020 (UTC)

I suggested earlier last year that we could have a subpage of Legacy Console Edition version history or Template:Console_versions or something with all the information on that subpage, then have "Xbox 360 Edition TU1" etc etc transclude that subpage. The subpage could also include #ifeqs to add edition-specific information. Mockup available at User:Nixinova/Xbox 360 Edition TU13 which transcludes User:Nixinova/TU13/1.00. Who would support this idea? Nixinova  T C 04:54, 1 January 2020 (UTC)

👁 Image
 Support I'd be up for this. - User-12316399 (talk) 00:04, 7 March 2020 (UTC)

👁 Image
 Oppose per my comment above. -BDJP ^(t|c) 01:02, 16 March 2020 (UTC)

Note that this user has since permanently retired from editing.

How does the content of your comment from last year apply this this specific proposal? This wouldn't create any redirects.  Nixinova  T  C  23:15, 18 April 2020 (UTC)

So when will we go through with this? - User-12316399 (talk) 11:06, 16 April 2020 (UTC)

When there's more support votes.  Nixinova  T  C  23:15, 18 April 2020 (UTC)

I 👁 Image
 Support this, it might improve searchability. —98.230.115.82 15:17, 10 May 2020 (UTC)

👁 Image
 Support. — Thomanski | t | c | 19:33, 6 September 2020 (UTC)

👁 Image
 Weak support. ---dr03ramos 👁 Image
(talk) Admin wiki[pt] 14:35, 12 September 2020 (UTC)

👁 Image
 Strong Support, it sounds so right and amazing, although what will happen to this pate, will it be disambiguation?---Humiebee ^{Discuss anything with me Look at my edits} 15:08, 12 September 2020 (UTC)

This would become a general index page similar to e.g. Bedrock Edition version history.  Nixinova   T   C   07:55, 13 September 2020 (UTC)

Can you implement this now? there has been 2 more supports. --Humiebee ^{Discuss anything with me Look at my edits} 15:09, 12 September 2020 (UTC)

I am now in the process of implementing this, using the new {{Console version}} template. Help would be appreciated.  Nixinova   T   C   04:00, 20 September 2020 (UTC)

---

Splitting instructions:

1. Create a new subpage of Template:Console_version with the title taking the YYYY-MM-DD format of the date that version was released and the content starting with {{cvnote}}.
   • If other variants of this version were released on different dates, redirect those newer pages to the oldest

     For example, if 1.00 was released on March 1 2020 and TU1 on March 2 2020 put all of the content on Template:Console_version/2020-03-01 and redirect Template:Console_version/2020-03-02 to Template:Console_version/2020-03-01.

   • The page should have Additions, Changes, and Fixes sections where appropriate just as a normal version page would.
   • A see also section should be used to list different names for this version. Use {{cx|!<edition>|[[<edition> Edition <version>]]}} to avoid selflinking.
2. Then create the individual pages (e.g. PlayStation 3 Edition 1.00) with simply {{Console version|<date>}}
   • If the next and prev links are not -1 or +1 from the current version, use |next= and |prev= as appropriate. Leave them empty to hide them.
   • Additional information can be added after the lead by using the second anon parameter in the template.
   • Additional refs can be added using |refs=

It may be useful to add these instructions to the versions style guide.  Nixinova   T   C   08:31, 20 September 2020 (UTC)

---

I have several thoughts and questions:

1. Will each of the editions be splitted into their respective version history? E.g. PlayStation 4 Edition version history.
2. This is just a suggestion, but perhaps would it be better to have the equivalent versions inside an infobox row instead of "see also"?
3. It seems that versions are going to be sorted by the date, shouldn't they be sorted by the date and the equivalent versions like beforehand? (assuming we aren't going with #1)

I think it's important to consider these decisions before making further changes. – ItsPlantseed ⟨₰|₢⟩ 11:43, 20 September 2020 (UTC)

Those issues don't have anything to do with the splitting, though, and are rather what to do with this page after the split. It would probably be better to split this page into at least platform headings with maybe an update name column, but separate version history pages would work too. At the moment I'm not changing the layout of this page when I'm done with splitting a year, except for changing the order of some really confusing instances of the old revision (December being before November just because it was released on one platform earlier etc), so a revamp of this page's layout can come later. I haven't listed the equivalent versions in the infobox as that would have to be done manually either on the content pages or in the template, which is more difficult than just using {{cx}}.  Nixinova   T   C   05:29, 22 September 2020 (UTC)

Splitting is now complete! That took a while.  Nixinova   T   C   05:46, 26 September 2020 (UTC)

I have Minecraft on my PS3, version 1.83 and it says to update to 1.84, the most recent update.

Fix for a crash that would could occur when loading a world or exploring an existing world. Fix for Salmon, Pufferfish or Tropical Fish dropping Cod when killed. Added fixes for crashing issues. Fixed issues with the recently released packs. Added fixes for stuttering/lag issues. Fixed framerate drop issues with Minecraft PS3 1.84. Minecraft 1.84 update added performance improvements. Fixed some players reported glitches. Various other minor bug fixes with Minecraft version 1.84.

Yes, that exists.

--2.83.119.156 18:00, 8 July 2020 (UTC)

The Xbox 360, PS3, PS Vita and Wii U logo images have been deleted! Reupload them now!

--2.83.119.156 11:18, 23 May 2021 (UTC)

The page currently lists 2.00, 2.06 and 2.52 as versions of PlayStation 4 Edition, despite the fact that they are Bedrock versions that just fix 1 or 2 bugs in LCE.

I believe that their inclusion is rather misleading, especially considering the fact that clicking on their links redirects to Bedrock Edition wiki page. 95.220.122.104 20:07, 7 July 2024 (UTC)

While most updates for Xbox One Edition related to bedrock edition are documented on the wiki, the update that it received in September 2017 is not documented anywhere. It seems that 4J did not post a changelog for this update and updates after this one are named as if this update didn't exist. The last update before that was CU49, which was equivalent to TU57 but then the update in November is called CU50. The update that I am talking about made it so that if you click "Play Game" it shows you a pop-up that there is a new version available with a button to download bedrock edition and a button to play Xbox One Edition. If I remember correctly, I downloaded the update on 21th September 2017 (I know that it was a Thursday), though there is a video about the update (https://youtu.be/EUWwDk_0XFo), which was already uploaded on 20th September, so I assume that that's the release date of the update, just like bedrock edition 1.2. (Legacy Console updates were usually released at earlier times of the day than the ones for bedrock.) I am unsure how this update should be called then, since it's essentially an update between CU49 and CU50. Should it maybe be called something like "CU49.1" then? It cannot have an official name, since there is no official changelog, similar to CU59. I remember testing if the update fixed the duplication glitch with pick block (https://youtu.be/BiwDyVj9TZc?t=288) and it didn't. When TU60 was released, I tried it again and it was fixed. And I remember a few months later (presumably in CU50, which is equivalent to TU59 and was somehow released to Xbox One Edition even though it didn't have the features from TU58 at that time?) they changed it so that they tell you they have fixed a bunch of crash issues on bedrock edition when showing the "New Version Available!" pop-up. BugsbugsbugsMinecraftWiki (talk) 16:17, 20 December 2024 (UTC)

I also updated on September 21, 2017. I'm sure the "Download the latest version of Minecraft for FREE!" button has been added to the main menu.--240D:F:2074:4B00:A5EF:874C:43A5:7532 04:32, 1 March 2025 (UTC)

No, the "Download the latest version of Minecraft for FREE!" button was added to the main menu almost 1 year later in CU57, see https://youtu.be/HESK5PXst8U. BugsbugsbugsMinecraftWiki (talk) 11:34, 1 March 2025 (UTC)

How about the name "Xbox One Edition Content Better Together Update"?--240D:F:2074:4B00:40A4:3B20:3B17:8C56 01:53, 2 March 2025 (UTC)

I own Minecraft: Nintendo Edition (Wii U Edition & Nintendo Switch Edition). I have one question regarding the Nintendo Switch Edition. It's a question regarding updates. Mainly the 2018 update for Nintendo Switch Edition. It says that the next version after version 1.0.15 is 1.0.17, but this is not the case. 1.0.16 is the update on June 21, 2018. Check out this page for proof. https://ameblo.jp/micra-eren/entry-12385327947.html Please see 0:47 of the next video. https://www.youtube.com/watch?v=sl6JpnRm4W4 Did you notice? Comparing the ameba and YouTube pages, the ameba page does not have the item ``Download the latest version of Minecraft for free! when you look at the main menu items for Nintendo Switch Edition after the update. On the other hand, there is an item on the Youtube page that says ``Download the latest version of Minecraft for free! It is confirmed that this YouTube version is 1.0.17 and Ameba version is 1.0.16. I don't know the release date of 1.0.17, but since the release date of updates for Nintendo Switch Edition is almost the same as Xbox One Edition, it can be assumed that the release date of Xbox One Edition CU57 https://x.com/4JStudios/status/1032673830697754625, which received a similar update, and Nintendo Switch Edition 1.0.17 are the same. By doing so, we know that the release date of Nintendo Switch Edition 1.0.17 is August 24, 2018.--240D:F:2074:4B00:388A:CE1A:B2F9:F6F3 07:25, 5 March 2025 (UTC)

What you are saying might be true but there is no hard evidence for it. Your comment is just an assumption, and assumptions don't go on the pages. - 👁 Image
StizzurpXDD^(talk) 07:31, 5 March 2025 (UTC)

Hm, changelog does say .16 is the June 21 version https://www.minecraftforum.net/forums/minecraft-editions/minecraft-nintendo-switch/mcswitch-discussion/2822437-minecraft-switch-edition-patch-change-logs  Nixinova   T   C   08:12, 5 March 2025 (UTC)

The build number for Patch 16 (1.0.16?) was 1.12.1913.0 if I remember correctly, and the build number for 1.0.17 (latest version) was 1.12.1920.0 when I checked. If I remember correctly, I think it was updated from 1.0.16 to 1.0.17. The contents seem to be an update to the Bedrock Edition upsell message, an internal change to the data transfer for Update Aquatic for Wii U Edition, and an item "Download the latest version of Minecraft for FREE!" was added to the main menu and options menu. In general, this version was the same as the Xbox One Edition CU57. Note that the patch changelog is Patch 16, not 17.--240D:F:2074:4B00:616A:4D29:5E46:596A 08:41, 5 March 2025 (UTC)

As expected, the update number on June 21, 2018 was 1.0.16. https://www.nintendo-insider.com/minecraft-nintendo-switch-edition-update-1-0-16-adds-the-incredibles-skin-pack/ There is no information about 1.0.17, but it is likely that it was released on the same day as Xbox One Edition CU57.--240D:F:2074:4B00:616A:4D29:5E46:596A 09:51, 5 March 2025 (UTC)

• PS4

Regarding PS4, there is no mention of 1.99, the release date is December 10, 2019, and "Launch New Minecraft" has been added to the main menu. And now, 2.06. The release date is April 15, 2020, and the button to transfer from PS3 and PS Vita to PS4 has been removed from the world selection screen.

• Xbox One

The version is unknown, but it was released on September 20, 2017. The main content was the addition of a screen to choose whether to play the Xbox One Edition or Bedrock when playing a world.

• Switch

This version, 1.0.16, was released on June 21, 2018. The content is almost the same as TU66, except that a screen has been added to choose whether to play the Switch Edition or the Bedrock Edition when playing a world. This version is different from 1.0.17, and I think this version was released shortly after the Bedrock Edition for Switch was released. I think the contents were the addition of a "Download the latest version of Minecraft for FREE!" button to the main menu and internal changes to the transfer of save data from the Wii U Edition. Sorry if I'm wrong. If I remember correctly, it was August 24, 2018. The build was 1.12.1920.0.--240D:F:2074:4B00:10B3:5F58:7945:2DF9 23:52, 19 March 2025 (UTC)

For more information, please see ja:ユーザー:EmpyreanSquid83/Sandbox.--EmpyreanSquid83 (talk) 08:08, 1 April 2025 (UTC)

Hello, I see that there are many edits being made where bedrock versions that made changes to the playstation 4 edition are being added and removed (e.g. 1.99 or 2.52). Is it useful to use the build number (1.12.????) of the playstation 4 edition for these updates. If necessary I can create separate pages for this build. Xbox Villager (talk) 08:55, 15 April 2025 (UTC)

I think the contents of 2.06 are almost the same as 1.84.--20px EmpyreanSquid83（トーク / 投稿記録） 06:05, 19 April 2025 (UTC)

What do you even mean with that awnser and how does that matter??? Xbox one edition cu59 has its own page even though it only removed one button in the options menu. Also a lot of java edition en bedrock edition versions that only fixed like one bug also have their own page. Xbox Villager (talk) 15:56, 19 April 2025 (UTC)

👁 Image
 Oppose. They're already part of Bedrock Edition. If we split these two pages, then we’d have to split all the other Bedrock version pages as well. -- Leo768 (talk) 00:05, 6 August 2025 (UTC)

User says it exists. Can this be corroborated?  Nixinova  T ⁄ C  11:59, 6 June 2026 (UTC)

Retrieved from "https://minecraft.wiki/w/Talk:Legacy_Console_Edition_version_history?oldid=3613150"