Data Aegis of the Legion

This template contains various independently retrievable data items about Aegis of the Legion in the form of parameter values of a variable template of choice, in a standardized fashion. It is a member of a family of templates, those with names starting with "Data" in Category:Data templates.

Parameters

Parameter name	Value	Meaning
1	Aegis of the Legion	last part of template name, used to identify it within the family of templates
article		article name; needs to be specified only if it differs from Aegis of the Legion; in applications, use [[{{{article|{{{1}}}}}}]] to link to the article (as has been done at the top of this page)
disp_name
fullname		full name
name	Aegis of the Legion	legacy used in Riot's old code.
ms		movement speed of the champion
range		attack range of the champion
attack_delay		used in Riot's old code.
as_base		the shortened decimal form of base attack speed found in game
as_lvl		attack speed per level (do not include the % symbol)
dam_base		base attack damage
dam_lvl		attack damage per level
arm_base		base armor
arm_lvl		armor per level
mr_base		base magic resistance
mr_lvl		magic resistance per level
hp_base		base health
hp_lvl		health per level
mp_base		base resource bar (100 for fury, heat; 200 for energy)
mp_lvl		resource bar per level (0 for fury, heat, or energy)
hp5_base		base health regen per 5 seconds
hp5_lvl		health regen per 5 seconds per level
mp5_base		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		champion square; ChampionSquare.png
title		champion title
herotype		official primary champion role as recommended by Riot
alttype		alternate or complimentary role
rangetype		classification of autoattack range type
date		release date (yyyy-mm-dd)
patch		released with patch
attack		official attack rating out of 10
health	200	official health rating out of 10
spells		official spells rating out of 10
difficulty		official difficulty rating out of 10
ip		IP cost
rp		RP cost

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.

Deprecated

The following parameters are now deprecated on the wiki.

Parameter name	Value	Meaning
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.

Retrieval of data items

{{data Aegis of the Legion|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 Aegis of the Legion|template name|..|..|..|..}}

so that this data template needs to be called only once. 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.

Efficiency

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.

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