Template:Quest table row meta

Usage
This template is not to be used directly in pages. Its purpose is to perform some calculations for phantom templates that want to display a table row for a quest. What it does is take all the parameters needed from Quest and produce a bunch of variables that a calling template can use to display table cells.

A phantom template for quests will normally call this template once as shown below. It will then use the generated variables (listed below) as table cells. See the examples below for how the variables can be used. Variables generated:

Note: The variables that indicate "sortable" have the cell attribute "data-sort-value=" set. This makes it impossible to modify other cell attributes when using those variables. If you want to apply other attributes to those cells either create them again using other variables from this template or add a new variable to this template that provides the value without the data-sort-value attribute.
 * free (Yes, No)
 * cell_color (according to free)
 * epic (No, Both, Yes, Unknown)
 * epiccol (No, Both, Yes, Unknown, sortable)
 * sortlevel (lowest quest level)
 * level (all levels, sortable)
 * casualxp, normalxp, hardxp, elitexp (unformatted xp numbers, can be empty)
 * ecasualxp, enormalxp, ehardxp, eelitexp (unformatted xp numbers, can be empty)
 * heroicxp (Xpcolors or whatever value xp has)
 * epicxp (Xpcolors or whatever value epicxp has)
 * xp (heroic + epic, Xpcolors)
 * casual (heroic + epic, sortable)
 * normal (heroic + epic, sortable)
 * hard (heroic + epic, sortable)
 * elite (heroic + epic, sortable)
 * name (linked, heroic/epic counterpart mentioned)
 * favor (max favor, sortable)
 * bestowloc (linked)
 * bestower (not linked)
 * loc (not linked)
 * duration (sortable)
 * patron (linked)
 * pack (linked, sortable)
 * flagging

Examples
|-
 * Let's say we want to create a quest table with 2 columns. First the name of the quest and second the level. We would first call this meta template and then use the variables  and  . Those variables contain the necessary code for the name to be linked correctly as well as the levels of the quest displayed properly and able to be sorted.
 * Let's say we want to create a quest table that allocates 2 rows for quests that are both heroic and epic. We would again call this meta template, but there are no variables doing that. So we'll use the existing variables to do what we want. First, we'll check to see if the quest has 2 versions with the variable . Then we will display the xp for heroic and epic in separate rows using ,  ,  , etc. variables.