FANDOM


AniviaSquare

This template contains various independently retrievable data items about Anivia 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:Champion data templates.

Champion pages

Anivia OriginalLoading
Anivia BE icon 3150 RP icon 790

Champion attribute background

Note that the client rates champions on a scale of 1-3, with champions that feature both None and Low in a particular strength being marked equally. In contrast, this Wikia uses a 0-3 scale for Toughness, Control, Mobility and Utility. Any champions listed as 0 can be considered a 1, officially.Damage - A champion's ability to deal damage.Toughness - A champion's ability to survive being focused.Control - A champion's ability to disable or disrupt enemies.Mobility - A champion's ability to move quickly around the map, blink or dash.Utility - A champion's ability to grant beneficial effects to their allies or to provide vision.Champion attribute overlay
Champion attribute segment 3
Champion attribute segment 1
Champion attribute segment 3
Champion attribute segment 2
the Cryophoenix
Rebirth
Flash Frost
Crystallize
Frostbite
Glacial Storm
Health: 1874  
Health Regen.: 14.9  
Mana: 1246  
Mana regen: 19.6  
Range: 600  
Attack Damage: 106  
Attack Speed: 0.804  
Armor: 89.2  
Magic Res.: 38.5  
Move. Speed: 325  
Level 18
Mage icon BattlemageRanged role Ranged
Champion style basic attacks inactiveChampion style 100Champion style abilities active


Parameters

Parameter Value Description
1 Anivia Necessary: Used for identification.
id {{{id}}} Riot's unique champion id in their API.
disp_name Anivia Name of the champion
Only necessary if the value differs from Anivia.
fullname Full name
ms 325 Movement speed of the champion
range 600 Attack range of the champion
as_base 0.625 The shortened decimal form of base attack speed found in game
as_lvl 1.68 Attack speed per level (do not include the % symbol)
as_lvl1bonus
dam_base 51.376 Base attack damage
dam_lvl 3.2 Attack damage per level
arm_base 21.22 Base armor
arm_lvl 4 Armor per level
mr_base 30 Base magic resistance
mr_lvl 0.5 Magic resistance per level
hp_base 480 Base health
hp_lvl 82 Health per level
mp_base 396.04 Base resource bar (100 for fury, heat; 200/400 for energy)
mp_lvl 50 Resource bar per level (0 for fury, heat, or energy)
hp5_base 5.574 Base health regen per 5 seconds
hp5_lvl 0.55 Health regen per 5 seconds per level
mp5_base 6 Base resource bar regen per 5 seconds (0 for fury or heat, 50 for energy)
mp5_lvl 0.8 Resource bar regen per 5 seconds per level (0 for fury, heat, or energy)
resource Content of secondary bar, usually a primary resource for abilities, but not vice versa. Also not a champion's resource, which refers to any resource (secondary, etc.). E.g. Mordekaiser has "shield" in resource bar, but his primary resource is "health".
image AniviaSquare.png Champion square; ChampionSquare.png
image2 Champion square 2; ChampionSquare.png
title the Cryophoenix Champion title
herotype Mage Official primary champion role as recommended by Riot
alttype Controller Alternate or complementary role
rangetype Ranged Classification of autoattack range type
date 2009-07-10 Release date (YYYY-MM-DD)
patch July 10, 2009 Patch Released with patch
changes V8.2 Last changed with patch
damage 3 Official damage rating 0-3
toughness 1 Official toughness rating
control 3 Official control rating
mobility 0 Official mobility rating
utility 2 Official utility rating
style 100 Official style rating 0-100
difficulty 3 Official difficulty rating 1-3
adaptivetype magic Adaptive damage default type magic or physical
BE 3150 BE cost
RP 790 RP cost
Skill images Use ; to separate multiple values!
skill_i Rebirth I Skill Rebirth Rebirth
skill_q Flash Frost Q Skill Flash Frost Flash Frost
skill_w Crystallize W Skill Crystallize Crystallize
skill_e Frostbite E Skill Frostbite Frostbite
skill_r Glacial Storm R Skill Glacial Storm Glacial Storm

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.

Derived data

True as_base is 0.625, rounded to 3 decimal places as 0.625[1]

At level 18, the attack speed is 0.8035

Name 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Anivia 0.625 0.633 0.64 0.649 0.657 0.666 0.676 0.686 0.696 0.706 0.718 0.728 0.74 0.752 0.764 0.777 0.79 0.804

Retrieval of data items

{{data Anivia|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 Anivia|template name|..|..|..|..}}

so that this data template needs to be called only once.[2] The default template is Template:Champion 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}}}}|{|..|..}}.

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.

  1. Attack speed
  2. 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:Champion data.


I contenuti della comunità sono disponibili sotto la licenza CC-BY-SA a meno che non sia diversamente specificato.