This template contains various independently retrievable data items about Rengar 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

Rengar BE icon 4800 RP icon 880

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 2
Champion attribute segment 2
the Pridestalker
Health: 2116  
Health Regen.: 15.5  
Ferocity: 4  
Range: 125  
Attack Damage: 94  
Attack Speed: 0.997  
Armor: 85  
Magic Res.: 53.4  
Move. Speed: 345  
Level 18
Fighter icon DiverMelee role Melee
Champion style basic attacks activeChampion style 30Champion style abilities inactive


Parameter Value Description
1 Rengar Necessary: Used for identification.
id {{{id}}} Riot's unique champion id in their API.
disp_name Rengar Name of the champion
Only necessary if the value differs from Rengar.
fullname Full name
ms 345 Movement speed of the champion
range 125 Attack range of the champion
as_base 0.625 The shortened decimal form of base attack speed found in game
as_lvl 3.5 Attack speed per level (do not include the % symbol)
dam_base 68 Base attack damage
dam_lvl 1.5 Attack damage per level
arm_base 34 Base armor
arm_lvl 3 Armor per level
mr_base 32.1 Base magic resistance
mr_lvl 1.25 Magic resistance per level
hp_base 586.2 Base health
hp_lvl 90 Health per level
mp_base 4 Base resource bar (100 for fury, heat; 200/400 for energy)
mp_lvl 0 Resource bar per level (0 for fury, heat, or energy)
hp5_base 7 Base health regen per 5 seconds
hp5_lvl 0.5 Health regen per 5 seconds per level
mp5_base 0 Base resource bar regen per 5 seconds (0 for fury or heat, 50 for energy)
mp5_lvl 0 Resource bar regen per 5 seconds per level (0 for fury, heat, or energy)
resource Ferocity 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 RengarSquare.png Champion square; ChampionSquare.png
image2 Champion square 2; ChampionSquare.png
title the Pridestalker Champion title
herotype Slayer Official primary champion role as recommended by Riot
alttype Fighter Alternate or complementary role
rangetype Melee Classification of autoattack range type
date 2012-08-21 Release date (YYYY-MM-DD)
patch V1.0.0.145 Released with patch
changes V8.2 Last changed with patch
damage 3 Official damage rating 0-3
toughness 1 Official toughness rating
control 2 Official control rating
mobility 2 Official mobility rating
utility 0 Official utility rating
style 30 Official style rating 0-100
difficulty 2 Official difficulty rating 1-3
adaptivetype physical Adaptive damage default type magic or physical
BE 4800 BE cost
RP 880 RP cost
Skill images Use ; to separate multiple values!
skill_i Unseen Predator;Bonetooth Necklace I Skill Unseen Predator Unseen Predator
Bonetooth Necklace Bonetooth Necklace
skill_q Savagery Q Skill Savagery Savagery
skill_w Battle Roar W Skill Battle Roar Battle Roar
skill_e Bola Strike E Skill Bola Strike Bola Strike
skill_r Thrill of the Hunt R Skill Thrill of the Hunt Thrill of the Hunt

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.996875

Name 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Rengar 0.625 0.641 0.657 0.675 0.693 0.711 0.731 0.751 0.772 0.794 0.819 0.84 0.865 0.889 0.915 0.942 0.969 0.997

Retrieval of data items

{{data Rengar|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 Rengar|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}}}}|{|..|..}}.


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.