Difference between revisions of "Template:Infobox User/adventure"

Revision as of 19:11, 4 January 2013 (view source) J McKalling (Talk | contribs) (Created page with "<includeonly>{{ #vardefine: lba | {{#var:lba|}}{{#ifeq: {{lc:{{#if:{{{lba1|}}}|{{{lba1}}}|no}}}} | no || 1 }}}}{{ #vardefine: lba | {{#var:lba|}}{{#ifeq: {{lc:{{#if:{{{lba2|}}...") Newer edit →

(No difference)

---

Revision as of 19:11, 4 January 2013

This template offers a multiple choice for defining which adventure you're experienced in, and your userpage belongs to. It can also automatically categorize your page under that category.

Parameters

• lba1: Whether or not to select the first adventure "FunFrock's Reign" (defaults to no, enable by any other nonempty value)
• lba2: Whether or not to select the second adventure "Twinsen's Odyssey" (defaults to no, enable by any other nonempty value)
• lba3: Whether or not to select the third adventure "Stellar Entity Genesis" (defaults to no, enable by any other nonempty value)
• nocat: Whether or not to suppress categorization under the chosen categories (defaults to false, which means auto categorization).

Note: the lba3 parameter is of cource a placeholder for until the highly anticipated sequel is finally released. You cannot possibly mean to specify it yet.

Note: this categorizer is multiple choice: you can specify any combination of the three options.

Note: if neither lba1, lba2 or lba3 specify a positive value, the default 'unknown' will be used.

Syntax

{{Infobox User/adventure|lba1=value|lba2=value|lba3=value}}

Examples

Common use include either the lba1 or lba2 parameter to specify the one adventure you are experienced in (value "yes" is recommended):

{{Infobox User/adventure|lba1=yes}}
{{Infobox User/adventure|lba2=yes}}

FunFrock's Reign ^{[list all]}

Twinsen's Odyssey ^{[list all]}

You can also specify multiple adventures for yourself (warning: this will force a table cell to split in two, so do not do this outside table cells!):

{{Infobox User/adventure|lba1=yes|lba2=yes}}

Multiple: ^{[list all]}

• FunFrock's Reign ^{[list all]}
• Twinsen's Odyssey ^{[list all]}

It doesn't matter which value you use, any nonempty value other than "no" will express a positive value, so these all have the same result:

{{Infobox User/adventure|lba1=aye, let's do this!}}
{{Infobox User/adventure|lba1=false}}
{{Infobox User/adventure|lba1=not}}
{{Infobox User/adventure|lba1=maybe}}
{{Infobox User/adventure|lba1=0}}
{{Infobox User/adventure|lba1=zero}}
{{Infobox User/adventure|lba1=null}}
{{Infobox User/adventure|lba1=n}}
{{Infobox User/adventure|lba1=whatever}}
{{Infobox User/adventure|lba1=yes}}
{{Infobox User/adventure|lba1=YES}}

FunFrock's Reign ^{[list all]}

The only ways to express a negative value is by leaving out the parameter, leaving it empty or specifying "no" (case insensitive), so these all have the same result:

{{Infobox User/adventure|lba1=yes}}
{{Infobox User/adventure|lba1=yes|lba2=}}
{{Infobox User/adventure|lba1=yes|lba2=no}}
{{Infobox User/adventure|lba1=yes|lba2=NO}}

FunFrock's Reign ^{[list all]}

When the in-game content of Little Big Adventure 3 is publicized, it may be specified as the adventure as well:

{{Infobox User/adventure|lba3=yes}}

Stellar Entity Genesis ^{[list all]}

You may leave the "adventure" undefined (which would raise the Users with unknown adventure xp maintenance task) by not specifying any positive value for any of the options, so these all have the same result:

{{Infobox User/adventure}}
{{Infobox User/adventure|lba1=no}}
{{Infobox User/adventure|lba1=|lba2=|lba3=}}

unknown ^{[list all]}

Eventhough technically allowed, if you're not experienced in any of the adventures, you shouldn't be editing the Twinsuniverse (yet).

The nocat parameter may be used to suppress automatic categorization like this (any value will do):

{{Infobox User/adventure|lba1=yes|nocat=true}}

This would render the same result as the first example above, but would not automatically categorize under Category:LBA1 characters. This feature works both on valid values and the maintenance task mentioned above.