Diferencia entre revisiones de «Plantilla:Historial/doc»

De Minecraft Wiki
Saltar a: navegación, buscar
(Página creada con « {{doc/start}} This template is used for creating the new history sections. It is currently a work in progress. To create a History section, you need to use this template ...»)
 
 
(No se muestran 13 ediciones intermedias de 9 usuarios)
Línea 1: Línea 1:
  +
{{documentation header}}
  +
{{shortcut|H}}
 
This template is used for creating the new history sections. To create a History section, you need to use this template multiple times.
   
  +
== Usage ==
{{doc/start}}
 
This template is used for creating the new history sections. It is currently a work in progress.
 
   
  +
=== Editions and development cycles ===
To create a History section, you need to use this template multiple times:
 
   
* The various development phases of ''[[Minecraft]]'' are represented by sections. For example, you start the [[Beta]] section with <tt><nowiki>{{History|beta}}</nowiki></tt>.
+
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 [[Java Edition Beta]] section with <code><nowiki>{{History|java beta}}</nowiki></code>. The following names are available:
  +
* '''''[[Java Edition]]''''':
:* Shorthands for the development phases include: '''c''' for [[Classic]], '''st''' for [[Survival Test]], '''in''' for [[Indev]], '''inf''' for [[Infdev]], '''a''' for [[Alpha]], '''b''' for [[Beta]], '''r''' for [[Minecraft 1.0|Official release]], '''u''' for [[Upcoming features]] or pre-releases, and '''pa''' for [[Pocket Edition]].
 
  +
** <code>java pre-classic</code> for [[Java Edition pre-Classic|pre-Classic]]
* A single version can be represented like so: <tt><nowiki>{{History|1.2|Added Sandstone.}}</nowiki></tt>.
 
  +
** <code>java classic</code> for [[Java Editiona Classic|Classic]]
:* 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.
 
  +
** <code>java indev</code> for [[Java Edition Indev|Indev]]
:* By default, the version number will be a link to the appropriate [[version history]] page. You can use <tt><nowiki>{{{link}}}</nowiki></tt> to change this. Possible values are:
 
  +
** <code>java infdev</code> for [[Java Edition Infdev|Infdev]]
::* <tt><nowiki>ver</nowiki></tt> — link to the version history, i.e. the default behavior.
 
  +
** <code>java alpha</code> for [[Java Edition Alpha|Alpha]]
::* Any URI/URL — external link to this URI/URL.
 
  +
** <code>java beta</code> for [[Java Edition Beta|Beta]]
::* <tt><nowiki>none</nowiki></tt> — no link.
 
  +
** <code>java edition</code> or <code>java</code> for [[Java Edition 1.0.0|1.0.0]] and forward
:* Use the developmental version number for newly added features to maintain specific change logs. After the upcoming snapshot features have been officially released, move the entries to the official section while maintaining the developmental version numbers.
 
  +
** <code>java upcoming</code> for development builds to upcoming versions
:* If multiple changes have been made in a single version update, simply list them like so: <tt><nowiki>{{History|1.3|Sandstone is now found below three blocks of naturally generated sand.|Added the ability to craft Sandstone slabs from Sandstone.}}</nowiki></tt>. The template currently supports up to 10 changes per version.
 
  +
* '''''[[Pocket Edition]]''''':
* End the history section with <tt><nowiki>{{History|foot}}</nowiki></tt>.
 
  +
** <code>pocket alpha</code> for [[Pocket Edition Alpha|Alpha]]
  +
** <code>pocket</code> for [[Pocket Edition 1.0.0|1.0.0]] until [[Pocket Edition 1.1.7|1.1.7]]
  +
* '''[[Bedrock Edition]]''':
  +
** <code>bedrock</code> for [[Bedrock Edition 1.2.0|1.2.0]] and forward
  +
** <code>bedrock upcoming</code> for development builds to upcoming versions
  +
* '''''[[Education Edition]]''''':
  +
** <code>education</code>
  +
* '''''[[Legacy Console Edition]]''''':
  +
** <code>console</code>
  +
* '''''[[New Nintendo 3DS Edition]]''''':
  +
** <code>new 3ds</code>
  +
* '''Other:'''
  +
** <code>realms</code> for [[Realms]]
  +
** <code>earth</code> for ''[[Minecraft Earth]]''
  +
** <code>dungeons</code> for ''[[Minecraft Dungeons]]''
   
  +
=== Versions ===
   
 
A single version can be represented using the second parameter like so: <code><nowiki>{{History||1.2|Added Sandstone.}}</nowiki></code>. 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.
Sample usage:
 
   
 
By default, the version number will be a link to the appropriate version page. You can use {{p|link}} to change this. Possible values are:
<pre><nowiki>
 
  +
* <code>ver</code> — link to the version article, i.e. the default behavior.
{{History|survival test}}
 
 
* Any URI/URL — external link to this URI/URL.
{{History||0.24 (August 14, 2009)|Added zombies - the second
 
  +
* Any page on the wiki — internal link to this page.
mob to be added to ''Minecraft'', after humans.}}
 
 
* <code><nowiki>none</nowiki></code> — 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 supports unlimited changes per version.
 
* <code><nowiki>{{History||1.3|Sandstone is now found below three blocks of naturally generated sand.|Added the ability to craft Sandstone slabs from Sandstone.}}</nowiki></code>.
  +
  +
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:Historial de versiones desconocido]]
  +
  +
==== Development versions ====
  +
  +
The parameter {{p|snap}} can be used to display a development version along with the version for the change. The title will always be the value of {{p|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 "{{verlink|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 {{p|slink}} to change this. Possible values are:
 
* <code><nowiki>ver</nowiki></code> — 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.
  +
* <code><nowiki>none</nowiki></code> — 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 {{p|xbox}}, {{p|xbone}}, {{p|ps}}, {{p|wiiu}}, or {{p|switch}} 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:Historial de versiones desconocido]]. If any of the three are set to <code>none</code>, 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 <code>none</code> 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 {{p|2}} acts as an additional content cell.
  +
  +
=== Foot ===
  +
  +
After this, you can add more editions, or close the table using <code><nowiki>{{History|foot}}</nowiki></code>.
  +
  +
== Categories ==
  +
  +
If the parameter {{p|1}} is set to "java edition upcoming", the page will get added to [[:Categoría:Próxima Edición Java]]. Likewise, setting it to "bedrock edition upcoming" will add the page to [[:Categoría:Próxima Edición Bedrock]].
  +
  +
If the parameter {{p|1}}, {{p|2}}, {{p|snap}}, {{p|xbox}}, {{p|xbone}}, {{p|ps}}, {{p|wiiu}}, or {{p|switch}} are set to "unknown", the page will get added [[:Category:Historial de versiones desconocido]]
  +
  +
== Example ==
  +
  +
<pre>
  +
{{History||May 21, 2009|link=http://notch.tumblr.com/post/110762705/my-list-on-tile-types-so-far|[[Notch]] shows interest in adding a "seaweed" block and colored stone bricks.}}
 
{{History|classic}}
 
{{History||0.24_SURVIVAL_TEST|Added zombies – the second mob to be added to ''Minecraft'', after humans.}}
 
{{History|indev}}
 
{{History|indev}}
{{History||unknown|Zombies' armor was removed, as well as their
+
{{History||unknown|Zombies' armor was removed, as well as their arm swinging attack animations.}}
arm swinging attack animations.}}
 
 
{{History|beta}}
 
{{History|beta}}
{{History||1.8|Zombies now dropped rotten flesh instead
+
{{History||1.8|snap=?|The crafting recipe of glowstone has changed to 2×2 glowstone dust.
  +
|The drop rate of glowstone dust from mined glowstone has increased to 2–4.}}
of feathers.}}
 
{{History|release}}
+
{{History|java edition}}
{{History||12w03a|The zombies' AI was improved, giving them a
+
{{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.}}
much better sense of direction when pursuing the player,
 
 
{{History|java edition upcoming}}
allowing them to navigate obstacles, and even small mazes
 
 
{{History||1.14|Zombie armor is added back into the game, and they can wear any type of armor.}}
if constructed, to get to the player.}}
 
 
{{History|pocket alpha}}
{{History||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||12w32a|Zombie armor was added back into the game,
 
and they could wear any type of armor. Zombies could now also
 
hold an iron sword or iron shovel.}}
 
{{History|pocketa}}
 
 
{{History||0.3.0|Added crafting.}}
 
{{History||0.3.0|Added crafting.}}
{{History|xbox}}
+
{{History|pocket}}
{{History||1.0|Added pistons.}}
+
{{History||1.0.0|snap=?|Added dyable shulkers.}}
 
{{History|bedrock}}
  +
{{History||1.2.0|snap=beta 1.2.0.2|Old worlds are now Infinite.}}
 
{{History|bedrock upcoming}}
  +
{{History||1.5.0|snap=beta 1.5.0.1|Added dyable zombies.}}
 
{{History|education}}
  +
{{History||1.0.2|Added parrots.}}
 
{{History|console}}
  +
{{History||xbox=TU3|ps=1.0|xbone=CU1|wiiu=Patch 1|switch=1.0.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}}
 
{{History|foot}}
</nowiki></pre>
+
</pre>
 
;Produces:
   
  +
{{History||May 21, 2009|link=http://notch.tumblr.com/post/110762705/my-list-on-tile-types-so-far|[[Notch]] shows interest in adding a "seaweed" block and colored stone bricks.}}
Produces:
 
  +
{{History|classic}}
 
 
{{History||0.24_SURVIVAL_TEST|Added zombies the second mob to be added to ''Minecraft'', after humans.}}
{{History|survival test}}
 
{{History||0.24 (August 14, 2009)|Added zombies - the second mob to be added to ''Minecraft'', after humans.}}
 
 
{{History|indev}}
 
{{History|indev}}
 
{{History||unknown|Zombies' armor was removed, as well as their arm swinging attack animations.}}
 
{{History||unknown|Zombies' armor was removed, as well as their arm swinging attack animations.}}
 
{{History|beta}}
 
{{History|beta}}
{{History||1.8|Zombies now dropped rotten flesh instead of feathers.}}
+
{{History||1.8|snap=?|The crafting recipe of glowstone has changed to 2×2 glowstone dust.
  +
|The drop rate of glowstone dust from mined glowstone has increased to 2–4.}}
{{History|release}}
 
  +
{{History|java edition}}
{{History||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||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||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|||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|java edition upcoming}}
{{History||12w32a|Zombie armor was added back into the game, and they could wear any type of armor. Zombies could now also hold an iron sword or iron shovel.}}
 
 
{{History||1.14|Zombie armor is added back into the game, and they can wear any type of armor.}}
{{History|pocketa}}
 
  +
{{History|pocket alpha}}
 
{{History||0.3.0|Added crafting.}}
 
{{History||0.3.0|Added crafting.}}
{{History|xbox}}
+
{{History|pocket}}
{{History||1.0|Added pistons.}}
+
{{History||1.0.0|snap=?|Added dyable shulkers.}}
  +
{{History|bedrock}}
  +
{{History||1.2.0|snap=beta 1.2.0.2|Old worlds are now Infinite.}}
  +
{{History|bedrock upcoming}}
  +
{{History||1.5.0|snap=beta 1.5.0.1|Added dyable zombies.}}
  +
{{History|education}}
  +
{{History||1.0.2|Added parrots.}}
  +
{{History|console}}
  +
{{History||xbox=TU3|ps=1.0|xbone=CU1|wiiu=Patch 1|switch=1.0.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}}
 
{{History|foot}}
   
  +
<includeonly>
{{doc/end}}
 
  +
<!-- Template categories/interwiki here -->
  +
[[Category:Table templates]]
  +
  +
[[cs:Šablona:History]]
  +
[[el:Πρότυπο:History]]
  +
[[en:Template:History]]
  +
[[fr:Modèle:Historique]]
  +
[[hu:sablon:History]]
  +
[[it:Template:History]]
  +
[[ja:テンプレート:History]]
  +
[[ko:Template:History]]
  +
[[nl:Sjabloon:History]]
  +
[[pl:szablon:Historia]]
  +
[[pt:Predefinição:Histórico]]
  +
[[ru:Шаблон:История]]
  +
[[tr:Şablon:Geçmiş]]
  +
[[uk:Шаблон:Історія]]
  +
[[zh:Template:History]]
  +
</includeonly>
  +
<noinclude>
  +
<!-- Documentation categories/interwiki here -->
  +
[[cs:Šablona:History/doc]]
  +
[[el:Πρότυπο:History/doc]]
  +
[[en:Template:History/doc]]
  +
[[fr:Modèle:Historique/doc]]
  +
[[it:Template:History/doc]]
  +
[[ja:テンプレート:History/doc]]
  +
[[ko:Template:History/doc]]
  +
[[nl:Sjabloon:History/doc]]
  +
[[pl:szablon:Historia/doc]]
  +
[[pt:Predefinição:Histórico/doc]]
  +
[[ru:Шаблон:История/док]]
  +
[[uk:Шаблон:Історія/doc]]
  +
[[zh:Template:History/doc]]
  +
</noinclude>

Revisión actual del 00:09 29 abr 2021

Esta es la página de documentación. Esta debería ser transcluída en la páginaplantilla principal. Véase la Plantilla:Documentación para más información
Atajo
H

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

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 Java Edition Beta section with {{History|java beta}}. The following names are available:

Versions

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 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 supports unlimited 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:Historial de versiones desconocido

Development versions

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

When the parameter |xbox=, |xbone=, |ps=, |wiiu=, or |switch= 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:Historial de versiones desconocido. 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

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

Categories

If the parameter |1= is set to "java edition upcoming", the page will get added to Categoría:Próxima Edición Java. Likewise, setting it to "bedrock edition upcoming" will add the page to Categoría:Próxima Edición Bedrock.

If the parameter |1=, |2=, |snap=, |xbox=, |xbone=, |ps=, |wiiu=, or |switch= are set to "unknown", the page will get added Category:Historial de versiones desconocido

Example

{{History||May 21, 2009|link=http://notch.tumblr.com/post/110762705/my-list-on-tile-types-so-far|[[Notch]] shows interest in adding a "seaweed" block and colored stone bricks.}}
{{History|classic}}
{{History||0.24_SURVIVAL_TEST|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|snap=?|The crafting recipe of glowstone has changed to 2×2 glowstone dust.
|The drop rate of glowstone dust from mined glowstone has increased to 2–4.}}
{{History|java edition}}
{{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|java edition 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.0|snap=?|Added dyable shulkers.}}
{{History|bedrock}}
{{History||1.2.0|snap=beta 1.2.0.2|Old worlds are now Infinite.}}
{{History|bedrock upcoming}}
{{History||1.5.0|snap=beta 1.5.0.1|Added dyable zombies.}}
{{History|education}}
{{History||1.0.2|Added parrots.}}
{{History|console}}
{{History||xbox=TU3|ps=1.0|xbone=CU1|wiiu=Patch 1|switch=1.0.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
May 21, 2009Notch shows interest in adding a "seaweed" block and colored stone bricks.
classic
0.24_SURVIVAL_TESTAdded 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?The crafting recipe of glowstone has changed to 2×2 glowstone dust.
The drop rate of glowstone dust from mined glowstone has increased to 2–4.
Java Edition
1.2.112w03aThe 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.
12w06aZombies 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.
Próxima Java Edition
1.14Zombie armor is added back into the game, and they can wear any type of armor.
Pocket Edition Alpha
0.3.0Added crafting.
Pocket Edition
1.0.0?Added dyable shulkers.
Bedrock Edition
1.2.0beta 1.2.0.2Old worlds are now Infinite.
Próxima Bedrock Edition
1.5.0beta 1.5.0.1Added dyable zombies.
Education Edition
1.0.2Added parrots.
Legacy Console Edition
TU3CU1 1.0 Patch 11.0.1Added pistons and sticky pistons.
TU14 1.04 Pistons now take double the amount of time (2 redstone ticks or 4 game ticks) to extend, but they still retract instantly.