Hello there! We are conducting a survey to better understand the user experience in making a first edit. If you have ever made an edit on Gamepedia, please fill out the survey. Thank you!

Minecraft Wiki:Style guide/Versions

From Minecraft Wiki
Jump to: navigation, search
Shortcut
MCW:VERSIONS

All version articles should use the following layout, to allow for consistency between version articles.

Introduction[edit]

At the very top of the article, {{version nav}} should be placed.

After the template should be an introduction with a general description. This description should contain the release date of the update, the official name (if it has one), the edition and development phase the version was released for, and a brief description of the update. If it is a development version, it should state which version of it is a development version.

A quote from the version changelog or from the developers may be placed before the introduction text.

Lead examples[edit]

Major release versions

1.10, the first release of the Frostburn Update,[1] is a major update to Minecraft (Java Edition) released on June 8, 2016, adding (...)

Minor release versions

1.14.1 is a minor update to Java Edition released on May 13, 2019, which improved performance and fixed bugs in 1.14. It is not compatible with 1.14 servers.

Development versions

18w43b is the second snapshot for Java Edition 1.14, released on October 24, 2018, which fixed bugs in 18w43a.

Additions and changes[edit]

These two sections are combined in the guide due to similarity, in the actual article this is two separate sections called Additions and Changes. General changes in a version should go within the two sections as follows:

  • Additions: Any new features added in the version. This includes features added in development versions.
  • Changes: Any changes to old features from the version. This includes features changed in development versions. Removals should be listed here and not in a separate section, unless there are many.

If the version is a full release or has a lot of features, each section also should have the following subsections:

  • Blocks: Features related to blocks.
  • Items: Features related to items.
  • Mobs: Features related to mobs.
  • Non-mob entities: Features related to non-mob entities, such as armor stands and minecarts.
  • World generation: Features related to world generation.
  • Gameplay: Features relating to gameplay mechanics, such as achievements, status effects, game modes, and visual changes.
  • Command format: Features related to block/entity tags or commands.
  • General: General features, such as options, splashes, and graphics changes.

If the features have not appeared in a development version yet, the feature should be contained in the separate but similar section Planned additions or Planned changes.

Unconfirmed features[edit]

Unless the information is well sourced, this section is not recommended to be added. This section is only for versions under development, and only contains features:

  • no longer confirmed as planned or upcoming for that (or any particular) version,
  • and evidenced, since the version started development, by:
    • a screenshot showing that a developer has worked on the feature,
    • or a developer's statement indicating they do plan to add the feature – not merely a statement responding to another person's idea.

It should start with the text: These features are not confirmed for <version>, but they were mentioned or showcased by developers during <version> development. Main article: Mentioned features

Each feature should consist of:

  • A name or short description of the feature,
  • No details, beyond what it takes to identify the feature (these belong on Mentioned features),
    • The purpose of this section is just for readers to identify the features that are unconfirmed, and to communicate why that is so – not to get into the feature's details.
  • A brief explanation, with supporting references, of when the feature was mentioned and why it is not confirmed.

Fixes[edit]

Bugs fixed in this version using {{fixes}}. Bugs should also be organised into sections using the following headers:

  • From released versions before <parent version> (;old)
  • From the <parent version> development versions (;dev)
  • From the previous development version (;prev)
  • From the current version, hotfixed (;hotfix)
  • Private issues (;private)

Note that {{fixes}} supports shortcuts for common headers.

The titles from the bug tracker issues may be freely edited to comply with the style guide. While users are encouraged to fix the titles as they find them, fixing the titles is not required; specifically when first adding the issues. Editors may make major changes to the title (such as rewording the whole title), though this is discouraged unless the original title fails to adequately describe the issue (eg, change "I found a bug" to "The player cannot jump when up against a block").

Bug fixes may only be added to a version page if the resolution is explicitly marked as “Fixed”. Bug fixes which have a resolution other than “Fixed” are subject to immediate removal.

Video[edit]

The video section of version pages should go below the fixes section, but above any other sections, such as trivia, gallery, and references. In most cases, video sections should only contain the following text, changing "video_id" to the YouTube video ID:

== Video ==
Video made by [[slicedlime]]:
{{yt|video_id}}

References[edit]

Should contain {{reflist}} usually, but if more columns are desired due to many references, add a number: {{reflist|2}}, {{reflist|3}}, and so on.

Footer[edit]

After references, place a double space, then add any applicable navigation templates, like {{Java Edition versions}}, and then any applicable categories.

The last thing on every version page will be the interwiki language links.