User:BELATHUS/Sandbox

BELATHUS/Sandbox Mnemonic [{{{mnemonic}}}] Base Duration {{{base_dur}}} Added Duration {{{add_dur}}} Span {{{span}}} Type {{{type}}}

Offensive is FF9	Defensive is CF9	Utility is 9CF	Attack is F99
Offensive is FFFFF8	Defensive is FCFFF8	Utility is F8FCFF	Attack is FFF8F8

Duration

The duration fields are easily replaced. If the variable (((duration}}} is defined, it automatically replaces the shown duration fields. This is to ensure backwards compatibility with the old spell template. Additionally, if the variable {{{custdur}}} is defined, it also replaces the shown fields and allows one to use the custom duration templates from the spellbox series of templates. These are Template:Spellbox instant, Template:Spellbox block, and Template:Spellbox duration, although the Spellbox duration template would be exactly similar to the default.

Types

The template changes drastically based on what type is chosen for the template. The preview, to the right, is what the template will look like with no type defined. Undefined, the template will be gray. However, the colors and parameters change when defined, and the type line will vanish so long as it meets one of four types: Attack, Defensive, Offensive, and Utility. It is case sensitive. Any unwanted line can be removed by defining the associated parameter as "None". This is case sensitive.

Attack

This type changes the template to have a pale red background in addition to adding lines for Subtype, Damage Type, Critical Type, State(s) Inflicted, and Duration. The Damage Type and Critical Type lines will show if the parameter {{{dtype}}} is defined. The State(s) Inflicted and Duration lines will show if the parameter {{{status}}} is defined.

Defensive

This type changes the template to have a pale green background in addition to adding lines for Subtype, Defensive Strength, Target Defense, Enhancement, and Availability.

• Subtypes for defensive spells would define which sort of defensive capabilities the spell offers, such as increases to DS, TD, and skills.
• Defensive Strength should be listed as the type of DS it provides, such as melee or bolt.
• Target Defense should be labelled by the type of TD it provides, like DS. Options are: Spiritual, Elemental, Mental, and Generic (or All).
• Enhancement would be used for spells such as Mass Blur which increase defensive capabilities by granting phantom ranks in the skill, Dodge; though, some spells increase ranks in Stalking and Hiding in addition to increasing defensive capabilities; such would go here.
• Availability defines who the spell can be cast on, such as self-cast, group (like Mass Blur), and all (such as Elemental Defense I).

Offensive

This type changes the template to have a light yellow background in addition to adding lines for Subtype, Enhancement type, and Availability or Requirements.

• Subtype defines what sort of enhancement that this spell provides. Generally, weapon enhancements, attack strength enhancements, or more.
• Enhancement type is split into two categories, defined by which variable is used -- {{{weapon}}} or {{{enhancement}}}.
  • {{{weapon}}} - defines the template as a weapon enhancement, and this field is used to define what sort of enhancement the spell provides to the weapon. There are currently three weapon enhancement spells, Holy Blade, Minor Elemental Edging, and Elemental Blade. Holy Blade grants a weapon the Blessed status, and thus would be simply labeled, "Bless". Minor Elemental Edging and Elemental Blade both grant enchantment bonuses (labeled, "Enchantment"), though, Elemental Blade also adds flares (and thus would be labeled "Enchantment, Flares"). Using this variable replaces Availability with Requirements.
  • {{{enhancement}}} - defines the template as a general enhancement spell. This would be used where the spell provides an enhancement to an offensive skill, such as Patron's Blessing, which increases ranks in the skill, Combat Maneuvers. Also, if the spell provides an increase to Attack Strength, it would be listed here.
• Availability is similar to the use with defensive spells as above, although, if this spell is labeled as a weapon enhancement by using the {{{weapon}}} variable, this line is replaced by the Requirements line.
• Requirements is used with weapon enhancements, and this line defines the requirements that are placed on the weapon to cast this spell. For example, to cast Holy Blade on a weapon, it cannot have flares or weighting. Additionally, to cast Minor Elemental Edging or Elemental Blade on a weapon, it cannot be magical in any way whatsoever. This includes weighting and flares.

Utility

This type changes the template to have a light blue background in addition to adding lines for Subtype, Skill Enhancement, Components, and Availability.

• Subtype is often defined as either being Combat, Enhancement, or None, although other subtypes may be defined.
• Skill Enhancement is used to list whatever skills might be enhanced by this spell. Increases to skills that are not directly offensive or defensive in nature, such as Stalking and Hiding, Skinning, and Foraging, will be listed as utility. If the spell does not enhance a skill, enter "None".
• Components lists the various components the spell may require. Listing the components as "None" will remove this line.
• Availability is used for enhancement utility spells, such as Sneaking or Whispering Willow. It is defined much like the Availability line in defensive spells.

Navigation

The parameter {{{navigation}}} allows the use of any of the navigational templates available from the Spellbox series of templates. All of the navigational templates are listed below.

• Template:Minor spiritual navigation
• Template:Major spiritual navigation
• Template:Cleric base navigation
• Template:Minor elemental navigation
• Template:Major elemental navigation
• Template:Ranger base navigation
• Template:Sorcerer base navigation
• Template:Wizard base navigation
• Template:Bard base navigation
• Template:Empath base navigation - Will be available soon.
• Template:Paladin base navigation

Notes

This template makes extensive use of the ParserFunctions extension. Many of these functions are severely nested and nested again and I admit the coding was rather confusing. I expect there to be bugs due to my inexperience with ParserFunctions and the complex structure of the template.

Nearly everything here is subject to change.