Difference between revisions of "Template:Ability (LW2)/doc"

From UFOpaedia
Jump to navigation Jump to search
Line 7: Line 7:
 
| s_name =
 
| s_name =
 
| s_descr =
 
| s_descr =
| s_info = {{ {{FULLPAGENAME}}/Info }}
+
| s_info = {{ {{subst:FULLPAGENAME}}/Info }}
 
| b_name = {{{ b_name }}}
 
| b_name = {{{ b_name }}}
 
| b_descr = {{{ b_descr }}}
 
| b_descr = {{{ b_descr }}}

Revision as of 01:07, 28 January 2017

Skeleton

{{Ability_(LW2)
| s_image =
| s_caption = 
| s_name = 
| s_descr =
| s_info = {{ {{subst:FULLPAGENAME}}/Info }}
| b_name = {{{ b_name }}}
| b_descr = {{{ b_descr }}}
| b_info = {{{ b_info }}}
}}

Parameters

s_image : Image filename without link or prefix, but including extension, e.g. Image_name.jpg. This get's expanded in the template to blahblah

s_caption : Rollover text for the main image.

s_name : The perk/ability name.

s_descr : A (shortish) description of the perk.

s_info : Rollover text for the info icon. In practice this should always point to the template's Info subpage via transclusion (see skeleton above) so that it can be referenced elsewhere easily.

b_name : Set if name is visible. 0 = invisible. 1 = visible. Default 1.

b_descr : Set if description is visible. 0 = invisible. 1 = visible. Default 0.

b_info : Set if info icon is visible. 0 = invisible. 1 = visible. Default 0.

Notes About the Boolean Parameters

The skeleton above treats these as passthroughs. It is expected that these parameters will be set wherever someone wants to include the ability info, and not inside the template itself. The skeleton above will take the parameters given from the initial call (say from the Main Page) and pass them on to this template.

If that didn't make sense, look at Category:Perks (Long War 2) for examples.

Bugs

Fixed

If using this in Template:Class_Tree_(LW2) you need to add a line break after this template.

If this template is used inside a Template:Class_Tree_(LW2) and b_info is not true, then for some blasted reason the text overflows the cells. With b_info set, the text behaves and stays inside the table's cells as they should. (How very, very annoying.)

The text also behaves if this template is instead used inside a subst: version of the Class_Tree template. It could be some weird issue with the parser/template-rendering-parsing-dohicky.

Update: It appears that for some reason, the subst: version has a bunch of line breaks it in the source code. Weird.