Consider looking for related projects to help. If you feel this defunct project may be worth reviving, please discuss with related projects first.
This page is part of the project.
There is information about the project below this notice.
The aim of this project is to improve the quality of all version pages across all editions of Minecraft.
Ideally, all version pages should conform to this layout, roughly set out at MCW:Style guide/Versions.
- Version nav
- Title should be the exact version name as seen in-game (eg "Minecraft ###" for Java versions).
- Footer links should be in the following format:
- If the version is a release version, the prev and next parents refer to their respective major versions ("X" in: 1.X for alpha, beta and release, 0.0.X in early classic, and 0.X in late classic/early indev), and the prev/next refer to the version directly before and after.
- If the version is a development version, the prev/next parents refer to minor versions, and prev/next refer to the development version before and after.
- Footer links should never link to a parent version.
- Lead
- For release versions: VERSION (the first release of UPDATE_NAME) is a (major/minor) update to EDITION released on DATE,<REF> which (adds/changes) LIST_OF_CHANGES.
- For example: 1.14, the first release of Village & Pillage, is a major update to Java Edition released on April 23, 2019, which adds (...)
- For development versions: VERSION is the Nth TYPE for PARENT, released on DATE,<REF> which (adds/changes) LIST_OF_CHANGES.
- For example: 1.14 Pre-Release 1 is the first pre-release for Java Edition 1.14, released on April 10, 2019, which optimizes (...)
- Should be written in past tense only if the version in question has been archived or is otherwise unavailable
- Additions/changes
- Subheading names can be found at MCW:Style guide/Versions.
- Make sure the amount of detail covered in each section is relatively consistent as described in the style guide page linked above.
- Fixes
- Using
{{fixes}}, list fixes in the version.
- For major versions, make sections for bugs before the last major release and for each minor version of the previous major release, e.g.
;Before 1.15, ;1.15, ;1.15.1, and ;1.15.2.
- For minor versions, use
;old for bugs before the last major version, and have separate sections for each minor release since (eg, 1.14.3 has ;old, ;From 1.14, ;From 1.14.1, and ;From 1.14.2)
- For development versions, use as above but with
;dev, and ;prev as well.
- Trivia
- Usually contains information relating to and comparing how long the update took to release and version numbers.
- Key
The first icon is for releases and second is for development versions.
Add your signature here using ~~~
