Template:History/doc

Usage 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: java classic for Classic 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:

ver — 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. none — 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 "Pocket Alpha 0.11.0 build 1" By default, the development version number will be a link to the appropriate version page. You can use to change this. Possible values are:

ver — 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. none — 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.

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