Template:Infobox skill/Sandbox
Skill images to use in infoboxes: Category:GUI Icon Images
Parameters
Basic Parameters
| Parameter | Function | Auto-categorizes? |
|---|---|---|
| name | ||
| image | ||
| image_alt1 | ||
| image_alt2 | ||
| size | ||
| caption | ||
| caption_alt1 | ||
| caption_alt2 |
Skill Parameters
| Parameter | Function | Auto-categorizes? |
|---|---|---|
| group | Y | |
| max_level | ||
| exp_level | ||
| sp_level | ||
| req_lvl_1 | ||
| req_lvl_2 | ||
| req_lvl_3 | ||
| req_lvl_4 | ||
| req_lvl_5 | ||
| effects | ||
| effectschance |
Perk Parameters
| Parameter | Function | Auto-categorizes? |
|---|---|---|
| perk | Boolean (y/n) | Y |
| required_player_level | Minimum player level required to obtain perk (gating) | |
| required_skill_name | Name of skill required to obtain perk (gating) | |
| required_skill_level | Level of required_skill_name required to obtain perk (gating)
|
Additional notes from progress.xml:
REQUIREMENTS:
Only use requirements on perks. Player, Crafting, and Action skills do not properly support requirements at this time. Requirements allow the gating of perks so that the benefits can be stretched out over the course of the game. Instead of having to make two perks with different requirements, this allows us to simply have perks with multiple tiers gated by player level or the level of some other skill or perk.
There can be any number of requirements, even for the same skill_level. The parameter "skill_level" is required on all requirement entries. "required_skill_level" must exist if "required_skill_name" exists. If "required_skill_name" exists, it will ignore "required_player_level" so never use both in one <requirement> node.
The above documentation is transcluded from Template:Infobox skill/Sandbox/doc. (edit | history)