Template:History

From Minecraft Wiki
Jump to: navigation, search
[view | edit | history | purge]Documentation

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

Usage[edit source]

Editions and development cycles[edit source]

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 {{History|beta}}. The following names are available:

Versions[edit source]

A single version can be represented using the second parameter like so: {{History||1.2|Added Sandstone.}}. 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 {{{link}}} 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 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.

  • {{History||1.3|Sandstone is now found below three blocks of naturally generated sand.|Added the ability to craft Sandstone slabs from Sandstone.}}.

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[edit source]

The parameter {{{snap}}} can be used to display a development version along with the version for the change. The title will always be the value of {{{snap}}}

  • 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 {{{slink}}} 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.

Legacy Console Editions[edit source]

When the parameter {{{xbox}}}, {{{xbone}}}, {{{ps}}}, or {{{wiiu}}} 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 none, 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 none 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 {{{2}}} acts as an additional content cell.

Foot[edit source]

After this, you can add more editions, or close the table using {{History|foot}}.

Categories[edit source]

If the parameter {{{1}}} is set to "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 {{{1}}}, {{{2}}}, {{{snap}}}, {{{xbox}}}, {{{xbone}}}, {{{ps}}}, {{{wiiu}}}, or {{{switch}}} 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[edit source]

{{History|classic}}
{{History||0.24 (August 14, 2009)|Added zombies - the second mob to be added to ''Minecraft'', after humans.}}
{{History|indev}}
{{History||unknown|Zombies' armor was removed, as well as their arm swinging attack animations.}}
{{History|beta}}
{{History||1.8|Zombies now dropped rotten flesh instead of feathers.}}
{{History|release}}
{{History||1.2.1|snap=12w03a|The zombies' AI was improved, giving them a much better sense of direction when pursuing the player, allowing them to navigate obstacles, and even small mazes if constructed, to get to the player.}}
{{History|||snap=12w06a|Zombies chase and attack villagers, attack doors (breaking them on Hard and Hardcore difficulties), and sometimes drop iron ingots, helmets, shovels and swords as rare drops.}}
{{History|upcoming}}
{{History||1.14|Zombie armor is added back into the game, and they can wear any type of armor.}}
{{History|pocket alpha}}
{{History||0.3.0|Added crafting.}}
{{History|pocket}}
{{History||1.0|Added dyable shulkers.}}
{{History|bedrock}}
{{History||1.2|snap=build 1|Old worlds are now Infinite.}}
{{History|bedrock upcoming}}
{{History||1.4|Added dyable zombies.}}
{{History|console}}
{{History||xbox=TU3|ps=1.0|xbone=CU1|wiiu=Patch 1|switch=Patch 1|Added pistons and sticky pistons.}}
{{History||xbox=TU14|ps=1.04|Pistons now take double the amount of time (2 redstone ticks or 4 game ticks) to extend, but they still retract instantly.}}
{{History|foot}}
Produces
Classic
0.24 (August 14, 2009) Added zombies - the second mob to be added to Minecraft, after humans.
Indev
?Zombies' armor was removed, as well as their arm swinging attack animations.
Beta
1.8 Zombies now dropped rotten flesh instead of feathers.
Official release
1.2.1 12w03a The zombies' AI was improved, giving them a much better sense of direction when pursuing the player, allowing them to navigate obstacles, and even small mazes if constructed, to get to the player.
12w06a Zombies chase and attack villagers, attack doors (breaking them on Hard and Hardcore difficulties), and sometimes drop iron ingots, helmets, shovels and swords as rare drops.
Upcoming
1.14 Zombie armor is added back into the game, and they can wear any type of armor.
Pocket Edition Alpha
0.3.0 Added crafting.
Pocket Edition
1.0 Added dyable shulkers.
Bedrock Edition
1.2 build 1 Old worlds are now Infinite.
Upcoming Bedrock Edition
1.4 Added dyable zombies.
Legacy Console Edition
TU3CU11.0Patch 1Patch 1Added pistons and sticky pistons.
TU141.04Pistons now take double the amount of time (2 redstone ticks or 4 game ticks) to extend, but they still retract instantly.
[view | edit | history | purge]The above documentation is transcluded from Template:History/doc.