5,148 Pages

(Created page with "{{{{{1<noinclude>|Tip data</noinclude>}}}|Script|{{{2|}}}|{{{3|}}}|{{{4|}}}|{{{5|}}} |type = Ability attributes |image = false |link = Damage |descripti...")

Revision as of 16:14, February 3, 2020

This template contains various independently retrievable data items about Script in the form of parameter values of a variable template of choice, in a standardized fashion.

See also

Preview

Script

The game has two damage systems in place: an engine-level system and script-level system. Scripts are used by most "modern" game features, such as Runes Reforged.

In most cases, the two systems correlate. A combination of the two systems is responsible for effects such as Poison Trail persistent area damage, with systems like life steal, on-hit effects and spell vamp being connected to the engine-level damage types and Arcane Comet rune Arcane Comet being connected to script-level tags.

Instances where script-level tags create deviations from engine-level rules are noted in the ability-details.


Parameters

Parameter Value Description
1 Script Necessary: Used for identification.
disp_name Display Name
Only necessary if the value differs from Script.
link Damage Link
Only necessary if it should link to a different page.
description The game has two damage systems in place: an engine-level system and script-level system. The following are engine-level damage classifications:

<div class="columntemplate" style="-moz-column-count:2

-webkit-column-count
2
column-count
2

The following are script-level damage classifications: AOE, Periodic, Indirect, BasicAttack, ActiveSpell, Proc, Pet and NonRedirectable. Scripts are used by most "modern" game systems, such as Runes Reforged.

Description
description2 In most cases, the two systems correlate. A combination of the two systems is responsible for effects such as Poison Trail persistent area damage, with systems like life steal, on-hit effects and spell vamp being connected to the engine-level damage types and Arcane Comet rune Arcane Comet being connected to script-level tags. Description2
type Ability attributes Type
image false Image, including filetype.
image2
image3
interrupts Interrupts (CC)
reduction Reduction (CC)
resist Resist (CC)
removal Removal (CC)
footer Instances where script-level tags create deviations from engine-level rules are noted in the ability-details. Description that is placed at the bottom of all other things.

All tip data templates use the same parameter.

Retrieval of data items

{{data Script|pst2|interrupts}}, using parameter selection template Template:Pst2, gives the parameter interrupts, etc.

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

{{data Script|template name|..|..|..|..}}

so that this data template needs to be called only once.[1] The default template is Template:Tip 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}}}}|{|..|..}}. Until here the documentation is automatically generated by Template:Tip data.

References

  1. See the first two rows of the first table in m:Help:Array#Summary of counts for template limits.
Community content is available under CC-BY-SA unless otherwise noted.