Talk:Legacy Console Edition version history

Splitting into separate pages for each update?
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 /CU /PS . If one update is only for one or two platforms, just make the title Console Edition CU /PS  or Console Edition PS . 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 /CU /PS  but have a redirect for each version number. TU , CU , 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)

2019
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)


 * . Would lead to too many redirects and too many links to fix. -BDJP (t 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 Nixinova sig1.png Nixinova sig2.png 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 per my comment above, and I also disagree with making pages just to redirect to such versions prior to 1.85. -BDJP (t 20:50, 7 March 2019 (UTC)
 * 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)


 * 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 Nixinova sig1.png Nixinova sig2.png 03:07, 30 March 2019 (UTC)


 * , 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)


 * 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 Nixinova sig1.png Nixinova sig2.png 07:01, 21 April 2019 (UTC)


 * per BDJP. 174.252.195.18 09:41, 21 April 2019 (UTC)


 * 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)


 * per above. 64.134.162.32 17:40, 22 April 2019 (UTC)
 * Note that this is this user's first and only edit.  Nixinova </b> T</b> </b> C</b> </b> 04:49, 1 January 2020 (UTC)


 * 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)

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)

Subpage transclusion idea
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 s 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</b> </b> T</b> </b> C</b> </b> 04:54, 1 January 2020 (UTC)


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


 * per my comment above. -BDJP (t 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</b> </b> T</b> </b> C</b> </b> 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. <b style=background:#0800aa;padding:2px> <b style=color:white>Nixinova</b> </b><b style=background:#006eff;padding:2px> <b style=color:white>T</b> </b><b style=background:#00a1ff;padding:2px> <b style=color:white>C</b> </b> 23:15, 18 April 2020 (UTC)