Wiki League of Legends
Wiki League of Legends

Esta predefinição contém vários items de data recuperáveis independentes sobre Vel'Koz na forma de valor de parâmetro de uma predefinição variável de escolha, em forma padronizada. É um membro da família de predefinições, aqueles com nome começando com "Data" em Categoria:Data templates.


Nome do Parâmetro Valor Significado
1 Vel'Koz last part of template name, used to identify it within the family of templates[1]
article nome do artigo; só precisa ser especificado caso esse nome difere de Vel'Koz; na aplicação, use [[{{{article|{{{1}}}}}}]] para linkar para o artigo (como foi feito no topo desta página)
disp_name Vel'Koz
fullname nome completo
name legacy used in Riot's old code.
ms 340 velocidade de movimento do campeão
range 525 alcance de ataques básicos do campeão
attack_delay 0 uso no código antigo da Riot
as_base 0.625 the shortened decimal form of base attack speed found in game
as_lvl 1.36 velocidade de ataque por nível (não inclua o símbolo %)
dam_base 51.7 dano de ataque base
dam_lvl 3.14 dano de ataque por nível
arm_base 12 armadura base
arm_lvl 3.5 armadura por nível
mr_base 30 resistência mágica base
mr_lvl 0 resistência mágica por nível
hp_base 456 vida base
hp_lvl 76 vida por nível
mp_base 250 Barra de recurso base (100 para Fúria, Aquecimento; 200 para energia)
mp_lvl 45 resource bar per level (0 for fury, heat, or energy)
hp5_base 4.5 regen. de hp por 5 segundos base
hp5_lvl regen. de hp por 5 segundo por nível
mp5_base 7 base resource bar regen per 5 seconds (0 for fury or heat, 50 for energy)
mp5_lvl resource bar regen per 5 seconds per level (0 for fury, heat, or energy)
resource champion resource. Not the same as the resource bar. For example, some champions have "Shield" resource bar and use "Health" for their abilities.
image Vel'KozSquare.png ícone do campeão; ChampionSquare.png
title O Olho do Vazio título do campeão
herotype Mago função primária oficial como recomendada pela Riot
alttype função alternativa ou complementar
rangetype Ranged classificação do tipo de alcance de ataque básico
date 27/02/2014 data de lançamento (dd/mm/aaa)
patch V4.3 lançado com o patch
health 2 official health rating out of 10
attack 2 official attack rating out of 10
spells 10 official spells rating out of 10
difficulty 8 official difficulty rating out of 10
ip 6300 custo de IP
rp 975 custo de RP

Throughout the family of templates, fixed names are used for the parameters. (The parameter names are kept short to reduce counts for the post expand include size and the template argument size in cases where these are applicable.) However, not necessarily all parameters have been given a value: some parameters may not be applicable, while for some other parameters the value may just have not been specified yet. The table shows all parameters, and for each the value, if specified.


The following parameters are now deprecated on the wiki.

Nome do Parâmetro Valor Significado
hp1_base Base health regeneration per 1 second.
mp1_base Base resource bar regeneration per 1 second.
hp1_lvl Health regeneration per 1 second increase per level.
mp1_lvl Resource bar regeneration per 1 second increase per level

Riot provides regeneration values as per 5 seconds.

Derived data

True as_base is 0,625, rounded to 3 decimal places as 0,625[2]

At level 18, the attack speed is 0,7695

Retrieval of data items

{{data Vel'Koz|pst2|as_base}}, using parameter selection template Template:Pst2, gives the parameter as_base, etc.

For retrieval of more data items it is more efficient to prepare a template for that, to be used as follows:

{{data Vel'Koz|template name|..|..|..|..}}

so that this data template needs to be called only once.[3] The default template is Template:Show data, producing this page.

The four parameters are optional, they are passed on to the prepared template as parameters 2-5.

A parameter being undefined or empty typically means the same, see below. {{data ..|pst2|..}} gives the empty string and the text "{{{..}}}", respectively. Therefore an application checking the parameter has to check both. Checking whether a result is equal to e.g. the text "{{{popinc}}}" cannot be done directly with #ifeq in a template which itself has also a parameter with that name, because if that is defined, there would be a comparison with the value instead of the text itself. Instead, it can be checked whether the first character of the result is "{", e.g.: {{#ifeq:{{padleft:|1|{{data {{{continent}}}|pst2|popinc}}}}|{|..|..}}.

Creating new data templates

Template:Data/preload can be used to create new data templates. The wikitext can be copied to the new data template. For parameters which are not applicable, the parameter definition can be deleted. For parameters to be filled in later the parameter definition (specifying the empty string as value) can be left in the wikitext to be filled in later. Do not forget parameter 1.


In this template system each template contains various properties of a single entity, as opposed to the other common system, where a template contains one property (e.g. population or area) of many entities. Although that other system can be convenient if updates of a property for all these entities become available together, in the case of large-scale use of data on one page that other system can be problematic due to its inefficiency. This is because of the following:

  • There are often more entities than properties, and page counts (or in the case of #switch, average page counts) are proportional to the number of data items in the data template (if they are stored in a linear way, not in a tree, and not stored as unnamed parameters).
  • In the case of large-scale use of data on one page there are usually one or more tables, where an entity forms a row and a property a column, because there are often more entities than properties, and because this way the sorting feature allows sorting entities based on a property. In this template system this allows producing a row with only one call of the data template, making the count not grow faster than proportional to the average number of data items stored per data template, times the number of entities in the table.

The include part of the data template of an entity does not contain a long list of its sub-entities or their properties, because that would make this method inefficient too.

  1. It may seem odd, but a template cannot retrieve its own name (PAGENAME only provides this on the template page itself), and even if it could, a string operation would be needed to remove "Data ". Putting the name of the entity in the data template removes the need to supply it as a parameter when the data template is called (in the cases that it would need this name).
  2. Attack speed
  3. See the first two rows of the first table in m:Help:Array#Summary of counts for template limits.

Until here the documentation is automatically generated by Template:Show data.