Template:History/doc

This template is used for creating the new history sections. To create a History section, you need to use this template multiple times.

Editions and development cycles
Set the first parameter to one of the various development phases and platform versions of Minecraft, and they will be represented by sections. For example, you start the Beta section with. The following names are available:
 * Java:
 * for Pre-classic
 * for Classic
 * for Indev
 * for Infdev
 * for Alpha
 * for Beta
 * or  for Java Edition
 * for development builds to upcoming Java Edition
 * Pocket:
 * for Pocket Edition Alpha
 * for Pocket Edition 1.0.0 until Pocket Edition 1.1.7
 * Bedrock:
 * for Bedrock Edition 1.2.0 and forward
 * for development builds to upcoming Bedrock Edition versions
 * Console:
 * for Legacy Console Edition
 * New 3DS:
 * for New Nintendo 3DS Edition
 * Other:
 * for Realms

Versions
A single version can be represented using the second parameter like so:. Do not specify the development stage here (e.g. use 1.2, not Beta 1.2). The development stage is already in the section header.

By default, the version number will be a link to the appropriate version page. You can use to change this. Possible values are:
 * — link to the version article, i.e. the default behavior.
 * Any URI/URL — external link to this URI/URL.
 * Any page on the wiki — internal link to this page.
 * — no link.

If the feature was mentioned in a tweet, etc, prior to release, place that info at the top of the History section without a header.

If multiple changes have been made in a single version update, simply list them like follows. The template currently supports up to 10 changes per version.

If the version is unknown, the parameter can be set to "unknown" or "?", which will display a ? in the cell and place the page in Category:Unknown version history

Development versions
The parameter can be used to display a development version along with the version for the change. The title will always be the value of
 * If the development version starts with "pre" or "RC", it will link to that pre-release or release candidate of the parent version. For example, a development version of "pre1" with a parent version of "1.8" links to "1.8-pre1"
 * If the development version starts with "build", its link will be to that alpha build of the parent version. For example, a development version of "build 1" with a parent version of "0.11.0" acts as ""

By default, the development version number will be a link to the appropriate version page. You can use to change this. Possible values are:
 * — link to the version article, i.e. the default behavior.
 * Any URI/URL — external link to this URI/URL.
 * Any page on the wiki — internal link to this page.
 * — no link.

If there are multiple development changes for a version, simply omit the second parameter or set it to the same as the last parent version, and it will automatically merge.

If the development version is unknown, the parameter can be set to "unknown" or "?", which will display a ? in the cell and place the page in Category:Unknown version history. If the change was made in the release of a version, simply set the parameter to "release" and the cell will display as blank.

Legacy Console Editions
When the parameter, , , or is set, the normal single or two column mode is replaced with three, one for each type of legacy console edition. Each of the three parameters controls one column, in which the link will be to the appropriate version page.

If any of the four parameters is set to "unknown" or "?", that cell will display a ? and the page will be added to Category:Unknown version history. If any of the three are set to, the cell will display as blank, signifying no relevant version for that change. If one version on one console covers multiple updates on another, simply set the version on the first change and all others below which are unset or the same as the first will be merged automatically, similarly to the snapshot feature. To prevent this feature, just set the row to  or another version.

Additionally, when using this mode, the development version column and link parameters are disabled (if a link is required, use the single column mode), and the parameter acts as an additional content cell.

Foot
After this, you can add more editions, or close the table using.

Categories
If the parameter is set to "java edition upcoming", the page will get added to Category:Java Edition upcoming. Likewise, setting it to "bedrock edition upcoming" will add the page to Category:Bedrock Edition upcoming.

If the parameter, , , , , , , or are set to "unknown", the page will get added Category:Unknown version history

If the header uses a deprecated header name, the page will be added to Category:History uses deprecated header

Example

 * Produces:

es:Plantilla:Historial fr:Modèle:Historique it:Template:History ko:Template:History nl:Sjabloon:History pt:Predefinição:Histórico ru:Шаблон:История zh:Template:History

es:Plantilla:Historial/doc fr:Modèle:Historique/doc it:Template:History/doc ko:Template:History/doc nl:Sjabloon:History/doc pt:Predefinição:Histórico/doc ru:Шаблон:История/док zh:Template:History/doc