Difference between revisions of "Minecraft Wiki talk:Projects/Renaming"

From Minecraft Wiki
Jump to: navigation, search
m (Undo revision 1153401 by Dentedharp90041 (talk). guess not)
(→‎Project's next step: Added clarification re 4J and naming)
Line 291: Line 291:
::: Isn't it? I haven't done a lot of new version updates, but I have the impression it involves something like a couple of dozen pages and that the individual edits are all different, so barely noticeable individually. That seems very different from updating a small number of phrases and abbreviations repeated on hundreds of pages, most with the high visibility of a wikilink. That's why I'm worried that a lot of readers will be bothered by seeing our work half-baked. But then I'm very alert to PE-specific info since I only play Win 10 Edition, so I suppose I might have a skewed viewpoint. – [[User:Auldrick|Auldrick]] <small>([[User talk:Auldrick|talk]] &middot; [[Special:Contributions/Auldrick|contribs]])</small> 04:51, 5 August 2017 (UTC)
::: Isn't it? I haven't done a lot of new version updates, but I have the impression it involves something like a couple of dozen pages and that the individual edits are all different, so barely noticeable individually. That seems very different from updating a small number of phrases and abbreviations repeated on hundreds of pages, most with the high visibility of a wikilink. That's why I'm worried that a lot of readers will be bothered by seeing our work half-baked. But then I'm very alert to PE-specific info since I only play Win 10 Edition, so I suppose I might have a skewed viewpoint. – [[User:Auldrick|Auldrick]] <small>([[User talk:Auldrick|talk]] &middot; [[Special:Contributions/Auldrick|contribs]])</small> 04:51, 5 August 2017 (UTC)
:::: Hey folks- we actually need to NOT call it "Bedrock Edition" because there is no Bedrock Edition. It's most certainly not Minecraft: Bedrock Edition. This will confuse people who will look for it in the stores & not be able to find it because that's not the name. Or who think there's a different version. Also, for everything but Xbox (& Switch later), there wasn't a relaunch- the edition names just got dropped. I do agree that we need to put a qualifier. Why not just Minecraft Bedrock & when it's referred to in text have it Minecraft (Bedrock). The whole point is that everything running Bedrock proper (not Education Edition or DS as they are special snowflakes) doesn't have an Edition name with it. --[[User:HelenAngel|HelenAngel]] ([[User talk:HelenAngel|talk]]) 01:47, 3 October 2017 (UTC)
:::: Also I can confirm that 4J Studios is working with Bedrock. --[[User:HelenAngel|HelenAngel]] ([[User talk:HelenAngel|talk]]) 01:47, 3 October 2017 (UTC)
== Page prefixes ==
== Page prefixes ==

Revision as of 01:47, 3 October 2017

Moving pages

I believe that we would need to move the PC version pages, since they do not currently specify a version. For example. 1.12 would be moved to "Java Edition 1.12", and Minecraft would need to be moved to "Java Edition". The BlobsPaper JE2 BE2.png 13:28, 13 June 2017 (UTC)

Before doing this we should have a working updated version of {{version link}} ready to go.
And a to-do list to work from.
And for the major versions, that idea works, but I suggest it's unnecessary for the snapshot pages, just because I don't anticipate snapshot names being duplicated or causing confusion, what do people think? – Sealbudsman talk/contr 14:21, 13 June 2017 (UTC)
We would need an admin to edit the page, since it is used on the main page. We may also want a bot to move the pages. Majr, can you do the task. The BlobsPaper JE2 BE2.png 04:06, 14 June 2017 (UTC)
We may need to ask permission from the Admin before starting this project. Skylord wars (talk) 14:05, 15 August 2017 (UTC)
Majr is already part of this project. --Pepijn (talk) 14:14, 15 August 2017 (UTC)

The "standard"

So I saw this:

"Right now we have it so Java Minecraft is the standard, normal Minecraft, and everything that's on the MCPE game we're just calling Pocket, and marking those as exceptions. To match what Mojang/Microsoft are doing, we should change the language, I think, so that the MCPE game is just the normal Minecraft, and treat Java Edition differences as the exceptions. Of course I'm not suggesting a whitewashing; Java's historic precedence would be preserved in things like History sections, or articles that talk about the history of the game like Minecraft itself." – Sealbudsman talk/contr 00:48, 13 June 2017 (UTC)

I can agree with not treating pocket or console editions like "exceptions" anymore, but I want to take it a step further and don't treat any edition as an exception or the "standard". Just always specifying what version you're talking about makes things so much easier IMO, for both the editors and the readers. It means that we should probably establish a standard order of editions though, which is a whole other topic. --Pepijn (talk) 15:51, 13 June 2017 (UTC)

I agree. As a user of Windows 10 Edition exclusively, I have often felt twice mildly snubbed when reading the wiki, first that Java Edition was the standard against which everything is compared, and second that the shortening to "Pocket Edition", while entirely reasonable for brevity, relegates W10 Edition to little brother status. I expect many Classic players will similarly take the rebranding of Classic to, in effect, the other Minecraft as a touch demeaning; we needn't rub their noses in it. But on the other hand, establishing a standard order of editions serves a useful purpose: Users can more quickly find the information they're looking for if the layout is conventional. The question is, is there a way to do this without implying a hierarchy of importance? I would suggest listing editions in audience size order in prose, and in alphabetical order in history sections, tables, infoboxes, and other non-prose areas. Assuming we adopt JE to replace PC, it would be listed before MC, which would help keep things balanced. It would also eliminate a lot of rearranging, especially of the bits that are hardest to edit (as in did I cut the "|-" before the table entry, or the one after it?). – Auldrick (talk · contribs) 16:59, 13 June 2017 (UTC)
Agreed. Well said, both of you.
I would even say that part of avoiding the "snub" might be, being thoughtful about how we rename the version pages (see discussion above). Does literally every PC version page need to have "Java Edition" on it, or just those particular ones where there could be a confusion? Does that create a hodgepodge, or is there a rhyme or reason to it? Something to explore I think ..
For the order of things, I like what you say, but, how about in history, what if we just did it in chronological order of which edition got which feature? So in Stone, it would be Java, Bedrock, Console, but in Observer, it would be Bedrock, Java, (eventually Console last), and in Fireworks it would be Java, Console, (eventually Bedrock last)?
Note on table rearranging: if you use Visual Editor, it's so much easier to manipulate tables -- though I would advise, first, always switch to edit source mode (for instance I did this here: Special:Diff/1109656) because Visual Edit will screw up lots of things if you're not careful. – Sealbudsman talk/contr 19:02, 13 June 2017 (UTC)
I have suggested the equality idea independently on the community portal yesterday, without being aware of this topic.
Sealbudsman, who said that we need to list editions exactly one after another? History section uses a table, why not compose it into three columns? Then we can place all versions with changes to the item chronologically; in beetroot’s case, for example, some parts of the history table related to PC/Java or console editions would be empty in places refering to the time when beetroot was only exclusive to Pocket (Portable) Edition. If you didn’t understand that messy speech above, here is what I mean:
Portable edition Java edition Console edition
0.8.0: Added beetroot.    
0.1x.0: add something here 1.9: Added beetroot. add something here
But revising the {{History}} template should be discussed on that template’s talk page, of course. — NickTheRed37 (talk) 13:54, 15 June 2017 (UTC)
Not a good idea. The problem with listing everything chronologically is that currently there are no dates in the history sections, so the first step in replacing them would be to tag each entry with a date followed by marging them–manually–into chronological order. It would be a huge amount of work to do this to all the histories. Furthermore, the resulting table would have a lot of blank cells making it ugly in my opinion: There would be years of history for Java Edition before you started getting entries in other columns, and from there on it would only have one filled cell per row (a so-called 'sparse array'). Finally, I don't think many people would find it very useful. The only information it makes clearer is how features evolved in one edition with respect to another, which is more of a curiosity than the kind of information most readers would be searching for. – Auldrick (talk · contribs) 04:34, 17 June 2017 (UTC)
The history is already listed chronologically. You don't need specific dates to make something chronologically ordered, nor do we have to match the different columns by their dates (which would cause a lot of empty space on the top of the console and bedrock codebase editions). --Pepijn (talk) 10:17, 17 June 2017 (UTC)
I beg to differ. What we currently have is three separate chronologies, listed serially in one table. We were discussing how to sequence those three chronologies. NickTheRed37 recommended a single merged chronology with all editions on a single timeline. His sample even shows the resulting empty space above the console and bedrock entries you object to. You certainly do need specific dates to merge a set of chronologies, although I guess it would make sense to start by making a merged timeline of the releases and builds and then using that to order the merged history. Even so, it would be a lot of work that adds no additional information and results in a table littered with blank cells. – Auldrick (talk · contribs) 11:25, 17 June 2017 (UTC)
I wasn't talking about what Nick meant, I was talking about how I think we should solve this: 3 separate chronologies in parallel to avoid putting one edition above another. I think we really have to stop working with a "standard" and "exceptions" when it comes to the different editions. We mostly have the Java edition as the main edition on this wiki and it's causing a lot of trouble now. If we make something else the main version, it can happen again. --Pepijn (talk) 11:43, 17 June 2017 (UTC)
Sorry, your indentation made it look like you were replying to my comment. We're in complete agreement about not having a "standard" version. I do prefer to maintain the current sequence of the histories, though. – Auldrick (talk · contribs) 11:50, 17 June 2017 (UTC)
I can see that, I should have made it more clear. The main "fear" I have with listing the editions in serie is that for some pages the Java section of the history is going to become really long over time, pushing any editions beneath it very far down (which is kind of annoying for players who want to look up something in the history for those editions). Maybe we should add anchors to the history template? That way we can have links to the specific editions just in case the history table becomes really long. --Pepijn (talk) 11:58, 17 June 2017 (UTC)
I was also thinking about the anchors. Another possibility would be collapsible sections, which would make finding the history for a particular codebase easier and would reduce the wiki server load for some pages. – Auldrick (talk · contribs) 12:06, 17 June 2017 (UTC)

We seem to be in agreement that we don't want to suggest a supremacy of Minecraft over Minecraft: Java Edition. Unfortunately, I think the official names are going to make that troublesome in some cases. I'm specifically thinking about uses of the {{only}} template to generate ‌[Pocket Edition only] or ‌[Pocket and Legacy Console editions only]. Do we want those to read[Minecraft only]? I'm not sure it's clear that the embedded use of italicized Minecraft will be clear enough, but what would be better? Would[Non-Java Minecraft] work? How should the title text (hover hint) read? Keep in mind that this question's scope isn't limited to {{only}}; it applies to mentions of Pocket Edition etc. in straight prose as well. – Auldrick (talk · contribs) 05:59, 17 June 2017 (UTC)

I am opposed to the fact that the Java Edition will occupy the top position, even if they changed the main edition. I personally think the Java Edition history on the first place is better, but not that consistent. Sure, if we want all the editions to get their own pages, but the order must be changed independently.
The "Minecraft" is definitely not clear enough to be italicized, but I also disagree if the Unified Minecraft considered as an edition. By the fact that the new Unified Minecraft will not have a suffix, we can't deny that they are going to change the main edition. We can just have Console and Java for {{only}}, and the statement about "Minecraft" will be stayed without any tags or notes. – ItsPlantseed|⟩ 08:50, 17 June 2017 (UTC)
I don't really understand what you're trying to say in the first part, what top position? What first place? What order?
I can agree with Minecraft not being a good name for an edition on the wiki. The thing I can suggest is "Bedrock" (which has been suggested above already, which you apparently haven't read?), since that seems to be the name they gave the engine. --Pepijn (talk) 10:17, 17 June 2017 (UTC)
But will "Bedrock" be meaningful to our readers? It's a technical term that has only recently been used among the developers and those like us closely watching them. I'm not confident it will ever enter common use given that Microsoft and Mojang call it Minecraft, and that "bedrock" already has a firmly established denotation in the Minecraft context. Most of the wiki readers are still in grade school, after all. They take their usage from YouTube and Xbox Online, and so far those platforms are rarely using "Bedrock" to refer to the cross-platform version. – Auldrick (talk · contribs) 11:25, 17 June 2017 (UTC)
I prefer it over treating any edition as a "main" edition, and the other editions as exceptions. I understand that readers might not know what the term means initially, but the news outlets covering this topic also used this term (the ones I read anyway). If people don't understand it, they can click the link that comes with [Bedrock edition only] (or something like that). --Pepijn (talk) 11:43, 17 June 2017 (UTC)
Forgive me if my wording was/(is) looked weird to you, at the first line I'm trying to say the history part. Secondly, I was telling about the "Minecraft" (bedrock-based editions), I just stated above that I kinda disagree if the bedrock engine edition is considered as an "edition", so we can only have Console and Java Editions for the {{only}} template, and any kind of statement about "Minecraft" will be stayed without any tags or notes. – ItsPlantseed|⟩ 13:17, 17 June 2017 (UTC)
That would suggest that "Minecraft"/"Bedrock" is the standard and main Minecraft game, which I and most others here want to avoid. It creates confusion when people who are not familiar with this new way of handling information, read something that exists only in the Bedrock "edition" and they're going to assume that it exists in other editions as well because it's not stated specifically. Specifying exactly what is in what edition makes things so much easier for both the editors and the readers. --Pepijn (talk) 14:02, 17 June 2017 (UTC)
Hey folks, just wanted to weigh in here given that I've been thinking about this issue a lot. Bedrock is a name that we're going to be using frequently and the console community has already latched on to this name to differentiate between console editions that will get 1.2 and the ones that won't. Based on this, and from what I've already picked up in the various communities, my suggestion (which you can take or leave, of course!) is for Computer Edition to be renamed to Java Edition, Pocket Edition to be renamed to Minecraft (Bedrock), Console Edition to be renamed to Legacy Console Edition, and a separate section for Education Edition (which while technically powered by the Bedrock engine has different features, releases, etc. and we are considering it a separate edition). Under Education Edition we can also build out pages for the modules that come with it such as Code Connector & Classroom Mode. By grouping them like this, it also makes it scalable if, for instance, (and this is purely an example- not saying this is happening) we come out with an edition based on Bedrock but only runs on robots. If it has cross-play it could go under Minecraft (Bedrock) but if you couldn't cross-play, it would need to be Minecraft: Robot Edition and under its own section. --HelenAngel (talk) 00:37, 23 June 2017 (UTC)
I was already hoping you would hop in here sometime to share your views. Sounds all good to me but I have a question about the Education Edition (I have zero experience with it). How different is Education Edition? Is it completely the same as Bedrock for shared features (so not taking the totally exclusive Education Edition features into account)? If it is, we might not need a different section for it on pages (we could get away with just having a page for it and a {{education}} template on the pages about the completely exclusive features, basically like we have it now). --Pepijn (talk) 01:15, 23 June 2017 (UTC)
Thought about it a bit more and it has some problems with our current visions on the reformatting. The current idea is to have sections for the different editions on pages so it's clearly stated which piece of information belongs to which editions (and possibly have a way of only showing sections of interest to the viewer using CSS). Using the "Minecraft (Bedrock)" section only for the cross-play editions means that we would have a lot more sections for all the editions, even though for shared features they would have the same information (I think). So maybe we should use "Minecraft (Bedrock)" as a name for the page but name the section that we would have on each page something that includes all bedrock engine editions? This is all under the assumption that shared features between all bedrock engine editions are completely the same. --Pepijn (talk) 02:03, 23 June 2017 (UTC)
If we use the term "Minecraft (Bedrock)" to refer only to the cross play editions, what would be a good term for all Bedrock Engine editions, including also Education Edition, Fire OS and Fire TV and whatever else doesn't get cross play? – Sealbudsman talk/contr 01:46, 23 June 2017 (UTC)
HelenAngel It would be greatly appreciated if you could clarify whether Fire OS and Fire TV will gain cross play (I assume they probably will do). If so, it shouldn't be an issue as we can use that name for all Bedrock Engine Editions (Helen Angel stated below that they treat the Education Edition as a separate version). I would be happy with Minecraft (Bedrock) as the edition identifier, replacing the pocket edition name in pages, history table etc. E.g. Pocket Edition 1.2 would be moved to Minecraft (Bedrock) 1.2. GoandgooTalk
06:46, 24 June 2017 (UTC)
Not a fan of a parenthesised prefix. For the edition page, then it's not so bad (although it does make it look more like a disambiguation of Minecraft), but as a prefix for the version pages it doesn't look good. I'd much prefer just "Bedrock Edition", which also lends itself to the natural abbreviation: BE, to go with JE, and CE (or LCE now, I guess). I would be okay with completely separating edu from bedrock, if it has a completely different release timeline, and thus wouldn't make sense to group with the bedrock version pages. We don't necessarily have to duplicate the bedrock version pages either, if the releases are equivalent to a previous bedrock release, we can just point to the changes there, and note any differences. As for Legacy Console Edition, are there going to be other Console Edition versions which need to be distingished from the "legacy" ones? If not, I don't see much of an advantage to the new name, as long as the console edition page makes it clear that it is considered legacy. That being said, with its combined version page, it's certainly a lot easier to rename it. MajrTalk
10:13, 24 June 2017 (UTC)

Thinking about it, I do believe Bedrock Edition is probably the best way to go to simplify things. We have to remember that the name "Console Edition" was never an official name that 4J studios or Microsoft used and was just the name that was chosen for the wiki. Therefore we could use Bedrock Edition in the same vein. The only problem is that unlike the name "Console Edition" which is fairly self-referential, Bedrock Edition may not be as familiar to the layman.

I do however prefer Legacy Console Edition for the existing 4J Studios version. This would make it clearer for readers using the Xbox One and Nintendo Switch, and potentially other consoles which will probably gain the Bedrock Edition.

For the Education Edition, I think there is probably only a need to create a version page should there actually be updates/features added which differ from Bedrock Edition. I'm not entirely sure, but I believe most of the exclusive features were added in the 1.0 Education Edition release, and hence there would be no point creating a version page for each subsequent version if they simply follow the Bedrock Edition progression. GoandgooTalk
12:21, 24 June 2017 (UTC)

It is confirmed that Fire OS and Fire TV will also have a cross-play access. The Education Edition, I guess we can just redirect the version page into the equivalent version of Bedrock Edition, with a section of differences between two versions called Education Edition on the very bottom of the page. But I'm afraid that there will be an update to EE that have no relation between the two versions. – ItsPlantseed|⟩ 16:21, 24 June 2017 (UTC)
I think we can manage Education Edition as a separate edition even though it runs on the bedrock engine. My initial fear was that there would be more of these types of editions (bedrock but no crossplay) which would have made a bit of a mess. --Pepijn (talk) 17:03, 24 June 2017 (UTC)
Java Edition is just as technical. As long as "Bedrock" in general is adopted as the term by the community, there shouldn't be any confusion between Minecraft (Bedrock) and Minecraft: Bedrock Edition. MajrTalk
04:48, 26 June 2017 (UTC)
Thinking about it, I am starting to lean more towards Bedrock Edition (helps for simplicity sake as well). So currently I support Bedrock Edition and Legacy Console Edition. GoandgooTalk
08:05, 27 June 2017 (UTC)
Education Edition will most likely continue to get features exclusive to it. It is very different from the other editions, so much so that I think it would cause more confusion to associate it with Bedrock since it doesn't have cross-play with any of the other Bedrock titles. It also has Classroom Mode and Code Connector which are free companion applications that no other edition of Minecraft has, in fact the whole concept of the companion app isn't even applicable to the other versions of Minecraft. I promise sometime soon I'll get some time to sit down and flesh out those pages! :) --HelenAngel (talk) 03:07, 28 June 2017 (UTC)
But are the features that it SHARES with Bedrock different in any way? Is there any page about a feature both in Bedrock and Education where we would need to specify some sort of behavior that only occurs in Education (or only in Bedrock and not in Education)? I get that it's an Edition on its own with all the exclusive features, but our current plan is to associate colored sections to specify what behavior occurs in which edition on pages about features that are in multiple editions but behave differently across them. So would we even need such a section for Education Edition? --Pepijn (talk) 12:26, 28 June 2017 (UTC)
There are features they share, however it is important to note that they are fundamentally very different. For instance, Education Edition does not support cross-play with any other Bedrock editions. Since Education Edition is actually more of a tool/platform than a game, it doesn't have things like the Marketplace, or even in-game patch notes, or an in-game seed picker, or the ability to upload custom skins. The environment is very different as well as it was purposely designed to be as restrictive or as open as an individual educator needs. The game play is not even fundamentally the same- there are additional inventory spaces that can be controlled by the host. In addition, in-game settings allow for rapid changes on-the-fly, including a global pause which is not present in any other version of Minecraft. The login itself is fundamentally different as is the purchasing- it can only be obtained through Windows Store for Education and to even access the game, a person needs to log in with a Microsoft Education account. --HelenAngel (talk) 01:07, 6 July 2017 (UTC)
The history of Minecraft should be Java edition first. Skylord wars (talk) 14:05, 15 August 2017 (UTC)
Please provide arguments. --Pepijn (talk) 14:16, 15 August 2017 (UTC)

Opportunity for CSS stylesheets

At the risk of being shot down in flames, let me mention an idea I've mulled over for some time. It closely parallels what we're undertaking in this project so it should take little additional effort, if any. The idea is this: Could we give edition-specific sections of articles different CSS classes, generated by whatever edition templates we finally settle on to mark the sections? Default stylesheets would produce the same style for each of them, preserving the current look, but users could use custom stylesheets to collapse out information for editions that don't interest them. Maybe we could even let logged-in users choose such a stylesheet in their preferences. With irrelevant editions suppressed, readers would enjoy a smoother reading experience. – Auldrick (talk · contribs) 17:30, 13 June 2017 (UTC)

Interesting, is this something you'd be able to demo somehow? Or is this existing on some other wiki? – Sealbudsman talk/contr 18:37, 13 June 2017 (UTC)
It's been a very long time since I did any CSS, but I'll try to work up something. If there are any CSS gurus reading, hints would be more than welcome. – Auldrick (talk · contribs) 18:41, 13 June 2017 (UTC)
By the way, the infrastructure for this is already present. You can see it in your Preferences, at the top of the Appearance tab. There seem to be two levels of stylesheet customization, one for Hydra and a global one. I'll have to research how these are supposed to interact. – Auldrick (talk · contribs) 18:57, 13 June 2017 (UTC)
Gamepedia has now confirmed to me that this is permitted and should be possible. (In fact, they're discussing whether they should try to come up with a more elegant solution, though of course they can't give a timetable for it.) So I'll start working on a demo page now. – Auldrick (talk · contribs) 16:37, 17 June 2017 (UTC)
This is something I've wanted for years (since pocket edition came out, basically), but I've never pursued it because it would require changing basically every page on the wiki. Since we're doing that anyway, now is a great time to implement it. The CSS itself is pretty simple, it's just the implementation details to work out.
In my head, I've always seen it as a drop-down box where you pick your favoured version (placed at the end of the heading using indicators), then the content of other versions are collapsed, showing just a stub saying something like "5 PE version exclusive features" (assuming we were to group the exclusive features together in a section). Additionally, there could be a checkbox to hide other versions entirely. The functionality would just be a simple JS script which sets the appropriate preferences to load the gadgets (localstorage for ip users), same as MediaWiki:Gadget-refTooltip.js already does. The drop-down box could be replaced with checkboxes to allow selecting multiple favourite versions.
Unified/Bedrock Edition only
Since we're encapsulating edition specific information, we can also take the opporitunity to use improved styling. I'm thinking a dashed border in the canonical colour for the edition, perhaps a rather transparent background in the same colour when the section is hovered over, the editions icon and name can be at the top. This paragraph is a simple example of the styling, minus hovering, which can't be done inline.
Small exclusive features in the middle of a paragraph could use similar styling, with a tooltip stating that the highlighted area is exclusive, which replaces the heading in the full paragraph version. This, I think, would look much nicer than the {{only}} tag which we use now. MajrTalk
07:32, 21 June 2017 (UTC)
Can you do a test page to see how that would look? – NixinovaGrid Book and Quill.png Grid Diamond Pickaxe.png Grid Map.png • 07:45, 21 June 2017 (UTC)
Here's an example of section styling. MajrTalk
12:17, 22 June 2017 (UTC)
Looks great. Would we duplicate info that is true for multiple versions and thus use 3 sections on almost every page (since the CSS idea is to only show stuff for the editions you're interested in?) or have other sections for general information true for all editions and just specify what is different in the appropriate sections? --Pepijn (talk) 16:11, 22 June 2017 (UTC)
It's looking great, but I wonder how it is for articles with only minor variations between versions. For your test there you've used the different crafting methods on each platform, however how would it work for pages where there are minor variations between versions - Dye is an example of this. How would this work to eliminate duplication of information so that the same information isn't repeated three times on each page? GoandgooTalk
05:06, 23 June 2017 (UTC)
I added examples of "inline" references, for minor variations. However the issue that occurs to me now, is how to display features exclusive to a couple of editions, a.k.a "Unified & Java Editions only". Perhaps a multi-colour border/striped gradient background? (border example) This would still limit us to 2 editions with the same feature. A 3 colour border seems quite difficult to do, unless they are layered rather than overlapping. MajrTalk
06:16, 24 June 2017 (UTC)

I think it definitely looks much cleaner than what we have currently with the only template. Regarding the exclusive features in multiple editions, I think the dotted border looks pretty good. We only need to have a 2 colour border as the maximum as there essentially are only three version types anyway. So all in all we'd have the following border types:

  • Minecraft (Bedrock) only - orange
  • Java Edition only - green
  • Console Edition only - blue
  • Minecraft (Bedrock) & Java Editions only - orange and green
  • Minecraft (Bedrock) & Console Editions only - orange and blue
  • Java & Console Editions only - green and blue GoandgooTalk
    07:00, 24 June 2017 (UTC)
I guess we'll have to see what we decide on, what with education edition, and potential other non-unified bedrock editions causing issues.
I thought I should note, it occurred to me that this design should work fine for platform specific features too, as we can keep the colour for the parent edition, and just change the title to specify the platform(s) it applies to (and put a platform logo in for good measure). Also, for the inline references, I don't plan to have those hidden in any way, unless we can implement it in a way that work break the flow of the sentence. It may be possible to allow hiding with list entries, however. Although in the demo above, that would just leave a single list entry, which would look odd. Maybe it will just have to be enabled on a case-by-case basis. MajrTalk
10:20, 24 June 2017 (UTC)
I asked HelenAngel on Twitter, she said all Bedrock Editions are gaining cross play with the exception of Education Edition, so I think it still stands that we have three main versions/editions of Minecraft. Regarding hiding version-specific features - is this something that we can do retroactively? Could we convert everything to this new style and then later on decide whether it's possible to only show info for Java Edition for example? GoandgooTalk
01:32, 25 June 2017 (UTC)
I'm not sure what you mean. Hiding specific editions would be a user preference, the only thing we would decide is just how hideable things are. Hiding edition-specific information within a sentence (or list) could make the sentence awkward, so it likely wouldn't be hideable, or would require individually specifying that it can be hidden (and thus write the sentence in a way which still makes sense when part of it is missing). Sections should always be hideable, as they should always be distinct from the rest of the article, and won't be missed if they disappear. However, we could also make sections not hideable in individual cases if that were to make sense somewhere. MajrTalk
05:01, 26 June 2017 (UTC)
Now that we've established the Education Edition is essentially a separate edition, when would we be able to start implementing this? It could sit alongside {{only}} until pages have fully converted over to the new format. I see that Sealbudsman has been updating computer edition to Java Edition and having this template ready would be able to further assist with this process (this template could automatically apply the relevant Edition specific categories without them manually being added). As above, I believe we can have the following different border types:
  • Bedrock Edition only - orange
  • Java Edition only - green
  • Console Edition only - blue
  • Bedrock & Java Editions only - orange and green
  • Bedrock & Console Editions only - orange and blue
  • Java & Console Editions only - green and blue
  • Education Edition only - grey?
I don't think there's a need to consider any more combinations with the Education Edition, as that version contains specific additions while still sharing the bedrock codebase. GoandgooTalk
06:05, 8 July 2017 (UTC)
I agree with you about Education Edition.
As an update, I've been just using search results for "computer edition" and for "computer version" to find pages to switch to java / add 'specific information' categories that aren't already using "only" tags (or where it would be awkward to do so). Still to-do is that there are 70-some "pc edition" pages and 70-some "pc version" pages which need the same thing. – Sealbudsman talk/contr 07:30, 8 July 2017 (UTC)
I ran into some issues with the colours, as the green and blue were too similar, and were hard to distingish in the border, additionally, I couldn't find a way to have two background colours which didn't look awful, so I ditched it entirely. I tried changing console to purple, but weirdly it looked cyan when next to the green, so I ended up changing it to yellow. You're welcome to suggest alternative colour schemes, I added a test of all the variations. As for education edition, we could steal blue from console now, which makes more sense since education edition logo is blue. MajrTalk
12:44, 8 July 2017 (UTC)
Would it be possible to use darker colours, at the moment I feel that the light colours of the borders blend in too well with the page background colour. Also, I feel like what made the previous test really stand out was the different coloured shading, is there any way we could somehow keep that without making it confusing? Perhaps another idea is to use solid colours for when a feature is exclusive to one edition and the dotted border if it is not in a certain edition? Just throwing different ideas out there.
Another thing to keep in mind is that the legacy console edition seems likely to be ultimately phased out in favour of the bedrock edition, so this could simplify things somewhat. GoandgooTalk
14:00, 3 August 2017 (UTC)

Exclusive features pages

What should happen to the Pocket Edition exclusive features page? What about a Java Edition exclusive features page? I think both should still exist in some form. GoandgooTalk
05:00, 14 June 2017 (UTC)

Well since PE is now the main version *sigh* I think Pocket Edition exclusive features should be removed and Java Edition exclusive features should be created. – NixinovaGrid Book and Quill.png Grid Diamond Pickaxe.png Grid Map.png • 05:09, 14 June 2017 (UTC)
 Oppose, nothing is the "main version". See this discussion. IMO, we should have a Minecraft (PE, Win10, new Xbox/Switch), Java Edition and Console edition (Playstation for now atleast and the old console editions) exclusive features page. --Pepijn (talk) 11:56, 14 June 2017 (UTC)
 Neutral. I see the way you were saying, but is it needed anyway? Currently, the wiki doesn't have exclusive features page for Java Edition, and almost the features that were listed on Pocket Edition exclusive page are not transferred yet onto the related page. So I think the same thing should happen for Java Edition after the Better Together Update was released. – ItsPlantseed|⟩ 14:10, 14 June 2017 (UTC)
I meant that we shouldn't see anything as the main edition anymore, so I'm fine with no "exclusive features" pages at all. But if we make/have one for one edition, we should have them for all the others. --Pepijn (talk) 17:03, 14 June 2017 (UTC)
There are always going to be features that only appear in one version. One example is putting potions in cauldrons. The BlobsPaper JE2 BE2.png 01:22, 15 June 2017 (UTC)
True, but the question is if we want/need a separate page for them. --Pepijn (talk) 07:05, 15 June 2017 (UTC)
What about a single Exclusive features page, with sections for all three? – Sealbudsman talk/contr 14:29, 14 June 2017 (UTC)
 Oppose That would make the page too complicated. The BlobsPaper JE2 BE2.png 14:35, 14 June 2017 (UTC)
That's fair, I could see that. – Sealbudsman talk/contr 21:00, 14 June 2017 (UTC)
I think exclusive features of Pocket Edition should continue. Skylord wars (talk) 14:06, 15 August 2017 (UTC)

Exclusive template

I made a template for exclusive features, based off User:ItsPlantseed's on Template talk:Desktop: Template:Exclusive. Example of the template:

Legacy Console Edition.png
This feature is exclusive to . 

NixinovaGrid Book and Quill.png Grid Diamond Pickaxe.png Grid Map.png • 05:56, 15 June 2017 (UTC)

Should we use this instead of {{desktop}}, {{pocket}}, etc? – NixinovaGrid Book and Quill.png Grid Diamond Pickaxe.png Grid Map.png • 06:51, 24 June 2017 (UTC)
I think this is a template we could definitely use, but I think we should decide on the name of the Bedrock Edition (as above) first before using this. GoandgooTalk
06:53, 24 June 2017 (UTC)

Category:Computer edition specific information

When {{only}} was changed to output "Java Edition", it caused the pages in this category to instead be added to Category:Java edition specific information. That is, all except 4 pages: Blaze Powder, Carpet, Item (entity)/ED, and Jukebox still appear on the old category page and not on the new one. It's as if they were still using the old version of {{only}}. I can't figure out why. The templates seem to be correct. Category maintenance is a real-time function of MediaWiki, isn't it? Can anybody explain this? – Auldrick (talk · contribs) 20:20, 18 June 2017 (UTC)

@Auldrick: Editing categorizing templates doesn't apply category changes immediately for all pages.
An easy fix - go to the affected pages, and perform a null edit - open the editor, don't change anything (except edit summary and checkboxes - these are ignored, except watchlist - pages will be added there if you don't uncheck) and save. Nothing will be added to history or RC. It's basically a purge that also affects categories. I've done that for the 4 pages you linked already. (Or you can just wait, the category should be updated at some point.) --Hubry (talk) 11:36, 19 June 2017 (UTC)

Main page

I think we're all in agreement that the wiki needs to be reoriented to not favor the computer edition. Our intent has been to fix this as part of this project, since the project will touch so many pages, but in reality the reorientation effort doesn't depend on the release of the Better Together update: It can begin right now, and the more reorientation work we do ahead of time the less chaos we'll have when the update comes out.

I've been looking at the Main Page Minecraft with this in mind. The orientation is there, in both subtle and obvious ways. I propose to split out the Java-specific information into a new Computer Edition page (which currently redirects to the Main Page Minecraft). Then, when the update comes out we can simply move it to Java Edition (currently also a redirect to Main Page Minecraft). Until then, we can start fixing wikilinks to go to one or the other depending on which page is implied by the context. We can get a lot of this project's work done in advance this way.

Since we're talking about updating the Main Page, I'm looking for consensus on this plan. If I get it, I volunteer to split the main page Minecraft and present the results for review by the community before changing Main Page/editcopy it. I'm also asking for opinions on whether to create a new project to cover the reorientation, or to keep it within this project. – Auldrick (talk · contribs) 15:58, 19 June 2017 (UTC)

Edit: One more thing: It's likely the reorientation won't be finished before the Better Together update comes out. If we create a project for the reorientation, it should be merged back into this project at that time. – Auldrick (talk · contribs) 16:26, 19 June 2017 (UTC)

One moment: Computer Edition and Java Edition actually redirect to the Minecraft page, a separate page from the Main Page. – Sealbudsman talk/contr 16:12, 19 June 2017 (UTC)
Arghhhh! I can't believe I did that! Fixed now. – Auldrick (talk · contribs) 16:18, 19 June 2017 (UTC)
 Support! I think keeping it within this project would be fine. Maybe just make a bullet point for it on the project page. – Sealbudsman talk/contr 19:22, 19 June 2017 (UTC)
 Support One thing I would question is starting with the name "Computer Edition", since it is already called the Java Edition. The BlobsPaper JE2 BE2.png 00:25, 20 June 2017 (UTC)
I went with Computer Edition because it has a history of usage and because the name Minecraft: Java Edition isn't official yet, but I like your idea better. After all, M&M have announced the name, so there's virtually no chance it'll change. What do we do with Computer Edition then, leave it as it is or redirect it to Java Edition? (Java Edition will have an {{about}} for linking back to Minecraft.) – Auldrick (talk · contribs) 01:40, 20 June 2017 (UTC)
The name "Java edition" is pretty official already. The latest Minecraft news articles on minecraft.net have used that term to describe the edition. Since Computer Edition is a bit confusing (considering Minecraft Bedrock edition will also be available on computers with Windows 10) and not as official we should use Java edition instead. --Pepijn (talk) 01:48, 20 June 2017 (UTC)
Does that mean you would favor deleting Computer Edition at some point? It's a redirect, there are only about 10 pages that link to it (and those should be changed anyway), and it has never been edited, so it doesn't seem like that big a deal. – Auldrick (talk · contribs) 03:30, 20 June 2017 (UTC)
Maybe make it a disambiguous page directing users to either the Java Edition page or the Bedrock(or whatever) edition page because of Win10? Once those pages exist of course. --Pepijn (talk) 03:37, 20 June 2017 (UTC)
I would keep the redirect because "Computer Edition" usually refers to the Java Edition.
@PepijnMC: We could put {{redirect}} on the Java Edition page. The BlobsPaper JE2 BE2.png 03:45, 20 June 2017 (UTC)
That would kind of suggest that the Java edition is the main edition for the computer, which can be pretty subjective and other topics on this talk page have been talking about avoiding these things. IMO it's better to completely get rid of and avoid any favoritism towards any edition so we don't have to change a ton of small stuff in the future (like we have to do now). --Pepijn (talk) 03:57, 20 June 2017 (UTC)
I think just making the page Java Edition would be the best option to prevent having to redirect the page in the future. I think replacing all instances of Computer versions on the wiki with Java Edition is something we can do immediately before the Better Together version has been released. I would even support moving all computer version pages to be preceded with Java Edition, however what should happen to all the Pocket Edition pages (including all Pocket Edition version pages?) Clearly the Pocket Edition label is no longer sufficient. GoandgooTalk
06:11, 20 June 2017 (UTC)
 Disagree I think that would take a lot of work, and is unnecessary. I think the future cross-platform updates should be "Bedrock Engine/Edition/Whatever 1.x" – NixinovaGrid Book and Quill.png Grid Diamond Pickaxe.png Grid Map.png • 04:23, 21 June 2017 (UTC)
Actually, the Main Page did not treat the Java edition as the Main edition as well as Pocket. Skylord wars (talk) 14:07, 15 August 2017 (UTC)
This topic is about the Minecraft page, it was confused with the Main page by the creator of the topic at first. The Minecraft page did favor the Java Edition, but it has since been updated and a lot of its content has been moved over to the Java Edition page. --Pepijn (talk) 14:21, 15 August 2017 (UTC)

Education Edition

Could we please get a separate section for Education Edition? While powered by the Bedrock engine, it is considered by us (Minecraft Studio) to be a completely separate edition with different features, different uses, etc. I know we have a page for it but I'd like to build it out with more information and differentiate it from all the other versions of Minecraft. --HelenAngel (talk) 00:43, 23 June 2017 (UTC)

That sounds fair, I've made a minor edit and separated out the Education Edition from the Pocket category of the Minecraft template. In terms of where else Education Edition should be displayed, my view is that we probably don't need to really mention it that much outside the articles where it deviates from the Bedrock edition (i.e. we can definitely do more to properly describe them on pages such as Chalkboard). Similarly I don't really think we need to put it in the history templates except for where there are exclusive blocks (again on Chalkboard for example). GoandgooTalk
04:30, 23 June 2017 (UTC)
I feel like the pages about Education Edition aren't as fleshed out because it's a bit more exclusive than the other editions. Most editors (I think) have no experience with it.--Pepijn (talk) 17:06, 24 June 2017 (UTC)
I'm working on it. I've just been completely slammed as of late with all my other work! --HelenAngel (talk) 01:09, 6 July 2017 (UTC)

Which one should I move?

Do I need to move Asset update, Pre-release, Release candidate, Build and Joke update? --Beans1512Talk/Contribs 11:29, 17 July 2017 (UTC)

Project's next step

Now that it looks like the transition to the Bedrock Edition is all but confirmed (see the FAQ on Minecraft.net), are we at a stage where we can start moving and renaming Pocket Edition related pages? I don't see a need necessarily to wait until the edition (version 1.2) actually drops seeing we already have the first betas and it is very clear that the change is happening.

Also are we as a community in agreement with referring to this unified edition as the Bedrock Edition and the previous 4J studios version as the Legacy Console Edition? GoandgooTalk
14:05, 3 August 2017 (UTC)

As eager as I am to get started changing Pocket to Bedrock everywhere, I'm reluctant for the wiki to show a Pocket/Bedrock/PC/Java/Console/Legacy Console mashup for the week(s) it will take to get even the frequently accessed pages updated. It's unprofessional and makes the wiki look like the work of amateurs. [Oh...er...never mind. ;-)]. Besides, it's avoidable with no additional effort.
I'd like to propose a method that not only prevents the chaos but also allows us to get started editing right away with no changes appearing until we're ready and/or the BTU is released. Specifically, we can create some trivial templates to replace the common forms we use to refer to editions in prose and infoboxes. They would be named to make editing fast and easy. For now, they would generate the same text they replace. When the BTU is released, we can update them as shown and Blam! almost the whole wiki changes in an instant. (I imagine we should do it at a non-peak hour to spread out the server load from purging practically the entire page cache at once.) At first glance we would need the following templates:
Template Used in Replaces and generates After BTU generates
{{pelink}} prose and infoboxes [[Pocket Edition]] [[Bedrock Edition]]
{{pelink | <text>}} prose and infoboxes [[Pocket Edition | <text>]] [[Bedrock Edition | <text>]]
{{celink}} prose and infoboxes [[Console Edition]] [[Legacy Console Edition]]
{{celink | <text>}} prose and infoboxes [[Console Edition | <text>]] [[Legacy Console Edition | <text>]]
{{pe}} infoboxes PE BE
{{pe | link=1}} infoboxes [[Pocket Edition | PE]] [[Bedrock Edition | BE]]
{{ce}} infoboxes CE LCE
{{pc}} infoboxes PC JE
{{pc | link=1}} infoboxes [[Java Edition | PC]] [[Java Edition | JE]]
I left out a {{pclink}} template because the change from PC Edition to Java Edition is already well under way. I also left out a {{ce | link=1}} parameter, because I don't remember ever seeing CE linked in an infobox. What else have I left out?
If this idea doesn't fly, I suggest that we at least put a "Pardon Our Dust!" banner on the Main Page explaining why there's so much inconsistency and linking to a (Help?) page explaining which names mean the same thing.
After all that, I guess I don't need to say that I  Support getting started right away and those edition names are fine with me. – Auldrick (talk · contribs) 02:59, 5 August 2017 (UTC)
I see where you're coming from, but personally I'm not too sure we need so many different intermediate templates during this change. It's not that different to when a new version comes out and for a couple hours/days the information needs to be quickly updated en-masse. GoandgooTalk
03:54, 5 August 2017 (UTC)
Isn't it? I haven't done a lot of new version updates, but I have the impression it involves something like a couple of dozen pages and that the individual edits are all different, so barely noticeable individually. That seems very different from updating a small number of phrases and abbreviations repeated on hundreds of pages, most with the high visibility of a wikilink. That's why I'm worried that a lot of readers will be bothered by seeing our work half-baked. But then I'm very alert to PE-specific info since I only play Win 10 Edition, so I suppose I might have a skewed viewpoint. – Auldrick (talk · contribs) 04:51, 5 August 2017 (UTC)
Hey folks- we actually need to NOT call it "Bedrock Edition" because there is no Bedrock Edition. It's most certainly not Minecraft: Bedrock Edition. This will confuse people who will look for it in the stores & not be able to find it because that's not the name. Or who think there's a different version. Also, for everything but Xbox (& Switch later), there wasn't a relaunch- the edition names just got dropped. I do agree that we need to put a qualifier. Why not just Minecraft Bedrock & when it's referred to in text have it Minecraft (Bedrock). The whole point is that everything running Bedrock proper (not Education Edition or DS as they are special snowflakes) doesn't have an Edition name with it. --HelenAngel (talk) 01:47, 3 October 2017 (UTC)
Also I can confirm that 4J Studios is working with Bedrock. --HelenAngel (talk) 01:47, 3 October 2017 (UTC)

Page prefixes

With 1.2 right around the corner, what pages are we going to move, and should someone set up a bot?

Will we be moving Java versions to have a "Java Edition" prefix? Or should they stay at their current title, and have bedrock versions at "Bedrock (Edition)"? What about Legacy Console; will they still be at Console Edition version history or get a separate page?

The Pocket Edition and old (current) Console Edition pages should not be moved, as they are different versions.

What are your thoughts? – Nixinova Grid Book and Quill.png Grid Diamond Pickaxe.png Grid Map.png 03:25, 5 August 2017 (UTC)

With regards to page moves, it will pretty much involve moving most pages with Pocket Edition in the title to Bedrock Edition (without brackets as they do not work too well in page titles). I think all references to Console Edition should be changed to Legacy Console Edition including page names.
Which pages are you suggesting not to move? Already existing Pocket Edition version pages could stay with Pocket Edition in their titles, but then this would create inconsistency (and the Pocket Edition has always been built on the Bedrock platform anyway, with the current page titles not reflecting the Windows 10 Edition either). I wouldn't mind prefixing Java Edition version pages though. Pages such as Xbox One Edition could stay where they are currently with a message at the top indicating it has been superseded. GoandgooTalk
04:03, 5 August 2017 (UTC)

About renaming certain pages

Please explain why the following pages should be renamed: – Dentedharp90041tce 11:57, 1 October 2017 (UTC)