Editor's notes have apparently been ineffective. Many of these edits have been due to VisualEditor, which does not make editor's notes obvious; they are effectively invisible to these editors.

We have just had to continue to revert these edits.

My own thoughts on why this problem is happening

I believe such people look at the page, and see simply that, for instance, Nether Wart blocks are not mentioned, and put an entry into the Planned Additions section.

I have the feeling that the majority of occasional editors are only slightly aware, if at all, of our Mentioned features page, and the distinction we try to strictly maintain, and this unawareness, in turn, is another reason they make that edit.

People who do see the notes know about the policy can still believe that the features are confirmed for 1.10.

It's my belief that most people can easily get the impression that since the developers tweeted it during 1.10 development, that means it's confirmed. This can lead to the editor note not preventing them from adding it.

If you look at who is adding the edits, it's sometimes even regular editors as well as casual editors.

I offer my criticism of that suggestion: For a person who scans the page looking for Nether Wart blocks, not seeing any specific mention of it, and not knowing enough about our policy to also consider the mentioned features page, that link will likely do nothing to stop them making their edit.

My proposed solution

It would be nice if something were stated on the page about those blocks, listing those blocks, stating they are not, in fact, stated as coming in 1.10, but instead have only been mentioned in the course of 1.10 development.

I do not propose muddling the meaning of the #Additions and changes guidelines, or making changes to that at all. I fully believe it's important to be clear about what's planned and stated, with good references.

I do not propose a specific case-by-case exception to be made, temporarily, for the 1.10 page; I like it when rules are clear and can work well without exception, so I am proposing an amendment to the rules.

I propose a new section where such features and their status could be stated.

I believe that if editors read the text of the page, they would then easily find the mention of Nether Wart blocks. Furthermore, their mistaken impression that they're confirmed would be corrected, since we could include references and so forth.

Specific proposal

A new top-level section shall be permitted, called "Unconfirmed features".

It would be allowed only for versions in development. It would only be permitted to contain features mentioned since that version started development, and only those that were never confirmed as planned / upcoming, and only those that were never released in a development version, and only those not explicitly promised for a different version.Added 21:24, 10 May 2016 (UTC)

It should start with the text: "These features were never confirmed for 1.10, but developers have shown screenshots or discussed adding them during 1.10 development. Main article: Mentioned features Changed 04:38, 11 May 2016 (UTC)

It should be concise -- It should not allow a big, multi-line description of each block / item / feature, as if we were detailing it fully. It would just be, for instance, "Taiga villages", "Observer block", etc -- because the purpose of this section is really to just state that these are unconfirmed features, and you shouldn't confuse them with confirmed features, the purpose is not to document the nitty gritty details. That can be done at mentioned features.

The features should be supported either by either:

a (non-joke) screenshot showing that a developer has worked on the idea

a developer's statement indicating they do plan to add the feature, not merely a statement responding to another person's idea.Added 21:24, 10 May 2016 (UTC)

Example

Unconfirmed features

These features were never confirmed for 1.10, but developers have shown screenshots or discussed adding them during 1.10 development. Main article: Mentioned features

It can directly educate the casual editor of the difference between confirmed and not-confirmed, a long-term benefit.

It can acknowledge the existence of the feature, and accurately describe its 'unconfirmed' status -- not leaving a reader with the impression that the wiki might be incomplete.

It communicates facts about the development of the version, and so, while it's definitely just a 'mentioned feature', it's also a 'feature mentioned during 1.10 development' and so it has a natural place on the page, from that perspective.

It doesn't encourage duplication of content, because it's simply naming some features, describing their status, and pointing to the main 'Mentioned features' page, where the screenshots and full details could be.

For all of the above reasons, it will probably stop people making so many edits to Planned Additions and Changes, which is the goal.

The original reason I proposed the planned additions/changes sections was for a similar purpose as this, basically editors kept adding features to the update article with no distinction of what was added, what was planned, and what was unsourced.

Along those lines, I think the section looks pretty good and should help with the issue of editors adding unconfirmed features. It might even be worth adding sectional links to Mentioned features for the features just so users can be directed to the exact location with more information. My only concern is to make sure features are actually have something to show the developer is planning them for some update soon and its not just a random idea they mentioned, basically not adding features where someones asks a dev on twitter "please add this" and the dev responds with "maybe" or "I like the idea".

On a related note, it might be worth combining planned additions and planned changes into planned features, as there is rarely enough content for both there and the difference when unadded is a little arbitrary at times

I agree with this change, and think it could work very well. Maybe we could also have links to the Pocket Edition pages for some features that were confirmed for 0.15.0, but not 1.10? Anyway, this would work out great and I hope it is implemented. Who decides whether these things gets changed? -PancakeMan77 (talk) 20:08, 10 May 2016 (UTC)

If there's a consensus that people are okay with it / like it / won't oppose it, I think it's just as simple as agreeing on some wording, and once that's done, updating the Style Guide page. I think we're a little ways away from that; there's only 2 in support (3 including me) and personally I think it would be more credible if we, at minimum, heard the people from Talk:1.10, namely AttemptToCallNil, BDJP007301, Anomie x and Orthotope. – Sealbudsmantalk/contr 20:40, 10 May 2016 (UTC)

Sounds like you've thought about this a fair amount and tried to come up with a good solution. I'm willing to give it a try; if this doesn't work out as intended, we can always come back and revise the policy. -- Orthotopetalk 21:40, 10 May 2016 (UTC)

Even though I was leaning towards supporting it at first, unfortunately I've decided to ultimately Oppose per my comment from Talk:1.10. -BDJP(t|c) 02:01, 11 May 2016 (UTC)

Your first point on that page, "... doesn't mean it's just straight-up going to be in 1.10", I think if you look at the example (both as it was and currently), it would be very hard to look at the thing and get the impression that those features would be in 1.10, you would almost have to ignore 2/3 of what you're reading.

As for "driving speculation", are you thinking people would then just add their own ideas and wishes into the list? I think that is probably directly proportional to how tight the language is on the subtitle. I'll change it now to something that makes it clearer what does / doesn't belong in the list. – Sealbudsmantalk/contr 04:38, 11 May 2016 (UTC)

At the moment we have (in order) General, Gameplay, Commands, Command format, World generation, Blocks, Items, Mobs. You have to scroll far down to get the new features, and at the top it starts with Splashes, then goes to Options, etc. I propose we put Blocks, Items, Mobs, and World generation to the top, so you can get the list of new features quickly without having to scroll far down. For example, in 1.8, you have to scroll down a quarter of the page before you get 'interesting' features — Nixinova (talk • edits • pages) 19:27, 19 May 2017 (UTC)

I'd be up for that.

And not to muddle your suggestion too much, but while we're at it, why not put General at the bottom. It's kind of another word for "miscellaneous." – Sealbudsmantalk/contr 19:37, 19 May 2017 (UTC)

Gamepedia

Tools

Content is available under CC BY-NC-SA 3.0 unless otherwise noted.Minecraft content and materials are trademarks and copyrights of Mojang and its licensors. All rights reserved.
This site is a part of Curse, Inc. and is not affiliated with Mojang.