Template:Ability infobox/doc

This template performs a number of functions:


 * It draws information about a ability from a data page if it finds one for the ability. It can also draw information directly from its parameters like a typical infobox.
 * It displays an infobox using that information by calling Ability infobox/layout. Note that the visual and layout code is in that template with the exception of the multiple data page warning.
 * It sets properties and categories, which are used to create automated lists such as the one used by Ability table.

Finding the data page
The template finds a data page for an item in one of four ways:

When the,  , and   parameters are not given values, the infobox looks for a data page in Category:Imported ability data where Property:Has name is the same as the name of the page the infobox is being used on.

When the  parameter is given a value but   is not, the infobox looks for a data page in Category:Imported ability data where Property:Has name has that value.

When  is given a value, the infobox looks for that page, but will return it only if the page is in Category:Imported ability data. When using this, specify only the page name of the data page. For example, for "Data:EXAMPLE", just specify "EXAMPLE".

Note that an item data page should be set up with Ability data, and the  parameter on that template sets the value of Property:Has name. If the  parameter doesn't get a value, Property:Has name is set to the page name.

works the same as  except that it requires the full name of the data page, including the namespace. This is useful for testing data pages set up in a user namespace.

When there is no data page
If an item doesn't have a data page for some reason, you can treat this as a normal infobox and supply the values yourself.

Note that if a data page for the ability is imported later, the values of these parameters will be ignored.

Overriding data page values
If necessary, it is possible to override the values pulled from the data page. When data is simply outdated, it's probably better to just change it on the data page itself, as it would probably have been corrected in the next data import anyway. But if for some reason imports seem to be consistently bringing in incorrect data, you can override it by using the  parameters: