Template:Icon damage-type multi

From War Commander Wiki
Jump to navigation Jump to search


Useful for showing many damage-type icons.

Template parameters[Edit template data]

This template prefers inline formatting of parameters.

ParameterDescriptionTypeStatus
1st type1

can be none, sustain, area, burst, fire, plasma or energy

Default
none
Example
sustain
Auto value
sustain
Stringoptional
2nd type2

sustain, area, burst, fire, plasma or energy

Default
area
Example
area
Auto value
area
Stringoptional
3rd type3

sustain, area, burst, fire, plasma or energy

Default
burst
Example
burst
Auto value
burst
Stringoptional
4th type4

sustain, area, burst, fire, plasma or energy

Default
fire
Example
fire
Auto value
fire
Stringoptional
5th type5

sustain, area, burst, fire, plasma or energy

Default
plasma
Example
plasma
Auto value
plasma
Stringoptional
6th type6

sustain, area, burst, fire, plasma or energy

Default
energy
Example
energy
Auto value
energy
Stringoptional

Example 1

{{Icon damage-type multi|plasma}}

Plasma - More damage over longer distances.


Example 2

{{Icon damage-type multi|sustain|burst}}

Sustain - Fast rate of fire, but low damage per projectile.    Burst - Slow rate of fire, but high damage per projectile.


Example 3

{{Icon damage-type multi|burst|sustain|area|energy|fire|plasma}}

Burst - Slow rate of fire, but high damage per projectile.    Sustain - Fast rate of fire, but low damage per projectile.    Area - Big area of effect.    Energy - ...    Fire - More effective against certain enemy types.    Plasma - More damage over longer distances.



Best Practice

To edit or experience with the templates, use the following sandbox and testcase pages:

Steps:

  1. The /sandbox may not have the latest version of the template code in it, so before you make a change, you need to synchronize it with the main template. Copy the entire contents of the main template to the /sandbox subpage, and save the page. Your edit summary should be something like "synchronize with the main template", or simply "sync".
  2. Have fun editing the sandbox. When you have some code you want to test, save the page.
  3. If you have added any new features or changed any parameters, you should add new test cases to the /testcases subpage so that they can be tested. Also, bear in mind that the existing test cases may not be complete. It's okay to rewrite the test cases if they aren't useful for what you're trying to achieve, but also consider editors who may use the test cases after you.
  4. Purge the /testcases page to update the results.
  5. Verify that the test case results are correct. If everything looks good, copy the code from the sandbox to the main template.